Pirate Party Belgium - User contributions [en]

Form:Meeting event

2024-09-16T16:46:48Z

HgO: replace obsolete extension regexfun with regexfunction

<includeonly>{{{info|page name={{#rreplace:{{#if:<MeetingSidebar[workgroup]>|<MeetingSidebar[workgroup]>|<MeetingSidebar[topics]>}}|/^[^,]+/}}{{#if:<MeetingSidebar[workgroup]><MeetingSidebar[topics]>|/}}Meeting/{{#time:d m Y|<MeetingSidebar[date]>}} }}}

<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>

{{#switch: {{int:language-code}}
| fr = {{{for template|MeetingSidebar|label=Réunion}}}
| nl = {{{for template|MeetingSidebar|label=Samenkomst}}}
| {{{for template|MeetingSidebar|label=Meeting}}}
}}

{{int:event-form-meeting-description}}

{| style="text-align: left; width:100%;"
{| style="text-align: left; width:100%;"
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-title}}:
| colspan="5" | {{{field|meetingname|size=50|input type=text with autocomplete|property=Has title|mandatory}}}
|-
! style="vertical-align: middle;"| {{int:sidebar-workgroup}}:
| {{{field|workgroup|size=50|input type=text with autocomplete|list|property=Organized by}}}
! style="vertical-align: middle;"| {{int:sidebar-topics}}:
| colspan="3" | {{{field|topics|size=50|input type=text with autocomplete|list|property=In topic}}}
|-
! style="vertical-align: middle;" | {{int:sidebar-date}}:
| {{{field|date|input type=datepicker|property=Has date|mandatory}}}
! style="vertical-align: middle;" | {{int:sidebar-time}}:
| {{{field|time|size=10|input type=text with autocomplete|property=Has time}}}
! style="vertical-align: middle;" | {{int:sidebar-end-time}}:
| {{{field|endtime|size=10|input type=text with autocomplete|property=Has time}}}
|-
! style="height: 1em;" colspan="6" |
|-
! style="vertical-align: middle;" | {{int:sidebar-venue}}:
| colspan="5" | {{{field|venue|size=30|input type=text with autocomplete|property=In venue}}}
|-
! style="vertical-align: middle;" | {{int:sidebar-address}}:
| colspan="5" | {{{field|address|size=50|input type=text with autocomplete|property=Has address}}}
|-
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-postal-code}}:
| {{{field|postalcode|size=10|input type=text with autocomplete|property=In postal code}}}
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-city}}:
| colspan="3" | {{{field|city|size=30|input type=text with autocomplete|property=In city}}}
|-
! style="height: 1em;" colspan=6 |
|-
! style="vertical-align: middle;" | {{int:sidebar-link}}:
| colspan="5" | {{{field|linkvenue|size=50|input type=text with autocomplete|property=Has link venue}}}
|-
! style="vertical-align: middle;"| {{int:sidebar-attendees}}:
| colspan="5" | {{{field|attendees|size=100|input type=text with autocomplete|list|property=Has attendee}}}
|-
! style="vertical-align: middle;"| {{int:sidebar-absentees}}:
| colspan="5" | {{{field|absentees|size=100|input type=text with autocomplete|list|property=Has absentee}}}
|-
! style"height: 1em;" colspan=6 |
|-
! style="vertical-align: middle;" | Image:
| colspan="5" | {{{field|image|size=100|uploadable|input type=text with autocomplete|values from namespace=File}}}
|}
{{{end template}}}

{{#switch: {{int:language-code}}
| fr = {{{standard input|free text|editor|rows=20|preload=Template:EmptyMeeting/fr}}}
| nl = {{{standard input|free text|editor|rows=20|preload=Template:EmptyMeeting/nl}}}
| {{{standard input|free text|editor|rows=20|preload=Template:EmptyMeeting/en}}}
}}

{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|cancel}}}</includeonly><noinclude>{{int:event-form-meeting}}.</noinclude>

Form:External event

2024-09-16T16:46:27Z

HgO: replace obsolete extension regexfun with regexfunction

<includeonly>{{{info|page name={{#rreplace:{{#if:<ExternalEventSidebar[workgroup]>|<ExternalEventSidebar[workgroup]>|<ExternalEventSidebar[topics]>}}|/^[^,]+/}}{{#if:<ExternalEventSidebar[workgroup]><ExternalEventSidebar[topics]>|/}}Event/{{#time:d m Y|<ExternalEventSidebar[date]>}}/<unique number;start=1> }}}

<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>

{{#switch: {{int:language-code}}
| fr = {{{for template|ExternalEventSidebar|label=Évènement}}}
| nl = {{{for template|ExternalEventSidebar|label=Evenement}}}
| {{{for template|ExternalEventSidebar|label=Event}}}
}}

{{int:event-form-external-description}}

{| style="text-align: left; width:100%;"
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-title}}:
| colspan="5" | {{{field|title|size=50|input type=text with autocomplete|property=Has title|mandatory}}}
|-
! style="vertical-align: middle;"| {{int:sidebar-workgroup}}:
| {{{field|workgroup|size=50|list|input type=text with autocomplete|property=Organized by}}}
! style="vertical-align: middle;"| {{int:sidebar-topics}}:
| colspan="3" | {{{field|topics|size=50|list|input type=text with autocomplete|property=In topic}}}
|-
! style="vertical-align: middle;" | {{int:sidebar-date}}:
| {{{field|date|input type=datepicker|list|property=Has date|mandatory}}}
! style="vertical-align: middle;" | {{int:sidebar-time}}:
| {{{field|time|size=10|input type=text with autocomplete|property=Has time}}}
! style="vertical-align: middle;" | {{int:sidebar-end-time}}:
| {{{field|endtime|size=10|input type=text with autocomplete|property=Has time}}}
|-
! style="vertical-align: middle;" | {{int:sidebar-price}}:
| colspan="5" | {{{field|price|size=10|input type=text with autocomplete|property=Has price|default={{int:sidebar-price-free}} }}}
|-
! style="height: 1em;" colspan="6" |
|-
! style="vertical-align: middle;" | {{int:sidebar-venue}}:
| {{{field|venue|size=30|input type=text with autocomplete|property=In venue}}}
! style="vertical-align: middle;" | {{int:sidebar-link}}:
| colspan="3" | {{{field|linkvenue|size=50|input type=text with autocomplete|property=Has link venue}}}
|-
! style="vertical-align: middle;" | {{int:sidebar-address}}:
| colspan="5" | {{{field|address|size=50|input type=text with autocomplete|property=Has address}}}
|-
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-postal-code}}:
| {{{field|postalcode|size=10|input type=text with autocomplete|property=In postal code}}}
! style="width: 100px; vertical-align: middle;" | {{int:sidebar-city}}:
| colspan="3" | {{{field|city|size=30|input type=text with autocomplete|property=In city}}}
|-
! style="height: 1em;" colspan="6" |
|-
! style="vertical-align: middle;" | {{int:sidebar-url}}:
| colspan="5" | {{{field|url|size=50|input type=text}}}
|-
! style"height: 1em;" colspan=6 |
|-
! style="vertical-align: middle;" | Image:
| colspan="5" | {{{field|image|size=100|uploadable|input type=text with autocomplete|values from namespace=File}}}
|}
{{{end template}}}

{{#switch: {{int:language-code}}
| fr = {{{standard input|free text|editor|rows=20|preload=Template:EmptyExternalEvent/fr}}}
| nl = {{{standard input|free text|editor|rows=20|preload=Template:EmptyExternalEvent/nl}}}
| {{{standard input|free text|editor|rows=20|preload=Template:EmptyExternalEvent/en}}}
}}

{{{standard input|summary}}}

{{{standard input|minor edit}}} {{{standard input|watch}}}

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|cancel}}}</includeonly><noinclude>{{int:event-form-external}}.</noinclude>

Template:TimeRegex

2024-09-16T16:44:58Z

HgO: replace obsolete extension regexfun with regexfunction

<includeonly>{{#rreplace:
{{#rreplace:
{{{1}}}
| /[hu]/i
| :
}}
| /:\s*$/
| :00
}}</includeonly>

Topic:Ychoy0uudb0h7iv8

2024-09-16T16:37:00Z

HgO (talk | contribs) commented on "Test" (Test pour la version 1.39)

Topic:Ychoy0uudb0h7iv8

2024-09-16T15:03:06Z

HgO (talk | contribs) commented on "Test" (Test réussi)

Topic:Ychoy0uudb0h7iv8

2024-09-16T15:02:26Z

HgO (talk | contribs) commented on "Test" (Test de la mise à jour)

ITSquad

2021-09-28T15:30:48Z

HgO: /* Expenses */ add mumble server

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 54,75€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|<s>depiratenpartij.be</s>
|
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|<s>diepiratenpartei.be</s>
|
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 431,64€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since March 2020
|3,01€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] (with 125Go volume) since October 2019
|11,98€
|Monthly
|-
|[https://talk.pirateparty.be/ Mumble server] since March 2020
|3,01€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
|[https://status.pirateparty.be/ Monitoring server] since January 2020
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,93€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 606,39€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2021-09-28T15:14:55Z

HgO: /* Expenses */ add mastodon volumes and monitoring vm

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 54,75€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|<s>depiratenpartij.be</s>
|
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|<s>diepiratenpartei.be</s>
|
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 406.56€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since March 2020
|3,01€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|6,9€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
|[https://status.pirateparty.be/ Monitoring server] since January 2020
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
| Volume for Mastodon database (25Go) since September 2021
| 1,21€
| Monthly
|-
| Volume for Mastodon media (100Go) since July 2021
| 4,84€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 581,31€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad/Mastodon/Maintenance

2021-01-09T12:38:25Z

HgO: add pgbackrest and borg, remove autofs, and add new steps to upgrade Mastodon

This page aims to describe procedures to maintain the [[ITSquad/Mastodon|Pirate Party's Mastodon]] instance.

== Storage Box ==

Due to the size of the media, we decided to store them on a storage box provided by Hetzner. This can also be used for storing our backups.

This storage box is mounted with sshfs.

First, we need to create a ssh key pair for the root user and install it on the storage box. In the ITSquad, we decided to create a sub-account of the storage-box per server, so we can safely overwrite the storage box's authorized_keys file:
ssh-keygen -t ed25519 -f /root/.ssh/storage-box
scp -P 23 .ssh/storage-box.pub <user>@<storage box server>:/home/.ssh/authorized_keys

Then, we create the directory that will be used as the storage box's mountpoint:
mkdir /mnt/mastodon

We add the following line in /etc/fstab to mount the storage box volume:
# <file system> <mount point> <type> <options> <dump> <pass>
<storage box>:/home/media /mnt/mastodon fuse.sshfs delay_connect,_netdev,user,idmap=user,transform_symlinks,allow_other,default_permissions,reconnect,uid=mastodon,gid=mastodon 0 0
We give the ownership of this volume to the mastodon user in order to avoid HTTP error 500 on file uploads.<ref>Source: https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Docker-Guide.md#using-a-prebuilt-image</ref>.

We configure the SSH client config at /root/.ssh/config to define which port, user and private key to use to connect to the storage box:
Host <storage box>
User <user>
Port 23
IdentityFile /root/.ssh/storage-box
PreferredAuthentications publickey,password

We mount the storage box volume:
mount /mnt/mastodon

Finally, we create a link on the mastodon directory:
ln -s /mnt/mastodon/media /path/to/mastodon/public/system

And we restart the Mastodon instance \o/

'''Note:''' We first tried to use autofs to mount the storage box, but this was resulting in socket errors because the docker container didn't get the information that the volume had been disconnected and mounted again.

== How to upgrade? ==

A script called '''upgrade.sh''' located in /home/mastodon will reproduce the steps below. Note: this script stops at step 12 and does not go further.

Before running this script or the following commands, please check [https://github.com/tootsuite/mastodon/releases the instruction for the current release]. Sometimes, aditionnal actions are needed (other than migrate database and compile assets)

# git fetch -t # update the git branch, including new tags
# git stash # prevent changes made to the files to be overwritten (mainly, the docker-compose.yml file)
# git pull
# git stash pop # restore your changes
# docker-compose build # build the image
# docker-compose exec -u postgres pgbackrest --retention-diff 3 --stanza main --type incr backup # backup the database (see [[#WAL_archiving with_pgBackRest]])
# tail ../your_dump_file.sql # check if the backup worked, with your_dump_file.sql being the dumpfile you have created in the previous step.
# docker-compose run --rm -e SKIP_POST_DEPLOYMENT_MIGRATIONS=true web rails db:migrate # upgrade the database (pre-install)
# docker-compose down # shut down the containers.
# docker-compose run --rm web bin/tootctl cache clear # clear the cache
# docker-compose run --rm web rails db:migrate # upgrade the database
# docker-compose up -d # start the mastodon instance (create new volumes)
# docker-compose logs -ft web # (optional) if you want to monitor the progress. Once this is done you ctrl+c
# docker system prune -a # remove all unused volumes, old images, etc.

=== What to do when something went wrong? ===

Don't panic.

If you made a dump of the database before upgrading, you can restore the database as follows:

# docker-compose stop
# docker-compose start db
# docker-compose exec db dropdb postgres -U postgres # remove the db !!!!!!!
# docker-compose exec db createdb postgres -U postgres # create a fresh and new db
# cat ../your_dump_file.sql | docker exec -i mastodon_db_1 psql -U postgres # restore the database, with "your_dump_file" being a database backup
# docker-compose down
# docker-compose up -d

If you are using pgBackRest, you can follow these steps: https://pgbackrest.org/user-guide.html#quickstart/perform-restore

As the tool is inside a docker container, you can enter the container like this:

docker-compose run --rm -u postgres db bash

Then, you can execute the commands from there.

== What to backup? ==

Backups of the database are not enough. We need to backup medias, user feeds, etc.

According to the official Mastodon documentation,<ref>https://docs.joinmastodon.org/administration/migrating/</ref> we need to take special cares of the following files and directories:
* The ''public/system'' directory, which contains user-uploaded images and videos
* The ''.env.production'' and ''docker-compose.yml'' files, which contain server config and secrets
* The Postgres database, using pg_dump (see below)
* The ''/etc'' directory, which contains the system's configuration files

Moreover, the backups must be encrypted on the storage server.

== How to backup? ==

'''Currently''': Every night, an encrypted backup of the database is made on the server and is stored on at least two other locations. The backups are incremental every day, differential every Sunday, and we perform a full backup every month. Backups for configuration files are created every night. These backups are incremental and are stored for 6 months and are stored on at least two different locations. Finally, backups and media are stored on a storage box provided by Hetzner. A snapshot of this storage box is scheduled every night.

=== Database ===

For an instant backup, we can just dump the database as follows:
docker-compose exec -u postgres db pg_dump -Fc postgres > /home/mastodon/backup/db/dump_$(date +%d-%m-%Y"_"%H_%M_%S).sql

In short, the option ''-Fc'' enables data compression. Postgres ensures data consistency during the backup<ref>https://www.postgresql.org/docs/current/app-pgdump.html</ref>, which means that we don't have to stop Mastodon while dumping the database ;)

==== WAL archiving with pgBackRest ====

However, over a long time period, we usually wants incremental backups to avoid duplicating the whole database each day. Fortunately, Postgres provides all the tools we need to set up incremental backups.<ref>https://www.opsdash.com/blog/postgresql-backup-restore.html</ref>

First, we have to enable WAL (Write Ahead Log) archiving.<ref>https://www.opsdash.com/blog/postgresql-wal-archiving-backup.html</ref>. We just modify the Postgres config, which is located in /path/to/mastodon/postgres/postgressql.conf:
# The WAL level must be archive or higher.
wal_level = replica

# This is a soft upper limit on the total size of WAL files.
max_wal_size = 1GB

# The archive_mode must be set to on for archiving to happen.
archive_mode = on

# This is the command to invoke for each WAL file to be archived.
archive_command = '/usr/local/bin/pgbackrest --log-level-console=info --stanza=main archive-push %p'

# Max number of processes to generate the WAL files
max_wal_senders=3

This configuration tells PostgreSQL to archive transaction by executing the command:
/usr/local/bin/pgbackrest --log-level-console=info --stanza=main archive-push %p
Note that this command must be executable by the postgres user. If the script fails, PostgreSQL will try to execute it again and again. Please check the Postgres logs to be sure that everything is fine.

Then, we must install pgBackRest<ref>https://pgbackrest.org/user-guide.html</ref>, which is the tool that will backup the WAL files. Although the user guide of pgBackRest is dense, it is quite straightforward, so we recommend you to read it.

Since we are using docker, we had to create a custom docker image that includes pgBackRest. We created the following Dockerfile in /home/mastodon/pgbackrest/Dockerfile:
FROM postgres:12-alpine

ARG PGBACKREST_VERSION="2.31"
ARG PGBACKREST_SHA256SUM="7157ec4ad2428379243c30acf2b15c2e9339beeec14697714f8eac2ce4c19896"
RUN apk add --virtual build-dependencies \
build-base gcc make wget postgresql-dev openssl-dev libxml2-dev pkgconfig lz4-dev bzip2-dev \
&& apk add lz4-libs coreutils libbz2 \
&& pgbackrest_archive="pgbackrest-${PGBACKREST_VERSION}.tar.gz" \
&& pgbackrest_dir="/opt/pgbackrest-release-${PGBACKREST_VERSION}" \
&& wget -O $pgbackrest_archive -q https://github.com/pgbackrest/pgbackrest/archive/release/${PGBACKREST_VERSION}.tar.gz \
&& echo "${PGBACKREST_SHA256SUM} $pgbackrest_archive" | sha256sum -c - \
&& tar zxf $pgbackrest_archive -C /opt \
&& cd $pgbackrest_dir/src \
&& ./configure \
&& make \
&& make install \
&& ln -s /usr/local/bin/pgbackrest /usr/bin/pgbackrest \
&& apk del build-dependencies \
&& cd / \
&& rm -rf $pgbackrest_archive $pgbackrest_dir

COPY --chown=postgres:postgres pgbackrest.sh /opt/
RUN chmod 744 /opt/pgbackrest.sh

COPY --chown=postgres:postgres pgbackrest.conf /etc/
RUN chmod 640 /etc/pgbackrest.conf

CMD ["postgres", \
"-c", "archive_command=/usr/local/bin/pgbackrest --log-level-console=info --stanza=main archive-push %p", \
"-c", "archive_mode=on", \
"-c", "wal_level=replica", \
"-c", "max_wal_senders=3"]

Because pgbackrest wasn't packaged for alpine images, we had to build it from sources.

We also create the pgBackRest config file in /home/mastodon/pgbackrest/pgbackrest.conf:

[global]
log-level-file=off
log-level-console=info

repo1-path=/mnt/pgbackrest
repo1-retention-full=2
repo1-retention-diff=2
repo1-cipher-pass=<pgbackrest password>
repo1-cipher-type=aes-256-cbc

[main]
pg1-path=/var/lib/postgresql/data

Don't forget to generate your pgbackrest password.

Finally, change the /path/to/mastodon/docker-compose.yml file to build and use this custom postgres docker image:
db:
...
build: /home/mastodon/pgbackrest
image: pgbackrest:12
...
volumes:
...
- /mnt/pgbackrest:/mnt/pgbackrest
...

Here, we can see that we are mounting a volume that will contain the backup. We use the same method as the one for storing the media (see [[#Storage_Box]]), and we gave the ownership to the postgres user, i.e. the uid 70 as this user only exists inside the postgres docker container.

'''Note:''' We upgraded the PostgreSQL database from 9.6 to 12, so adapt this configuration according to your needs.

Finally, build the docker image and recreate the database container:

docker-compose build db
docker-compose down
docker-compose up -d

=== Medias ===

It can be interesting to execute the following command before making a backup of the medias:
docker-compose run --rm web bin/tootctl media remove --days=14
This will remove local cache of media older than NUM_DAYS (=7 by default, but here we set it at 14 days). Note that this command is daily executed on our instance.

'''Important note''': Due to the size of the media, we decided to store them on a storage box (500Go) provided by Hetzner. Every night, a snapshot of this storage box is scheduled, and we keep 4 snapshots.

=== Configuration files ===

We are backuping the config files with Borg<ref>https://simonlefort.be/informatique:borg</ref> and borgmatic<ref>https://simonlefort.be/informatique:borgmatic</ref>.

We created a storage box mountpoint at /mnt/backup (see [[#Storage_Box]]) and we gave ownership to the root user and the backup-sync group

First, we initialize the Borg repository:
borg init -e keyfile --umask 0027 /mnt/backup/borg

This will prompt for a passphrase. You'll have to backup the keyfile as it is needed to decrypt the borg repository, and it is stored on the server, under /root/.config/borg/keys

The umask option is there to allow read-write permission to the owner, allow read-only permission to the group, and remove all permissions for other users. See also the [https://en.wikipedia.org/wiki/Umask Wikipedia about umask].

Then, we create the borgmatic config file at /etc/borgmatic/config.yaml:
location:
exclude_patterns:
- /path/to/elasticsearch
- /path/to/redis
repositories:
- <storage box>:/home/backup/borg
source_directories:
- /path/to/mastodon
- /etc
retention:
keep_daily: 7
keep_hourly: 24
keep_monthly: 6
keep_weekly: 4
storage:
compression: zlib,7
encryption_passphrase: <borg passphrase>
umask: '0027'

We can now trigger a backup with this command:
borgmatic --create --prune

We can also check the consistency of the backup with:
borgmatic --check

'''Important note''': These two commands are executed every night, and backups are stored on at least two locations.

== References ==

<references/>

ITSquad

2021-01-08T22:06:15Z

HgO: /* Expenses */ adapt the yearly total

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 54,75€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|<s>depiratenpartij.be</s>
|
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|<s>diepiratenpartei.be</s>
|
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 297,84€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since March 2020
|3,01€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|6,9€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 472,59€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2021-01-03T19:34:20Z

HgO: update wordpress pricing

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 297,84€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since March 2020
|3,01€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|6,9€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 494,49€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2021-01-03T19:29:48Z

HgO: reduce size of Mastodon volume after database migration

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 351,25€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since December 2016
|8,35€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|6,9€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 547,9€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2020-12-27T17:52:03Z

HgO: /* Ansible */

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 354,13€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since December 2016
|8,35€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|7,14€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 550,78€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our servers in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2020-12-27T17:51:54Z

HgO: /* Administration Docs */ ansible

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 354,13€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since December 2016
|8,35€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|7,14€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 550,78€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Ansible ===

To manage our server in an automated way: https://dev.parley.be/PPBe/ansible-infra

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad/Mumble

2020-12-27T17:49:24Z

HgO: ansible role

{{ProjectSidebar
| title = Mumble
| start = 2020/03/22
| status = doing
| workgroup = ITSquad
| contact = it [at] pirateparty (point) be
}}

== Description ==

Mumble is a server for holding audio conferences.

Since March 2020, the PPBe is hosting a Mumble server together with a web client on https://talk.parley.be or https://mumble.parley.be

It is also possible to connect through [https://www.mumble.com/mumble-download.php another Mumble client] either at <code>mumble.parley.be</code> or <code>talk.parley.be</code> with port <code>64738</code>.

To connect you can give the username you wish. No password is needed, although we could decide to setup a password if we see that there are too much spam.

== Install ==

'''Note:''' We are setting two domain names. However, you can as well use a single domain name for both applications, or a domain name for the web client and another for the Mumble server. Indeed, the Mumble server listens on port 64738, while the client listens on ports 80 and 443, so they won't conflict ;) Just reuse the same certificate for both applications and you should be fine.

Since December 2020, we are using our Ansible role to install both the web client and the Mumble server: https://github.com/L-P/ansible-role-murmur Therefore, the below install procedure won't be updated anymore.

You can see how we configured our instance here: https://dev.parley.be/PPBe/ansible-infra

=== Server ===

'''Note''' This install procedure is for the umurmur server, which is a lightweight Mumble server. However, we switched to the official murmur server, as the latest umurmur release is becoming old and outdated.

Install dependencies:

apt install git build-essential cmake libconfig-dev libprotobuf-c-dev libmbedtls-dev ssl-cert

Create the directory for the server sources:

mkdir /opt/umurmur
cd /opt/umurmur

Clone the umurmur git repository:

git clone https://github.com/umurmur/umurmur.git .

Checkout to the latest version (see the [https://github.com/umurmur/umurmur/releases releases list]):

git checkout 0.2.17

Create the build directory:

mkdir ./build
cd ./build

Build the sources:

cmake .. -DSSL=mbedtls
make

Install the umurmur binary on the system:

make install

You can now edit the configuration file at <code>/usr/local/etc/umurmur.conf</code>. Check the doc for an example. We will define the certificates later on. You can setup a password if you wish.

Generate a random password for the admin:

pwgen -s 42 1

And copy/paste this password to the umurmur config file.

Create the systemd service unit (just copy/paste this block):

<nowiki>
cat > /etc/systemd/system/umurmur.service << EOF
[Unit]
Description=Minimalistic Mumble server
After=network.target

[Service]
Type=simple
User=nobody
Group=ssl-cert
Restart=on-failure
RestartSec=3
PIDFile=/run/umurmurd.pid
ExecStartPre=/usr/local/bin/umurmurd -t -c /usr/local/etc/umurmur.conf
ExecStart=/usr/local/bin/umurmurd -d -r -c /usr/local/etc/umurmur.conf
ExecReload=/bin/kill -HUP $MAINPID
PrivateDevices=yes
PrivateTmp=yes
ProtectSystem=strict
ReadWriteDirectories=/usr/local/etc/
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
LockPersonality=yes
NoNewPrivileges=yes
LimitRTPRIO=1

[Install]
WantedBy=multi-user.target
EOF</nowiki>

Reload the systemd service unit config:

systemctl daemon-reload

=== Web client ===

Install nodejs repository (LTS is v0.12.x):

curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -

Install nodejs and websockify:

apt install nodejs websockify

Create the directory for mumble-web:

mkdir /var/www/mumble-web
cd /var/www/mumble-web

Clone the mumble-web git repository:

git clone https://github.com/Johni0702/mumble-web.git .

Build the sources:

npm install
npm audit fix

Build the assets and config:

npm run build

Edit the configuration file at <code>./dist/config.local.js</code>. Add the following options in the config file:

<nowiki>
// Which fields to show on the Connect to Server dialog
config.connectDialog.address = false
config.connectDialog.port = false
config.connectDialog.token = false
config.connectDialog.password = false

// Default values for user settings
config.settings.pttKey = 'shift'

// Default values (can be changed by passing a query parameter of the same name)
config.defaults.address = 'talk.parley.be/mumble'</nowiki>

This will tell the client to only ask for an username. If you setup a password for the server, you can set it to true.

The config also indicates to which address the client should connect. The <code>/mumble</code> path will be defined later in the Nginx section, but basically we will create a websocket proxy to the mumble server.

Create the systemd service unit (just copy paste this block):

<nowiki>
cat > /etc/systemd/system/mumble-web.service << EOF
[Unit]
Description=Mumble web client using websockets
After=network.target

[Service]
Type=simple
User=nobody
Group=nogroup
Restart=on-failure
RestartSec=3
PIDFile=/run/mumble-web.pid
ExecStart=/usr/bin/websockify --ssl-target 64737 localhost:64738
ExecReload=/bin/kill -HUP $MAINPID
PrivateDevices=yes
PrivateTmp=yes
ProtectSystem=strict
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
LockPersonality=yes
NoNewPrivileges=yes
LimitRTPRIO=1

[Install]
WantedBy=multi-user.target
EOF</nowiki>

Reload the systemd service unit config:

systemctl daemon-reload

=== Nginx ===

Install nginx:

apt install nginx

Create the config for your web client (just copy/paste this block):

<nowiki>
cat > /etc/nginx/sites-available/mumble.conf << EOF
server {
listen 80;
listen [::]:80;
server_name talk.parley.be mumble.parley.be;

# Useful for Let's Encrypt
location /.well-known/acme-challenge/ {
allow all;
}

location / {
return 301 https://$host$request_uri;
}
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;

server_name talk.parley.be;

ssl_certificate /etc/letsencrypt/live/talk.parley.be/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/talk.parley.be/privkey.pem;

include /etc/letsencrypt/options-ssl-nginx.conf;

location / {
root /var/www/mumble-web/dist/;
}

location /mumble {
proxy_pass http://127.0.0.1:64737;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}
}

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
EOF</nowiki>

Install certbot for managing the certificates ([https://certbot.eff.org check on their website] if you need to install the certbot repository):

apt install certbot python-certbot-nginx

Add the following hook in <code>/etc/letsencrypt/cli.ini</code>:

post-hook = chmod 0640 /etc/letsencrypt/archive/*/privkey*.pem && chmod g+rx /etc/letsencrypt/live /etc/letsencrypt/archive && chown -R root:ssl-cert /etc/letsencrypt/live /etc/letsencrypt/archive

This will give the read permissions for the group <code>ssl-certs</code>. It is required for the umurmur server which will be run as member of that group.

Generate two certificates, one for the client and one for the server:

certbot certonly --nginx -d talk.parley.be
certbot certonly --nginx -d mumble.parley.be

Enable the nginx configuration:

ln -s /etc/nginx/sites-available/mumble.conf /etc/nginx/sites-enabled/

Check that everything is fine:

nginx -t

Reload the nginx server:

systemctl reload nginx

Change the certificates for umurmur in the config file <code>/usr/local/etc/umurmur.conf</code>. The paths should be something like:

certificate = "/etc/letsencrypt/live/mumble.parley.be/fullchain.pem";
private_key = "/etc/letsencrypt/live/mumble.parley.be/privkey.pem";

You can finally start the client and server:

systemctl start umurmur
systemctl start mumble-web

Don't forget to open the port <code>64738</code> of your firewall if you want to allow people connecting from the desktop Mumble client!

When everything looks good, enable the services:

systemctl enable umurmur mumble-web

Enjoy!

ITSquad

2020-12-27T16:53:15Z

HgO: /* Expenses */ comma

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 354,13€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since December 2016
|8,35€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|7,14€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 550,78€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

ITSquad

2020-12-27T16:52:33Z

HgO: /* Expenses */ add 5Gb disk space for Mastodon database

{{ProjectSidebar
|title=ITSquad
|status=doing
|topics=Pirate Party
|start=2012/05/20
|contact=it +@+ pirateparty.be, or meet us at our [[Pirate Lab]]
|members=[[User:Tierce|tierce]], [[User:HgO|HgO]], [[User:ZeFredz|Fred]], [[User:Ilja|Ilja]], anyone else?
}}
[[Category:Operational]]
[[Category:Active Projects]]

== Description ==

The ITSquad takes care of the IT-infrastructure of the pirate party. Contact if you want to do an IT-project, need an email address, have requests for a Crew, would like to add a feature to the site, etc.

We can also help with finding, and sometimes providing, tools and services whose values are in line with the values of the Pirateparty. Take a look on our [[ITSquad/Pirates_Selection|Pirates Selection page]] for more information.

== Expenses ==

{| class="wikitable"
!style="text-align:left" |[[ITNow#Networking4all|Networking4All]] (''registrar'')
! style="text-align:left" | 76,65€
! style="text-align:left" | Yearly
|-
|parley.be
|10,95€
|Yearly
|-
|thepirateparty.be
|10,95€
|Yearly
|-
|depiratenpartij.be
|10,95€
|Yearly
|-
|lepartipirate.be
|10,95€
|Yearly
|-
|diepiratenpartei.be
|10,95€
|Yearly
|-
|piratenpartij.be
|10,95€
|Yearly
|-
|pirateparty.be
|10,95€
|Yearly
|-
!style="text-align:left;" colspan="3"| [[ITNow#Infomaniak|Infomaniak]] (''hosting provider'')
|-
|Mailboxes @pirateparty.be and old mailing lists @piratepary.be
|120,00€
|Yearly
|-
!style="text-align:left;" | [[ITNow#Hetzner|Hetzner]] (''hosting provider'')
!style="text-align:left;" | 354,13€
!style="text-align:left;" | Yearly
|-
|[https://wiki.pirateparty.be/ Mediawiki webserver] since October 2019
|3,01€
|Monthly
|-
|[https://pirateparty.be/ Wordpress websites] (en,fr,nl) since December 2016
|8,35€
|Monthly
|-
|[https://mastodon.pirateparty.be/ Mastodon server] since October 2019
|7.14€
|Monthly
|-
|[https://liege.pirateparty.be/ Liège yunohost server] since September 2018
|3,01€
|Monthly
|-
|[https://parley.be/ parley yunohost server] since November 2018
|3,01€
|Monthly
|-
| Storage box (500Go) since September 2019
| 5,88€
| Monthly
|-
!style="text-align:left;"| TOTAL (''if nothing changes'')
! style="text-align:left" | 550,78€
! style="text-align:left" | Yearly
|}

== Ressources ==

* the [[ITNow]] page for some kind of '''inventory''' of our «channels & tools».
* the [[Emails]] page for a '''list of emails''' +@+pirateparty.be.
* the [[ITSquad/piratelab.be|Pirate Labs]] pad to work on '''different LABz''' projects.
* the [https://pad.pirateparty.be/p/pirateparty.be Pirate Party Website] pad for '''comments, remarks, todos...'''
* the [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad Website Squad Loomio Group] about '''website posts and content'''.
* the [[ITSquad/Pirates Selection|Pirates Selection]], a [[ITSquad/Pirates Selection/brainstorming|brainstorming]] about IT tools that could be useful for pirates.
* the [[ITSquad/Hackathon|Hackathon]], to work together on IT stuff during one long day.
* [https://pad.parley.be/p/it-squad Pad] dedicated for the ITSquad

== Administration Docs ==

=== Mastodon ===

To maintain a decentralized and libre social-network

See the [[ITSquad/Mastodon|Mastodon]] page

=== Parley ===

[https://parley.be Parley] is a place where we provide simple services open for everyone. All are free software.

==== Upgrading ====

Upgrading can be done from [https://parley.be/yunohost/admin/ the admin interface] or from the cli over ssh. Before updating applications, make a backup. Backups will be created automatically during upgrade, but if you do them manually, you can check that they haven't failed. When doing risky upgrades, please take a snapshot from the Hetzner admin console. An example of a risky upgrade is for migrations like Debian Stretch to Debian Buster.

==== Landing page ====

The landing page is a simple HTML page with css and javascript (but has graceful degradation for those who want to disable javascript). The files can be found on [https://dev.parley.be/PPBe/parley_landing_page/ our git repo]. Updates should be pushed to there. More information can be found in the README.md

The files for the webapp-application are stored on the Parley server in ''/var/www/my_webapp__2/''. You can find a systemlink to the nginx configuration and to a daily cronjob file. The files of the site themselves are stored in the ''www'' folder. It uses git, so updating is ''cd /var/www/my_webapp__2/www; git pull''.

There is also an sftp connection (but can probably be removed since updating happens using git and the nginx and cronjob files can't be changed through sftp).

You can update the website on the server and then ''git add <changed-files>; git commit; git push'', or you can make the changes to the repo and then wait for the daily job to do it's work.

==== Jirafeau ====

When updating Jirafeau the config file gets overwritten. There's an issue, but it doesn't seem like something that will be fixed soon https://github.com/YunoHost-Apps/jirafeau_ynh/issues/49 . Make sure you test before and after the upgrade if everything is still as it should be.
* Settings are stored in ''/var/www/jirafeau/lib/config.local.php''. The settings from before the upgrade are stored in ''/var/www/jirafeau/lib/var/www/jirafeau/lib/config.original.php''.
* The default time to keep a file is a week, the maximum is a month.
* The max uploadlimit is 2000MB (2GB)
* You can set an admin user. If you're the one who mostly maintains this, you can add yourself. It's the username for the user-interface (at time of writing and afaik, this is only one user max). Another option is to use a shared password and set that instead.

Also note that we've added a file ''/home/yunohost.app/jirafeau-filesystem'' as a filesystem so we can limit the total uploads (to 2.7 GiB). See https://blog.ilja.space/~/MyLearningCurve/limiting-total-size-of-uploads-in-jirafeau

When removing Jirafeau the filesystem should be removed manually, but don't forget to also change ''/etc/fstab'' otherwise the server may not boot anymore! (See the blogpost to know what was done so you can remove safely, best is to make a take a snapshot from the Hetzner admin console beforehand so it can be put back if something fails.)

=== Yunohost ===

We try to promote and use yunohost because it's a good server OS for self hosting. Crews who want to administer their own services can get a ynh server. We can provide the service to set everything up, teach some basics and provide support in case of trouble. An explanation on how and why can be found on [https://blog.ilja.space/~/B/yunohost-for-decentralised-grassroot-movements this blogpost].

==== Setting up an instance ====

If a crewmember is interested in running their server from home, an option is [https://neutrinet.be/nl/brique an internet cube], but typically we'll use a vps. To set up a vps:

* See liege.pirateparty.be for an example
* At least one person of the crew will be admin and contact for us. Make sure we know who that is.
* Log in to Hetzner > cloud > Default > make a new server > install Debian and run the [https://yunohost.org/#/install yunohost installer for Debian]
* Run the post-install and add a subdomain to ynh and set up the DNS records. The easiest is to set A and AAAA records for the crew.pirateparty.be and a CNAME for *.crew.pirateparty.be. Make sure to set up the other DNS records as well (CAA, TXT...)
* Add reverse DNS: Log in to hetzner > cloud > Default > Choose correct server > Networking > Under Primary IPS you can see the reverse DNS. Set it for both ipv4 and ipv6
* Run the diagnostics from the admin interface and set everything up correctly

==== Things to know for the admin(s) ====

* Please keep the server updatet
* If there are problems, contact us via chat or mail. We're here to help, make use of it
* Keep an eye on resources
* There's a good chance that mails will be blacklisted by default by MS and Google. What you can do is "warm up" your domain. Send mails to people who use outlook and gmail accounts and make sure they reply. Or have them send to you. Basically, you want MS and Google to see 'healthy' traffic form your domain/ip.
* Total cost to ppbe is €X/month and ppbe pays for this. If people want to give some monetary support for it, they can donate to ppbe whatever amount they see fit (pay-what-you-want). It's also possible to [https://donate.yunohost.org/ donate to the yunohost project].
* Try to give a short tour of the admin and user interface, so they know what they can do and how

== Todo ==

* Follow our latest discussions and work flow there on [https://www.loomio.org/d/TEqnO5ek/we-need-to-clarify-the-it-roles-and-entrust-our-it-people- a Loomio thread].

== Meetings ==
{{Events|type=Meeting|ITSquad|lang=fr|limit=10}}

Crew BW

2020-12-14T16:06:07Z

HgO: still a member

{{CrewSidebar
|image = Logo-heart-bw 135px.png
|crewname=Crew BW
|region=Wallonie
|province=Brabant Wallon
|city=Louvain-la-Neuve
|postalcode=1348
|captain=Y en n'a pas
|navigator=Ca tourne
|members=[[User:ZeFredz|Fred]], [[User:Wilmotte|Jean-Pierre]], [[User:Rutabaga|Patrick]], [[User:Valerie|Valérie]], [[User:HgO|Hadrien]], [[User:Damiens|Damiens]]?
|socialnetworks=[https://www.facebook.com/pages/Parti-Pirate-Brabant-wallon/132640623428484 Facebook],[https://www.loomio.org/g/XdDUxQf0/crew-du-b-w-friendz Loomio]
|contact = bw (at) pirateparty [point] be
|status=active
}}

== Introduction ==

Bienvenue sur la page de l'équipage des Pirates du Brabant Wallon !

Les Pirates du Brabant Wallon ont pour objectif de promouvoir les idées pirates dans leur province, d'encourager la citoyenneté et la démocratie et de soutenir les candidats pirates qui se présentent aux élections. Voir notre [[Crew_BW/non_reglement|Non-règlement]].

Nous discutons de nos projets, idées, etc. sur [https://www.loomio.org/g/XdDUxQf0/equipage-bw-sympathisants notre groupe loomio], et nous annonçons nos prochaines évènements via notre mailing list: '''pastispatate at framalistes point be'''

Sur cette page, vous trouverez la liste de nos réunions (où vous êtes le·a bienvenu·e) ainsi que nos projets en cours (où toute aide est également la bienvenue).


== Nos projets ==

Voici les (principaux) projets dans lesquels nous mettons notre énergie pour le moment :
* Démocratie 2.0
** [[Internal Democracy|Démocratie interne]] : commençons par travailler à la démocratie au sein même du parti pirate
** [[Local Democracy|Démocratie locale]] : réfléchir et améliorer la démocratie au niveau de sa commune --> au sein du collectif [https://collectifdemoloc.wordpress.com/ "Demoloc"]
* [[Transparency|Transparence]]
** Accès aux documents administratifs : car la démocratie commence par l'accès aux documents
* Elections communales 2018
** [[Local_Democracy|Liste citoyenne]] : en réflexion avec d'autres habitants et collectifs de Ottignies-Louvain-la-Neuve pour mettre en place une liste citoyenne aux prochaines élections, au sein du collectif [https://collectifdemoloc.wordpress.com/ "Demoloc"]
** [[Crew BW/Kayoux|Kayoux]] : liste citoyenne pour les élections 2018
* Autres activités
** [[Crew BW/DsC|Débats sans conférence]] : cercle de parole/éducation populaire à Louvain-la-Neuve, co-organisé avec le groupe local du mPOC (Mouvement politique des objecteurs de croissance)

== Prochains Rendez-vous ==

Nous essayons d'organiser des rencontres régulières, mais une bonne partie de notre équipage étant impliquée dans la liste citoyenne [[Crew_BW/Kayoux|Kayoux]] à Ottignies-Louvain-la-Neuve, c'est difficile en ce moment. Le plus simple est de consulter la liste des prochains événements ci-dessous.

Vous trouverez la liste complète de nos dernière réunions [[Crew BW/Meeting|en cliquant sur ce lien]].

Nos réunions sont publiques et ouvertes à tous·tes. Mais pour faire connaissance dans un cadre informel sans les contraintes d'un ordre du jour, choisissez plutôt de nous retrouver lors de notre prochaine "Pirate Drink".

Vous trouverez également ci-dessous la liste des prochains évènements auxquels des pirates pourraient participer. Notez que ces évènements — identifiés par l'icône [[File:Toicon-icon-avocado-schedule.svg|link=|class=icon]] — sont externes au Parti Pirate et ne sont en général pas organisés par celui-ci. La liste complète des évènements externes impliquant la Crew BW se trouve [[Crew BW/Event|sur cette page]].

=== Prochains événements ===

{{Events|Crew BW|start=now|order=asc}}

== Réunions ==

Vous pouvez consulter les ordres du jour et comptes-rendus de nos dernières réunions [[Crew_BW/Meeting | sur cette page]].

{{Events|limit=10|type=Meeting|Crew BW}}

== Participer ==

Lien vers le pad : [https://pad.pirateparty.be/p/Accueil_BW https://pad.pirateparty.be/p/Accueil_BW]

<eplite id="Accueil_BW" />

[[category:Crew en Wallonie]]
[[category:Crew en Province du Brabant Wallon]]

User:HgO

2020-11-27T16:52:44Z

HgO: just a test

{{PirateSidebar
| name = HgO
| city = Braine-l'Alleud
| crew = Crew BW
| workgroups = Internal Democracy, ITSquad, WikiSquad
| topics = Democracy, Transparency
| mastodon = [https://mastodon.pirateparty.be/@HgO @HgO@mastodon.pirateparty.be]
| jabber = hg@jabber.fr,(ceci n'est pas une adresse mail !!)
| website = [https://batato.be batato.be]
| diaspora = [https://framasphere.org/u/hgo hgo@framasphere.org]
| contact = hadrien at pirateparty point be (Clé PGP : [https://sks-keyservers.net/pks/lookup?op=vindex&search=0x26687C5A 0x26687C5A])
| git = https://framagit.org/u/HgO
}}

~24 ans<ref>Je vais laisser ce nombre comme ça, car la flemme d'incrémenter chaque année, et puis 24 c'est le miroir de 42 donc c'est cool ^_^</ref>, pirate de l'[[crew BW|équipage Brabant Wallon]], [http://fr.wikipedia.org/wiki/B%C3%A9po bépoête], [http://fr.wikipedia.org/wiki/Libriste libriste], [http://fr.wiktionary.org/wiki/zététique zététicien] convaincu, patatiste (concept flou), canarchiste (concept à définir), apprenti [http://fr.wikipedia.org/wiki/Esp%C3%A9rantiste espérantiste], apprenti photographe, apprenti informaticien, [http://potagerdesarchers.be apprenti jardinier], et apprenti apprenti. Orang-outang sur son temps libre.

Je suis admin sur l'[https://mastodon.pirateparty.be instance Mastodon du Parti Pirate], donc si vous avez un problème c'est probablement ma faute ^^

Vous pouvez me contacter via :
* [[{{TALKPAGENAME}}|ma page de discussion]]
* par mail : hadrien at pirateparty point be
** Clé PGP : [https://sks-keyservers.net/pks/lookup?op=vindex&search=0x26687C5A 0x26687C5A] (plus d'infos à propos de PGP [http://wiki.partipirate.org/wiki/Tutoriel:PGP ici] et [http://wiki.partipirate.org/wiki/S%C3%A9curiser_vos_courriels_avec_GPG là] + [[Wikipedia:fr:Pretty_Good_Privacy|wikipédia]])
* ou simplement via [[Special:EmailUser/HgO|ce formulaire]] (n'oubliez pas de communiquer votre e-mail pour avoir une réponse)

== Introduction ==

Avant de rejoindre les pirates, j'ai combattu l'[[Wikipedia:fr:Accord_commercial_anti-contrefaçon|ACTA]] en 2010 en participant à plusieurs manifestations et en essayant de sensibiliser un maximum de personnes, notamment sur la problématique du droit d'auteur et du partage de culture sur internet. J'ai ensuite suivi de très près le mouvement des [[Wikipedia:fr:Indignés|Indignés]] en 2011.

Pirate depuis 2012 au sein de l'[[Crew BW|équipage Brabant Wallon]], j'ai participé aux élections communales et provinciales de 2012 (sans pour autant me présenter), avec toutes les joyeusetés que cela implique (j'adore faire les marchés pour récolter des signatures, si si ^^'). Après les élections, tous les membres du parti ont été invités à proposer de nouveaux statuts pour le Parti Pirate, dans le but de lui donner une meilleure structure. Après plusieurs AGs passées à voter (urgh) des centaines de propositions (re-urgh), j'en suis ressorti avec le sentiment que le vote n'était pas la bonne méthode pour obtenir des décisions démocratiques. Ce sentiment n'a fait que se renforcer au fil des AGs, lesquelles m'ont permis d'observer que le vote avait la fâcheuse habitude de créer des conflits et tensions au sein d'un groupe. C'est pourquoi, depuis février 2017, je participe au groupe de travail « [[Internal Democracy|Démocratie interne]] » qui s'est donné pour objectif de produire des [[Internal Democracy/Guidelines|règles de bonnes conduites]] permettant d'avoir des réunions démocratiques et co-créatives.

Administrateur depuis 2013, je m'efforce d'améliorer le wiki des pirates, en le cassant puis en le réparant, et en le re-cassant à nouveau :D Vous aurez probablement l'occasion d'observer cet étrange comportement au travers de la [[Special:RecentChanges|page des modifications récentes]]. D'ailleurs, il est possible que quelque chose ne fonctionne pas comme il le faudrait sur le wiki : dans ces cas-là, n'hésitez pas à me contacter, et je ferai de mon mieux pour trouver une solution ! Vous pouvez également laisser un message sur la [[Talk:WikiSquad|page de discussion]] de la [[WikiSquad]], elle est là pour ça ;) Mon projet actuel est de créer un [[:Category:Event|système d'évènements]] qui soit le plus simple d'utilisation possible. Vos suggestions sont les bienvenues :) Si vous avez d'autres idées pour améliorer le wiki, je suis également preneur ;) D'ailleurs, n'hésitez pas à contribuer au wiki, et n'ayez crainte de le casser : nous pouvons à tout moment revenir en arrière. En d'autres termes, un wiki est fait pour être cassé (parole d'expert ^^) !

Je suis également l'un des administrateurs de [https://mastodon.pirateparty.be l'instance Mastodon des pirates], un réseau social qui ressemble à Twitter mais qu'il est mieux ! Je m'occupe principalement d'effectuer les mises à jour du logiciel. À nouveau, si vous rencontrez des problèmes sur Mastodon, je me ferai un plaisir de vous aider :)

Au niveau politique, je m'amuse pour le moment à [[Transparency|libérer des documents administratifs]]. La transparence de nos institutions n'est qu'une des pierres nécessaires à la construction d'une démocratie directe. Comme vous l'aurez deviné, je suis très attaché au concept de démocratie directe, et je m'interroge beaucoup sur la prétendue efficacité du vote et des élections, etc.

Je pense qu'il est illusoire de croire qu'une révolution globale viendra bouleverser le système capitaliste qui nous est imposé, du moins à moyen terme. Cela ne veut pas dire que je ne combats pas ce système injuste, au contraire. Mais j'essaie de faire bouger les choses au niveau local, c'est-à-dire au niveau du quartier ou de la commune principalement. Par exemple, je suis persuadé que les potagers collectifs sont une des clés pour retisser du lien social, et redonner vie à un quartier. Récemment, j'ai découvert le concept de [[Municipalism|municipalisme]] qui semble confirmer mon hypothèse.

Pour le reste, je m'intéresse en ce moment à l'économie. J'ai eu la terrible chance d'assister à un cours de micro-économie durant mon cursus universitaire. C'était une vaste blague. Mais malheureusement je n'avais pas le bagage suffisant pour comprendre ce qui n'allait pas dans les « théories » (c'est un bien grand mot) actuelles sur l'économie néo-libérale. Je m'intéresse donc à des auteurs tels que [[Wikipedia:fr:Paul Jorion|Jorion]] et [[Wikipedia:fr:Keynes|Keynes]], et bientôt [[Wikipedia:fr:Silvio Gesell|Gesell]] et [[Wikipedia:fr:Polanyi|Polanyi]]. Comme il est difficile de parler d'économie sans parler de travail, je vous recommande également la lecture de l'''[[Wikipedia:fr:Éloge de l'oisiveté|éloge de l'oisiveté]]'' de [[Wikipedia:fr:Bertrand Russell|Bertrand Russell]] (une adaptation mise en scène par le fabuleux Dominique Rongvaux est disponible [https://www.youtube.com/watch?v=7KpxsqwNF0o sur youtube]).

Enfin, la liberté est une question fondamentale à mes yeux. Je m'inspire des œuvres de [[Wikipedia:fr:Henry David Thoreau|Thoreau]] et son concept de [[Wikipedia:fr:Désobéissance_civile|désobéissance civile]], qui sera plus tard repris et développé par [[Wikipedia:fr:Gandhi|Gandhi]] (je privilégie d'ailleurs les méthodes non-violentes autant que possible). Je me considère également comme étant un anarchiste, mais ce concept étant mal compris par la plupart de mes contemporains, je préfère le terme « canarchiste » qui est plus rigolo. Sinon, ''pirate'', c'est bien aussi ;)

== Projets ==

* [[User:HgO/PatateBox|PatateBox]], mes expériences bizarres sur ma PirateBox.
* [http://b.oook.in Oook], bibliothèque numérique prévue pour être installée sur des PirateBox (je cherche encore comment compiler le moteur de recherche pour OpenWrt, l'OS utilisé dans les PirateBox).
* [https://framagit.org/HgO/chatbox ChatBox], un petit chat prévu pour fonctionner sur une PirateBox.
* [https://framagit.org/HgO/tradis Tradis], un logiciel permettant de prendre « facilement » note lors des conseils communaux.

== Livres conseillés ==
Voici quelques livres intéressants concernant certains sujets qui me tiennent à cœur :

* [http://www.framablog.org/index.php/post/2011/02/12/ivan-illich-une-societe-sans-ecole Une société sans école], 1971, Ivan Illich
** interview d'Ivan Illich résumant bien ses idées: https://www.youtube.com/watch?v=K-eauppsNf0
* [http://www.framablog.org/index.php/post/2012/01/07/monde-sans-copyright Pour un monde sans copyright… et sans monopole], 2011, Joost Smiers & Marieke van Schijndel
* L'espéranto, 1973, Pierre Janton
* Tentatives de lucidité, 2005, Albert Jacquard
* Petit traité de décroissance sereine, 2007, Serge Latouche
* [[Wikipedia:fr:Désobéissance_civile|La désobéissance civile]], 1849, Henry David Thoreau
* [[Wikipedia:fr:Discours de la servitude volontaire|Discours de la servitude volontaire]], La Boétie

<references />

----
Pas de panique ! Cette page se construira au fil du temps, désolé pour le dérangement… {{#set:Notifications group member of=Calendar}}

Municipalism/Documentation/Articles/en

2020-06-25T12:01:25Z

HgO: remove facebook surveillance

==2018==

=== 6 November : [https://www.greeneuropeanjournal.eu/municipalism-murray-bookchins-legacy Libertarian Municipalism & Murray Bookchin’s Legacy] ===
; Green European Journal : ''From the USA to Spain and beyond, the last decade has seen a surge in municipalist and local democracy citizens’ movements. Many have been influenced by the ideas of American writer and thinker Murray Bookchin (1921-2006), which envisaged a new left politics based on popular assemblies and grassroots democracy. We sat down with Debbie Bookchin to discuss how these movements are implementing her father’s ideas and what the potential challenges are for libertarian municipalism.''

==2017==
=== 16 August : [http://www.redpepper.org.uk/fearless-cities-the-new-urban-movements/ Fearless Cities: the new urban movements] ===
;Red Pepper : ''A wave of new municipalist movements has been experimenting with how to take – and transform – power in cities large and small. Bertie Russell and Oscar Reyes report on the growing success of radical urban politics around the world''
=== 22 July : [https://medium.com/@tinazucchini/what-municipalism-and-fearlesscities-could-mean-for-new-zealand-389dd54d133a What Municipalism and #FearlessCities could mean for New Zealand] ===
*Medium
=== 21 July : [https://roarmag.org/magazine/municipalism-feminization-urban-politics/ Municipalism and the Feminization of Politics] ===
; ROAR Magazine : ''Beside turning local institutions into mechanisms of self-governance, municipalism also has the potential to feminize politics in a way that action at the national level does not.''
=== 21 July : [https://roarmag.org/magazine/cities-against-the-wall/ Cities Against the Wall] ===
; ROAR Magazine : ''Two years into its governing mandate, how is Spain’s municipalist movement fighting back against the impositions of global capital?''
=== 21 July : [https://roarmag.org/magazine/new-municipal-movements/ The New Municipal Movements] ===
*ROAR Magazine
=== 21 July : [https://roarmag.org/magazine/debbie-bookchin-municipalism-rebel-cities/ Radical Municipalism: The Future We Deserve] ===
; ROAR Magazine : ''Only a global confederation of rebel cities can lead us out of the death-spiral of neoliberalism towards a new rational society that delivers on the promise of humankind.''
=== 10 July : [http://www.alphr.com/technology/1006261/how-one-european-smart-city-is-giving-power-back-to-its-citizens How one European smart city is giving power back to its citizens] ===
*Alphr
=== 10 July : [http://piratetimes.net/a-just-future-starts-at-the-local-level/ A Just Future Starts at the Local Level] ===
*Pirate Times
=== 4 July : [http://magazine.ouishare.net/2017/07/what-if-cities-led-the-fight-against-climate-change-an-interview-with-mark-watts/ What if cities led the fight against climate change? – An interview with Mark Watts] ===
*OuiShare
=== 3 July : [http://politicalcritique.org/world/eu/2017/paolini-barcelona-superblocks-neoliberal-city/ Are Barcelona’s ‘superblocks’ a radical challenge to the neoliberal city?] ===
*PoliticalCritique
=== 27 June : [http://theconversation.com/how-madrids-residents-are-using-open-source-urban-planning-to-create-shared-spaces-and-build-democracy-79717 How Madrid’s residents are using open-source urban planning to create shared spaces – and build democracy ] ===
*The Conversation
=== 26 June : [https://www.opendemocracy.net/plan-c/radical-municipalism-demanding-future Radical municipalism: demanding the future] ===
*OpenDemocracy
=== 20 June : [http://magazine.ouishare.net/2017/06/building-the-networked-city-from-the-ground-up-with-citizens-interview-with-francesca-bria/ Building the networked city from the ground up with citizens – Interview with Francesca Bria]===
*OuiShare
=== 19 June : [https://govinsider.asia/inclusive-gov/barcelona-city-council-citizen-data-sharing-francesca-bria/ How Barcelona’s citizens will control the use of their data] ===
*GovInsider
=== 15 June : [http://urbandemos.nyu.edu/fearless-cities-a-dispatch-from-barcelona/ Fearless Cities: A Dispatch from Barcelona] ===
*Urban Democracy Lab
=== 14 June : [https://www.opendemocracy.net/can-europe-make-it/ignasi-calb-sunny-hundal/sanctuary-and-refuge-cities Sanctuary and refuge cities] ===
*OpenDemocracy
=== 12 June : [https://medium.com/enspiral-tales/fearlesscities-introducing-a-global-municipalist-network-b364f10c25ea How a Global Network of #FearlessCities is Making Racist Colonial Nation States Obsolete] ===
*Medium
=== 7 June : [http://politicalcritique.org/world/2017/from-citizen-platforms-to-fearless-cities-europes-new-municipalism/ From Citizen Platforms to Fearless Cities: Europe’s New Municipalism] ===
*PoliticalCritique
=== 7 June : [https://www.opendemocracy.net/can-europe-make-it/kate-shea-baird/new-international-municipalist-movement-is-on-rise-from-small-vic A new international municipalist movement is on the rise – from small victories to global alternatives] ===
*OpenDemocracy
=== 25 May : [http://politicalcritique.org/world/2017/in-naples-we-are-all-illegal-or-no-one-is/ Luigi de Magistris: “In Naples we are all illegal or no-one is”] ===
*PoliticalCritique
=== 7 May : [https://cooperativecity.org/2017/05/07/community-capital-in-action/ Community Capital in Action: New Financial Models for Resilient Cities] ===
*CooperativeCity
=== 25 April : [http://politicalcritique.org/world/2017/naples-common-good-empty-buildings/ What Makes an Empty Building in Naples a “Common Good”?] ===
*PoliticalCritique
=== 22 March : [https://www.opendemocracy.net/democraciaabierta/yago-bermejo-abati/random-election-g1000-and-deliberation-to-change-madrid Random election, the G1000 and deliberation to change Madrid] ===
*OpenDemocracy
=== 20 February : [https://energycommonsblog.wordpress.com/2017/02/20/rc04-remunicipalisation-of-energy-systems-part-2/ R&C04 – Remunicipalisation of energy systems – Part 2] ===
*Energycommonsblog
=== 30 January : [https://energycommonsblog.wordpress.com/2017/01/30/rc04-remunicipalisation-of-energy-systems/ R&C04 - Remunicipalisation of energy systems – Part 1] ===
*Energycommonsblog

== 2016 ==
=== 21 December : [http://commonstransition.org/this-is-how-people-power-wins-an-election-the-story-of-ahora-madrid/ This is how people power wins an election: the story of Ahora Madrid] ===
*CommonsTransition.org
=== 20 December : [http://commonstransition.org/common-space-for-exchange-cities-in-transition-and-citizen-struggles/ Common space for exchange: cities in transition and citizen struggles] ===
*CommonsTransition.org
=== 15 November : [https://qz.com/837383/cities-will-be-a-powerful-antidote-to-donald-trump-social-scientist-benjamin-barber-on-the-emergence-of-a-new-urban-radicalism/?utm_source=qzfb “Cities will be a powerful antidote to Donald Trump”: Social scientist Benjamin Barber on the emergence of a new urban radicalism] ===
*Quartz
=== 4 October : [https://www.weforum.org/agenda/2016/10/forget-the-nation-state-cities-will-transform-the-way-we-conduct-foreign-affairs/ Forget the nation-state: cities will transform the way we conduct foreign affairs] ===
*WeForum
=== 24 September : [https://blog.p2pfoundation.net/barcelona-en-comus-guide-to-urban-revolution-stresses-shared-priorities-over-party-politics/2016/09/24 Barcelona en Comú’s Guide to Urban Revolution Stresses Shared Priorities over Party Politics] ===
*P2PFoundation
=== 9 September : [https://qz.com/776882/mayors-from-70-cities-around-the-world-are-gathering-to-try-to-solve-the-worlds-problems/ Mayors from 70 global cities are gathering to try to solve the world’s problems] ===
*Quartz
== 2015 ==
=== 30 October : [http://www.huffingtonpost.com/sheila-foster/cities-inequality-and-the_b_8435316.html Cities, Inequality and the Common Good] ===
*Huffington Post
=== 14 July : [http://commonstransition.org/the-commons-have-come-to-town/ The Commons Have Come to Town] ===
*Commons Transition
=== 9 June : [http://commonstransition.org/6-lessons-for-the-u-s-from-spains-democratic-revolution/ 6 Lessons for the U.S. from Spain’s Democratic Revolution] ===
*Commons Transition
=== 1 June : [http://www.smartcitiesdive.com/ex/sustainablecitiescollective/smart-city-collective-intelligence-radical-change-brewing-barcelona/1078466/ From 'Smart City' to 'collective intelligence': radical change in Barcelona ] ===
*SmartCitiesDive
=== 27 May : [https://www.opendemocracy.net/can-europe-make-it/kate-shea-baird/beyond-ada-colau-common-people-of-barcelona-en-com%C3%BA Beyond Ada Colau: the common people of Barcelona en Comú] ===
*OpenDemocracy.net
=== 27 May : [http://commonstransition.org/towards-a-new-municipal-agenda-in-spain Towards a new municipal agenda in Spain] ===
*Commons Transition
=== 4 March : [https://roarmag.org/essays/barcelona-en-comu-guanyem/ Barcelona en Comú: the city as horizon for radical democracy] ===
*ROAR Magazine

{{Documentation|lang=en|type=article}}

Mastodon/Code of Conduct

2020-06-13T21:12:47Z

HgO:

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/06/29
| end = 2020/06/13
| status = done
| contact = it [at] pirateparty (point) be
| workgroup = ITSquad/Mastodon
}}

== Description ==

The purpose of this project was to create a Code of Conduct for the [https://mastodon.pirateparty.be/ PPBe instance of Mastodon].

As a reminder, Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

In August 2019, a first draft of the Code of Conduct was published. Then, in June 2020, the first version was released.

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]
* [[ITSquad/Mastodon/Moderation|This document aims to help Mastodon moderators to do their job more easily. ]]

== Events ==

{{Events|{{PAGENAME}}}}

ITSquad/Mastodon

2020-04-19T12:00:39Z

HgO: /* Related */

{{ProjectSidebar
| title = Mastodon
| start = 2017/04/09
| status = doing
| workgroup = ITSquad
| contact = it [at] pirateparty (point) be
}}

== Description ==

Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

Since 9th April 2017, the ITSquad proposes the Pirate Party's instance of Mastodon, available at http://mastodon.pirateparty.be/

On this project page, you'll find resources useful for installing and keeping up-to-date an instance of Mastodon.

Maintenance instructions for our instance can be found [[ITSquad/Mastodon/Maintenance|here]]

== Ressources ==

* https://docs.joinmastodon.org : Mastodon documentation
* [https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Docker-Guide.md Running Mastodon : Docker Guide] : A guide to configure and install a Mastodon instance with Docker. It seems that this guide won't be updated anymore.
** Currently, we are using [https://www.mailgun.com/ Mailguin] for sending mails.
* [https://github.com/tootsuite/mastodon/releases Mastodon releases] : The list of Mastodon releases.
* [[ITSquad/Mastodon/Maintenance|Maintenance instructions]] for the Pirate Party's Mastodon instance.
* [https://pad.pirateparty.be/p/mastodon Mastodon pad] : This pad contains the notes and documents used during the installation and upgrades of the Pirate Party's Mastodon instance.
** It's quite a mess at the moment, should be cleaned someday...
* [https://www.ssllabs.com/ssltest/analyze.html?d=mastodon.pirateparty.be SSL Server Test] : Analyse the SSL configuration of our Mastodon server
* [https://observatory.mozilla.org/analyze.html?host=mastodon.pirateparty.be Mozilla's HTTP Observatory] : Results for our Mastodon server
* [https://mozilla.github.io/server-side-tls/ssl-config-generator/ Mozilla's SSL Config Generator]
* [https://discourse.joinmastodon.org/t/mastodon-server-security-basics-how-to-get-an-a-in-the-xyz-list Mastodon server security basics]: How to get an A+ in the xyz list.
* [https://bjornjohansen.no/optimizing-https-nginx Optimizing HTTPS on nginx]

== Related projects ==

{{Projects|ITSquad/Mastodon}}

== Events ==

{{Events|ITSquad/Mastodon}}

ITSquad/Mastodon/Moderation

2020-04-19T11:59:33Z

HgO: HgO moved page ITSquad/Mastodon/Moderation to Mastodon/Moderation

#REDIRECT [[Mastodon/Moderation]]

Mastodon/Moderation

2020-04-19T11:59:33Z

HgO: HgO moved page ITSquad/Mastodon/Moderation to Mastodon/Moderation

This document aims to help Mastodon moderators to do their job more easily.

As a reminder, the Code of Conduct of our instance is located [https://mastodon.pirateparty.be/about/more there], and changes and remarks are made [https://pad.parley.be/p/mastodon-welcome on this pad].

== How is moderation handled? ==

'''''Note:''' "Suspend" or "block" means that the account is completely removed from our server. "Silence" or "mute" means that people from our instance won't see their toots, unless they decide to follow them.''

First, discuss with the mods about which action should be taken regarding the problematic person. Usually, we try to contact the person in order to explain what is the problem, and to clarify if needed. Once a consensus is reached within the moderation team, we can decide whether to suspend or silence the account.

In the case of spamming, harassment, bullying, porn without content warning and, in some case, illegal stuff, a moderator can decide by themself to suspend or silence the account. However, they must report of their decision with the moderation team, either by using the report tool or by directly messaging the other moderators. A discussion may follow to see if this was the right decision to take.

We can decide to suspend or silence a whole instance when we feel the community is problematic. For example, we would silence any dedicated porn instance where users don't use content warnings. We would suspend instances that don't respect users privacy, or that are dedicated to bullying, fascism, etc. If we have solid information about that instance, we might react preventively (e.g. a known fascist community opens an instance). Whenever an instance is suspended or silenced, a public statement is made with the PPBe account.

Cleanup old projects/Meeting/10 05 2020

2020-04-19T11:56:23Z

HgO: /* Agenda */

{{MeetingSidebar
|meetingname=Cleanup old projects meeting
|workgroup=Cleanup old projects
|date=2020/05/10
|time=14:00
|venue=Online (Sayyida al Hurra Room)
|address=https://talk.parley.be
|linkvenue=https://talk.parley.be
}}
== Details ==

We meet online on Mumble (link address in sidebar). The goal is to see how far we got in cleaning up active projects and work further on project [[Cleanup old projects]].

== Agenda ==

* How far did we get?
* What do we still need to do?
* Work!

Todo list from last meeting:
* Check the events of the subprojects that are not appearing on the "main project" page
* Check why some projects appear twice
** https://wiki.pirateparty.be/Com-X#Archived
* Work on Mastodon's Code of Conduct (see [[Mastodon/Code_of_Conduct/Meeting/02_05_2020|dedicated meeting]])
* Split the project "Improving the Wiki" into smaller one, to improve readability...
* Decide what to do with Kayoux project (discussions with Crew BW)
* Work on the important projects :
** Cleanup
** Complete the project
** Translate if needed
** Start working on it

== Report ==

The report will be provided at the end of the meeting.

Cleanup old projects/Meeting/10 05 2020

2020-04-19T11:55:41Z

HgO: Created page with "{{MeetingSidebar |meetingname=Cleanup old projects meeting |workgroup=Cleanup old projects |date=2020/05/10 |time=14:00 |venue=Online (Sayyida al Hurra Room) |address=https://..."

{{MeetingSidebar
|meetingname=Cleanup old projects meeting
|workgroup=Cleanup old projects
|date=2020/05/10
|time=14:00
|venue=Online (Sayyida al Hurra Room)
|address=https://talk.parley.be
|linkvenue=https://talk.parley.be
}}
== Details ==

We meet online on Mumble (link address in sidebar). The goal is to see how far we got in cleaning up active projects and work further on project [[Cleanup old projects]].

== Agenda ==

* How far did we get?
* What do we still need to do?
* Work!

Todo list from last meeting:
* Check the events of the subprojects that are not appearing on the "main project" page
* Check why some projects appear twice
** https://wiki.pirateparty.be/Com-X#Archived
* Work on Mastodon's Code of Conduct (see dedicated meeting)
* Split the project "Improving the Wiki" into smaller one, to improve readability...
* Decide what to do with Kayoux project (discussions with Crew BW)
* Work on the important projects :
** Cleanup
** Complete the project
** Translate if needed
** Start working on it

== Report ==

The report will be provided at the end of the meeting.

Mastodon/Code of Conduct

2020-04-19T11:40:41Z

HgO: start date

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/06/29
| status = doing
| contact = it [at] pirateparty (point) be
| workgroup = ITSquad/Mastodon
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the [https://mastodon.pirateparty.be/ PPBe instance of Mastodon].

As a reminder, Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]
* [[ITSquad/Mastodon/Moderation|This document aims to help Mastodon moderators to do their job more easily. ]]

== Events ==

{{Events|{{PAGENAME}}}}

Pirate Lab/Meeting/29 06 2019

2020-04-19T11:40:26Z

HgO:

{{MeetingSidebar
|meetingname=Pirate Lab June 2019
|workgroup=Pirate Lab,Defining the values of PPBe,Mastodon/Code of Conduct
|date=2019/06/29
|time=14:00
|venue=Expression
|address=Koning Albertplein 14
|postalcode=2800
|city=Mechelen
}}
= Pirate Lab June 2019 =

== About this meeting ==

Meetings are open to everyone! You don't need to be a member to come here! 
[[Pirate Lab|Pirate Labs]] can be seen as incubators for pirate projects. This is the perfect place for people to propose their ideas and to launch new projects.

If you have any ideas of projects, or want to help other projects, please do come!

We will use the [[Internal_Democracy/Guidelines|meeting guidelines]] proposed by the [[Internal Democracy|internal democracy group]]. Please have a look at them before coming to the lab :)

Languages: English, français, nederlands

== To-do list ==
# Define venue
# Confirm venue
# Create facebook event (then destroy facebook)

== Preparation ==

'''Lab starts at 2 pm'''. For those who want to lunch together before the lab, they can coordinate on the following pad:

https://pad.pirateparty.be/p/Piratelab2019-June

Suggestions for the agenda happen on this pad as well. We strongly advise you to '''read the pad''' before coming to this lab!

== Reporting ==

===First round : Values===
Discussion about the values (Freedom + Cooperation + Trust + General interest = 4 values on our website's frontpage). The values are quite vague, what do they actually mean? What kind of freedom? Free will... freedom only if it is real freedom? Could we be more specific? See also definition on [http://www.toupie.org/Dictionnaire/Liberte.htm La Toupie] (in French). Privacy is also essential, people change their behaviour once they feel they can be under surveillance.

===Second round : splitting into subgroups===
====Subgroup 1 : Code of Conduct====
Draft is on the pad : https://pad.pirateparty.be/p/mastodon-welcome

Call for feedback on Mastodon

====Subgroup 2 : How to organize informal events ====
The discussion actually centered mostly around Pirate Drinks.

There are 2 objectives for these events :
*provide an opportunity to non-pirates to meet us
*have a nice informal moment between Pirates

For the Pirate Drinks, it seems the first objective is more important.

Different ideas came out :

* We (HgO) should add on the Pirate Drink events template on the wiki that it's a meeting between Pirates and non-Pirates, not a speech/conference/exposé from Pirate Party.
* To lower the expectation and to avoid misunderstandings, we should warn (in the invitation/event description) that it's quite intimate/small/personal meeting, not a big meeting with lots of people.
* We must pay attention to make clear where the meeting actually takes place. If it's in a bar, have a flag or rollup and/or warn the bar workers where the Pirate meeting happens). This should also be added on the wiki (HgO)
* At the end of the meeting, we should offer a flyer containing basic information (contact, website, maybe more). Examples already exist on our [[Resources/Flyers|Flyers' page]]. You can also write/print the info on paper and cut it in small pieces. It doesn't have to be fancy, it needs to be practical.
* We could have guidelines for organizing informal moments (like we have for formal moments already)
* Should we invest in large display (flags, rollups...)? It seems more suited for bigger events.

=== Closing===
Roundtable where everyone says how they feel, what should be improved and what went fine.

* Ilja : Clarification during roundtable is interesting. Without having a debate a counterproposal/new proposal based on the understanding can already be given. The "no discussion" is too strict imo. Closing of subgroups isn't always needed imo.
* HgO: Beginning of the meeting was a bit messy because we where only three in the beginning and couldn't split. We tried to discuss about where to go (which topic to discuss). Proposition for the guidelines: Make explicit that a subgroup of one is possible.
* JF: Happy about the meeting, even though we're a small group. Feels that it does show that we work well in small group. Proposition for the guidelines: In beginning we where three and we discussed what's most important. I think this is an interesting discussion. Maybe three is a special case and should be added to the guidelines? Anyone should always be able to not participate in the subgroup, but rather avoid splitting a group of three. We began to talk about moderation, but someone wasn't present so we postponed <- this is a good decision
* Renaud: Feel good about meeting, we've been productive. Feels the beginning was indeed chaotic. Don't think we moved forward with the values, which is problematic. Also, good vibes during the whole meeting.

Next Lab : [[Pirate_Lab/Meeting/27_07_2019|Braine-l'Alleud on 27/07]]

Mastodon/Code of Conduct

2020-04-19T11:37:21Z

HgO: add Mastodon parent workgroup

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/08/01
| status = doing
| contact = it [at] pirateparty (point) be
| workgroup = ITSquad/Mastodon
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the [https://mastodon.pirateparty.be/ PPBe instance of Mastodon].

As a reminder, Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]

== Events ==

{{Events|{{PAGENAME}}}}

Mastodon/Code of Conduct

2020-04-19T11:36:04Z

HgO:

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/08/01
| status = doing
| contact = it [at] pirateparty (point) be
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the [https://mastodon.pirateparty.be/ PPBe instance of Mastodon].

As a reminder, Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]

== Events ==

{{Events|{{PAGENAME}}}}

Mastodon/Code of Conduct

2020-04-19T11:35:13Z

HgO:

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/08/01
| status = doing
| contact = it [at] pirateparty (point) be
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the PPBe instance of Mastodon [mastodon.pirateparty.be/].

Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]

== Events ==

{{Events|{{PAGENAME}}}}

Mastodon/Code of Conduct

2020-04-19T11:34:49Z

HgO:

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/08/01
| status = doing
| contact = it [at] pirateparty (point) be
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the PPBe instance of Mastodon [mastodon.pirateparty.be/].

Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]

== Events ==

{{Events|Mastodon/Code_of_Conduct}}

Mastodon/Code of Conduct

2020-04-19T11:34:39Z

HgO: Created page with "{{ProjectSidebar | title = Mastodon's Code of Conduct | start = 2019/08/01 | status = doing | contact = it [at] pirateparty (point) be }} == Description == This project aims..."

{{ProjectSidebar
| title = Mastodon's Code of Conduct
| start = 2019/08/01
| status = doing
| contact = it [at] pirateparty (point) be
}}

== Description ==

This project aims to create, maintain and improve the Code of Conduct of the PPBe instance of Mastodon [mastodon.pirateparty.be/].

Mastodon is a decentralized and libre microblogging network. It can be viewed as an alternative to Twitter (except that Mastodon is better :D)

== Ressources ==

* [https://mastodon.pirateparty.be/about/more Mastodon's Code of Conduct]
* [https://pad.parley.be/p/mastodon-welcome Pad to work on Mastodon's Code of Conduct]

== Events ==

{{Events|ITSquad/Mastodon/Code_of_Conduct}}

Mastodon

2020-04-19T11:27:30Z

HgO: Redirected page to ITSquad/Mastodon

#REDIRECT [[ITSquad/Mastodon]]

Redaction

2020-04-19T11:22:01Z

HgO: change status to doing instead of active

{{ProjectSidebar
|title = Redaction
|topics= Pirate Party
|workgroup = Com-X Squad
|start = 2012/12/30
|end =
|contact = [https://www.loomio.org/d/Cx8tp4Qj/external-communication-of-ppbe Loomio thread]
|status = doing
}}

=== Description ===

The objective of this project is to create textual content that will be published on the website of PPBe.

=== Process ===
There is a process that is used since a few years and that usually goes like this :
#A Pirate opens a thread on [https://www.loomio.org/g/X01fxy2L/pirates-be-permanent-assembly-website-squad the Loomio subgroup of the Website Squad]
##That thread contains [Post] in the title so that other Pirates recognize it's about a potential publication on the website
##The thread opens with a description of what the article is about
##There is also a link to a pad
#Two works happen in parallel :
##On the pad, there is a draft being written, often after mentioning some key elements that should be included in the article
##On the Loomio thread, a more general discussion about the article happens, also including where it stands, if it needs help in a specific section etc
#Once the article is written, some time is given for late feedback and for three Pirates to validate the article (usually the Pirates who have already contributed themselves)
#Depending of the topic of the article, a translation from French to Dutch or from Dutch to French is made, unless it is seen as useless or irrelevant
#The article is published on the website, which usually include a picture to illustrate it
#Once it's published, it can be shared by other channels (social networks, newsletter, etc)

This is not a mandatory process, but it's usually that way that is followed. If another process is used, it's a good practice to make it clear so that Pirates can know where and how they can contribute and give their feedback.

=== Articles currently open to contribution ===
If you want to contribute to the following articles (as a writer, to give input, to translate, to illustrate, to share, etc), you can join one of these open articles :

==== 17/04/2020 : Pirate comment on the coronavirus crisis ====
Article about the coronavirus crisis // [https://www.loomio.org/d/3b5lmUz7/-post-pirate-comment-on-the-coronavirus-crisis Loomio thread] // [https://pad.parley.be/p/pirate-comment-on-coronavirus Pad]

==== 27/01/2020 : New eID card with fingerprints ====
Article about new Belgian ID cards that contain fingerprints // [https://www.loomio.org/d/zDNxLXEU/-post-new-eid-card-with-fingerprints Loomio thread] // [https://pad.parley.be/p/beidcard-with-fingerprints Pad]

==== 02/12/2019 : Privacy alternatives ====
Article about alternatives to avoid surveillance // [https://pad.parley.be/p/wvl-privacy Pad]

==== 21/11/2019 : Amnesty International ====
Article about AI's report that Facebook and Google are threats to our privacy // [https://www.loomio.org/d/WNRuGFbY/-post-google-facebook-are-a-danger-for-human-rights-amnesty-international- Loomio thread] // [https://pad.parley.be/p/amnesty-report Pad]

=== Already published articles ===
This sections lists the articles that have already been published on our website. The dates are the day the Loomio thread was opened. List to be completed.

* 25/02/2019 : '''Privacy : red card for the public services''' // [https://www.loomio.org/d/POmFthv3/-post-fisconet-est-contraire-au-rgpd Loomio thread] // [https://fr.pirateparty.be/vie-privee-carton-rouge-pour-les-services-publics/ Publication en français], [https://nl.pirateparty.be/respect-voor-privacy-rode-kaart-voor-de-overheid/ Publicatie in nederlands]

* 08/02/2019 : '''Intimidation de la part de Florence Reuter : la réaction des Pirates''' // [https://www.loomio.org/d/oJKgVNiQ/intimidation-de-la-part-de-florence-reuter-r-action-de-notre-part- Loomio thread] // [https://fr.pirateparty.be/intimidation-de-la-part-de-florence-reuter-la-reaction-des-pirates/ Publication en français]

* 12/01/2019 : '''De meeste communautaire discussies leiden ons nergens. Zie hier waarom.''' // [https://www.loomio.org/d/sFaHZNJ7/-post-most-discussions-between-citizens-about-the-flawed-belgian-state-lead-nowhere-this-is-why Loomio thread] // [https://nl.pirateparty.be/particratie2/ Publicatie in nederlands]

Topic:Vkbiwvqz5yuoj1by

2020-04-11T23:43:39Z

HgO (talk | contribs) commented on "Names for the rooms" (I've added them! Thanks :))

Template:Events

2020-04-05T11:17:07Z

HgO: show meeting for abandoned and done projects as well

<includeonly>{{#ask:
{{#if: {{{type|}}}
| [[Has event type::{{#arraymap:{{{type}}}|,|x|x|{{!}}{{!}}}}]]
| [[Has event type::+]]
}} {{#if: {{{1|}}}
| [[Organized by::{{#arraymap:{{{1}}}|,|x|x|{{!}}{{!}}}}{{#ask: [[Category:Project]] [[In topic::{{#arraymap:{{{1}}}|,|x|x|{{!}}{{!}}}}{{#ask: [[Category:Topic]] [[Has parent::{{{1}}}]]
| link = none
| intro = {{!}}{{!}}
| sep = {{!}}{{!}}
}}]] [[Has status::doing||active||inactive||done||abandoned]] OR [[Category:Project]] [[Organized by::{{#arraymap:{{{1}}}|,|x|x|{{!}}{{!}}}}]] [[Has status::doing||active||inactive||done||abandoned]]
| link = none
| intro = {{!}}{{!}}
| sep = {{!}}{{!}}
}}]]
}} {{#if: {{{start|}}}
| [[Has date::>{{#time:Y/m/j|{{{start}}} }}]]
}} {{#if: {{{end|}}}
| [[Has date::<{{#time:Y/m/j|{{{end}}} }}]]
}} OR {{#if: {{{type|}}}
| [[Has event type::{{#arraymap:{{{type}}}|,|x|x|{{!}}{{!}}}}]]
| [[Has event type::+]]
}} {{#if: {{{1|}}}
| [[In topic::{{#arraymap:{{{1}}}|,|x|x|{{!}}{{!}}}}{{#ask: [[Category:Topic]] [[Has parent::{{{1}}}]]
| link = none
| intro = {{!}}{{!}}
| sep = {{!}}{{!}}
}}]]
}} {{#if: {{{start|}}}
| [[Has date::>{{#time:Y/m/j|{{{start}}} }}]]
}} {{#if: {{{end|}}}
| [[Has date::<{{#time:Y/m/j|{{{end}}} }}]]
}}
| ?Has page=page
| ?Has title=title
| ?Has date#ISO=date
| ?Has time=time
| ?In venue=venue
| ?Has link venue=linkvenue
| ?Has address=address
| ?In city=city
| ?In postal code#=postalcode
| ?Organized by#=workgroup
| ?Has event type=type
| ?In topic=topics
| ?Has location=location
| mainlabel = -
| format = {{#switch: {{{format|}}}
| list = list
| ul = ul
| template
}}
| link = none
| limit = {{{limit|10}}}
| introtemplate = {{#switch: {{{format|}}}
| list =
| ul =
| calendar =
| {{#if: {{{1|}}}
| {{#switch: {{{type|}}}
| Meeting = Table meeting intro
| Table event intro
}}
| {{#switch: {{{type|}}}
| Meeting = Table meeting organized intro
| Table event organized intro
}}
}}
}}
| template = {{#switch: {{{format|}}}
| list = Event item
| ul = Event item
| calendar = CalendarEvent
| {{#if: {{{1|}}}
| Table event
| Table event organized
}}
}}
| outrotemplate = {{#switch: {{{format|}}}
| list =
| ul =
| calendar =
| Table outro
}}
| sep = {{#if: {{{sep|}}}
| {{{sep}}}
| {{#switch: {{{format|}}}
| list = <hr />
}}
}}
| sort = Has date
| order = {{{order|desc}}}
| searchlabel = {{#ifeq: {{{more|true}}} | true
| {{#switch: {{{type|}}}
| Meeting = {{int:event-show-more-meetings}}
| PirateDrink = {{int:event-show-more-pirate-drinks}}
| {{int:event-show-more}}
}}
}}
| userparam = true
| default = {{NoEvent|{{{1|}}}|type={{{type|}}}}}
| named args = {{#switch: {{{format|}}}
| list = 1
| ul = 1
| calendar = 1
| 0
}}
}}{{#ifeq: {{{formlink|true}}} | true
| {{#switch: {{{format|}}}
| list = <hr />
}}''{{NewEvent|{{{1|}}}|preload={{{preload|}}}|type={{{type|}}}}}'' 
}} {{#ifeq: {{{export|true}}} | true
| ''{{ExportEvent|workgroup={{{1|}}}|type={{{type|}}}|limit={{{limit|10}}}|date={{{start|}}}|text={{int:event-export-for|iCalendar}} }}'' 
}}</includeonly><noinclude>
== Usage ==

<nowiki>{{Events|An awesome crew|type=Event|start=now|order=desc|limit=10|preload=page|format=table|formlink=true|export=true|more=true}}</nowiki>

== Examples ==

=== No event ===

<nowiki>{{Events|An awesome crew}}</nowiki>

{{Events|An awesome crew}}

=== Events by [[Crew BW]] ===

<nowiki>{{Events|Crew BW|limit=5}}</nowiki>

{{Events|Crew BW|limit=5}}

=== Future events by [[Pirates de Liège]] ===

<nowiki>{{Events|Pirates de Liège|format=calendar|start=now|order=asc}}</nowiki>

{{Events|Pirates de Liège|format=calendar|start=now|order=asc}}

=== Future [[Pirate Lab]] ===

This example will preload the content of [[Template:EmptyPirateLab/Preload|this page]] to create an new meeting.

<nowiki>{{Events|Pirate Lab|type=Meeting|format=list|start=now|preload=Template:EmptyPirateLab/Preload}}</nowiki>

{{Events|Pirate Lab|type=Meeting|format=list|start=now|preload=Template:EmptyPirateLab/Preload}}</noinclude>

ITSquad/Mumble

2020-03-29T16:45:02Z

HgO: /* Web client */

{{ProjectSidebar
| title = Mumble
| start = 2020/03/22
| status = doing
| workgroup = ITSquad
| contact = it [at] pirateparty (point) be
}}

== Description ==

Mumble is a server for holding audio conferences.

Since March 2020, the PPBe is hosting a Mumble server together with a web client on https://talk.parley.be.

It is also possible to connect through [https://www.mumble.com/mumble-download.php another Mumble client] at <code>mumble.parley.be</code> with port <code>64738</code>.

To connect you can give the username you wish. No password is needed, although we could decide to setup a password if we see that there are too much spam.

As we are using [https://umurmur.net/ umurmur], a lightweight Mumble server, there are some limitations. For instance, the number of rooms is fixed on server startup, and we cannot grant permissions for certain users. There is only one admin password, which gives the right to silent people.

== Install ==

'''Note:''' We are using two separate domain names, one for the mumble server and another for the web interface. However, you can as well use a single domain name for both applications. Indeed, the mumble server listens on port 64738, while the client listens on ports 80 and 443, so they won't conflict ;) Just reuse the same certificate for both applications and you should be fine.

=== Server ===

Install dependencies:

apt install git build-essential cmake libconfig-dev libprotobuf-c-dev libmbedtls-dev ssl-cert

Create the directory for the server sources:

mkdir /opt/umurmur
cd /opt/umurmur

Clone the umurmur git repository:

git clone https://github.com/umurmur/umurmur.git .

Checkout to the latest version (see the [https://github.com/umurmur/umurmur/releases releases list]):

git checkout 0.2.17

Create the build directory:

mkdir ./build
cd ./build

Build the sources:

cmake .. -DSSL=mbedtls
make

Install the umurmur binary on the system:

make install

You can now edit the configuration file at <code>/usr/local/etc/umurmur.conf</code>. Check the doc for an example. We will define the certificates later on. You can setup a password if you wish.

Generate a random password for the admin:

pwgen -s 42 1

And copy/paste this password to the umurmur config file.

Create the systemd service unit (just copy/paste this block):

<nowiki>
cat > /etc/systemd/system/umurmur.service << EOF
[Unit]
Description=Minimalistic Mumble server
After=network.target

[Service]
Type=simple
User=nobody
Group=ssl-cert
Restart=on-failure
RestartSec=3
PIDFile=/run/umurmurd.pid
ExecStartPre=/usr/local/bin/umurmurd -t -c /usr/local/etc/umurmur.conf
ExecStart=/usr/local/bin/umurmurd -d -r -c /usr/local/etc/umurmur.conf
ExecReload=/bin/kill -HUP $MAINPID
PrivateDevices=yes
PrivateTmp=yes
ProtectSystem=strict
ReadWriteDirectories=/usr/local/etc/
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
LockPersonality=yes
NoNewPrivileges=yes
LimitRTPRIO=1

[Install]
WantedBy=multi-user.target
EOF</nowiki>

Reload the systemd service unit config:

systemctl daemon-reload

=== Web client ===

Install nodejs repository (LTS is v0.12.x):

curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -

Install nodejs and websockify:

apt install nodejs websockify

Create the directory for mumble-web:

mkdir /var/www/mumble-web
cd /var/www/mumble-web

Clone the mumble-web git repository:

git clone https://github.com/Johni0702/mumble-web.git .

Build the sources:

npm install
npm audit fix

Build the assets and config:

npm run build

Edit the configuration file at <code>./dist/config.local.js</code>. Add the following options in the config file:

<nowiki>
// Which fields to show on the Connect to Server dialog
config.connectDialog.address = false
config.connectDialog.port = false
config.connectDialog.token = false
config.connectDialog.password = false

// Default values for user settings
config.settings.pttKey = 'shift'

// Default values (can be changed by passing a query parameter of the same name)
config.defaults.address = 'talk.parley.be/mumble'</nowiki>

This will tell the client to only ask for an username. If you setup a password for the server, you can set it to true.

The config also indicates to which address the client should connect. The <code>/mumble</code> path will be defined later in the Nginx section, but basically we will create a websocket proxy to the mumble server.

Create the systemd service unit (just copy paste this block):

<nowiki>
cat > /etc/systemd/system/mumble-web.service << EOF
[Unit]
Description=Mumble web client using websockets
After=network.target

[Service]
Type=simple
User=nobody
Group=nogroup
Restart=on-failure
RestartSec=3
PIDFile=/run/mumble-web.pid
ExecStart=/usr/bin/websockify --ssl-target 64737 localhost:64738
ExecReload=/bin/kill -HUP $MAINPID
PrivateDevices=yes
PrivateTmp=yes
ProtectSystem=strict
ProtectHome=yes
ProtectControlGroups=yes
ProtectKernelModules=yes
ProtectKernelTunables=yes
LockPersonality=yes
NoNewPrivileges=yes
LimitRTPRIO=1

[Install]
WantedBy=multi-user.target
EOF</nowiki>

Reload the systemd service unit config:

systemctl daemon-reload

=== Nginx ===

Install nginx:

apt install nginx

Create the config for your web client (just copy/paste this block):

<nowiki>
cat > /etc/nginx/sites-available/mumble.conf << EOF
server {
listen 80;
listen [::]:80;
server_name talk.parley.be mumble.parley.be;

# Useful for Let's Encrypt
location /.well-known/acme-challenge/ {
allow all;
}

location / {
return 301 https://$host$request_uri;
}
}

server {
listen 443 ssl http2;
listen [::]:443 ssl http2;

server_name talk.parley.be;

ssl_certificate /etc/letsencrypt/live/talk.parley.be/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/talk.parley.be/privkey.pem;

include /etc/letsencrypt/options-ssl-nginx.conf;

location / {
root /var/www/mumble-web/dist/;
}

location /mumble {
proxy_pass http://127.0.0.1:64737;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
}
}

map $http_upgrade $connection_upgrade {
default upgrade;
'' close;
}
EOF</nowiki>

Install certbot for managing the certificates ([https://certbot.eff.org check on their website] if you need to install the certbot repository):

apt install certbot python-certbot-nginx

Add the following hook in <code>/etc/letsencrypt/cli.ini</code>:

post-hook = chmod 0640 /etc/letsencrypt/archive/*/privkey*.pem && chmod g+rx /etc/letsencrypt/live /etc/letsencrypt/archive && chown -R root:ssl-cert /etc/letsencrypt/live /etc/letsencrypt/archive

This will give the read permissions for the group <code>ssl-certs</code>. It is required for the umurmur server which will be run as member of that group.

Generate two certificates, one for the client and one for the server:

certbot certonly --nginx -d talk.parley.be
certbot certonly --nginx -d mumble.parley.be

Enable the nginx configuration:

ln -s /etc/nginx/sites-available/mumble.conf /etc/nginx/sites-enabled/

Check that everything is fine:

nginx -t

Reload the nginx server:

systemctl reload nginx

Change the certificates for umurmur in the config file <code>/usr/local/etc/umurmur.conf</code>. The paths should be something like:

certificate = "/etc/letsencrypt/live/mumble.parley.be/fullchain.pem";
private_key = "/etc/letsencrypt/live/mumble.parley.be/privkey.pem";

You can finally start the client and server:

systemctl start umurmur
systemctl start mumble-web

Don't forget to open the port <code>64738</code> of your firewall if you want to allow people connecting from the desktop Mumble client!

When everything looks good, enable the services:

systemctl enable umurmur mumble-web

Enjoy!

Template:EmptyProject/fr

2020-03-29T13:06:35Z

HgO: Created page with ""

<noinclude><languages />

= Utilisation =

Vous pouvez soit utiliser {{#formlink:form=Project|link text=ce formulaire}}, soit copier/coller le code ci-dessous pour créer une nouvelle page de projet :

<nowiki>{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
}}



== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==



</nowiki>

= Exemple =

{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
| nocat = true 
}}

</noinclude>

== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==

Translations:Template:EmptyProject/32/fr

2020-03-29T13:06:35Z

HgO: Created page with ""

Template:EmptyProject/fr

2020-03-29T13:06:26Z

HgO: Created page with "</noinclude>"

<noinclude><languages />

= Utilisation =

Vous pouvez soit utiliser {{#formlink:form=Project|link text=ce formulaire}}, soit copier/coller le code ci-dessous pour créer une nouvelle page de projet :

<nowiki>{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
}}



== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==



</nowiki>

= Exemple =

{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
| nocat = true 
}}

</noinclude>

== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==

Translations:Template:EmptyProject/22/fr

2020-03-29T13:06:26Z

HgO: Created page with "</noinclude>"

</noinclude>

Template:EmptyProject/fr

2020-03-29T13:06:04Z

HgO: Created page with "* <s>Première étape, qui est terminée</s> * Seconde étape toujours en cours. -->"

<noinclude><languages />

= Utilisation =

Vous pouvez soit utiliser {{#formlink:form=Project|link text=ce formulaire}}, soit copier/coller le code ci-dessous pour créer une nouvelle page de projet :

<nowiki>{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
}}



== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==



</nowiki>

= Exemple =

{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
| nocat = true 
}}

</noinclude>


== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==

Translations:Template:EmptyProject/37/fr

2020-03-29T13:06:04Z

HgO: Created page with "* <s>Première étape, qui est terminée</s> * Seconde étape toujours en cours. -->"

* <s>Première étape, qui est terminée</s>
* Seconde étape toujours en cours.
-->

Template:EmptyProject/fr

2020-03-29T13:05:53Z

HgO: Created page with "<!-- Quelles sont les étapes nécessaires (généralement écrite sous forme de liste). Lorsqu'une étape est réalisée, vous pouvez la barrer de la liste."

<noinclude><languages />

= Utilisation =

Vous pouvez soit utiliser {{#formlink:form=Project|link text=ce formulaire}}, soit copier/coller le code ci-dessous pour créer une nouvelle page de projet :

<nowiki>{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
}}



== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==



</nowiki>

= Exemple =

{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
| nocat = true 
}}

</noinclude>


== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==

Translations:Template:EmptyProject/35/fr

2020-03-29T13:05:53Z

HgO: Created page with "<!-- Quelles sont les étapes nécessaires (généralement écrite sous forme de liste). Lorsqu'une étape est réalisée, vous pouvez la barrer de la liste."

<!-- Quelles sont les étapes nécessaires (généralement écrite sous forme de liste). Lorsqu'une étape est réalisée, vous pouvez la barrer de la liste.

Template:EmptyProject/fr

2020-03-29T13:05:37Z

HgO: Created page with "Exemple:"

<noinclude><languages />

= Utilisation =

Vous pouvez soit utiliser {{#formlink:form=Project|link text=ce formulaire}}, soit copier/coller le code ci-dessous pour créer une nouvelle page de projet :

<nowiki>{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
}}



== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==



</nowiki>

= Exemple =

{{ProjectSidebar
| image = Logo-heart 135px.png
| title = Un magnifique projet
| workgroup = Une grande équipe
| topics = Un bon thème
| start =
| end =
| contact = Tentacules
| status = doing
| nocat = true 
}}

</noinclude>


== Description ==



== Objectifs ==



== Évènements ==

{{Events|{{PAGENAME}}|type=Meeting}}

== Documentation ==



== Ligne du temps ==



== À faire ==

Translations:Template:EmptyProject/36/fr

2020-03-29T13:05:37Z

HgO: Created page with "Exemple:"

Exemple: