Pirate Party Belgium - User contributions [en]

User:Manu

2017-07-29T18:14:34Z

Manu:

Ancien membre de la [[Crew_Leuven|Leuvense crew]], [[Coreteam]] et [[WikiSquad]]. Plus actif depuis fin 2014.

WikiSquad

2016-09-15T15:57:48Z

Manu: /* Members */ removing myself from the list

To take care of the Wiki of the Belgian Pirate Party.

Pour s'occuper de la maintenance du Wiki des Pirate de Belgique.

== Members ==
Les membres de l'esquouade ont les droits d'administrateurs. Il peuvent donc supprimer, restaurer ou protéger une page et bloquer une adresse IP ou un compte utilisateur. N'hésitez pas à faire appel à eux si nécessaire.
* [[User:HgO|Hadrien]]
* [[User:Vincent.L|Vincent L]]
* [[User:ZeFredz|Fred]] ([[User talk:ZeFredz|talk]])
* Damiens (Co-opted Jan 02 2015)
* [[User:Tierce|tierce]] ([[User talk:Tierce|talk]])

== Vision ==
What the wiki should provide :
* A place to share and find information
* An efficient and noninvasive way to communicate between pirates.

== Projects ==
* [[Help:Contents|Document the wiki]]

=== Visual editor ===
We consider the option of installing the [http://www.mediawiki.org/wiki/Extension:VisualEditor Visual Editor] to ease page edition.

'''Blocking :'''
* Still in beta, doesn't seem to be quite ready for production (release expected in 2014).
* Requires to set up a [http://www.mediawiki.org/wiki/Parsoid Parsoid service]. This has to be done in collaboration with the IT guys.

=== Future ===
* Move the Wiki to a new server.
* Provide adequate tools to crews and squads to easy their workflow.
* Offer an easy way to write and manage bilingual pages.
* Implement an alternative to the mailing list (with semantic).
* Implement a calendar through Semantic Mediawiki, see [http://www.semantic-mediawiki.org/wiki/Help:Event_calendar_format].
* Improve the searching tool.

== TODO ==

* <s>Create a WikiBar</s>.
* <s>Make the white ground color of the logo transparent.</s>
** <s>There is a bug to upload files.</s>
* Fix translation system.
* <s>Fix the <nowiki><ref></nowiki> system, see [http://pirateparty.be/issues/install-cite-extension-wiki issue].</s>
* <s>Add subpage feature, see [http://pirateparty.be/issues/activate-subpages-wiki issue].</s>
* <s>Make the category tool efficient.</s>
* <s>Install navboxes, see [http://interi.org/2012/05/wikipedias-navbox-template/].</s>
* Create/import a template 'outdated content/page'.
* <s>Bug : Redirection to blank page when you are on [[Special:Watchlist]]</s>
* <s>Enable PageNotice (cf [[Talk:WikiSquad#PageNotice]])</s>
* Organise, distribute and manage statues administrator and Burocrate and delete obsolet user compte.
* <s> Receive notification for all pages of the wiki then send it to Patrick on a regular basis </s>
* Traduire le message d'introduction de [[WikiSquad|cette page]] en néerlandais français et anglais.
* Proposer des templates de page wiki [[Resources/Templates_Wiki|sur la page dédiée]]
* Clarifier la [[Elections:2014|Page dédiée aux élections]] ou trouver des gens pour s'en occuper.
* Installer un système de calendrier (cf. [[Talk:WikiSquad#Calendar]])

== Off line Meetings ==
*Past :
**Sunday 27/10/2013 17H00 on Pirate local in Brussels
**Sunday 05/01/2014 13H00 on Pirate local in Brussels
**Saturday 18/01/2014 10H00 - 14H00 [[Events/EGA:2014-01|on Pirate GA]]
**Friday 02/01/2015 14H00 in LLN
**Friday 12/06/2015 19H30 in pl. des Sciences, LLN (cf. [[Talk:WikiSquad#Meeting_on_June_12_2015_in_LLN|Talk Page]] and [[Crew BW/ODJ40|agenda]])
*Next :
**Saturday 15/10/2016 19H30 in LLN (cf. [[Crew BW/ODJ42|Crew BW agenda]])

== Online Meetings ==

*Past
**13 janvier [[WikiSquad/pad|Meeting pad]] sur base du [http://www.framadate.org/studs.php?sondage=yrhjlcriojzl6c4w sondage pour la période du 12 au 17 Janvier]

*Next
** I'd like to do a new meeting. Shall we do it online or just before the coreteam meeting on the 16th? --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 19:38, 3 February 2014 (CET)
[[category:Squad]]
[[Category:Project Squad]]
[[Category:Operational Squad]]
[[Category:Operational]]

Talk:WikiSquad/Archive 1

2015-02-06T20:45:36Z

Manu: /* Parcourir et éditer les statuts via le wiki */

Let's speak here between members of the Wikisquad about maintaining and developing the pirate wiki.

== A l'attention de [[user:Manu|Manu]] ==

Peux-tu revoir suivre mes modifications question orthographe ?

== Refonte Crew BW ==

À la [[Crew BW]], nous sommes en train de faire une [[Refonte de la page wiki bw| refonte de notre page wiki]].

Ce faisant, j'ai remarqué quelques problèmes:

* Si on stylise les titres (par ex, mettre un fond mauve comme en page d'accueil), le lien « modifier » n'apparait plus. Y a-t-il moyen de régler ça ?
* Lorsque l'on crée une sous-page (par ex [[Crew BW/Meeting Minutes]], il n'y a pas de lien vers la page parente qui se crée (alors que c'est le cas pour les sous-pages utilisateur...). Ce serait vachement chouette si on pouvait intégrer ça.

Au passage, nous avons traduit le [[Template:CrewSidebarFR| template]] pour les infos des crews (il n'était qu'en néerlandais).

Voilà, et si vous avez besoin d'aide pour la refonte du wiki général, dites-le nous !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:24, 19 October 2013 (CEST)

:Pour le problème des sous-pages, j'ai crée un [http://pirateparty.be/issues/activate-subpages-wiki ticket]. Il faut des droits d'administrateur pour pouvoir configurer ça.
:Merci pour la traduction, et oui, toute aide/initiative est la bienvenue! [[User:Manu|Manu]] ([[User talk:Manu|talk]])

::Salut [[User:HgO|HgO]], je trouve ça super ton initiative de refondre la page de ton équipage. Je viens de jetter un coup d'oeuil et je te propose d'intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. Comme tu sembles déjà avoir compris que sur un wiki, il suffit de s'inspirer de ce qui existe déjà et d'avancer par copier-coller-prévisualisation, cela ne devrait pas trop être compliqué pour toi. Pour la question de droit d'admin, il te suffit de t'inscrire dans la squad et je te les donnes. A ce propos [[User:Manu|Manu]] si tu en as besoin dis le moi. Pour les questions technique, je dois encore voir et peut-être demander à quelqu'un qui s'y connait mieux que moi... Lio
:::Merci Manu ! Pour l'aide, que puis-je faire ? J'ai l'impression qu'aucun des points listés sur la page de la squad ne sont possibles pour moi. Par ex, j'ai créé un logo avec fond transparent, mais je ne sais pas où le mettre...

::: Lio, être administrateur ne poserait pas de problème. Je ne suis pas un expert dans la gestion des wiki, mais j'apprends assez vite. De plus, j'ai vu qu'il y aura une sorte réunion ce dimanche 27/10, je passerai sans doute dire bonjour. Par contre, je n'ai pas compris ce que tu veux dire par « intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. ». C'est bien ce qu'on a fait, non ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:58, 19 October 2013 (CEST)
::::Te voilà Admin [[User:HgO|HgO]]. Si tu viens dimanche 27 ce sera parfait car un des admin de wikipédia sera normalement présent et on pourra lui poser toute les questions. Lio
::::: @HgO : Notre objectif global est de rendre le wiki beaucoup plus clair et accessible, de sorte à ce qu'on puisse trouver des infos facilement. Donc en gros, toute initiative allant dans cette direction est la bienvenue! D'ailleurs, perso, je trouve la refonte de la page BW que tu as faite vraiment nickelle dans cette optique. Si tu pouvais en faire un nouveau modèle genre 'crew frontpage', ce serait génial! Je pense aussi qu'on pourrait grandement s'en inspirer pour simplifier la page d'accueil. Si t'es chaud, fonce! :D
::::: @Lio : Oui, je veux bien les droits, ça me permettrait de pouvoir faire les choses directement au lieu d'embêter tout le monde^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]])

:::::: Merci Lio ^^
:::::: @Manu : Merci, mais je n'étais pas tout seul ^^ Pour le reste, je vais y réfléchir et j'y travaillerai sans doute le week-end prochain. Au pire, on en discute dimanche IRL :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:10, 20 October 2013 (CEST)

== List of squads and crews ==

J'ai commencé à créer des sous-catégories crews in Vlaanderen etc pour chaque région, et voulais faire de même par province, pour affiner le classement. Mais finalement, je me rends compte que d'un point de vue utilisateur, c'est nettement mieux de présenter ça sous forme de liste pour faciliter la navigation. Donc j'ai un peu laissé tomber ça pour reformer des listes de [[Crew List|crews]] et [[List of squads|squads]].
Le fait qu'elles soient hors de modèles permet aussi de simplifier leur modification par de nouveaux utilisateurs, voulant créer un nouveau groupe par exemple. Je prévois d'adapter les pages explicatives du wiki.
J'ai également changé la page d'accueil en conséquence pour limiter le nombre d'infos. [[User:Manu|Manu]] ([[User talk:Manu|talk]])

: Je viens de refondre le [[Template:CrewSidebar/sandbox|template CrewSidebar]] en fusionnant les 3 anciens modèles existants (un pour chaque langue). Dorénavant, il suffit de renseigner un attribut supplémentaire ''language=FR,NL'' pour que l'affichage se fasse dans la langue désirée. Vous trouverez un exemple d'utilisation [[Crew Leuven|ici]].
: Il y a à mon goût beaucoup trop de paramètres, mais je les ai laissés pour assurer la rétrocompatibilité.

: Avantages du nouveau template, pêle-mêle :
:* Un modèle unique pour les 3 langues.
:* Beaucoup plus de champs laissés optionnels pour ne pas surcharger l'affichage par défaut.
:* Documentation complète.
:* Catégorisation automatique des pages contenant le template.
:* Les champs ''province'' et ''ville'' sont renseignés par une propriété sémantique, ce qui permet de générer des listes automatiquement (voir [[User:Manu/sandbox]]. Ok, pas très impressionnant avec une seule crew...)

: Concernant ce dernier point, je viens de voir seulement maintenant que Vincent avait modifié la [[Crew_List|liste des équipages]]. Vincent, est-ce que tu penses que la présentation automatique en tableau comme je le propose est acceptable, ou souhaites-tu que je travaille la présentation pour garder le même affichage que le tien?

: Inconvénient :
:* Code plus complexe.
:Si personne n'a d'objection, je compte remplacer toutes les occurences des 3 anciens templates par celui-ci. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:00, 2 March 2014 (CET)

== Category tool ==

Hi every one, just take a look [[Talk:List of squads|here]] to understand how work's MediaWiki category tool and how to simplifie our wiki and reduce our work.
Lio

:Je comprends bien l'avantage des catégories : on catégorise et hop, ça apparait sur la page correspondante, pas besoin d'éditer une autre page. Mais en même temps, je pense que d'un point de vue utilisabilité, c'est assez mauvais.

:D'abord, on n'a aucune emprise sur la mise en page des pages catégories. Pour l'utilisateur final souhaitant trouver une page, tout semble morcelé, et s'il faut commencer à parcourir les sous-catégories, on n'en a pas fini de cliquer.

:Ensuite, pour quelqu'un non familier avec le wiki souhaitant créer une nouvelle crew/squad, il est plus simple de devoir ajouter un lien dans une liste, que de devoir catégoriser; ne fut-ce que parce que cette dernière action nécessite une syntaxe particulière.

:Tout ça pour dire que je ne suis pas convaincu par l'utilisation des catégories pour simplifier le wiki :) [https://fr.wikipedia.org/wiki/Aide:Liste Petit comparatif] qui à mon sens plaide en faveur des listes pour leur flexibilité.
:Ou alors, j'ai mal compris l'utilisation que tu veux en faire? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:13, 22 October 2013 (CEST)

::Je partage ton avis Manu, les catégories sont complémentaires aux listes. Je propose donc que tu tables sur les listes pendant que je m'occupe de celles-ci. Ca te vas ? Lio
:::Owkay ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:43, 23 October 2013 (CEST)

== Réunion 27/10 ==

Je devrais pouvoir passer demain pour discuter du wiki, mais un temps limité. L'atelier wiki se tient de 14h à 17h, mais je vois que sur la page de la squad, Lio a mis réunion 17h. En gros, c'est mieux que je passe quand?^^ (Hadrien tu comptes passer?) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:26, 26 October 2013 (CEST)
:Pour répondre à ta question, de 14 à 17h il sera question du wiki de wikipédia et après 17h du wiki pirate mais dans les deux cas nous parlerons du logiciel commun mediawiki. Au faite, je sais toujours pas qui va pouvoir m'ouvrir la porte avant deux heure... Lio
:: Ok, je serai là vers 17h. Mais j'ai de toute façon pas de clé pour t'ouvrir :( [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:16, 27 October 2013 (CET)
:::Ca roule ! Lio
: Yep, je viendrai vers 14h. À tout' :) [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:40, 27 October 2013 (CET)

== CrewHeader et CrewSidebar ==

J'ai créé le template pour l'header des équipages, comme discuté hier : [[Template:CrewHeader]]. J'ai tenté de le faire le plus flexible possible. Par ex, les noms des paramètres des colonnes sont row1col1, row1col2, ..., row2col3, ceci afin de ne pas imposer aux équipages le contenu des colonnes.

J'ai également amélioré le template [[Template:CrewSidebar]]. Désormais, on peut préciser les réseaux sociaux de l'équipage, et le paramètre est totalement facultatif.

J'ai appliqué mes changement dans la [[Crew BW]], n'hésitez pas à y jeter un œil ^^

Pour ce qui est de transformer les tableaux en template (par ex, faire un Template:TablePurple), je ne pense pas que ce serait possible simplement... Le mieux serait de le faire avec du css, je pense.

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:16, 28 October 2013 (CET)

== Refonte de la page d'accueil du wiki ==

Apparemment, Vincent avait déjà commencé le boulot en septembre : [[Main Page test]]. Je propose de faire nos expérimentations sur cette page. On peut aussi s'inspirer de ce qu'il avait fait.

On peut également s'inspirer des autres partis pirates. Celui des Britanniques est plein de couleurs : [http://www.pirateparty.org.uk/wiki/Main_Page]. Je trouve également intéressant le fait de mettre une liste de membres dans chaque équipage : [http://www.pirateparty.org.uk/wiki/Scotland]. Cela permet d'avoir des noms, des comptes twitter à suivre, etc. C'est important je pense lorsqu'on débarque dans un nouveau parti.

Les Français quant à eux ont gardé une structure très proche des wiki traditionnels : [http://wiki.partipirate.org/Accueil]. On remarque par exemple qu'ils affichent leurs équipages sous forme de catégorie : [http://wiki.partipirate.org/wiki/Cat%C3%A9gorie:Section_locale].

Si vous avez d'autres exemples, n'hésitez pas !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:58, 28 October 2013 (CET)

:J'aurai plus de temps jeudi pour regarder à tout cela. Juste en passant, je trouve que les multicouleurs du site britanique ou de la page test de Vincent n'apporte rien. Ca fait même un peu confus point de vue graphique je trouve. Pour le reste, je ferai jeudi quelque test sur la page de lacrew de Walcourt en fonction de mes gouts perso. Cela dit je ne vois aucun inconvénent à ce que les crew personnalisent leurs page chacune d'une manière différente. Lio

:: Selon moi, les couleurs apportent au moins deux choses :
::* une meilleure lisibilité (l'œil humain distinguant nettement plus facilement deux couleurs différentes que n'importe quel autre motif),
::* un design plus chaud et agréable, ce qui rend les gens de bonne humeur :)

:: Sinon, je suis conscient que le modèle n'est pas encore parfait, mais il reste selon moi meilleur que la page d'accueil actuelle. Quelqu'un a une objection pour reverser ces changements sur la vraie page d'accueil? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:22, 1 November 2013 (CET)

::: J'attendrais encore un peu avant de reverser les changements (on doit encore mettre les réseaux sociaux (pas urgent), et remplir la Highlight box) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:29, 1 November 2013 (CET)

== Navboxes ==

J'aimerais bien importer les navboxes de wikipedia (les boites de navigation en bas des pages) dans le wiki pirate. J'ai commencé à importer les templates, seulement, selon [http://interi.org/2012/05/wikipedias-navbox-template/ ce site], il faut également installer l'extension [https://www.mediawiki.org/wiki/Extension:ParserFunctions ParserFunctions], installer le paquet php5-tidy sur le serveur, et copier des fichiers css protégés. Tous des trucs demandant plein de droits partout, que je ne sais donc pas faire moi-même :(

:C'est Jonas qui a les droits d'accès, faudrait lui demander d'installer tout ça. Je pense que ça pourrait effectivement nous être utile. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:51, 1 November 2013 (CET)

:: J'ai fait des tests en local sur ma machine, on peut faire fonctionner les navboxes sans rien installer, sauf qu'il faut changer les fichiers Common.css et .js de Mediawiki. Ce sera donc fait dès que j'aurai les droits d'administration du wiki B-) (j'en ai déjà préparé une belle pour les assemblées générales^^) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:04, 10 November 2013 (CET)

== PageNotice ==

Je suis tombé sur le wiki du PPI hier, et je me disais que leur système pour annoncer les prochaines AG est pas mal : [http://wiki.pp-international.net/Main_Page]. Je pense que ça nécessite l'installation de l'extension [http://www.mediawiki.org/wiki/Extension:PageNotice PageNotice] (faudrait vérifier).

Vous en pensez quoi ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:54, 1 November 2013 (CET)

: Installer l'extension ne peut sûrement pas faire de tord ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:18, 1 November 2013 (CET)
:: Je l'ai installée en local pour tester. Pour info, les notices générées sont placées ''en dessous'' du titre de chaque page, et non au-dessus comme sur le site du PPI, et j'ai pas vu d'option pour changer ça. Donc ça perd un peu de son intérêt, et c'est sans doute pas la bonne extension^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:21, 17 November 2013 (CET)

::: Ah. Et ça peut-être : http://www.mediawiki.org/wiki/Manual:Interface/Sitenotice ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:42, 17 November 2013 (CET)

::: J'ai un peu mieux regardé, et apparemment y a rien à installer, juste modifier [[Mediawiki:Sitenotice]] :D (voir par ex : [http://wiki.pp-international.net/MediaWiki:Sitenotice]) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:47, 17 November 2013 (CET)

:::: Ah ben voilà, c'est ce que j'allais te répondre :P [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:39, 18 November 2013 (CET)

== Pages bilingues ==

J'ai travaillé sur des templates permettant un affichage bilingue des pages. [[How_to_:_Mise_en_page_bilingue_/_Tweetalige_opmaak|Voir la documentation]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:20, 9 November 2013 (CET)

== Bug watchlist ==

Il y a un bug lorsque l'on se trouve sur la liste de suivi : [[Special:Watchlist]].

La page apparaît puis un centième de seconde plus tard, je suis redirigé vers une page blanche.

C'est peut-être dû aux changements que tu as fait, Manu ?

: Tu as raison, c'était mystérieusement dû à du code js que j'ai ajouté. J'ai supprimé ce qui n'était pas nécessaire => tout rentre dans l'ordre :)

== SubPageList ==

@HgO : Toi qui réclamais subpage^^ : penses-tu que l'extension [http://www.mediawiki.org/wiki/Extension:SubPageList SubPageList] pourrait avoir son utilité? Je n'ai pas assez travaillé avec le wiki comme outil de crew pour pouvoir m'en rendre compte.

: Je ne suis pas certain que cela servirait, vu qu'on n'utilise qu'un niveau de hiérarchie (du style Crew/Sous-page). L'intérêt des sous-pages était qu'on puisse revenir facilement en arrière. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:49, 17 November 2013 (CET)

== Concernant la gestion de la main page... ==

Bon les gars, j'interviens avant le fiasco.

Trois possibilités :

* Soit on supprime la page test
* Soit on reporte les modifications de la vrai page sur la page test chaque fois que l'on en fait.
* Soit on ne fait plus de petites modification sur la vrai page mais uniquement des copiés collés de la page test vers la vrai page.

Je vote pour la troisième solution quel est l'avis des autres membres de l'escouade ?

Lio
:La page test nous sert encore, la deuxième option n'est pas viable sur le long terme car les deux pages vont diverger, je vote donc pour la dernière solution.

:C'est d'ailleurs ce que je proposais dans un mail. Peut-être verrouiller temporairement la page d'accueil ? Ou mettre un message en haut de la page comme quoi c'est en bêta et les modifs doivent se faire sur la page test ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:20, 17 November 2013 (CET)

:: J'ai déjà verrouiller la page vrai page d'accueil et toutes les pages qui influence ce qui apparait sur celle-ci cela signifie que seuls les utilisateurs ayant le statut d'administrateur peuvent éditer celles-ci.Lio
::: Agreed. J'ai mis un message sur la [[Talk:Main_Page|page de discussion]] de la page d’accueil. Je préfère éviter de mettre un message sur la page elle-même pour éviter de la surcharger, surtout qu'il y a un lien dans la rubrique 'À la une' qui mène ici. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:52, 18 November 2013 (CET)

== Un lien vers la WikiSquad désormais dans l'onglet WikiHelp ==

Pour faciliter notre travail et la communication entre membre de l'escouade... Lio
== Passons au sémantique! ==

Hello!

En naviguant dans les extensions de MediaWiki, je suis tombé sur [http://www.semantic-mediawiki.org/ Semantic MediaWiki]. Et y'a pas à dire, c'est de la bombe! Le meilleur moyen de voir de quoi il en retourne est de lire l'[http://semantic-mediawiki.org/wiki/Help:Editing introduction].

Je pense que dans un projet comme celui du PPBE, elle pourrait jouer un rôle essentiel. Quelques exemples :
* Plus besoin de tenir à jour des listes manuellement. [http://www.semantic-mediawiki.org/wiki/Help:Inline_queries] (vu le rôle essentiel que jouent les catégories là-dedans, je sens que Lio va aimer ;p)
* Simplification de l'utilisation de modèles (avec [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Forms])
* Création d'une propriété <nowiki>[[Needs help::]]</nowiki> pour voir en un coup d'œil les projets ayant besoin de renfort.
* Gestion de projets, de bugs, etc.
* Unleash your ideas!
Toutefois, comme il s'agit d'une grosse extension, j'aurais aimé des retours avant d'installer ça. Qui est chaud pour commencer à sémantiser le wiki? Qui souhaite en discuter en live? (en marge de la réunion coreteam du 24/11?)

:Notez que de mon point de vue il ne s'agit pas de Yet Another Tool, mais de bâtir sur ce qu'on a déjà pour simplifier ce qui se fait déjà. Pas de révolution, mais une évolution :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:28, 18 November 2013 (CET)

::Hello gentlemen, pour un tel changement, un environnement de test vous serait-il utile? Je crois pouvoir fournir ça via un serveur local chez moi. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 09:23, 25 November 2013 (CET)

:::Je suis partant pour l'idée. Malheureusement, je réagit trop tard pour la possibilité de réunion off line le 24. Mais on peut envisager une autre date. Quand à l'idée d'un environnement test je ne trouve pas cela nécessaire étant donné que MediaWiki est déjà conçu pour être évolutif sans gèner la continuité dans son utilisation courante. Mais bon en même temps je n'ai pas une conessance sufisante au niveau de la gestion de ce logiciel pour avoir une position catégorique. Maintenant que l'on est une petite équipe dans l'esquouade je vais contacter mon pot administrateur et programateur wikipédia pour voir si il ne pourrait pas nous dédiez un peu de temps pour un atelier wiki accé sur notre plateforme pirate. Je vous tiens au courant. Lio

:::: Pour info, je vais me pencher à nouveau là-dessus fin de semaine, j'aurai un ou deux jours de congé :) Hadrien m'a aussi montré ce qui se fait sur le wiki du Hackerspace, ce sera une bonne source d'inspiration. (j'ai aussi une installation en local, donc je peux faire tous les tests nécessaires avant de me lancer sur le wiki pirate ;) ) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:30, 1 December 2013 (CET)

== Attribution des droit d'administrateur à Vincent.L ==

Etant donné que Vincent a rejoint la WikiSquad, je viens de lui attribuer le statut d'administrateur. Welcome !

== Edition main page suite. ==

Je viens de faire un update de la main page test en fonction des modifications qui avaient été faite par Marrouanne et HgO...
Il en résulte donc que nos résolutions prisent concernant la gestion de ces deux pages ne fonctionne pas ou en tout cas ne sont pas respèctée.
Que fait-on ? Je vais toujour afficher un message dans le code pour informer les editeurs du passage obligé par la page test. Ou alors quoi ? On abandonne la page test ? Lio
:Pour moi la Main Page est stable à présent. Je pense que l'on peut déverrouiller la page, mais j'attends votre avis. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:22, 28 November 2013 (CET)
:: Tu veux déverouiller la page ? Sais-tu que actuellement n'importe qui peut se crée un profil sur ce wiki et la modifier par la suite ? Pour preuve voici [[user:Nimportequi|un compte]] créé après log out et qui pourra nous servir comme profil pour les administrateurs du site qui voudrait tester le comportement du site sans leurs privilèges. C'est une des raisons pour lesquels nous devons prendre des décisions par rapport à la gestion des droits d'édition et l'attribution des statuts administrateur et autres. Une réunion s'impose avant la prochaine AG pour faire des propositions concrètes concernant cette gestion avec un eventuel vote de l'assemblée pour avaliser et fixer les choses. --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:11, 28 November 2013 (CET)

:::Oui, je souhaite la déverouiller dans la mesure où l'on est tous des adultes responsables, et que l'on peut [https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Supposer_la_bonne_foi « supposer la bonne foi »]. Je ne crois pas que ce soit viable à terme de garder la page d'accueil verrouillée et de faire nos ajouts sur les deux pages (test et main). Par ex, ici j'ai rajouté l'appel à candidature pour les élections, mais il manque la traduction en néerlandais. J'aimerais que n'importe qui puisse rajouter cette traduction, ou rajouter quelque chose à la une, car on ne pourra pas penser à tout... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:38, 28 November 2013 (CET)

:::: Pour moi la seule utilité de la page test devrait être de tester un nouveau design. Passer par là pour chaque petit changement n'est clairement pas pratique. Donc oui, déverrouillons, on a bien survécu de longues années sans page d'accueil verrouillée ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:16, 1 December 2013 (CET)

:::::Voilà qui est fait. Lio

== Prochaine réunion off line. ==

J'ai envoyé un mail à Sébastien pour voir si il serait d'accord de faire un workshop sur la maintenance de notre wiki pirate. Dès que j'ai une réponse, je vous en fais part. Mais nous pouvons déjà décider du jour, de l'heure et de l'enfroit pour tenir cette réunion en espérant que cela pourra lui convenir. Je ne serai malheureusement pas en Belgique si la prochaine réunion coreteam se fait le dimanche 8 décembre. On peut aussi choisir une autre lieu et une autre date il nous faut par contre un accès facile en transport en commun et un accès internet. Pourquoi pas quelque part à Louvain-la-Neuve ? Cela arrangerait la plus part des actuels membre du l'escouade en tout cas moi cela me convient parfaitement. Quelqu'un a-t-il une proposition ? --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:40, 28 November 2013 (CET)

:Malheureusement, mes examens risquent de pas mal m'occuper durant ces prochaines semaines. Je ne pourrai souffler qu'en février...
:Mais sinon, en ce qui concerne le lieu, faire une réunion à Bruxelles ou Louvain-la-Neuve est équivalent pour moi (enfin, c'est à voir au cas par cas, mais à priori...) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:37, 28 November 2013 (CET)

::Ok, ben on risque de faire sans toi dans ce cas car il serait bon que l'on prépare en live l'attelier wiki pour la prochaine AG. Si jamais tu avais des jours qui te conviennent le mieux tiens nous au courant. Lio
:::Ce n'est pas grave, du moment que vous me tenez informé ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:39, 28 November 2013 (CET)

:::: Hello,

::::Je relance sur la préparation de ce fameux atelier wiki, l'échéance approchant^^ Lio, as-tu reçu une réponse de Sébastien?

::::Personnellement, j'avais pensé faire plusieurs niveaux : un pour les néophytes et un faisant découvrir des fonctionnalités avancées.
::::Pour le niveau de base, après une mini introduction générale, on pourrait proposer un petit projet de page à réaliser et se tenir à disposition pour aider dans cette réalisation. Il faudrait sans doute au moins 2-3 personnes FR et 2-3 NL pour animer ça.

::::Des gens motivés et disponibles? Lio, tu as plus d'expérience que moi là-dedans, qu'avais-tu en tête?

::::Peut-être pourrait-on se voir rue Gérard ce dimanche en fin d'après-midi? Ou en soirée la semaine prochaine (Bxl, LLN...) Au pire, on peut s'organiser online, mais en tout cas il ne faudrait pas tarder :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:23, 2 January 2014 (CET)

:::: Je serai rue Gérard dimanche. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:40, 3 January 2014 (CET)

== SMW installé, système d'annonces ==

Voilà, je viens d'installer [[#Passons_au_s.C3.A9mantique.21|SemanticMediawiki]]! Comme première application, j'ai fait un système d'[[Annonces - Mededelingen|annonces]]. L'objectif est que n'importe quel pirate puisse de manière simple prévenir tous les autres pirates à propos de n'importe quel sujet (demande d'aide, d'information, présentation de projet etc).
Il suffit de remplir un [[Form:Announcement|formulaire]], et ça s'affiche automatiquement par ordre de dernière modification sur la [[Annonces - Mededelingen|page d'annonces]].

J'ai aussi prévu un nouveau cadre sur la [[Main Page test|page d'accueil]] qui recueillerait les toutes dernières annonces (actuellement limitées arbitrairement à 3). La différence avec la cadre "À la une" est que les annonces sont plus ponctuelles, tandis que le cadre 'À la une' devrait inclure des sujets de fond qu'on veut mettre en avant.

Si quelqu'un se sent chaud pour améliorer la présentation des annonces, c'est sur ce [[Template:Announcement query|template]] que ça se passe.

Voilà, dites-moi ce que vous en pensez :) J'écrirai une page d'aide si le système est adopté. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:37, 20 December 2013 (CET)

== Sandboxes ==

J'essaie de mettre un peu plus d'espaces sandbox disponibles et visibles. Première étape réalisée à l'instant : une fois connecté, vous avez un petit lien vers votre sandbox personnelle en haut à droite de chaque page. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:01, 4 January 2014 (CET)

== La WikiSquade pourra-t-elle se rencontrer avant l'AG pour préparer l'attelier ? ==

Il ne reste plus beaucoup de jours...

Personnelement, je suis libre demain dimanche, mercredi, jeudi et vendredi avec une préférence pour le vendredi soir si le rendez-vous est à Bruxelles.

Lio
----
:Je suis partant, Mumble a ma préférence. Je peux aussi passer à Ottignies si tu veux, Lionnel. '''[http://www.framadate.org/studs.php?sondage=yrhjlcriojzl6c4w Sondage ici pour la date]''' --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 17:50, 11 January 2014 (CET)

----
:: Oui c'est vrai, il y a aussi mumble... J'oublie souvent. Lio

----
::: Rempli :) Si on veut éviter de devoir tout boucler à la bourre, aujourd'hui semble idéal ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:10, 12 January 2014 (CET)

----
::: À propos, j'ai créé une [[Events/EGA:2014-01/Wiki_workshop|page dédiée]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 11:16, 12 January 2014 (CET)

----
::::On a toujours pas l'avis des deux autres. Je sais que Hadrien est en blocus mais quid de Rutabaga ? Je vais lui envoyer un mail. Autre chose, j'ai oublié que j'avais la garde de mon fils cette aprèm... Donc demain soir semble définitivement la meilleur solution et mumble me semble le plus adéquat. On pourrait déjà choisir ou créer de façon définitive un canal WikiPirate.be que l'on pourrait indiquer sur la page de présentation du squad. Je n'ai pas la compétence. Quelqu'un peut s'en occuper ? Lio
----
:::::Hello ! Effectivement, je suis encore en blocus, donc ne m'attendez pas pour la réunion ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:46, 12 January 2014 (CET)

----
::::: Pour créer un canal sur Mumble il nous faut les droits sur le serveur, je ne sais pas qui chez les Allemands pourrait nous donner ça. Patrick Schiffer peut-être. Mais c'est aussi bien de rester sur le channel principal (international\pirateparty belgium) à mon avis, c'est pas comme si on allait se faire squatter par un autre squad. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:04, 12 January 2014 (CET)
:::::On peut déjà débroussailler le terrain sur la page du [[WikiSquad/pad|Meeting pad]]

----

::::::Waw ! Génial de pouvoir mette un pad sur les pages wiki !!! On a vraiment tout maintenant pour pouvoir centraliser les activités écrites et les rapports d'activité verbale sur un seul site. Enfin... Lio

::::::Alors ? Ou et quand se retrouve-t-on ce soir ? Le pad ? Mumble ? Les deux à partir de 19h ça vous va ? Lio
----
:::::::"Les deux à partir de 19h" me convient :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 16:54, 13 January 2014 (CET)
----
:::::: Ah, j'avais pas vu le pad intégré ! C'est vraiment chouette ! Par contre, le chargement n'a pas l'air de fonctionner sous Firefox 26 (Linux, Opensuse 12.3). Donc peut-être faudrait-il rajouter le lien vers le pad, au cas où certains auraient des problèmes ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:15, 14 January 2014 (CET)
::::::: Vérifie que <tt>piratepad.be</tt> est autorisé à déposer des cookies tiers sur ta machine ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:57, 21 January 2014 (CET)
:::::::: Yeah, c'était ça ! Par contre, faudra penser à l'indiquer quelque part sur le wiki. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 23:07, 21 January 2014 (CET)
::::::::: Pour l'instant ça se trouve [[Help:Contents|ici]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:03, 22 January 2014 (CET)
----
J'ai terminé d'éditer les pages pour l'[[Events/EGA:2014-01/Wiki workshop|atelier]] (anti-sèches, exemples, etc). Je compte imprimer 40 anti-sèches puisqu'il y a 30 inscrits.
Aussi, je ferai un dump du wiki dans la journée pour le mettre en local sur mon pc, au cas où.
À demain! [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:31, 17 January 2014 (CET)

:Fait! Fin prêt B-) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:19, 17 January 2014 (CET)

== Suppression de compte administrateur ==

[[user:David]] alias Danid L tient à garder ses droits d'administrateur sur wiki.pirate.

----

== Prochaine réunion ==

Il y a une réunion coreteam le 16, probablement vers 13h. Ca intéresse quelqu'un de venir plus tôt et de faire une réunion wiki? J'aimerais qu'on tombe d'accord sur le layout de la page d'accueil (essentiellement la quantité d'informations affichées). --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:05, 7 February 2014 (CET)
:J'essaierai d'être présent, mais ma mi-février est assez chargée (projets à rendre, ce genre de choses) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:09, 7 February 2014 (CET)
:: D'accord pour le principe de la réunion. En plus de la mise en page de la page d'accueil, j'aimerais qu'on décide des priorités de la squad pour avoir une idée claire de la direction que vont prendre les choses. Dans cette perspective, ça me ferait plaisir qu'Hadrien puisse être présent, ça fait longtemps qu'on n'a plus pu profiter de ses insights :) Pour moi le dimanche 16 n'est pas idéal, mais si ça arrange tout le monde, j'y serai. Framadate? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:42, 8 February 2014 (CET)
::: Ah, merci Manu, ça fait plaisir ! :) Mais par contre, si réunion le 16 il y a, je crains que je ne pourrai pas venir. Mon week-end est déjà pas mal chargé... Donc je plussoie l'idée du framadate ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:49, 9 February 2014 (CET)
:::: [http://www.framadate.org/studs.php?sondage=25qhd78yr2ttgqu6 Here we go] [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:52, 10 February 2014 (CET)
:::::J'attends de pouvoir bloquer d'autres dates ce w-e avant de savoir quand je serai dispo pour la réunion. Mais j'ai discuté avec Vincent L. vendredi, et je crois que le mieux serait une réunion après le 28 février. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:09, 17 February 2014 (CET)

----

Il y a quelques success stories pour le Wiki ces derniers temps, à commencer par [[Debat_Tv/Controverse_140413|le squad controverse]], J'aimerais retravailler le [[Templates_Wiki/Empty_Squad|template de squad]] pour prendre en compte les derniers exemples. Je pense que la liste de membres d'un squad fait peur aux gens. J'ai l'impression qu'un squad anonyme peut plus facilement être rejoint par un nouveau venu.

== Extend upload file size limit to 3Mo ==

Hello, I have some pdf documents from the Pirate Lab to put on the Wiki. Two of them are a bit too large for the actual 2Mo upload limit. Is it possible to extand the limit to 3Mo so I can upload the documents ? Thanks in advance --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 07:39, 11 June 2014 (CEST)

== Sidebar, Mainpage: Resources - Tools==

J'ai ajouté dans la sidebar les outils et les ressources, je crois qu'ils sont mieux là qu'en page d'accueil.

J'aimerais donc simplifier la page d'accueil pour ne garder que la présentation du parti et les news. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:: Est-ce que les rubriques "à la une" et "à propos" ne devraient pas être inversées ? ou au moins "à la une" ne serait-il pas mieux dans la colonne de gauche --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:44, 6 August 2014 (CEST)

:: ça mettrait déjà la une en évidence sans devoir trop modifier la page --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:45, 6 August 2014 (CEST)

::: Je trouve aussi. [[Main_Page_test|Voilà ce que ça donne sur la page de test]].--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:::: Je trouve que ça donne plutôt bien. ^^ En passant, je me dis qu'on pourrait rajouter une adresse de contact, en dessous de « À propos », pour les curieux (qui pointerait vers la coaching squad, ou autre truc du même genre). 'Fin c'est surtout pour pas oublier, vu qu'on doit attendre l'AG pour ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:28, 6 August 2014 (CEST)

::::: J'aimerais que ce soit en ligne pour l'AG. Sans objection d'ici vendredi je balance le test en main page. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 18:29, 6 August 2014 (CEST)

== Sidebar, Op Squads ==

Hey! Je pensais rajouter la liste des operational squads dans la sidebar, qu'en pensez-vous ? Si l'on fait cela, il faudra créer la page wiki de la squad, et je ne sais pas si cela est nécessaire dans la mesure où chaque squad se gère comme elle le sent, si j'ai bien compris. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:41, 12 August 2014 (CEST)

----

Bonne idée. Le lien ne doit pas nécessairement être un lien vers une page wiki, on peut le faire pointer vers le drupal si c'est cette option-là qu'ils choisissent. Ceci dit, il faudra quand même mettre un peu d'ordre dans la [[Squad_List|page des squads]] --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:45, 12 August 2014 (CEST)

:Fait. Les squads Coaching, Coordination, Finance et Secretary pointent pour l'instant vers des pages inexistantes. J'attends de voir quel moyen de communication ces squads vont-elles choisir. Pour l'instant, seule la GA Squad pointe vers le site drupal.
:Pour la page listant les squads, je vais ce que je peux faire.. En attendant, je vais un peu mettre à jour la page de la coreteam. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:07, 12 August 2014 (CEST)

----

J'ai fait une refonte de la [[Squad_List|liste des squads]]. C'était un vrai bordel, et j'ai fait comme j'ai pu. J'espère que c'est suffisamment clair, à présent. Il faut encore voir quelles sont les escouades encore actives. Si quelqu'un de plus au courant que moi peut s'en charger, ce serait génial. Bonne nuit, [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:44, 14 August 2014 (CEST)

----

Pour tenir à jour la liste des pages actives, pas moyen de se passer des catégories à mon avis.
J'ai brûlé quelques étapes dans le processus de modification de la page d'accueil et j'ai ajouté un [[Template:Top_Menu|menu]] . Il contient des liens vers des pages utilisant les catégories. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:33, 21 October 2014 (CEST)
----

:Je viens d'insérer ton menu dans la page [[Mediawiki:Sitenotice]]. Le line-height est un peu différent, va savoir pourquoi. Le menu apparait donc sur toutes les pages du wiki, mais il y a deux différences:
:* Les liens des pages du menu ne se désactivent pas quand on est sur l'une d'entre-elles. Par ex, si on est sur la page des équipages, le lien n'est pas désactivé comme c'était le cas avant. M'enfin, ce n'est pas trop important je trouve.
:* Le menu apparait au dessus des titres de page, ce qui est bien je trouve.
:Dis-moi ce que t'en penses afin que j'enlève le menu sur les pages qui y sont listées. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:22, 7 November 2014 (CET)

----

:: J'ai ajouté la ligne "__ NOCACHE __" (sans espaces) sur la page [[Mediawiki:Sitenotice]], pour essayer de corriger un problème de lien non cliquable dans le topmenu. Feedback souhaité si vous rencontrez ce problème malgré tout.

----

::Je n'ai plus rencontré de problèmes, j'en induis donc que ça marche :)
::J'ai rajouté une annonce dans le Sitenotice pour la prochaine AG. Je me suis vaguement inspiré de http://wiki.pp-international.net/Main_Page --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:47, 27 November 2014 (CET)

== Calendar ==

J'aimerais implémenter: [http://semantic-mediawiki.org/w/index.php?title=Demo:Event_calendar&oldid=29851 Event calendar]

Plus simple: pomper le [http://wiki.gentilsvirus.org/index.php/Cat%C3%A9gorie:Evenements setup des gentils virus]

:Ce serait en effet plus simple d'installer le système d'agenda des gentils virus. Tu sais s'il y a une procédure d'installation (je n'en ai pas trouvé à première vue) ? Limite, on pourrait même ajouter un champ pour lier les events Fb, G+ et site drupal.
:Sinon, toujours pas de nouvelles de nos sysadmins ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:01, 5 November 2014 (CET)

----

Yo. Je viens de voir [http://video.rmll.info/videos/lagenda-du-libre-un-agenda-communautaire/ cette conférence] (25min) à propos de http://agendadulibre.be/ et je me demandais si ce ne serait pas une piste à envisager pour fédérer les évènements. Bon par contre, j'ai essayé de l'installer sur ma machine (pour tester), mais je n'y suis pas arrivé... C'est développé en Ruby, et je ne m'y connais pas trop dans ce langage. Bref, vous en pensez quoi ? On pourrait demander conseils au dev, à la limite. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:28, 18 November 2014 (CET)

----

: Je n'ai pas encore regardé ce lien, sans doute pas possible pour moi avant décembre.

: A explorer quand on a du temps: http://wiki.davical.org Dernière version stable en septembre 2012 donc pas certain que ce soit l'idéal mais je préfèrerais éliminer cette piste en connaissance de cause. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:29, 21 November 2014 (CET)

== Crews ==

Yo ! J'ai rajouté les conventions pour les catégories et les équipages : [[Help:Conventions]]. C'est en français pour l'instant, mais y a plein de place pour qu'un gentil néerlandophone traduise le tout. N'hésitez pas à rajouter/modifier des trucs si vous pensez que ça doit être amélioré.

J'ai également terminé la réorganisation des catégories concernant les équipages : [[:Category:Crew]]. J'ai mis cette page dans le [[Template:Top Menu]] de Vincent (à la place de [[:Category:Active Crews]]), car cela me semblait important d'avoir facilement à disposition la liste de tous les équipages, y compris ceux qui sont inactifs. Mais je reste ouvert aux critiques, comme toujours.

Il reste encore à rédiger une petite aide à la création des équipages. J'ai déjà écrit deux-trois lignes dans la [[:Category:Crew]]. Je crois qu'on pourrait se servir de cette base pour commencer. On peut aussi récupérer quelques morceaux de la page [[List of Crews]], avant de la supprimer à terme.

Enfin, j'ai remarqué dans mon nettoyage qu'il existe une [[Brussels Crew]] et une [[Crew Brussels]], l'une étant active, l'autre non. Ce serait sympa de clarifier tout ceci, en fusionnant les deux pages par exemple.

PS: Nous n'avons pas définit de conventions pour les pages d'aide : pluriel ou singulier ? J'ai choisi pluriel pour la page [[Help:Conventions]], mais pour la page d'aide pour les équipages, je choisirais plutôt le singulier... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:31, 5 November 2014 (CET)

----

Je préférerais que le menu n'amène que sur les crews actives. En laissant un lien vers la catégorie "crews" dans "active crew" si tu veux.

Je pense que balancer toutes les crews inactives et mortes d'entrée de jeu nous fait retomber dans les travers du wiki: un ratio signal/bruit tout pourri.

--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 16:57, 5 November 2014 (CET)

----

:Mpf. J'imagine que tu n'as pas tord. J'avoue que j'hésitais entre balancer toutes les crews pour le « nouveau » qui voudrait savoir s'il y a eu un jour de l'activité dans sa région, et n'afficher que les crews actives pour gagner en efficacité. Sinon, que penses-tu du texte d'introduction ? Pas trop long ? Je pensais expliquer en détail le concept de crew et leur fonctionnement dans la page Help:Crew(s). Mais je continue de réfléchir à tout ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:13, 6 November 2014 (CET)

----
:: Je pense que le texte explicatif a toute sa pertinence dans la page "crews", mais la page "active crew" devrait aller à l'essentiel. D'une manière générale, je garderais cette logique: un clic amène sur une page qui va à l'essentiel et un clic de plus à partir de celle-ci permet d'obtenir toute la théorie et l'historique. De cette manière on garde une navigation claire sans sacrifier la profondeur. Quelqu'un qui a de toute façon prévu de se taper toute la littérature est prêt à faire un clic de plus. Tandis que pour quelqu'un qui sait exactement ce qu'il cherche, chaque clic/scroll est une action de trop. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:29, 6 November 2014 (CET)
----
:::Ok, c'est modifié :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:43, 6 November 2014 (CET)

== Please add a description when saving a page ==

It would be a good practice for everybody, and especially if you are a member of the Wiki Squad, to add a description of the changes made to a page when saving --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:06, 7 November 2014 (CET)
----
:Apologies, but when we edit a template page, it's really difficult to see the effects without saving it...--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:52, 9 November 2014 (CET)
----
::And what about the "Show preview" button ? ^^ By the way it's a general remark. It has been triggered by your last changes but it's not limited to you --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 18:18, 9 November 2014 (CET)
----
:::Well, template parameters are very tricky, and I still have some difficulties understanding undefined parameters and parser functions. These things couldnt be tested by previewing, because I'm not really sure if the parameters' value are correct or not. Maybe I'm wrong, but as I said I'm still learning. By the way, I know it was a general remark, and I think you did well to highlight this, and you can see that we try to apply it now --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:39, 9 November 2014 (CET)

== Traductions ==

Salut. J'ai intégré le template [[Template:Bilingual]] au système d'annonce [[Annonces_-_Mededelingen]]. J'ai aussi ajouté des catégories [[:Category:A traduire]] et [[:Category:Te vertalen]] qui apparaissent quand une traduction est manquante. Mon idée est de pouvoir facilement trouver quelles pages doivent être traduites. L'idéal serait de classer les pages à traduire par date de modification et non par nom de page. On pourrait peut-être s'inspirer de la page des annonces pour faire ça ? Je me suis rendu compte que la page en question ne fait qu'afficher une catégorie selon un template. Rien de bien compliquer, je pense. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:58, 9 November 2014 (CET)

== Visual editor ==

[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil_principal Wikipedia FR] is now using the visual editor, I think we can make a few tests with [https://www.mediawiki.org/wiki/Extension:VisualEditor this module]

Edit: Even better, [https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf9 check this].
--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 20:57, 22 November 2014 (CET)

== Upgrade to Mediawiki v1.25 ==

Hi there,

I'd like to prepare the upgrade to Mediawiki version 1.25, including the visual editor.
Wanna make a meeting to discuss the topic?

Sources:

http://www.mediawiki.org/wiki/VisualEditor#Status

http://www.mediawiki.org/wiki/MediaWiki_1.25

----

:Hey Vincent. We need to do some backup before upgrading the wiki. Have you the proper access permissions ? More generally, we should list people who have ssh access, etc.
:Regarding the visual editor, it has only been released a few weeks ago. I'd like to be sure about its stability before installing anything. Maybe we should test it on a local machine ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:00, 24 November 2014 (CET)

----

:: Aye, the proper order is: (1) Make a local copy of the wiki (2) Upgrade the local copy (3) Upgrade the website. I want to get all the team informed on this project before we start, that's why I'm talking about it here. I think I have the requested access but I'm interested in your feedback. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:09, 24 November 2014 (CET)

----

:::That seems fine for me :) My view: I think the wiki needs to be upgraded and the visual seems great, but maybe still unstable. I will be back in Belgium on the 15th December, so we can do a squad meeting (more general or specific on the upgrading, you choose) from this date, unless you want to upgrade the whole thing before the GA, but I don't think so. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:27, 24 November 2014 (CET)

----

::::Good idea to have a squad meeting --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 19:58, 13 December 2014 (CET)

----

:::::Ok, I've created a framadate https://framadate.org/osqtc4wm97qtjfib (see how beautiful the new version is ! :D ). Note that I'm not really sure about my agenda, so I might change my choices later. We shall define a location, by the way. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:45, 13 December 2014 (CET)

-----

Hi ! I propose a meeting on tuesday 30th december 2014, 2pm, at LLN. Is it ok for you, Fred ? As I don't know much LLN, maybe you can suggest a location ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:00, 27 December 2014 (CET)

== Parcourir et éditer les statuts via le wiki ==

Je viens d'intégrer un nouveau bazar :) Voir la nouvelle page [[statutes]].
Quelques explications:
* Chaque article a sa propre page, de la forme <code>Statutes/Art. xx</code>. L'avantage est qu'on peut traquer l'évolution de chaque article séparément, et que ça permet toutes sortes de manips.
* Grâce à la page [[Special:RunQuery/Statutes_query]] on peut afficher juste les articles qu'on veut, dans la langue qu'on veut (l'affichage bilingue est bien synchronisé!)
* L'édition des articles peut se faire via un formulaire adéquat, pour plus de lisibilité.

Plus d'infos sur les pages [[statutes]] et [[statutes/Help]].

Par contre, je n'ai encore rempli que les 6 premiers articles sur la petite centaine... Petit boulot en perspective^^ À ce propos, quelqu'un sait où trouver la dernière version des statuts? Je ne suis tombé que sur un texte de 2013...

Voilà, j'espère que ça permettra d'éditer les statuts plus facilement et de se débarrasser du google doc :)
[[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:14, 3 January 2015 (CET)
----
:: Alors là, chapeau ! C'est juste ce qu'il fallait. Pour le reste, c'est la GA Squad qui doit remettre à jour les statuts. La dernière version est dans [https://docs.google.com/document/d/1xehdgHlPZzZgKXctedzpPxVNPZXml-Kge37UiKIVisk/edit?usp=sharing un google doc énorme qui plante les navigateurs]. Je transmets l'info à la Squad :) --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 21:35, 3 January 2015 (CET)
:: LA conversation de la squad ag est là http://pirateparty.be/statutes-pages-wiki --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 21:50, 3 January 2015 (CET)
----
::Il est fort. Il est très fort. Bon boulot! --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 23:12, 3 January 2015 (CET)
----
:: Je plussoie :-). Ca m'a l'air très bien. L'idée de n'afficher qu'une des version est très chouette, ça allège, mais l' affichage bilingue reste très clair. Je me demande juste à quoi ça va ressembler si on ajoute des notes pour pouvoir amender. Peut-on utiliser les sidenotes ? (trouvées par Hadrien). Le mieux serait de se lancer et voir à l'usage, non ? Je pense que le mieux serait que je transfère le texte moi-même depuis le google doc car comme je vais devoir proposer un "nettoyage", autant que je continue à l'assimiler... J'aurais juste besoin d'un point de contact au cas où y a besoin de chipoter au template. --[[User:Valerie|Valerie]] ([[User talk:Valerie|talk]]) 10:35, 4 January 2015 (CET)
----
::: Le plus simple est d'essayer [[Template:Sidenote]] --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 19:25, 4 January 2015 (CET)
::: Ça ne marche pas :( --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 19:29, 4 January 2015 (CET)
----
:: Bravo pour ton travail Manu ! C'est assez impressionnant!
:: Par contre, je me pose quelques questions:
::* Que se passe-t-il si on insère des points entre le 5 et le 6, par exemple ? On devra tout décaler ? Idem si on supprime un point ?
::* A-t-on une solution pour le brouillon des statuts ? L'idéal serait d'avoir deux versions des statuts : une que l'on présente aux pirates, et une autre qui est un document de travail (avec sidenotes, etc). Il suffirait ensuite de faire un merge de tout ça une fois que les discussions sont terminées. Un peu comme on a fait avec la main page test, mais en mieux. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:36, 4 January 2015 (CET)
----
::: À la limite, pour le problème des sidenotes, on peut toujours rajouter un champ pour les commentaires dans le formulaire, et on pourrait même n'afficher le contenu que pour les rédacteurs des statuts. Cependant, j'ai l'impression que ça revient à mettre du scotch pour régler le problème... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:40, 4 January 2015 (CET)
----
::@Valérie: Je t'avoue que je n'ai pas pensé qu'on ferait de l'amendement/discussion à partir de cet affichage, parce que la gestion d'amendements me semble fort compliquée (cfr. [[User:ZeFredz/AmendmentsTool|travail entamé par Fred]]). Tu peux toujours me contacter si tu as des soucis avec le template ;)

::@HgO:
::- Si on suit ce qui se fait dans les vrais textes de loi, on introduit dans ce cas des articles numérotés 5.2, 5.3, etc. Donc pas de décalage :)
::- À nouveau, le brouillonnage demandera une autre louche de réflexion :/ Perso, je ne m'attends pas à avoir du temps prochainement pour pouvoir penser à ça :( [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:32, 5 January 2015 (CET)
----
::En fait, si, je sais ce qu'il nous faut pour amender: [http://www.mediawiki.org/wiki/Extension:Annotator Annotator]. [http://annotator.wmflabs.org/wiki/Lorem_ipsum Regardez ici] et cliquez sur "view annotations" en haut à droite. C'est pas juste parfait? :D Par contre l'extension est marquée comme instable et le développement est pas super actif :( À voir... [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:46, 5 January 2015 (CET)
----
::* Annotations : Pour l'instant on fera sans les annotations (mais oui ça a l'air très bien comme extension !). De toute façon je crois que les annotations ne seront peut-être plus nécessaires. On peut aussi essayer d'utiliser l'ongle discussion. Bref, on va voir à l'usure. Je dois juste trouver le temps de commencer à copier-coller les tartines...
::* Brouilllon : oui j'avais perdu ça de vue. Mais je suppose qu'on peut simplement créer une nouvelle page avec le même template, et préciser laquelle est le brouillon, laquelle est la finale ? --[[User:Valerie|Valerie]] ([[User talk:Valerie|talk]]) 10:30, 8 January 2015 (CET)
----
::: Oui, on peut :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:52, 18 January 2015 (CET)
----
:: Granularité des statuts : je vais jouer mon rabat-joie, mais pour faciliter la maintenance des statuts, la granularité doit être au niveau des paragraphes (ou des sous-sections des articles), pas des articles eux-mêmes. Est-ce possible ? --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 12:14, 18 January 2015 (CET)
::: Bon en ait, c'est plus un problème de définir si article = chapitre ou article = sous-section d'un chapitre... on y réfléchit... --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 12:19, 18 January 2015 (CET)
----
:::: Les articles ne sont-ils pas déjà numérotés comme tels dans le google doc? Pour moi, article = entité votée comme telle à l'ag, à caractère auto-suffisant. Par exemple, l'article 5 est un gros bazar qui a été voté en un bloc, et dont les sous-sections ne font pas sens prises indépendamment (c'est plus une liste), c'est pour ça qu'il n'est pas subdivisé en plus petits morceaux. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:52, 18 January 2015 (CET)
----
::::: Oui, a priori la granularité devrait suivre les articles votés. Mais certains sont très longs, ce qui donne une très mauvaise lisibilité de front pour les deux langues... pas pratique du tout pour travailler dessus. (cf. article 5 par exemple...).
::::: Et puis, il faudrait pouvoir garder la hiérarchie de manière visible : je veux dire, savoir que (imaginons) les articles 23 à 32 sont une sous-section à propos des squads. --[[User:Valerie|Valerie]] ([[User talk:Valerie|talk]]) 16:18, 18 January 2015 (CET)
----
:::::: Pour le dernier point, j'y ai pas mal réfléchi, et finalement la solution ayant le meilleur ratio simplicité d'implémentation/résultat satisfaisant était de faire apparaître la structure sur la [[statutes|page des statuts]], chaque sous-section contenant un lien affichant précisément les articles correspondants. Tu ne trouves pas cela suffisant? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:45, 6 February 2015 (CET)

Talk:WikiSquad/Archive 1

2015-01-18T14:52:05Z

Manu: /* Parcourir et éditer les statuts via le wiki */

Talk:WikiSquad/Archive 1

2015-01-05T20:46:21Z

Manu: /* Parcourir et éditer les statuts via le wiki */

Talk:WikiSquad/Archive 1

2015-01-05T20:32:54Z

Manu: /* Parcourir et éditer les statuts via le wiki */

Talk:WikiSquad/Archive 1

2015-01-03T20:53:40Z

Manu: /* Parcourir et éditer les statuts via le wiki */ typo

Let's speak here between members of the Wikisquad about maintaining and developing the pirate wiki.

== A l'attention de [[user:Manu|Manu]] ==

Peux-tu revoir suivre mes modifications question orthographe ?

== Refonte Crew BW ==

À la [[Crew BW]], nous sommes en train de faire une [[Refonte de la page wiki bw| refonte de notre page wiki]].

Ce faisant, j'ai remarqué quelques problèmes:

* Si on stylise les titres (par ex, mettre un fond mauve comme en page d'accueil), le lien « modifier » n'apparait plus. Y a-t-il moyen de régler ça ?
* Lorsque l'on crée une sous-page (par ex [[Crew BW/Meeting Minutes]], il n'y a pas de lien vers la page parente qui se crée (alors que c'est le cas pour les sous-pages utilisateur...). Ce serait vachement chouette si on pouvait intégrer ça.

Au passage, nous avons traduit le [[Template:CrewSidebarFR| template]] pour les infos des crews (il n'était qu'en néerlandais).

Voilà, et si vous avez besoin d'aide pour la refonte du wiki général, dites-le nous !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:24, 19 October 2013 (CEST)

:Pour le problème des sous-pages, j'ai crée un [http://pirateparty.be/issues/activate-subpages-wiki ticket]. Il faut des droits d'administrateur pour pouvoir configurer ça.
:Merci pour la traduction, et oui, toute aide/initiative est la bienvenue! [[User:Manu|Manu]] ([[User talk:Manu|talk]])

::Salut [[User:HgO|HgO]], je trouve ça super ton initiative de refondre la page de ton équipage. Je viens de jetter un coup d'oeuil et je te propose d'intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. Comme tu sembles déjà avoir compris que sur un wiki, il suffit de s'inspirer de ce qui existe déjà et d'avancer par copier-coller-prévisualisation, cela ne devrait pas trop être compliqué pour toi. Pour la question de droit d'admin, il te suffit de t'inscrire dans la squad et je te les donnes. A ce propos [[User:Manu|Manu]] si tu en as besoin dis le moi. Pour les questions technique, je dois encore voir et peut-être demander à quelqu'un qui s'y connait mieux que moi... Lio
:::Merci Manu ! Pour l'aide, que puis-je faire ? J'ai l'impression qu'aucun des points listés sur la page de la squad ne sont possibles pour moi. Par ex, j'ai créé un logo avec fond transparent, mais je ne sais pas où le mettre...

::: Lio, être administrateur ne poserait pas de problème. Je ne suis pas un expert dans la gestion des wiki, mais j'apprends assez vite. De plus, j'ai vu qu'il y aura une sorte réunion ce dimanche 27/10, je passerai sans doute dire bonjour. Par contre, je n'ai pas compris ce que tu veux dire par « intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. ». C'est bien ce qu'on a fait, non ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:58, 19 October 2013 (CEST)
::::Te voilà Admin [[User:HgO|HgO]]. Si tu viens dimanche 27 ce sera parfait car un des admin de wikipédia sera normalement présent et on pourra lui poser toute les questions. Lio
::::: @HgO : Notre objectif global est de rendre le wiki beaucoup plus clair et accessible, de sorte à ce qu'on puisse trouver des infos facilement. Donc en gros, toute initiative allant dans cette direction est la bienvenue! D'ailleurs, perso, je trouve la refonte de la page BW que tu as faite vraiment nickelle dans cette optique. Si tu pouvais en faire un nouveau modèle genre 'crew frontpage', ce serait génial! Je pense aussi qu'on pourrait grandement s'en inspirer pour simplifier la page d'accueil. Si t'es chaud, fonce! :D
::::: @Lio : Oui, je veux bien les droits, ça me permettrait de pouvoir faire les choses directement au lieu d'embêter tout le monde^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]])

:::::: Merci Lio ^^
:::::: @Manu : Merci, mais je n'étais pas tout seul ^^ Pour le reste, je vais y réfléchir et j'y travaillerai sans doute le week-end prochain. Au pire, on en discute dimanche IRL :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:10, 20 October 2013 (CEST)

== List of squads and crews ==

J'ai commencé à créer des sous-catégories crews in Vlaanderen etc pour chaque région, et voulais faire de même par province, pour affiner le classement. Mais finalement, je me rends compte que d'un point de vue utilisateur, c'est nettement mieux de présenter ça sous forme de liste pour faciliter la navigation. Donc j'ai un peu laissé tomber ça pour reformer des listes de [[Crew List|crews]] et [[List of squads|squads]].
Le fait qu'elles soient hors de modèles permet aussi de simplifier leur modification par de nouveaux utilisateurs, voulant créer un nouveau groupe par exemple. Je prévois d'adapter les pages explicatives du wiki.
J'ai également changé la page d'accueil en conséquence pour limiter le nombre d'infos. [[User:Manu|Manu]] ([[User talk:Manu|talk]])

: Je viens de refondre le [[Template:CrewSidebar/sandbox|template CrewSidebar]] en fusionnant les 3 anciens modèles existants (un pour chaque langue). Dorénavant, il suffit de renseigner un attribut supplémentaire ''language=FR,NL'' pour que l'affichage se fasse dans la langue désirée. Vous trouverez un exemple d'utilisation [[Crew Leuven|ici]].
: Il y a à mon goût beaucoup trop de paramètres, mais je les ai laissés pour assurer la rétrocompatibilité.

: Avantages du nouveau template, pêle-mêle :
:* Un modèle unique pour les 3 langues.
:* Beaucoup plus de champs laissés optionnels pour ne pas surcharger l'affichage par défaut.
:* Documentation complète.
:* Catégorisation automatique des pages contenant le template.
:* Les champs ''province'' et ''ville'' sont renseignés par une propriété sémantique, ce qui permet de générer des listes automatiquement (voir [[User:Manu/sandbox]]. Ok, pas très impressionnant avec une seule crew...)

: Concernant ce dernier point, je viens de voir seulement maintenant que Vincent avait modifié la [[Crew_List|liste des équipages]]. Vincent, est-ce que tu penses que la présentation automatique en tableau comme je le propose est acceptable, ou souhaites-tu que je travaille la présentation pour garder le même affichage que le tien?

: Inconvénient :
:* Code plus complexe.
:Si personne n'a d'objection, je compte remplacer toutes les occurences des 3 anciens templates par celui-ci. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:00, 2 March 2014 (CET)

== Category tool ==

Hi every one, just take a look [[Talk:List of squads|here]] to understand how work's MediaWiki category tool and how to simplifie our wiki and reduce our work.
Lio

:Je comprends bien l'avantage des catégories : on catégorise et hop, ça apparait sur la page correspondante, pas besoin d'éditer une autre page. Mais en même temps, je pense que d'un point de vue utilisabilité, c'est assez mauvais.

:D'abord, on n'a aucune emprise sur la mise en page des pages catégories. Pour l'utilisateur final souhaitant trouver une page, tout semble morcelé, et s'il faut commencer à parcourir les sous-catégories, on n'en a pas fini de cliquer.

:Ensuite, pour quelqu'un non familier avec le wiki souhaitant créer une nouvelle crew/squad, il est plus simple de devoir ajouter un lien dans une liste, que de devoir catégoriser; ne fut-ce que parce que cette dernière action nécessite une syntaxe particulière.

:Tout ça pour dire que je ne suis pas convaincu par l'utilisation des catégories pour simplifier le wiki :) [https://fr.wikipedia.org/wiki/Aide:Liste Petit comparatif] qui à mon sens plaide en faveur des listes pour leur flexibilité.
:Ou alors, j'ai mal compris l'utilisation que tu veux en faire? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:13, 22 October 2013 (CEST)

::Je partage ton avis Manu, les catégories sont complémentaires aux listes. Je propose donc que tu tables sur les listes pendant que je m'occupe de celles-ci. Ca te vas ? Lio
:::Owkay ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:43, 23 October 2013 (CEST)

== Réunion 27/10 ==

Je devrais pouvoir passer demain pour discuter du wiki, mais un temps limité. L'atelier wiki se tient de 14h à 17h, mais je vois que sur la page de la squad, Lio a mis réunion 17h. En gros, c'est mieux que je passe quand?^^ (Hadrien tu comptes passer?) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:26, 26 October 2013 (CEST)
:Pour répondre à ta question, de 14 à 17h il sera question du wiki de wikipédia et après 17h du wiki pirate mais dans les deux cas nous parlerons du logiciel commun mediawiki. Au faite, je sais toujours pas qui va pouvoir m'ouvrir la porte avant deux heure... Lio
:: Ok, je serai là vers 17h. Mais j'ai de toute façon pas de clé pour t'ouvrir :( [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:16, 27 October 2013 (CET)
:::Ca roule ! Lio
: Yep, je viendrai vers 14h. À tout' :) [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:40, 27 October 2013 (CET)

== CrewHeader et CrewSidebar ==

J'ai créé le template pour l'header des équipages, comme discuté hier : [[Template:CrewHeader]]. J'ai tenté de le faire le plus flexible possible. Par ex, les noms des paramètres des colonnes sont row1col1, row1col2, ..., row2col3, ceci afin de ne pas imposer aux équipages le contenu des colonnes.

J'ai également amélioré le template [[Template:CrewSidebar]]. Désormais, on peut préciser les réseaux sociaux de l'équipage, et le paramètre est totalement facultatif.

J'ai appliqué mes changement dans la [[Crew BW]], n'hésitez pas à y jeter un œil ^^

Pour ce qui est de transformer les tableaux en template (par ex, faire un Template:TablePurple), je ne pense pas que ce serait possible simplement... Le mieux serait de le faire avec du css, je pense.

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:16, 28 October 2013 (CET)

== Refonte de la page d'accueil du wiki ==

Apparemment, Vincent avait déjà commencé le boulot en septembre : [[Main Page test]]. Je propose de faire nos expérimentations sur cette page. On peut aussi s'inspirer de ce qu'il avait fait.

On peut également s'inspirer des autres partis pirates. Celui des Britanniques est plein de couleurs : [http://www.pirateparty.org.uk/wiki/Main_Page]. Je trouve également intéressant le fait de mettre une liste de membres dans chaque équipage : [http://www.pirateparty.org.uk/wiki/Scotland]. Cela permet d'avoir des noms, des comptes twitter à suivre, etc. C'est important je pense lorsqu'on débarque dans un nouveau parti.

Les Français quant à eux ont gardé une structure très proche des wiki traditionnels : [http://wiki.partipirate.org/Accueil]. On remarque par exemple qu'ils affichent leurs équipages sous forme de catégorie : [http://wiki.partipirate.org/wiki/Cat%C3%A9gorie:Section_locale].

Si vous avez d'autres exemples, n'hésitez pas !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:58, 28 October 2013 (CET)

:J'aurai plus de temps jeudi pour regarder à tout cela. Juste en passant, je trouve que les multicouleurs du site britanique ou de la page test de Vincent n'apporte rien. Ca fait même un peu confus point de vue graphique je trouve. Pour le reste, je ferai jeudi quelque test sur la page de lacrew de Walcourt en fonction de mes gouts perso. Cela dit je ne vois aucun inconvénent à ce que les crew personnalisent leurs page chacune d'une manière différente. Lio

:: Selon moi, les couleurs apportent au moins deux choses :
::* une meilleure lisibilité (l'œil humain distinguant nettement plus facilement deux couleurs différentes que n'importe quel autre motif),
::* un design plus chaud et agréable, ce qui rend les gens de bonne humeur :)

:: Sinon, je suis conscient que le modèle n'est pas encore parfait, mais il reste selon moi meilleur que la page d'accueil actuelle. Quelqu'un a une objection pour reverser ces changements sur la vraie page d'accueil? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:22, 1 November 2013 (CET)

::: J'attendrais encore un peu avant de reverser les changements (on doit encore mettre les réseaux sociaux (pas urgent), et remplir la Highlight box) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:29, 1 November 2013 (CET)

== Navboxes ==

J'aimerais bien importer les navboxes de wikipedia (les boites de navigation en bas des pages) dans le wiki pirate. J'ai commencé à importer les templates, seulement, selon [http://interi.org/2012/05/wikipedias-navbox-template/ ce site], il faut également installer l'extension [https://www.mediawiki.org/wiki/Extension:ParserFunctions ParserFunctions], installer le paquet php5-tidy sur le serveur, et copier des fichiers css protégés. Tous des trucs demandant plein de droits partout, que je ne sais donc pas faire moi-même :(

:C'est Jonas qui a les droits d'accès, faudrait lui demander d'installer tout ça. Je pense que ça pourrait effectivement nous être utile. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:51, 1 November 2013 (CET)

:: J'ai fait des tests en local sur ma machine, on peut faire fonctionner les navboxes sans rien installer, sauf qu'il faut changer les fichiers Common.css et .js de Mediawiki. Ce sera donc fait dès que j'aurai les droits d'administration du wiki B-) (j'en ai déjà préparé une belle pour les assemblées générales^^) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:04, 10 November 2013 (CET)

== PageNotice ==

Je suis tombé sur le wiki du PPI hier, et je me disais que leur système pour annoncer les prochaines AG est pas mal : [http://wiki.pp-international.net/Main_Page]. Je pense que ça nécessite l'installation de l'extension [http://www.mediawiki.org/wiki/Extension:PageNotice PageNotice] (faudrait vérifier).

Vous en pensez quoi ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:54, 1 November 2013 (CET)

: Installer l'extension ne peut sûrement pas faire de tord ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:18, 1 November 2013 (CET)
:: Je l'ai installée en local pour tester. Pour info, les notices générées sont placées ''en dessous'' du titre de chaque page, et non au-dessus comme sur le site du PPI, et j'ai pas vu d'option pour changer ça. Donc ça perd un peu de son intérêt, et c'est sans doute pas la bonne extension^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:21, 17 November 2013 (CET)

::: Ah. Et ça peut-être : http://www.mediawiki.org/wiki/Manual:Interface/Sitenotice ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:42, 17 November 2013 (CET)

::: J'ai un peu mieux regardé, et apparemment y a rien à installer, juste modifier [[Mediawiki:Sitenotice]] :D (voir par ex : [http://wiki.pp-international.net/MediaWiki:Sitenotice]) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:47, 17 November 2013 (CET)

:::: Ah ben voilà, c'est ce que j'allais te répondre :P [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:39, 18 November 2013 (CET)

== Pages bilingues ==

J'ai travaillé sur des templates permettant un affichage bilingue des pages. [[How_to_:_Mise_en_page_bilingue_/_Tweetalige_opmaak|Voir la documentation]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:20, 9 November 2013 (CET)

== Bug watchlist ==

Il y a un bug lorsque l'on se trouve sur la liste de suivi : [[Special:Watchlist]].

La page apparaît puis un centième de seconde plus tard, je suis redirigé vers une page blanche.

C'est peut-être dû aux changements que tu as fait, Manu ?

: Tu as raison, c'était mystérieusement dû à du code js que j'ai ajouté. J'ai supprimé ce qui n'était pas nécessaire => tout rentre dans l'ordre :)

== SubPageList ==

@HgO : Toi qui réclamais subpage^^ : penses-tu que l'extension [http://www.mediawiki.org/wiki/Extension:SubPageList SubPageList] pourrait avoir son utilité? Je n'ai pas assez travaillé avec le wiki comme outil de crew pour pouvoir m'en rendre compte.

: Je ne suis pas certain que cela servirait, vu qu'on n'utilise qu'un niveau de hiérarchie (du style Crew/Sous-page). L'intérêt des sous-pages était qu'on puisse revenir facilement en arrière. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:49, 17 November 2013 (CET)

== Concernant la gestion de la main page... ==

Bon les gars, j'interviens avant le fiasco.

Trois possibilités :

* Soit on supprime la page test
* Soit on reporte les modifications de la vrai page sur la page test chaque fois que l'on en fait.
* Soit on ne fait plus de petites modification sur la vrai page mais uniquement des copiés collés de la page test vers la vrai page.

Je vote pour la troisième solution quel est l'avis des autres membres de l'escouade ?

Lio
:La page test nous sert encore, la deuxième option n'est pas viable sur le long terme car les deux pages vont diverger, je vote donc pour la dernière solution.

:C'est d'ailleurs ce que je proposais dans un mail. Peut-être verrouiller temporairement la page d'accueil ? Ou mettre un message en haut de la page comme quoi c'est en bêta et les modifs doivent se faire sur la page test ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:20, 17 November 2013 (CET)

:: J'ai déjà verrouiller la page vrai page d'accueil et toutes les pages qui influence ce qui apparait sur celle-ci cela signifie que seuls les utilisateurs ayant le statut d'administrateur peuvent éditer celles-ci.Lio
::: Agreed. J'ai mis un message sur la [[Talk:Main_Page|page de discussion]] de la page d’accueil. Je préfère éviter de mettre un message sur la page elle-même pour éviter de la surcharger, surtout qu'il y a un lien dans la rubrique 'À la une' qui mène ici. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:52, 18 November 2013 (CET)

== Un lien vers la WikiSquad désormais dans l'onglet WikiHelp ==

Pour faciliter notre travail et la communication entre membre de l'escouade... Lio
== Passons au sémantique! ==

Hello!

En naviguant dans les extensions de MediaWiki, je suis tombé sur [http://www.semantic-mediawiki.org/ Semantic MediaWiki]. Et y'a pas à dire, c'est de la bombe! Le meilleur moyen de voir de quoi il en retourne est de lire l'[http://semantic-mediawiki.org/wiki/Help:Editing introduction].

Je pense que dans un projet comme celui du PPBE, elle pourrait jouer un rôle essentiel. Quelques exemples :
* Plus besoin de tenir à jour des listes manuellement. [http://www.semantic-mediawiki.org/wiki/Help:Inline_queries] (vu le rôle essentiel que jouent les catégories là-dedans, je sens que Lio va aimer ;p)
* Simplification de l'utilisation de modèles (avec [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Forms])
* Création d'une propriété <nowiki>[[Needs help::]]</nowiki> pour voir en un coup d'œil les projets ayant besoin de renfort.
* Gestion de projets, de bugs, etc.
* Unleash your ideas!
Toutefois, comme il s'agit d'une grosse extension, j'aurais aimé des retours avant d'installer ça. Qui est chaud pour commencer à sémantiser le wiki? Qui souhaite en discuter en live? (en marge de la réunion coreteam du 24/11?)

:Notez que de mon point de vue il ne s'agit pas de Yet Another Tool, mais de bâtir sur ce qu'on a déjà pour simplifier ce qui se fait déjà. Pas de révolution, mais une évolution :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:28, 18 November 2013 (CET)

::Hello gentlemen, pour un tel changement, un environnement de test vous serait-il utile? Je crois pouvoir fournir ça via un serveur local chez moi. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 09:23, 25 November 2013 (CET)

:::Je suis partant pour l'idée. Malheureusement, je réagit trop tard pour la possibilité de réunion off line le 24. Mais on peut envisager une autre date. Quand à l'idée d'un environnement test je ne trouve pas cela nécessaire étant donné que MediaWiki est déjà conçu pour être évolutif sans gèner la continuité dans son utilisation courante. Mais bon en même temps je n'ai pas une conessance sufisante au niveau de la gestion de ce logiciel pour avoir une position catégorique. Maintenant que l'on est une petite équipe dans l'esquouade je vais contacter mon pot administrateur et programateur wikipédia pour voir si il ne pourrait pas nous dédiez un peu de temps pour un atelier wiki accé sur notre plateforme pirate. Je vous tiens au courant. Lio

:::: Pour info, je vais me pencher à nouveau là-dessus fin de semaine, j'aurai un ou deux jours de congé :) Hadrien m'a aussi montré ce qui se fait sur le wiki du Hackerspace, ce sera une bonne source d'inspiration. (j'ai aussi une installation en local, donc je peux faire tous les tests nécessaires avant de me lancer sur le wiki pirate ;) ) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:30, 1 December 2013 (CET)

== Attribution des droit d'administrateur à Vincent.L ==

Etant donné que Vincent a rejoint la WikiSquad, je viens de lui attribuer le statut d'administrateur. Welcome !

== Edition main page suite. ==

Je viens de faire un update de la main page test en fonction des modifications qui avaient été faite par Marrouanne et HgO...
Il en résulte donc que nos résolutions prisent concernant la gestion de ces deux pages ne fonctionne pas ou en tout cas ne sont pas respèctée.
Que fait-on ? Je vais toujour afficher un message dans le code pour informer les editeurs du passage obligé par la page test. Ou alors quoi ? On abandonne la page test ? Lio
:Pour moi la Main Page est stable à présent. Je pense que l'on peut déverrouiller la page, mais j'attends votre avis. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:22, 28 November 2013 (CET)
:: Tu veux déverouiller la page ? Sais-tu que actuellement n'importe qui peut se crée un profil sur ce wiki et la modifier par la suite ? Pour preuve voici [[user:Nimportequi|un compte]] créé après log out et qui pourra nous servir comme profil pour les administrateurs du site qui voudrait tester le comportement du site sans leurs privilèges. C'est une des raisons pour lesquels nous devons prendre des décisions par rapport à la gestion des droits d'édition et l'attribution des statuts administrateur et autres. Une réunion s'impose avant la prochaine AG pour faire des propositions concrètes concernant cette gestion avec un eventuel vote de l'assemblée pour avaliser et fixer les choses. --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:11, 28 November 2013 (CET)

:::Oui, je souhaite la déverouiller dans la mesure où l'on est tous des adultes responsables, et que l'on peut [https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Supposer_la_bonne_foi « supposer la bonne foi »]. Je ne crois pas que ce soit viable à terme de garder la page d'accueil verrouillée et de faire nos ajouts sur les deux pages (test et main). Par ex, ici j'ai rajouté l'appel à candidature pour les élections, mais il manque la traduction en néerlandais. J'aimerais que n'importe qui puisse rajouter cette traduction, ou rajouter quelque chose à la une, car on ne pourra pas penser à tout... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:38, 28 November 2013 (CET)

:::: Pour moi la seule utilité de la page test devrait être de tester un nouveau design. Passer par là pour chaque petit changement n'est clairement pas pratique. Donc oui, déverrouillons, on a bien survécu de longues années sans page d'accueil verrouillée ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:16, 1 December 2013 (CET)

:::::Voilà qui est fait. Lio

== Prochaine réunion off line. ==

J'ai envoyé un mail à Sébastien pour voir si il serait d'accord de faire un workshop sur la maintenance de notre wiki pirate. Dès que j'ai une réponse, je vous en fais part. Mais nous pouvons déjà décider du jour, de l'heure et de l'enfroit pour tenir cette réunion en espérant que cela pourra lui convenir. Je ne serai malheureusement pas en Belgique si la prochaine réunion coreteam se fait le dimanche 8 décembre. On peut aussi choisir une autre lieu et une autre date il nous faut par contre un accès facile en transport en commun et un accès internet. Pourquoi pas quelque part à Louvain-la-Neuve ? Cela arrangerait la plus part des actuels membre du l'escouade en tout cas moi cela me convient parfaitement. Quelqu'un a-t-il une proposition ? --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:40, 28 November 2013 (CET)

:Malheureusement, mes examens risquent de pas mal m'occuper durant ces prochaines semaines. Je ne pourrai souffler qu'en février...
:Mais sinon, en ce qui concerne le lieu, faire une réunion à Bruxelles ou Louvain-la-Neuve est équivalent pour moi (enfin, c'est à voir au cas par cas, mais à priori...) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:37, 28 November 2013 (CET)

::Ok, ben on risque de faire sans toi dans ce cas car il serait bon que l'on prépare en live l'attelier wiki pour la prochaine AG. Si jamais tu avais des jours qui te conviennent le mieux tiens nous au courant. Lio
:::Ce n'est pas grave, du moment que vous me tenez informé ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:39, 28 November 2013 (CET)

:::: Hello,

::::Je relance sur la préparation de ce fameux atelier wiki, l'échéance approchant^^ Lio, as-tu reçu une réponse de Sébastien?

::::Personnellement, j'avais pensé faire plusieurs niveaux : un pour les néophytes et un faisant découvrir des fonctionnalités avancées.
::::Pour le niveau de base, après une mini introduction générale, on pourrait proposer un petit projet de page à réaliser et se tenir à disposition pour aider dans cette réalisation. Il faudrait sans doute au moins 2-3 personnes FR et 2-3 NL pour animer ça.

::::Des gens motivés et disponibles? Lio, tu as plus d'expérience que moi là-dedans, qu'avais-tu en tête?

::::Peut-être pourrait-on se voir rue Gérard ce dimanche en fin d'après-midi? Ou en soirée la semaine prochaine (Bxl, LLN...) Au pire, on peut s'organiser online, mais en tout cas il ne faudrait pas tarder :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:23, 2 January 2014 (CET)

:::: Je serai rue Gérard dimanche. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:40, 3 January 2014 (CET)

== SMW installé, système d'annonces ==

Voilà, je viens d'installer [[#Passons_au_s.C3.A9mantique.21|SemanticMediawiki]]! Comme première application, j'ai fait un système d'[[Annonces - Mededelingen|annonces]]. L'objectif est que n'importe quel pirate puisse de manière simple prévenir tous les autres pirates à propos de n'importe quel sujet (demande d'aide, d'information, présentation de projet etc).
Il suffit de remplir un [[Form:Announcement|formulaire]], et ça s'affiche automatiquement par ordre de dernière modification sur la [[Annonces - Mededelingen|page d'annonces]].

J'ai aussi prévu un nouveau cadre sur la [[Main Page test|page d'accueil]] qui recueillerait les toutes dernières annonces (actuellement limitées arbitrairement à 3). La différence avec la cadre "À la une" est que les annonces sont plus ponctuelles, tandis que le cadre 'À la une' devrait inclure des sujets de fond qu'on veut mettre en avant.

Si quelqu'un se sent chaud pour améliorer la présentation des annonces, c'est sur ce [[Template:Announcement query|template]] que ça se passe.

Voilà, dites-moi ce que vous en pensez :) J'écrirai une page d'aide si le système est adopté. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:37, 20 December 2013 (CET)

== Sandboxes ==

J'essaie de mettre un peu plus d'espaces sandbox disponibles et visibles. Première étape réalisée à l'instant : une fois connecté, vous avez un petit lien vers votre sandbox personnelle en haut à droite de chaque page. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:01, 4 January 2014 (CET)

== La WikiSquade pourra-t-elle se rencontrer avant l'AG pour préparer l'attelier ? ==

Il ne reste plus beaucoup de jours...

Personnelement, je suis libre demain dimanche, mercredi, jeudi et vendredi avec une préférence pour le vendredi soir si le rendez-vous est à Bruxelles.

Lio
----
:Je suis partant, Mumble a ma préférence. Je peux aussi passer à Ottignies si tu veux, Lionnel. '''[http://www.framadate.org/studs.php?sondage=yrhjlcriojzl6c4w Sondage ici pour la date]''' --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 17:50, 11 January 2014 (CET)

----
:: Oui c'est vrai, il y a aussi mumble... J'oublie souvent. Lio

----
::: Rempli :) Si on veut éviter de devoir tout boucler à la bourre, aujourd'hui semble idéal ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:10, 12 January 2014 (CET)

----
::: À propos, j'ai créé une [[Events/EGA:2014-01/Wiki_workshop|page dédiée]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 11:16, 12 January 2014 (CET)

----
::::On a toujours pas l'avis des deux autres. Je sais que Hadrien est en blocus mais quid de Rutabaga ? Je vais lui envoyer un mail. Autre chose, j'ai oublié que j'avais la garde de mon fils cette aprèm... Donc demain soir semble définitivement la meilleur solution et mumble me semble le plus adéquat. On pourrait déjà choisir ou créer de façon définitive un canal WikiPirate.be que l'on pourrait indiquer sur la page de présentation du squad. Je n'ai pas la compétence. Quelqu'un peut s'en occuper ? Lio
----
:::::Hello ! Effectivement, je suis encore en blocus, donc ne m'attendez pas pour la réunion ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:46, 12 January 2014 (CET)

----
::::: Pour créer un canal sur Mumble il nous faut les droits sur le serveur, je ne sais pas qui chez les Allemands pourrait nous donner ça. Patrick Schiffer peut-être. Mais c'est aussi bien de rester sur le channel principal (international\pirateparty belgium) à mon avis, c'est pas comme si on allait se faire squatter par un autre squad. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:04, 12 January 2014 (CET)
:::::On peut déjà débroussailler le terrain sur la page du [[WikiSquad/pad|Meeting pad]]

----

::::::Waw ! Génial de pouvoir mette un pad sur les pages wiki !!! On a vraiment tout maintenant pour pouvoir centraliser les activités écrites et les rapports d'activité verbale sur un seul site. Enfin... Lio

::::::Alors ? Ou et quand se retrouve-t-on ce soir ? Le pad ? Mumble ? Les deux à partir de 19h ça vous va ? Lio
----
:::::::"Les deux à partir de 19h" me convient :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 16:54, 13 January 2014 (CET)
----
:::::: Ah, j'avais pas vu le pad intégré ! C'est vraiment chouette ! Par contre, le chargement n'a pas l'air de fonctionner sous Firefox 26 (Linux, Opensuse 12.3). Donc peut-être faudrait-il rajouter le lien vers le pad, au cas où certains auraient des problèmes ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:15, 14 January 2014 (CET)
::::::: Vérifie que <tt>piratepad.be</tt> est autorisé à déposer des cookies tiers sur ta machine ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:57, 21 January 2014 (CET)
:::::::: Yeah, c'était ça ! Par contre, faudra penser à l'indiquer quelque part sur le wiki. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 23:07, 21 January 2014 (CET)
::::::::: Pour l'instant ça se trouve [[Help:Contents|ici]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:03, 22 January 2014 (CET)
----
J'ai terminé d'éditer les pages pour l'[[Events/EGA:2014-01/Wiki workshop|atelier]] (anti-sèches, exemples, etc). Je compte imprimer 40 anti-sèches puisqu'il y a 30 inscrits.
Aussi, je ferai un dump du wiki dans la journée pour le mettre en local sur mon pc, au cas où.
À demain! [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:31, 17 January 2014 (CET)

:Fait! Fin prêt B-) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:19, 17 January 2014 (CET)

== Suppression de compte administrateur ==

[[user:David]] alias Danid L tient à garder ses droits d'administrateur sur wiki.pirate.

----

== Prochaine réunion ==

Il y a une réunion coreteam le 16, probablement vers 13h. Ca intéresse quelqu'un de venir plus tôt et de faire une réunion wiki? J'aimerais qu'on tombe d'accord sur le layout de la page d'accueil (essentiellement la quantité d'informations affichées). --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:05, 7 February 2014 (CET)
:J'essaierai d'être présent, mais ma mi-février est assez chargée (projets à rendre, ce genre de choses) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:09, 7 February 2014 (CET)
:: D'accord pour le principe de la réunion. En plus de la mise en page de la page d'accueil, j'aimerais qu'on décide des priorités de la squad pour avoir une idée claire de la direction que vont prendre les choses. Dans cette perspective, ça me ferait plaisir qu'Hadrien puisse être présent, ça fait longtemps qu'on n'a plus pu profiter de ses insights :) Pour moi le dimanche 16 n'est pas idéal, mais si ça arrange tout le monde, j'y serai. Framadate? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:42, 8 February 2014 (CET)
::: Ah, merci Manu, ça fait plaisir ! :) Mais par contre, si réunion le 16 il y a, je crains que je ne pourrai pas venir. Mon week-end est déjà pas mal chargé... Donc je plussoie l'idée du framadate ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:49, 9 February 2014 (CET)
:::: [http://www.framadate.org/studs.php?sondage=25qhd78yr2ttgqu6 Here we go] [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:52, 10 February 2014 (CET)
:::::J'attends de pouvoir bloquer d'autres dates ce w-e avant de savoir quand je serai dispo pour la réunion. Mais j'ai discuté avec Vincent L. vendredi, et je crois que le mieux serait une réunion après le 28 février. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:09, 17 February 2014 (CET)

----

Il y a quelques success stories pour le Wiki ces derniers temps, à commencer par [[Debat_Tv/Controverse_140413|le squad controverse]], J'aimerais retravailler le [[Templates_Wiki/Empty_Squad|template de squad]] pour prendre en compte les derniers exemples. Je pense que la liste de membres d'un squad fait peur aux gens. J'ai l'impression qu'un squad anonyme peut plus facilement être rejoint par un nouveau venu.

== Extend upload file size limit to 3Mo ==

Hello, I have some pdf documents from the Pirate Lab to put on the Wiki. Two of them are a bit too large for the actual 2Mo upload limit. Is it possible to extand the limit to 3Mo so I can upload the documents ? Thanks in advance --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 07:39, 11 June 2014 (CEST)

== Sidebar, Mainpage: Resources - Tools==

J'ai ajouté dans la sidebar les outils et les ressources, je crois qu'ils sont mieux là qu'en page d'accueil.

J'aimerais donc simplifier la page d'accueil pour ne garder que la présentation du parti et les news. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:: Est-ce que les rubriques "à la une" et "à propos" ne devraient pas être inversées ? ou au moins "à la une" ne serait-il pas mieux dans la colonne de gauche --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:44, 6 August 2014 (CEST)

:: ça mettrait déjà la une en évidence sans devoir trop modifier la page --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:45, 6 August 2014 (CEST)

::: Je trouve aussi. [[Main_Page_test|Voilà ce que ça donne sur la page de test]].--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:::: Je trouve que ça donne plutôt bien. ^^ En passant, je me dis qu'on pourrait rajouter une adresse de contact, en dessous de « À propos », pour les curieux (qui pointerait vers la coaching squad, ou autre truc du même genre). 'Fin c'est surtout pour pas oublier, vu qu'on doit attendre l'AG pour ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:28, 6 August 2014 (CEST)

::::: J'aimerais que ce soit en ligne pour l'AG. Sans objection d'ici vendredi je balance le test en main page. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 18:29, 6 August 2014 (CEST)

== Sidebar, Op Squads ==

Hey! Je pensais rajouter la liste des operational squads dans la sidebar, qu'en pensez-vous ? Si l'on fait cela, il faudra créer la page wiki de la squad, et je ne sais pas si cela est nécessaire dans la mesure où chaque squad se gère comme elle le sent, si j'ai bien compris. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:41, 12 August 2014 (CEST)

----

Bonne idée. Le lien ne doit pas nécessairement être un lien vers une page wiki, on peut le faire pointer vers le drupal si c'est cette option-là qu'ils choisissent. Ceci dit, il faudra quand même mettre un peu d'ordre dans la [[Squad_List|page des squads]] --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:45, 12 August 2014 (CEST)

:Fait. Les squads Coaching, Coordination, Finance et Secretary pointent pour l'instant vers des pages inexistantes. J'attends de voir quel moyen de communication ces squads vont-elles choisir. Pour l'instant, seule la GA Squad pointe vers le site drupal.
:Pour la page listant les squads, je vais ce que je peux faire.. En attendant, je vais un peu mettre à jour la page de la coreteam. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:07, 12 August 2014 (CEST)

----

J'ai fait une refonte de la [[Squad_List|liste des squads]]. C'était un vrai bordel, et j'ai fait comme j'ai pu. J'espère que c'est suffisamment clair, à présent. Il faut encore voir quelles sont les escouades encore actives. Si quelqu'un de plus au courant que moi peut s'en charger, ce serait génial. Bonne nuit, [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:44, 14 August 2014 (CEST)

----

Pour tenir à jour la liste des pages actives, pas moyen de se passer des catégories à mon avis.
J'ai brûlé quelques étapes dans le processus de modification de la page d'accueil et j'ai ajouté un [[Template:Top_Menu|menu]] . Il contient des liens vers des pages utilisant les catégories. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:33, 21 October 2014 (CEST)
----

:Je viens d'insérer ton menu dans la page [[Mediawiki:Sitenotice]]. Le line-height est un peu différent, va savoir pourquoi. Le menu apparait donc sur toutes les pages du wiki, mais il y a deux différences:
:* Les liens des pages du menu ne se désactivent pas quand on est sur l'une d'entre-elles. Par ex, si on est sur la page des équipages, le lien n'est pas désactivé comme c'était le cas avant. M'enfin, ce n'est pas trop important je trouve.
:* Le menu apparait au dessus des titres de page, ce qui est bien je trouve.
:Dis-moi ce que t'en penses afin que j'enlève le menu sur les pages qui y sont listées. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:22, 7 November 2014 (CET)

----

:: J'ai ajouté la ligne "__ NOCACHE __" (sans espaces) sur la page [[Mediawiki:Sitenotice]], pour essayer de corriger un problème de lien non cliquable dans le topmenu. Feedback souhaité si vous rencontrez ce problème malgré tout.

----

::Je n'ai plus rencontré de problèmes, j'en induis donc que ça marche :)
::J'ai rajouté une annonce dans le Sitenotice pour la prochaine AG. Je me suis vaguement inspiré de http://wiki.pp-international.net/Main_Page --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:47, 27 November 2014 (CET)

== Calendar ==

J'aimerais implémenter: [http://semantic-mediawiki.org/w/index.php?title=Demo:Event_calendar&oldid=29851 Event calendar]

Plus simple: pomper le [http://wiki.gentilsvirus.org/index.php/Cat%C3%A9gorie:Evenements setup des gentils virus]

:Ce serait en effet plus simple d'installer le système d'agenda des gentils virus. Tu sais s'il y a une procédure d'installation (je n'en ai pas trouvé à première vue) ? Limite, on pourrait même ajouter un champ pour lier les events Fb, G+ et site drupal.
:Sinon, toujours pas de nouvelles de nos sysadmins ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:01, 5 November 2014 (CET)

----

Yo. Je viens de voir [http://video.rmll.info/videos/lagenda-du-libre-un-agenda-communautaire/ cette conférence] (25min) à propos de http://agendadulibre.be/ et je me demandais si ce ne serait pas une piste à envisager pour fédérer les évènements. Bon par contre, j'ai essayé de l'installer sur ma machine (pour tester), mais je n'y suis pas arrivé... C'est développé en Ruby, et je ne m'y connais pas trop dans ce langage. Bref, vous en pensez quoi ? On pourrait demander conseils au dev, à la limite. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:28, 18 November 2014 (CET)

----

: Je n'ai pas encore regardé ce lien, sans doute pas possible pour moi avant décembre.

: A explorer quand on a du temps: http://wiki.davical.org Dernière version stable en septembre 2012 donc pas certain que ce soit l'idéal mais je préfèrerais éliminer cette piste en connaissance de cause. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:29, 21 November 2014 (CET)

== Crews ==

Yo ! J'ai rajouté les conventions pour les catégories et les équipages : [[Help:Conventions]]. C'est en français pour l'instant, mais y a plein de place pour qu'un gentil néerlandophone traduise le tout. N'hésitez pas à rajouter/modifier des trucs si vous pensez que ça doit être amélioré.

J'ai également terminé la réorganisation des catégories concernant les équipages : [[:Category:Crew]]. J'ai mis cette page dans le [[Template:Top Menu]] de Vincent (à la place de [[:Category:Active Crews]]), car cela me semblait important d'avoir facilement à disposition la liste de tous les équipages, y compris ceux qui sont inactifs. Mais je reste ouvert aux critiques, comme toujours.

Il reste encore à rédiger une petite aide à la création des équipages. J'ai déjà écrit deux-trois lignes dans la [[:Category:Crew]]. Je crois qu'on pourrait se servir de cette base pour commencer. On peut aussi récupérer quelques morceaux de la page [[List of Crews]], avant de la supprimer à terme.

Enfin, j'ai remarqué dans mon nettoyage qu'il existe une [[Brussels Crew]] et une [[Crew Brussels]], l'une étant active, l'autre non. Ce serait sympa de clarifier tout ceci, en fusionnant les deux pages par exemple.

PS: Nous n'avons pas définit de conventions pour les pages d'aide : pluriel ou singulier ? J'ai choisi pluriel pour la page [[Help:Conventions]], mais pour la page d'aide pour les équipages, je choisirais plutôt le singulier... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:31, 5 November 2014 (CET)

----

Je préférerais que le menu n'amène que sur les crews actives. En laissant un lien vers la catégorie "crews" dans "active crew" si tu veux.

Je pense que balancer toutes les crews inactives et mortes d'entrée de jeu nous fait retomber dans les travers du wiki: un ratio signal/bruit tout pourri.

--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 16:57, 5 November 2014 (CET)

----

:Mpf. J'imagine que tu n'as pas tord. J'avoue que j'hésitais entre balancer toutes les crews pour le « nouveau » qui voudrait savoir s'il y a eu un jour de l'activité dans sa région, et n'afficher que les crews actives pour gagner en efficacité. Sinon, que penses-tu du texte d'introduction ? Pas trop long ? Je pensais expliquer en détail le concept de crew et leur fonctionnement dans la page Help:Crew(s). Mais je continue de réfléchir à tout ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:13, 6 November 2014 (CET)

----
:: Je pense que le texte explicatif a toute sa pertinence dans la page "crews", mais la page "active crew" devrait aller à l'essentiel. D'une manière générale, je garderais cette logique: un clic amène sur une page qui va à l'essentiel et un clic de plus à partir de celle-ci permet d'obtenir toute la théorie et l'historique. De cette manière on garde une navigation claire sans sacrifier la profondeur. Quelqu'un qui a de toute façon prévu de se taper toute la littérature est prêt à faire un clic de plus. Tandis que pour quelqu'un qui sait exactement ce qu'il cherche, chaque clic/scroll est une action de trop. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:29, 6 November 2014 (CET)
----
:::Ok, c'est modifié :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:43, 6 November 2014 (CET)

== Please add a description when saving a page ==

It would be a good practice for everybody, and especially if you are a member of the Wiki Squad, to add a description of the changes made to a page when saving --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:06, 7 November 2014 (CET)
----
:Apologies, but when we edit a template page, it's really difficult to see the effects without saving it...--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:52, 9 November 2014 (CET)
----
::And what about the "Show preview" button ? ^^ By the way it's a general remark. It has been triggered by your last changes but it's not limited to you --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 18:18, 9 November 2014 (CET)
----
:::Well, template parameters are very tricky, and I still have some difficulties understanding undefined parameters and parser functions. These things couldnt be tested by previewing, because I'm not really sure if the parameters' value are correct or not. Maybe I'm wrong, but as I said I'm still learning. By the way, I know it was a general remark, and I think you did well to highlight this, and you can see that we try to apply it now --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:39, 9 November 2014 (CET)

== Traductions ==

Salut. J'ai intégré le template [[Template:Bilingual]] au système d'annonce [[Annonces_-_Mededelingen]]. J'ai aussi ajouté des catégories [[:Category:A traduire]] et [[:Category:Te vertalen]] qui apparaissent quand une traduction est manquante. Mon idée est de pouvoir facilement trouver quelles pages doivent être traduites. L'idéal serait de classer les pages à traduire par date de modification et non par nom de page. On pourrait peut-être s'inspirer de la page des annonces pour faire ça ? Je me suis rendu compte que la page en question ne fait qu'afficher une catégorie selon un template. Rien de bien compliquer, je pense. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:58, 9 November 2014 (CET)

== Visual editor ==

[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil_principal Wikipedia FR] is now using the visual editor, I think we can make a few tests with [https://www.mediawiki.org/wiki/Extension:VisualEditor this module]

Edit: Even better, [https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf9 check this].
--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 20:57, 22 November 2014 (CET)

== Upgrade to Mediawiki v1.25 ==

Hi there,

I'd like to prepare the upgrade to Mediawiki version 1.25, including the visual editor.
Wanna make a meeting to discuss the topic?

Sources:

http://www.mediawiki.org/wiki/VisualEditor#Status

http://www.mediawiki.org/wiki/MediaWiki_1.25

----

:Hey Vincent. We need to do some backup before upgrading the wiki. Have you the proper access permissions ? More generally, we should list people who have ssh access, etc.
:Regarding the visual editor, it has only been released a few weeks ago. I'd like to be sure about its stability before installing anything. Maybe we should test it on a local machine ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:00, 24 November 2014 (CET)

----

:: Aye, the proper order is: (1) Make a local copy of the wiki (2) Upgrade the local copy (3) Upgrade the website. I want to get all the team informed on this project before we start, that's why I'm talking about it here. I think I have the requested access but I'm interested in your feedback. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:09, 24 November 2014 (CET)

----

:::That seems fine for me :) My view: I think the wiki needs to be upgraded and the visual seems great, but maybe still unstable. I will be back in Belgium on the 15th December, so we can do a squad meeting (more general or specific on the upgrading, you choose) from this date, unless you want to upgrade the whole thing before the GA, but I don't think so. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:27, 24 November 2014 (CET)

----

::::Good idea to have a squad meeting --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 19:58, 13 December 2014 (CET)

----

:::::Ok, I've created a framadate https://framadate.org/osqtc4wm97qtjfib (see how beautiful the new version is ! :D ). Note that I'm not really sure about my agenda, so I might change my choices later. We shall define a location, by the way. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:45, 13 December 2014 (CET)

-----

Hi ! I propose a meeting on tuesday 30th december 2014, 2pm, at LLN. Is it ok for you, Fred ? As I don't know much LLN, maybe you can suggest a location ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:00, 27 December 2014 (CET)

== Parcourir et éditer les statuts via le wiki ==

Je viens d'intégrer un nouveau bazar :) Voir la nouvelle page [[statutes]].
Quelques explications:
* Chaque article a sa propre page, de la forme <code>Statutes/Art. xx</code>. L'avantage est qu'on peut traquer l'évolution de chaque article séparément, et que ça permet toutes sortes de manips.
* Grâce à la page [[Special:RunQuery/Statutes_query]] on peut afficher juste les articles qu'on veut, dans la langue qu'on veut (l'affichage bilingue est bien synchronisé!)
* L'édition des articles peut se faire via un formulaire adéquat, pour plus de lisibilité.

Plus d'infos sur les pages [[statutes]] et [[statutes/Help]].

Par contre, je n'ai encore rempli que les 6 premiers articles sur la petite centaine... Petit boulot en perspective^^ À ce propos, quelqu'un sait où trouver la dernière version des statuts? Je ne suis tombé que sur un texte de 2013...

Voilà, j'espère que ça permettra d'éditer les statuts plus facilement et de se débarrasser du google doc :)
[[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:14, 3 January 2015 (CET)
----
:: Alors là, chapeau ! C'est juste ce qu'il fallait. Pour le reste, c'est la GA Squad qui doit remettre à jour les statuts. La dernière version est dans [https://docs.google.com/folder/d/0B2ENMT97AP4oVTJQQ3Z2RDJPUEU/edit?pli=1&docId=0B2ENMT97AP4oUXQ5Mmt1R05XWEk un google doc énorme qui plante les navigateurs]. Je transmets l'info à la Squad :) --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 21:35, 3 January 2015 (CET)
:: LA conversation de la squad ag est là http://pirateparty.be/statutes-pages-wiki --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 21:50, 3 January 2015 (CET)

Talk:WikiSquad/Archive 1

2015-01-03T20:14:31Z

Manu: /* Parcourir et éditer les statuts via le wiki */ new section

Let's speak here between members of the Wikisquad about maintaining and developing the pirate wiki.

== A l'attention de [[user:Manu|Manu]] ==

Peux-tu revoir suivre mes modifications question orthographe ?

== Refonte Crew BW ==

À la [[Crew BW]], nous sommes en train de faire une [[Refonte de la page wiki bw| refonte de notre page wiki]].

Ce faisant, j'ai remarqué quelques problèmes:

* Si on stylise les titres (par ex, mettre un fond mauve comme en page d'accueil), le lien « modifier » n'apparait plus. Y a-t-il moyen de régler ça ?
* Lorsque l'on crée une sous-page (par ex [[Crew BW/Meeting Minutes]], il n'y a pas de lien vers la page parente qui se crée (alors que c'est le cas pour les sous-pages utilisateur...). Ce serait vachement chouette si on pouvait intégrer ça.

Au passage, nous avons traduit le [[Template:CrewSidebarFR| template]] pour les infos des crews (il n'était qu'en néerlandais).

Voilà, et si vous avez besoin d'aide pour la refonte du wiki général, dites-le nous !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:24, 19 October 2013 (CEST)

:Pour le problème des sous-pages, j'ai crée un [http://pirateparty.be/issues/activate-subpages-wiki ticket]. Il faut des droits d'administrateur pour pouvoir configurer ça.
:Merci pour la traduction, et oui, toute aide/initiative est la bienvenue! [[User:Manu|Manu]] ([[User talk:Manu|talk]])

::Salut [[User:HgO|HgO]], je trouve ça super ton initiative de refondre la page de ton équipage. Je viens de jetter un coup d'oeuil et je te propose d'intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. Comme tu sembles déjà avoir compris que sur un wiki, il suffit de s'inspirer de ce qui existe déjà et d'avancer par copier-coller-prévisualisation, cela ne devrait pas trop être compliqué pour toi. Pour la question de droit d'admin, il te suffit de t'inscrire dans la squad et je te les donnes. A ce propos [[User:Manu|Manu]] si tu en as besoin dis le moi. Pour les questions technique, je dois encore voir et peut-être demander à quelqu'un qui s'y connait mieux que moi... Lio
:::Merci Manu ! Pour l'aide, que puis-je faire ? J'ai l'impression qu'aucun des points listés sur la page de la squad ne sont possibles pour moi. Par ex, j'ai créé un logo avec fond transparent, mais je ne sais pas où le mettre...

::: Lio, être administrateur ne poserait pas de problème. Je ne suis pas un expert dans la gestion des wiki, mais j'apprends assez vite. De plus, j'ai vu qu'il y aura une sorte réunion ce dimanche 27/10, je passerai sans doute dire bonjour. Par contre, je n'ai pas compris ce que tu veux dire par « intégrer tes idées dans le [[Template:CrewSidebarFR|modèles préexistant]] de telle manière que tout le monde profite de tes idées. ». C'est bien ce qu'on a fait, non ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:58, 19 October 2013 (CEST)
::::Te voilà Admin [[User:HgO|HgO]]. Si tu viens dimanche 27 ce sera parfait car un des admin de wikipédia sera normalement présent et on pourra lui poser toute les questions. Lio
::::: @HgO : Notre objectif global est de rendre le wiki beaucoup plus clair et accessible, de sorte à ce qu'on puisse trouver des infos facilement. Donc en gros, toute initiative allant dans cette direction est la bienvenue! D'ailleurs, perso, je trouve la refonte de la page BW que tu as faite vraiment nickelle dans cette optique. Si tu pouvais en faire un nouveau modèle genre 'crew frontpage', ce serait génial! Je pense aussi qu'on pourrait grandement s'en inspirer pour simplifier la page d'accueil. Si t'es chaud, fonce! :D
::::: @Lio : Oui, je veux bien les droits, ça me permettrait de pouvoir faire les choses directement au lieu d'embêter tout le monde^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]])

:::::: Merci Lio ^^
:::::: @Manu : Merci, mais je n'étais pas tout seul ^^ Pour le reste, je vais y réfléchir et j'y travaillerai sans doute le week-end prochain. Au pire, on en discute dimanche IRL :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:10, 20 October 2013 (CEST)

== List of squads and crews ==

J'ai commencé à créer des sous-catégories crews in Vlaanderen etc pour chaque région, et voulais faire de même par province, pour affiner le classement. Mais finalement, je me rends compte que d'un point de vue utilisateur, c'est nettement mieux de présenter ça sous forme de liste pour faciliter la navigation. Donc j'ai un peu laissé tomber ça pour reformer des listes de [[Crew List|crews]] et [[List of squads|squads]].
Le fait qu'elles soient hors de modèles permet aussi de simplifier leur modification par de nouveaux utilisateurs, voulant créer un nouveau groupe par exemple. Je prévois d'adapter les pages explicatives du wiki.
J'ai également changé la page d'accueil en conséquence pour limiter le nombre d'infos. [[User:Manu|Manu]] ([[User talk:Manu|talk]])

: Je viens de refondre le [[Template:CrewSidebar/sandbox|template CrewSidebar]] en fusionnant les 3 anciens modèles existants (un pour chaque langue). Dorénavant, il suffit de renseigner un attribut supplémentaire ''language=FR,NL'' pour que l'affichage se fasse dans la langue désirée. Vous trouverez un exemple d'utilisation [[Crew Leuven|ici]].
: Il y a à mon goût beaucoup trop de paramètres, mais je les ai laissés pour assurer la rétrocompatibilité.

: Avantages du nouveau template, pêle-mêle :
:* Un modèle unique pour les 3 langues.
:* Beaucoup plus de champs laissés optionnels pour ne pas surcharger l'affichage par défaut.
:* Documentation complète.
:* Catégorisation automatique des pages contenant le template.
:* Les champs ''province'' et ''ville'' sont renseignés par une propriété sémantique, ce qui permet de générer des listes automatiquement (voir [[User:Manu/sandbox]]. Ok, pas très impressionnant avec une seule crew...)

: Concernant ce dernier point, je viens de voir seulement maintenant que Vincent avait modifié la [[Crew_List|liste des équipages]]. Vincent, est-ce que tu penses que la présentation automatique en tableau comme je le propose est acceptable, ou souhaites-tu que je travaille la présentation pour garder le même affichage que le tien?

: Inconvénient :
:* Code plus complexe.
:Si personne n'a d'objection, je compte remplacer toutes les occurences des 3 anciens templates par celui-ci. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:00, 2 March 2014 (CET)

== Category tool ==

Hi every one, just take a look [[Talk:List of squads|here]] to understand how work's MediaWiki category tool and how to simplifie our wiki and reduce our work.
Lio

:Je comprends bien l'avantage des catégories : on catégorise et hop, ça apparait sur la page correspondante, pas besoin d'éditer une autre page. Mais en même temps, je pense que d'un point de vue utilisabilité, c'est assez mauvais.

:D'abord, on n'a aucune emprise sur la mise en page des pages catégories. Pour l'utilisateur final souhaitant trouver une page, tout semble morcelé, et s'il faut commencer à parcourir les sous-catégories, on n'en a pas fini de cliquer.

:Ensuite, pour quelqu'un non familier avec le wiki souhaitant créer une nouvelle crew/squad, il est plus simple de devoir ajouter un lien dans une liste, que de devoir catégoriser; ne fut-ce que parce que cette dernière action nécessite une syntaxe particulière.

:Tout ça pour dire que je ne suis pas convaincu par l'utilisation des catégories pour simplifier le wiki :) [https://fr.wikipedia.org/wiki/Aide:Liste Petit comparatif] qui à mon sens plaide en faveur des listes pour leur flexibilité.
:Ou alors, j'ai mal compris l'utilisation que tu veux en faire? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:13, 22 October 2013 (CEST)

::Je partage ton avis Manu, les catégories sont complémentaires aux listes. Je propose donc que tu tables sur les listes pendant que je m'occupe de celles-ci. Ca te vas ? Lio
:::Owkay ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:43, 23 October 2013 (CEST)

== Réunion 27/10 ==

Je devrais pouvoir passer demain pour discuter du wiki, mais un temps limité. L'atelier wiki se tient de 14h à 17h, mais je vois que sur la page de la squad, Lio a mis réunion 17h. En gros, c'est mieux que je passe quand?^^ (Hadrien tu comptes passer?) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:26, 26 October 2013 (CEST)
:Pour répondre à ta question, de 14 à 17h il sera question du wiki de wikipédia et après 17h du wiki pirate mais dans les deux cas nous parlerons du logiciel commun mediawiki. Au faite, je sais toujours pas qui va pouvoir m'ouvrir la porte avant deux heure... Lio
:: Ok, je serai là vers 17h. Mais j'ai de toute façon pas de clé pour t'ouvrir :( [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:16, 27 October 2013 (CET)
:::Ca roule ! Lio
: Yep, je viendrai vers 14h. À tout' :) [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:40, 27 October 2013 (CET)

== CrewHeader et CrewSidebar ==

J'ai créé le template pour l'header des équipages, comme discuté hier : [[Template:CrewHeader]]. J'ai tenté de le faire le plus flexible possible. Par ex, les noms des paramètres des colonnes sont row1col1, row1col2, ..., row2col3, ceci afin de ne pas imposer aux équipages le contenu des colonnes.

J'ai également amélioré le template [[Template:CrewSidebar]]. Désormais, on peut préciser les réseaux sociaux de l'équipage, et le paramètre est totalement facultatif.

J'ai appliqué mes changement dans la [[Crew BW]], n'hésitez pas à y jeter un œil ^^

Pour ce qui est de transformer les tableaux en template (par ex, faire un Template:TablePurple), je ne pense pas que ce serait possible simplement... Le mieux serait de le faire avec du css, je pense.

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 10:16, 28 October 2013 (CET)

== Refonte de la page d'accueil du wiki ==

Apparemment, Vincent avait déjà commencé le boulot en septembre : [[Main Page test]]. Je propose de faire nos expérimentations sur cette page. On peut aussi s'inspirer de ce qu'il avait fait.

On peut également s'inspirer des autres partis pirates. Celui des Britanniques est plein de couleurs : [http://www.pirateparty.org.uk/wiki/Main_Page]. Je trouve également intéressant le fait de mettre une liste de membres dans chaque équipage : [http://www.pirateparty.org.uk/wiki/Scotland]. Cela permet d'avoir des noms, des comptes twitter à suivre, etc. C'est important je pense lorsqu'on débarque dans un nouveau parti.

Les Français quant à eux ont gardé une structure très proche des wiki traditionnels : [http://wiki.partipirate.org/Accueil]. On remarque par exemple qu'ils affichent leurs équipages sous forme de catégorie : [http://wiki.partipirate.org/wiki/Cat%C3%A9gorie:Section_locale].

Si vous avez d'autres exemples, n'hésitez pas !

--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:58, 28 October 2013 (CET)

:J'aurai plus de temps jeudi pour regarder à tout cela. Juste en passant, je trouve que les multicouleurs du site britanique ou de la page test de Vincent n'apporte rien. Ca fait même un peu confus point de vue graphique je trouve. Pour le reste, je ferai jeudi quelque test sur la page de lacrew de Walcourt en fonction de mes gouts perso. Cela dit je ne vois aucun inconvénent à ce que les crew personnalisent leurs page chacune d'une manière différente. Lio

:: Selon moi, les couleurs apportent au moins deux choses :
::* une meilleure lisibilité (l'œil humain distinguant nettement plus facilement deux couleurs différentes que n'importe quel autre motif),
::* un design plus chaud et agréable, ce qui rend les gens de bonne humeur :)

:: Sinon, je suis conscient que le modèle n'est pas encore parfait, mais il reste selon moi meilleur que la page d'accueil actuelle. Quelqu'un a une objection pour reverser ces changements sur la vraie page d'accueil? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:22, 1 November 2013 (CET)

::: J'attendrais encore un peu avant de reverser les changements (on doit encore mettre les réseaux sociaux (pas urgent), et remplir la Highlight box) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:29, 1 November 2013 (CET)

== Navboxes ==

J'aimerais bien importer les navboxes de wikipedia (les boites de navigation en bas des pages) dans le wiki pirate. J'ai commencé à importer les templates, seulement, selon [http://interi.org/2012/05/wikipedias-navbox-template/ ce site], il faut également installer l'extension [https://www.mediawiki.org/wiki/Extension:ParserFunctions ParserFunctions], installer le paquet php5-tidy sur le serveur, et copier des fichiers css protégés. Tous des trucs demandant plein de droits partout, que je ne sais donc pas faire moi-même :(

:C'est Jonas qui a les droits d'accès, faudrait lui demander d'installer tout ça. Je pense que ça pourrait effectivement nous être utile. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:51, 1 November 2013 (CET)

:: J'ai fait des tests en local sur ma machine, on peut faire fonctionner les navboxes sans rien installer, sauf qu'il faut changer les fichiers Common.css et .js de Mediawiki. Ce sera donc fait dès que j'aurai les droits d'administration du wiki B-) (j'en ai déjà préparé une belle pour les assemblées générales^^) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 20:04, 10 November 2013 (CET)

== PageNotice ==

Je suis tombé sur le wiki du PPI hier, et je me disais que leur système pour annoncer les prochaines AG est pas mal : [http://wiki.pp-international.net/Main_Page]. Je pense que ça nécessite l'installation de l'extension [http://www.mediawiki.org/wiki/Extension:PageNotice PageNotice] (faudrait vérifier).

Vous en pensez quoi ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:54, 1 November 2013 (CET)

: Installer l'extension ne peut sûrement pas faire de tord ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:18, 1 November 2013 (CET)
:: Je l'ai installée en local pour tester. Pour info, les notices générées sont placées ''en dessous'' du titre de chaque page, et non au-dessus comme sur le site du PPI, et j'ai pas vu d'option pour changer ça. Donc ça perd un peu de son intérêt, et c'est sans doute pas la bonne extension^^ [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:21, 17 November 2013 (CET)

::: Ah. Et ça peut-être : http://www.mediawiki.org/wiki/Manual:Interface/Sitenotice ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:42, 17 November 2013 (CET)

::: J'ai un peu mieux regardé, et apparemment y a rien à installer, juste modifier [[Mediawiki:Sitenotice]] :D (voir par ex : [http://wiki.pp-international.net/MediaWiki:Sitenotice]) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:47, 17 November 2013 (CET)

:::: Ah ben voilà, c'est ce que j'allais te répondre :P [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:39, 18 November 2013 (CET)

== Pages bilingues ==

J'ai travaillé sur des templates permettant un affichage bilingue des pages. [[How_to_:_Mise_en_page_bilingue_/_Tweetalige_opmaak|Voir la documentation]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:20, 9 November 2013 (CET)

== Bug watchlist ==

Il y a un bug lorsque l'on se trouve sur la liste de suivi : [[Special:Watchlist]].

La page apparaît puis un centième de seconde plus tard, je suis redirigé vers une page blanche.

C'est peut-être dû aux changements que tu as fait, Manu ?

: Tu as raison, c'était mystérieusement dû à du code js que j'ai ajouté. J'ai supprimé ce qui n'était pas nécessaire => tout rentre dans l'ordre :)

== SubPageList ==

@HgO : Toi qui réclamais subpage^^ : penses-tu que l'extension [http://www.mediawiki.org/wiki/Extension:SubPageList SubPageList] pourrait avoir son utilité? Je n'ai pas assez travaillé avec le wiki comme outil de crew pour pouvoir m'en rendre compte.

: Je ne suis pas certain que cela servirait, vu qu'on n'utilise qu'un niveau de hiérarchie (du style Crew/Sous-page). L'intérêt des sous-pages était qu'on puisse revenir facilement en arrière. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:49, 17 November 2013 (CET)

== Concernant la gestion de la main page... ==

Bon les gars, j'interviens avant le fiasco.

Trois possibilités :

* Soit on supprime la page test
* Soit on reporte les modifications de la vrai page sur la page test chaque fois que l'on en fait.
* Soit on ne fait plus de petites modification sur la vrai page mais uniquement des copiés collés de la page test vers la vrai page.

Je vote pour la troisième solution quel est l'avis des autres membres de l'escouade ?

Lio
:La page test nous sert encore, la deuxième option n'est pas viable sur le long terme car les deux pages vont diverger, je vote donc pour la dernière solution.

:C'est d'ailleurs ce que je proposais dans un mail. Peut-être verrouiller temporairement la page d'accueil ? Ou mettre un message en haut de la page comme quoi c'est en bêta et les modifs doivent se faire sur la page test ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:20, 17 November 2013 (CET)

:: J'ai déjà verrouiller la page vrai page d'accueil et toutes les pages qui influence ce qui apparait sur celle-ci cela signifie que seuls les utilisateurs ayant le statut d'administrateur peuvent éditer celles-ci.Lio
::: Agreed. J'ai mis un message sur la [[Talk:Main_Page|page de discussion]] de la page d’accueil. Je préfère éviter de mettre un message sur la page elle-même pour éviter de la surcharger, surtout qu'il y a un lien dans la rubrique 'À la une' qui mène ici. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 19:52, 18 November 2013 (CET)

== Un lien vers la WikiSquad désormais dans l'onglet WikiHelp ==

Pour faciliter notre travail et la communication entre membre de l'escouade... Lio
== Passons au sémantique! ==

Hello!

En naviguant dans les extensions de MediaWiki, je suis tombé sur [http://www.semantic-mediawiki.org/ Semantic MediaWiki]. Et y'a pas à dire, c'est de la bombe! Le meilleur moyen de voir de quoi il en retourne est de lire l'[http://semantic-mediawiki.org/wiki/Help:Editing introduction].

Je pense que dans un projet comme celui du PPBE, elle pourrait jouer un rôle essentiel. Quelques exemples :
* Plus besoin de tenir à jour des listes manuellement. [http://www.semantic-mediawiki.org/wiki/Help:Inline_queries] (vu le rôle essentiel que jouent les catégories là-dedans, je sens que Lio va aimer ;p)
* Simplification de l'utilisation de modèles (avec [http://www.mediawiki.org/wiki/Extension:Semantic_Forms Semantic Forms])
* Création d'une propriété <nowiki>[[Needs help::]]</nowiki> pour voir en un coup d'œil les projets ayant besoin de renfort.
* Gestion de projets, de bugs, etc.
* Unleash your ideas!
Toutefois, comme il s'agit d'une grosse extension, j'aurais aimé des retours avant d'installer ça. Qui est chaud pour commencer à sémantiser le wiki? Qui souhaite en discuter en live? (en marge de la réunion coreteam du 24/11?)

:Notez que de mon point de vue il ne s'agit pas de Yet Another Tool, mais de bâtir sur ce qu'on a déjà pour simplifier ce qui se fait déjà. Pas de révolution, mais une évolution :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:28, 18 November 2013 (CET)

::Hello gentlemen, pour un tel changement, un environnement de test vous serait-il utile? Je crois pouvoir fournir ça via un serveur local chez moi. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 09:23, 25 November 2013 (CET)

:::Je suis partant pour l'idée. Malheureusement, je réagit trop tard pour la possibilité de réunion off line le 24. Mais on peut envisager une autre date. Quand à l'idée d'un environnement test je ne trouve pas cela nécessaire étant donné que MediaWiki est déjà conçu pour être évolutif sans gèner la continuité dans son utilisation courante. Mais bon en même temps je n'ai pas une conessance sufisante au niveau de la gestion de ce logiciel pour avoir une position catégorique. Maintenant que l'on est une petite équipe dans l'esquouade je vais contacter mon pot administrateur et programateur wikipédia pour voir si il ne pourrait pas nous dédiez un peu de temps pour un atelier wiki accé sur notre plateforme pirate. Je vous tiens au courant. Lio

:::: Pour info, je vais me pencher à nouveau là-dessus fin de semaine, j'aurai un ou deux jours de congé :) Hadrien m'a aussi montré ce qui se fait sur le wiki du Hackerspace, ce sera une bonne source d'inspiration. (j'ai aussi une installation en local, donc je peux faire tous les tests nécessaires avant de me lancer sur le wiki pirate ;) ) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:30, 1 December 2013 (CET)

== Attribution des droit d'administrateur à Vincent.L ==

Etant donné que Vincent a rejoint la WikiSquad, je viens de lui attribuer le statut d'administrateur. Welcome !

== Edition main page suite. ==

Je viens de faire un update de la main page test en fonction des modifications qui avaient été faite par Marrouanne et HgO...
Il en résulte donc que nos résolutions prisent concernant la gestion de ces deux pages ne fonctionne pas ou en tout cas ne sont pas respèctée.
Que fait-on ? Je vais toujour afficher un message dans le code pour informer les editeurs du passage obligé par la page test. Ou alors quoi ? On abandonne la page test ? Lio
:Pour moi la Main Page est stable à présent. Je pense que l'on peut déverrouiller la page, mais j'attends votre avis. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:22, 28 November 2013 (CET)
:: Tu veux déverouiller la page ? Sais-tu que actuellement n'importe qui peut se crée un profil sur ce wiki et la modifier par la suite ? Pour preuve voici [[user:Nimportequi|un compte]] créé après log out et qui pourra nous servir comme profil pour les administrateurs du site qui voudrait tester le comportement du site sans leurs privilèges. C'est une des raisons pour lesquels nous devons prendre des décisions par rapport à la gestion des droits d'édition et l'attribution des statuts administrateur et autres. Une réunion s'impose avant la prochaine AG pour faire des propositions concrètes concernant cette gestion avec un eventuel vote de l'assemblée pour avaliser et fixer les choses. --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:11, 28 November 2013 (CET)

:::Oui, je souhaite la déverouiller dans la mesure où l'on est tous des adultes responsables, et que l'on peut [https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Supposer_la_bonne_foi « supposer la bonne foi »]. Je ne crois pas que ce soit viable à terme de garder la page d'accueil verrouillée et de faire nos ajouts sur les deux pages (test et main). Par ex, ici j'ai rajouté l'appel à candidature pour les élections, mais il manque la traduction en néerlandais. J'aimerais que n'importe qui puisse rajouter cette traduction, ou rajouter quelque chose à la une, car on ne pourra pas penser à tout... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:38, 28 November 2013 (CET)

:::: Pour moi la seule utilité de la page test devrait être de tester un nouveau design. Passer par là pour chaque petit changement n'est clairement pas pratique. Donc oui, déverrouillons, on a bien survécu de longues années sans page d'accueil verrouillée ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:16, 1 December 2013 (CET)

:::::Voilà qui est fait. Lio

== Prochaine réunion off line. ==

J'ai envoyé un mail à Sébastien pour voir si il serait d'accord de faire un workshop sur la maintenance de notre wiki pirate. Dès que j'ai une réponse, je vous en fais part. Mais nous pouvons déjà décider du jour, de l'heure et de l'enfroit pour tenir cette réunion en espérant que cela pourra lui convenir. Je ne serai malheureusement pas en Belgique si la prochaine réunion coreteam se fait le dimanche 8 décembre. On peut aussi choisir une autre lieu et une autre date il nous faut par contre un accès facile en transport en commun et un accès internet. Pourquoi pas quelque part à Louvain-la-Neuve ? Cela arrangerait la plus part des actuels membre du l'escouade en tout cas moi cela me convient parfaitement. Quelqu'un a-t-il une proposition ? --[[User:Nimportequi|Nimportequi]] ([[User talk:Nimportequi|talk]]) 12:40, 28 November 2013 (CET)

:Malheureusement, mes examens risquent de pas mal m'occuper durant ces prochaines semaines. Je ne pourrai souffler qu'en février...
:Mais sinon, en ce qui concerne le lieu, faire une réunion à Bruxelles ou Louvain-la-Neuve est équivalent pour moi (enfin, c'est à voir au cas par cas, mais à priori...) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:37, 28 November 2013 (CET)

::Ok, ben on risque de faire sans toi dans ce cas car il serait bon que l'on prépare en live l'attelier wiki pour la prochaine AG. Si jamais tu avais des jours qui te conviennent le mieux tiens nous au courant. Lio
:::Ce n'est pas grave, du moment que vous me tenez informé ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:39, 28 November 2013 (CET)

:::: Hello,

::::Je relance sur la préparation de ce fameux atelier wiki, l'échéance approchant^^ Lio, as-tu reçu une réponse de Sébastien?

::::Personnellement, j'avais pensé faire plusieurs niveaux : un pour les néophytes et un faisant découvrir des fonctionnalités avancées.
::::Pour le niveau de base, après une mini introduction générale, on pourrait proposer un petit projet de page à réaliser et se tenir à disposition pour aider dans cette réalisation. Il faudrait sans doute au moins 2-3 personnes FR et 2-3 NL pour animer ça.

::::Des gens motivés et disponibles? Lio, tu as plus d'expérience que moi là-dedans, qu'avais-tu en tête?

::::Peut-être pourrait-on se voir rue Gérard ce dimanche en fin d'après-midi? Ou en soirée la semaine prochaine (Bxl, LLN...) Au pire, on peut s'organiser online, mais en tout cas il ne faudrait pas tarder :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 14:23, 2 January 2014 (CET)

:::: Je serai rue Gérard dimanche. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:40, 3 January 2014 (CET)

== SMW installé, système d'annonces ==

Voilà, je viens d'installer [[#Passons_au_s.C3.A9mantique.21|SemanticMediawiki]]! Comme première application, j'ai fait un système d'[[Annonces - Mededelingen|annonces]]. L'objectif est que n'importe quel pirate puisse de manière simple prévenir tous les autres pirates à propos de n'importe quel sujet (demande d'aide, d'information, présentation de projet etc).
Il suffit de remplir un [[Form:Announcement|formulaire]], et ça s'affiche automatiquement par ordre de dernière modification sur la [[Annonces - Mededelingen|page d'annonces]].

J'ai aussi prévu un nouveau cadre sur la [[Main Page test|page d'accueil]] qui recueillerait les toutes dernières annonces (actuellement limitées arbitrairement à 3). La différence avec la cadre "À la une" est que les annonces sont plus ponctuelles, tandis que le cadre 'À la une' devrait inclure des sujets de fond qu'on veut mettre en avant.

Si quelqu'un se sent chaud pour améliorer la présentation des annonces, c'est sur ce [[Template:Announcement query|template]] que ça se passe.

Voilà, dites-moi ce que vous en pensez :) J'écrirai une page d'aide si le système est adopté. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:37, 20 December 2013 (CET)

== Sandboxes ==

J'essaie de mettre un peu plus d'espaces sandbox disponibles et visibles. Première étape réalisée à l'instant : une fois connecté, vous avez un petit lien vers votre sandbox personnelle en haut à droite de chaque page. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:01, 4 January 2014 (CET)

== La WikiSquade pourra-t-elle se rencontrer avant l'AG pour préparer l'attelier ? ==

Il ne reste plus beaucoup de jours...

Personnelement, je suis libre demain dimanche, mercredi, jeudi et vendredi avec une préférence pour le vendredi soir si le rendez-vous est à Bruxelles.

Lio
----
:Je suis partant, Mumble a ma préférence. Je peux aussi passer à Ottignies si tu veux, Lionnel. '''[http://www.framadate.org/studs.php?sondage=yrhjlcriojzl6c4w Sondage ici pour la date]''' --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 17:50, 11 January 2014 (CET)

----
:: Oui c'est vrai, il y a aussi mumble... J'oublie souvent. Lio

----
::: Rempli :) Si on veut éviter de devoir tout boucler à la bourre, aujourd'hui semble idéal ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:10, 12 January 2014 (CET)

----
::: À propos, j'ai créé une [[Events/EGA:2014-01/Wiki_workshop|page dédiée]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 11:16, 12 January 2014 (CET)

----
::::On a toujours pas l'avis des deux autres. Je sais que Hadrien est en blocus mais quid de Rutabaga ? Je vais lui envoyer un mail. Autre chose, j'ai oublié que j'avais la garde de mon fils cette aprèm... Donc demain soir semble définitivement la meilleur solution et mumble me semble le plus adéquat. On pourrait déjà choisir ou créer de façon définitive un canal WikiPirate.be que l'on pourrait indiquer sur la page de présentation du squad. Je n'ai pas la compétence. Quelqu'un peut s'en occuper ? Lio
----
:::::Hello ! Effectivement, je suis encore en blocus, donc ne m'attendez pas pour la réunion ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:46, 12 January 2014 (CET)

----
::::: Pour créer un canal sur Mumble il nous faut les droits sur le serveur, je ne sais pas qui chez les Allemands pourrait nous donner ça. Patrick Schiffer peut-être. Mais c'est aussi bien de rester sur le channel principal (international\pirateparty belgium) à mon avis, c'est pas comme si on allait se faire squatter par un autre squad. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:04, 12 January 2014 (CET)
:::::On peut déjà débroussailler le terrain sur la page du [[WikiSquad/pad|Meeting pad]]

----

::::::Waw ! Génial de pouvoir mette un pad sur les pages wiki !!! On a vraiment tout maintenant pour pouvoir centraliser les activités écrites et les rapports d'activité verbale sur un seul site. Enfin... Lio

::::::Alors ? Ou et quand se retrouve-t-on ce soir ? Le pad ? Mumble ? Les deux à partir de 19h ça vous va ? Lio
----
:::::::"Les deux à partir de 19h" me convient :) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 16:54, 13 January 2014 (CET)
----
:::::: Ah, j'avais pas vu le pad intégré ! C'est vraiment chouette ! Par contre, le chargement n'a pas l'air de fonctionner sous Firefox 26 (Linux, Opensuse 12.3). Donc peut-être faudrait-il rajouter le lien vers le pad, au cas où certains auraient des problèmes ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 11:15, 14 January 2014 (CET)
::::::: Vérifie que <tt>piratepad.be</tt> est autorisé à déposer des cookies tiers sur ta machine ;) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 22:57, 21 January 2014 (CET)
:::::::: Yeah, c'était ça ! Par contre, faudra penser à l'indiquer quelque part sur le wiki. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 23:07, 21 January 2014 (CET)
::::::::: Pour l'instant ça se trouve [[Help:Contents|ici]]. [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 10:03, 22 January 2014 (CET)
----
J'ai terminé d'éditer les pages pour l'[[Events/EGA:2014-01/Wiki workshop|atelier]] (anti-sèches, exemples, etc). Je compte imprimer 40 anti-sèches puisqu'il y a 30 inscrits.
Aussi, je ferai un dump du wiki dans la journée pour le mettre en local sur mon pc, au cas où.
À demain! [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 13:31, 17 January 2014 (CET)

:Fait! Fin prêt B-) [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 17:19, 17 January 2014 (CET)

== Suppression de compte administrateur ==

[[user:David]] alias Danid L tient à garder ses droits d'administrateur sur wiki.pirate.

----

== Prochaine réunion ==

Il y a une réunion coreteam le 16, probablement vers 13h. Ca intéresse quelqu'un de venir plus tôt et de faire une réunion wiki? J'aimerais qu'on tombe d'accord sur le layout de la page d'accueil (essentiellement la quantité d'informations affichées). --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:05, 7 February 2014 (CET)
:J'essaierai d'être présent, mais ma mi-février est assez chargée (projets à rendre, ce genre de choses) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:09, 7 February 2014 (CET)
:: D'accord pour le principe de la réunion. En plus de la mise en page de la page d'accueil, j'aimerais qu'on décide des priorités de la squad pour avoir une idée claire de la direction que vont prendre les choses. Dans cette perspective, ça me ferait plaisir qu'Hadrien puisse être présent, ça fait longtemps qu'on n'a plus pu profiter de ses insights :) Pour moi le dimanche 16 n'est pas idéal, mais si ça arrange tout le monde, j'y serai. Framadate? [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:42, 8 February 2014 (CET)
::: Ah, merci Manu, ça fait plaisir ! :) Mais par contre, si réunion le 16 il y a, je crains que je ne pourrai pas venir. Mon week-end est déjà pas mal chargé... Donc je plussoie l'idée du framadate ^^ --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:49, 9 February 2014 (CET)
:::: [http://www.framadate.org/studs.php?sondage=25qhd78yr2ttgqu6 Here we go] [[User:Manu|Manu]] ([[User talk:Manu|talk]]) 15:52, 10 February 2014 (CET)
:::::J'attends de pouvoir bloquer d'autres dates ce w-e avant de savoir quand je serai dispo pour la réunion. Mais j'ai discuté avec Vincent L. vendredi, et je crois que le mieux serait une réunion après le 28 février. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:09, 17 February 2014 (CET)

----

Il y a quelques success stories pour le Wiki ces derniers temps, à commencer par [[Debat_Tv/Controverse_140413|le squad controverse]], J'aimerais retravailler le [[Templates_Wiki/Empty_Squad|template de squad]] pour prendre en compte les derniers exemples. Je pense que la liste de membres d'un squad fait peur aux gens. J'ai l'impression qu'un squad anonyme peut plus facilement être rejoint par un nouveau venu.

== Extend upload file size limit to 3Mo ==

Hello, I have some pdf documents from the Pirate Lab to put on the Wiki. Two of them are a bit too large for the actual 2Mo upload limit. Is it possible to extand the limit to 3Mo so I can upload the documents ? Thanks in advance --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 07:39, 11 June 2014 (CEST)

== Sidebar, Mainpage: Resources - Tools==

J'ai ajouté dans la sidebar les outils et les ressources, je crois qu'ils sont mieux là qu'en page d'accueil.

J'aimerais donc simplifier la page d'accueil pour ne garder que la présentation du parti et les news. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:: Est-ce que les rubriques "à la une" et "à propos" ne devraient pas être inversées ? ou au moins "à la une" ne serait-il pas mieux dans la colonne de gauche --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:44, 6 August 2014 (CEST)

:: ça mettrait déjà la une en évidence sans devoir trop modifier la page --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:45, 6 August 2014 (CEST)

::: Je trouve aussi. [[Main_Page_test|Voilà ce que ça donne sur la page de test]].--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:42, 6 August 2014 (CEST)

:::: Je trouve que ça donne plutôt bien. ^^ En passant, je me dis qu'on pourrait rajouter une adresse de contact, en dessous de « À propos », pour les curieux (qui pointerait vers la coaching squad, ou autre truc du même genre). 'Fin c'est surtout pour pas oublier, vu qu'on doit attendre l'AG pour ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 17:28, 6 August 2014 (CEST)

::::: J'aimerais que ce soit en ligne pour l'AG. Sans objection d'ici vendredi je balance le test en main page. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 18:29, 6 August 2014 (CEST)

== Sidebar, Op Squads ==

Hey! Je pensais rajouter la liste des operational squads dans la sidebar, qu'en pensez-vous ? Si l'on fait cela, il faudra créer la page wiki de la squad, et je ne sais pas si cela est nécessaire dans la mesure où chaque squad se gère comme elle le sent, si j'ai bien compris. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:41, 12 August 2014 (CEST)

----

Bonne idée. Le lien ne doit pas nécessairement être un lien vers une page wiki, on peut le faire pointer vers le drupal si c'est cette option-là qu'ils choisissent. Ceci dit, il faudra quand même mettre un peu d'ordre dans la [[Squad_List|page des squads]] --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 15:45, 12 August 2014 (CEST)

:Fait. Les squads Coaching, Coordination, Finance et Secretary pointent pour l'instant vers des pages inexistantes. J'attends de voir quel moyen de communication ces squads vont-elles choisir. Pour l'instant, seule la GA Squad pointe vers le site drupal.
:Pour la page listant les squads, je vais ce que je peux faire.. En attendant, je vais un peu mettre à jour la page de la coreteam. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:07, 12 August 2014 (CEST)

----

J'ai fait une refonte de la [[Squad_List|liste des squads]]. C'était un vrai bordel, et j'ai fait comme j'ai pu. J'espère que c'est suffisamment clair, à présent. Il faut encore voir quelles sont les escouades encore actives. Si quelqu'un de plus au courant que moi peut s'en charger, ce serait génial. Bonne nuit, [[User:HgO|HgO]] ([[User talk:HgO|talk]]) 00:44, 14 August 2014 (CEST)

----

Pour tenir à jour la liste des pages actives, pas moyen de se passer des catégories à mon avis.
J'ai brûlé quelques étapes dans le processus de modification de la page d'accueil et j'ai ajouté un [[Template:Top_Menu|menu]] . Il contient des liens vers des pages utilisant les catégories. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:33, 21 October 2014 (CEST)
----

:Je viens d'insérer ton menu dans la page [[Mediawiki:Sitenotice]]. Le line-height est un peu différent, va savoir pourquoi. Le menu apparait donc sur toutes les pages du wiki, mais il y a deux différences:
:* Les liens des pages du menu ne se désactivent pas quand on est sur l'une d'entre-elles. Par ex, si on est sur la page des équipages, le lien n'est pas désactivé comme c'était le cas avant. M'enfin, ce n'est pas trop important je trouve.
:* Le menu apparait au dessus des titres de page, ce qui est bien je trouve.
:Dis-moi ce que t'en penses afin que j'enlève le menu sur les pages qui y sont listées. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:22, 7 November 2014 (CET)

----

:: J'ai ajouté la ligne "__ NOCACHE __" (sans espaces) sur la page [[Mediawiki:Sitenotice]], pour essayer de corriger un problème de lien non cliquable dans le topmenu. Feedback souhaité si vous rencontrez ce problème malgré tout.

----

::Je n'ai plus rencontré de problèmes, j'en induis donc que ça marche :)
::J'ai rajouté une annonce dans le Sitenotice pour la prochaine AG. Je me suis vaguement inspiré de http://wiki.pp-international.net/Main_Page --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 14:47, 27 November 2014 (CET)

== Calendar ==

J'aimerais implémenter: [http://semantic-mediawiki.org/w/index.php?title=Demo:Event_calendar&oldid=29851 Event calendar]

Plus simple: pomper le [http://wiki.gentilsvirus.org/index.php/Cat%C3%A9gorie:Evenements setup des gentils virus]

:Ce serait en effet plus simple d'installer le système d'agenda des gentils virus. Tu sais s'il y a une procédure d'installation (je n'en ai pas trouvé à première vue) ? Limite, on pourrait même ajouter un champ pour lier les events Fb, G+ et site drupal.
:Sinon, toujours pas de nouvelles de nos sysadmins ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:01, 5 November 2014 (CET)

----

Yo. Je viens de voir [http://video.rmll.info/videos/lagenda-du-libre-un-agenda-communautaire/ cette conférence] (25min) à propos de http://agendadulibre.be/ et je me demandais si ce ne serait pas une piste à envisager pour fédérer les évènements. Bon par contre, j'ai essayé de l'installer sur ma machine (pour tester), mais je n'y suis pas arrivé... C'est développé en Ruby, et je ne m'y connais pas trop dans ce langage. Bref, vous en pensez quoi ? On pourrait demander conseils au dev, à la limite. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:28, 18 November 2014 (CET)

----

: Je n'ai pas encore regardé ce lien, sans doute pas possible pour moi avant décembre.

: A explorer quand on a du temps: http://wiki.davical.org Dernière version stable en septembre 2012 donc pas certain que ce soit l'idéal mais je préfèrerais éliminer cette piste en connaissance de cause. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 12:29, 21 November 2014 (CET)

== Crews ==

Yo ! J'ai rajouté les conventions pour les catégories et les équipages : [[Help:Conventions]]. C'est en français pour l'instant, mais y a plein de place pour qu'un gentil néerlandophone traduise le tout. N'hésitez pas à rajouter/modifier des trucs si vous pensez que ça doit être amélioré.

J'ai également terminé la réorganisation des catégories concernant les équipages : [[:Category:Crew]]. J'ai mis cette page dans le [[Template:Top Menu]] de Vincent (à la place de [[:Category:Active Crews]]), car cela me semblait important d'avoir facilement à disposition la liste de tous les équipages, y compris ceux qui sont inactifs. Mais je reste ouvert aux critiques, comme toujours.

Il reste encore à rédiger une petite aide à la création des équipages. J'ai déjà écrit deux-trois lignes dans la [[:Category:Crew]]. Je crois qu'on pourrait se servir de cette base pour commencer. On peut aussi récupérer quelques morceaux de la page [[List of Crews]], avant de la supprimer à terme.

Enfin, j'ai remarqué dans mon nettoyage qu'il existe une [[Brussels Crew]] et une [[Crew Brussels]], l'une étant active, l'autre non. Ce serait sympa de clarifier tout ceci, en fusionnant les deux pages par exemple.

PS: Nous n'avons pas définit de conventions pour les pages d'aide : pluriel ou singulier ? J'ai choisi pluriel pour la page [[Help:Conventions]], mais pour la page d'aide pour les équipages, je choisirais plutôt le singulier... --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:31, 5 November 2014 (CET)

----

Je préférerais que le menu n'amène que sur les crews actives. En laissant un lien vers la catégorie "crews" dans "active crew" si tu veux.

Je pense que balancer toutes les crews inactives et mortes d'entrée de jeu nous fait retomber dans les travers du wiki: un ratio signal/bruit tout pourri.

--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 16:57, 5 November 2014 (CET)

----

:Mpf. J'imagine que tu n'as pas tord. J'avoue que j'hésitais entre balancer toutes les crews pour le « nouveau » qui voudrait savoir s'il y a eu un jour de l'activité dans sa région, et n'afficher que les crews actives pour gagner en efficacité. Sinon, que penses-tu du texte d'introduction ? Pas trop long ? Je pensais expliquer en détail le concept de crew et leur fonctionnement dans la page Help:Crew(s). Mais je continue de réfléchir à tout ça. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 21:13, 6 November 2014 (CET)

----
:: Je pense que le texte explicatif a toute sa pertinence dans la page "crews", mais la page "active crew" devrait aller à l'essentiel. D'une manière générale, je garderais cette logique: un clic amène sur une page qui va à l'essentiel et un clic de plus à partir de celle-ci permet d'obtenir toute la théorie et l'historique. De cette manière on garde une navigation claire sans sacrifier la profondeur. Quelqu'un qui a de toute façon prévu de se taper toute la littérature est prêt à faire un clic de plus. Tandis que pour quelqu'un qui sait exactement ce qu'il cherche, chaque clic/scroll est une action de trop. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 22:29, 6 November 2014 (CET)
----
:::Ok, c'est modifié :) --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 22:43, 6 November 2014 (CET)

== Please add a description when saving a page ==

It would be a good practice for everybody, and especially if you are a member of the Wiki Squad, to add a description of the changes made to a page when saving --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 14:06, 7 November 2014 (CET)
----
:Apologies, but when we edit a template page, it's really difficult to see the effects without saving it...--[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:52, 9 November 2014 (CET)
----
::And what about the "Show preview" button ? ^^ By the way it's a general remark. It has been triggered by your last changes but it's not limited to you --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 18:18, 9 November 2014 (CET)
----
:::Well, template parameters are very tricky, and I still have some difficulties understanding undefined parameters and parser functions. These things couldnt be tested by previewing, because I'm not really sure if the parameters' value are correct or not. Maybe I'm wrong, but as I said I'm still learning. By the way, I know it was a general remark, and I think you did well to highlight this, and you can see that we try to apply it now --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 18:39, 9 November 2014 (CET)

== Traductions ==

Salut. J'ai intégré le template [[Template:Bilingual]] au système d'annonce [[Annonces_-_Mededelingen]]. J'ai aussi ajouté des catégories [[:Category:A traduire]] et [[:Category:Te vertalen]] qui apparaissent quand une traduction est manquante. Mon idée est de pouvoir facilement trouver quelles pages doivent être traduites. L'idéal serait de classer les pages à traduire par date de modification et non par nom de page. On pourrait peut-être s'inspirer de la page des annonces pour faire ça ? Je me suis rendu compte que la page en question ne fait qu'afficher une catégorie selon un template. Rien de bien compliquer, je pense. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 15:58, 9 November 2014 (CET)

== Visual editor ==

[https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Accueil_principal Wikipedia FR] is now using the visual editor, I think we can make a few tests with [https://www.mediawiki.org/wiki/Extension:VisualEditor this module]

Edit: Even better, [https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf9 check this].
--[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 20:57, 22 November 2014 (CET)

== Upgrade to Mediawiki v1.25 ==

Hi there,

I'd like to prepare the upgrade to Mediawiki version 1.25, including the visual editor.
Wanna make a meeting to discuss the topic?

Sources:

http://www.mediawiki.org/wiki/VisualEditor#Status

http://www.mediawiki.org/wiki/MediaWiki_1.25

----

:Hey Vincent. We need to do some backup before upgrading the wiki. Have you the proper access permissions ? More generally, we should list people who have ssh access, etc.
:Regarding the visual editor, it has only been released a few weeks ago. I'd like to be sure about its stability before installing anything. Maybe we should test it on a local machine ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:00, 24 November 2014 (CET)

----

:: Aye, the proper order is: (1) Make a local copy of the wiki (2) Upgrade the local copy (3) Upgrade the website. I want to get all the team informed on this project before we start, that's why I'm talking about it here. I think I have the requested access but I'm interested in your feedback. --[[User:Vincent.L|Vincent L.]] ([[User talk:Vincent.L|talk]]) 13:09, 24 November 2014 (CET)

----

:::That seems fine for me :) My view: I think the wiki needs to be upgraded and the visual seems great, but maybe still unstable. I will be back in Belgium on the 15th December, so we can do a squad meeting (more general or specific on the upgrading, you choose) from this date, unless you want to upgrade the whole thing before the GA, but I don't think so. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 13:27, 24 November 2014 (CET)

----

::::Good idea to have a squad meeting --[[User:ZeFredz|ZeFredz]] ([[User talk:ZeFredz|talk]]) 19:58, 13 December 2014 (CET)

----

:::::Ok, I've created a framadate https://framadate.org/osqtc4wm97qtjfib (see how beautiful the new version is ! :D ). Note that I'm not really sure about my agenda, so I might change my choices later. We shall define a location, by the way. --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 20:45, 13 December 2014 (CET)

-----

Hi ! I propose a meeting on tuesday 30th december 2014, 2pm, at LLN. Is it ok for you, Fred ? As I don't know much LLN, maybe you can suggest a location ? --[[User:HgO|HgO]] ([[User talk:HgO|talk]]) 16:00, 27 December 2014 (CET)

== Parcourir et éditer les statuts via le wiki ==

Je viens d'intégrer un nouveau bazar :) Voir la nouvelle page [[statutes]].
Quelques explications:
* Chaque article a sa propre page, de la forme <code>Statutes/Art. xx</code>. L'avantage est qu'on peut traquer l'évolution de chaque article séparément, et que ça permet toutes sortes de manips.
* Grâce à la page [[Special:RunQuery/Statutes_query]] on peut afficher juste les articles qu'on veut, dans la langue qu'on veut (l'affichage bilingue est bien synchronisé!)
* L'édition des articles peut se faire via un formulaire adéquat, pour plus de lisibilité.

Plus d'infos sur les pages [[statues]] et [[statutes/Help]].

Par contre, je n'ai encore rempli que les 6 premiers articles sur la petite centaine... Petit boulot en perspective^^ À ce propos, quelqu'un sait où trouver la dernière version des statuts? Je ne suis tombé que sur un texte de 2013...

Voilà, j'espère que ça permettra d'éditer les statuts plus facilement et de se débarrasser du google doc :)
[[User:Manu|Manu]] ([[User talk:Manu|talk]]) 21:14, 3 January 2015 (CET)

Statutes

2015-01-03T19:59:23Z

Manu: /* Partie I : Nom, Valeurs communes & Adhésion | Deel I : Naam, gemeenschappelijke Waarden & Lidmaatschap */

Below are the statutes of the pirate party as voted through the [[:Category:Assembly|general assemblies]].

Paragraphs are directly accessible under links of the form <code>Statutes/Art. xxx</code>
To create a new paragraph, use [[Special:FormEdit/Statutes paragraph|this from]]. It will automatically appear under the heading whose range includes the number of the paragraph (see also [[Statutes/Help]]).
To browse paragraphs, use [[Special:RunQuery/Statutes query|this form]].

== Partie I : Nom, Valeurs communes & Adhésion | Deel I : Naam, gemeenschappelijke Waarden & Lidmaatschap ==
=== Chapitre I.1. Nom | Hoofdstuk I.1. Naam ===
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=1&Statutes%20query%5Bto%5D=4&wpRunQuery=true|link text= Texte bilingue - tweetalige tekst}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=1&Statutes%20query%5Bto%5D=4&Statutes%20query%5Blang%5D=FR&wpRunQuery=true|link text=Voir les articles en français uniquement}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=1&Statutes%20query%5Bto%5D=4&Statutes%20query%5Blang%5D=NL&wpRunQuery=true|link text=De artikels enkel in het Nederlands bekijken}}

=== Chapitre I.2. Valeurs communes | Hoofdstuk I.2. Gemeenschappelijke Waarden ===
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=5&Statutes%20query%5Bto%5D=5&wpRunQuery=true|link text= Texte bilingue - tweetalige tekst}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=5&Statutes%20query%5Bto%5D=5&Statutes%20query%5Blang%5D=FR&wpRunQuery=true|link text=Voir les articles en français uniquement}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=5&Statutes%20query%5Bto%5D=5&Statutes%20query%5Blang%5D=NL&wpRunQuery=true|link text=De artikels enkel in het Nederlands bekijken}}

=== Chapitre I.3. Adhésion | Hoofdstuk I.3. Lidmaatschap ===
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=6&Statutes%20query%5Bto%5D=27&wpRunQuery=true|link text= Texte bilingue - tweetalige tekst}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=6&Statutes%20query%5Bto%5D=27&Statutes%20query%5Blang%5D=FR&wpRunQuery=true|link text=Voir les articles en français uniquement}}
* {{#queryformlink:form=Statutes query|query string=Statutes%20query%5Bfrom%5D=6&Statutes%20query%5Bto%5D=27&Statutes%20query%5Blang%5D=NL&wpRunQuery=true|link text=De artikels enkel in het Nederlands bekijken}}

== Partie II : Structures | Deel II : Structuren ==
=== Chapitre II.1. Equipages | Hoofdstuk II.1. Crews ===

[[Category:Statutes]]

Statutes/Art. 6

2015-01-03T19:56:33Z

Manu:

{{Statutes paragraph
|number=6
|FR=Le montant minimal de la cotisation est de 1€.
|NL=Het minimale lidgeld bedraagt 1€.
}}

Statutes/Art. 6

2015-01-03T19:56:19Z

Manu: Created page with "{{Statutes paragraph |number=6 |FR=Le montant minimal de la cotisation est de 1€. |NL=6.Het minimale lidgeld bedraagt 1€. }}"

{{Statutes paragraph
|number=6
|FR=Le montant minimal de la cotisation est de 1€.
|NL=6.Het minimale lidgeld bedraagt 1€.
}}

Statutes/Art. 5

2015-01-03T19:55:25Z

Manu: Created page with "{{Statutes paragraph |number=5 |FR=Les Pirates agissent dans le respect des principes suivants. Ces principes constituent les valeurs communes aux Pirates : 5.1. Libertés ..."

{{Statutes paragraph
|number=5
|FR=Les Pirates agissent dans le respect des principes suivants. Ces principes constituent les valeurs communes aux Pirates :

5.1. Libertés

5.1.1. La liberté individuelle va de pair avec la responsabilité collective, l'indépendance, l'autonomie et l'esprit critique.

5.1.2 Les libertés fondamentales sur lesquelles les Pirates se concentrent plus particulièrement :

5.1.2.1 Droit à la vie privée : Ce droit nécessite d’être renforcé et consiste d'abord en la libre disposition de son propre corps et ensuite en une série de droits garantis à la confidentialité: correspondance, données personnelles, états financiers, identité, localisation. Ces droits privés ne peuvent être violés que par des autorités compétentes sur des soupçons concrets, préalables et individuels d'un crime spécifique, commis, et sérieux (et non sur de simples présomptions).

5.1.2.2 Liberté d’expression: Celle-ci ne consiste pas seulement à avoir le droit de dire ce que l’on veut, mais également celui d’être entendu, écouté et non-censuré et ce, quel que soit le sujet. Nous étendons la liberté d’expression à celle de pouvoir diffuser l’expression des autres sans limites. La liberté de conscience faisant partie intégrante de la liberté d'expression, les Pirates sont pour une séparation claire des religions et de l'Etat.

5.2. Solidarité :

5.2.1. Les Pirates n’acceptent pas la lâcheté et l’indifférence en société, et agissent quand un courage moral est nécessaire. Les Pirates s’engagent pour une société solidaire où les forts défendent les faibles, indépendamment des territoires ou communautés.

5.2.2. Les Pirates veulent rééquilibrer les relations entre générations.

5.3. Cosmopolitisme :

5.3.1. Les Pirates font partie d’un mouvement mondial, ils ont plusieurs identités et ne sont rivés à aucune d'elles en particulier.

5.3.2. Tous les modes de vie en communauté ont la même valeur.

5.4. Démocratie : Les Pirates font la promotion d’un système politique réellement démocratique, c’est à dire d’un système politique ouvert, simple et transparent où le peuple gouverne le plus directement possible.

Afin d’être effectif, un tel système nécessite l’existence une série de caractéristiques non exhaustives:

5.4.1. Souveraineté du peuple: Les pouvoirs sont définis et détenus par l’ensemble des citoyens.

5.4.2. Droit d’initiative: Droit de proposer des lois.

5.4.3. Isonomie: Égalité Politique. Droit égal de tous les citoyens à exercer leurs droits politiques.

5.4.4. Iségorie: Égalité devant le droit de parole. Droit pour chaque citoyen de prendre la parole et de faire des propositions dans les assemblées politiques. Quand un groupe membre est en désaccord avec la majorité, ce groupe a la liberté d'exprimer son point de vue.

5.4.5. Séparation des pouvoirs: Tous les types de pouvoir (législatif, judiciaire, exécutif, médiatique, financier, monétaire, etc.) sont exercés au sein d’institutions distinctes.

5.4.6. Mandat impératif: Tout mandaté exerce une mission définie dans son objet et sa durée et a l’obligation de s’y limiter. Ces mandats sont révocables et impliquent une reddition des comptes à l’échéance.

5.4.7. Non-professionnalisation: La politique est l’affaire de tous les citoyens et non seulement de professionnels ou d’experts. Les débats et les lois doivent s’exprimer dans un langage qui reste compréhensible par le plus grand nombre.

5.5. Créativité: Les Pirates sont créatifs, curieux, et ne se satisfont pas du statu quo. Ils défient les systèmes, cherchent leurs points faibles, et trouvent des façons de les corriger. Les Pirates apprennent de leurs erreurs.

5.6. Partage du savoir, de la technologie et de la culture: Ceci doit être considéré comme un droit fondamental.

Le système de droit d’auteur et de brevets en place actuellement limite artificiellement la circulation du savoir, des innovations technologiques, des logiciels et de la culture. En conséquence, les lois qui les définissent doivent être profondément réformées.

5.7. Ecologisme : Les Pirates luttent pour la pérennité des ressources naturelles et la libre circulation des ressources immatérielles. Ils n'acceptent aucun brevet sur le vivant.

5.8. Equivalence :

5.8.1. Les Pirates entretiennent entre eux et avec les citoyens des relations d'égal à égal.

5.8.2. Parce que chacun doit disposer des mêmes potentialités d'action, les Pirates font de l'inclusion numérique une priorité.

5.8.3. Les Pirates sont attentifs à l'égalité réelle et effective entre les genres, sans préjugés.

5.9. Objectivité :

5.9.1. Les Pirates préfèrent les décisions basées sur les sciences et les arguments plutôt que sur les justifications réglementaires, d'habitude ou des capacités d'un seul homme.

5.9.2. Les Pirates sont positifs, ils préfèrent se battre pour que contre.
|NL=De piraten handelen volgens de volgende principes, die de gemeenschappelijke piratenwaarden vormen:

5.1. Vrijheden

5.1.1. Individuele vrijheid hoort bij een collectieve verantwoordelijkheid, onafhankelijkheid, autonomie en kritisch oordeel.

5.1.2. Piraten focussen in het bijzonder op deze fundamentele vrijheden:

5.1.2.1 Recht op privacy: Dit recht moet sterker afgedwongen worden. Het bestaat uit, om te beginnen, het vrij beschikken over je eigen lichaam. Het wordt dan uitgebreid naar een reeks rechten op confidentialiteit: correspondentie, persoonlijke data, financiële situatie, identiteit, locatie. Deze rechten kunnen enkel gebroken worden door de bevoegde autoriteiten, gebaseerd op eerdere, solide, individu-specifieke verdenkingen, in tegenstelling tot enkel vermoedens.

5.1.2.2 Recht op vrije meningsuiting: vrije meningsuiting is meer dan enkel het recht om vrij je mening te uiten. Het is ook het recht om gehoord te worden, en om niet gecensureerd te worden op om het even welk onderwerp. We breiden vrijemeningsuiting uit tot het kopiëren van de mening van anderen, zonder grenzen. Vrijheid van religie is ook een belangrijk deel van de vrije meningsuiting. Piraten zijn voor een duidelijke en strikte scheiding tussen kerk en staat.

5.2. Solidariteit :

5.2.1. Piraten kunnen geen lafheid of onverschilligheid aanvaarden in een samenleving. Ook wanneer moed nodig is, gaan ze in de bres springen. Piraten engageren zich om een maatschappelijk model te promoten gebaseerd op solidariteit, op de sterken die de zwakken verdedigen, onafhankelijk van territoria of gemeenschappen.

5.2.2. Piraten willen de balans tussen de generaties herstellen.

5.3. Cosmopolitisme :

5.3.1. Piraten zijn een deel van een wereldwijde beweging. Ze zitten niet vast aan één van hun vele identiteiten.

5.3.2. Alle samenlevingsvormen moeten gelijkwaardig zijn.

5.4. Democratie : Piraten promoten een echt democratisch politiek systeem: dat is een open, simpel en transparant systeem die de mensen de kans heeft om zo direct als mogelijk te regeren.

Om effectief te kunnen zijn, moet zo'n systeem minstens de volgende lijst van karakteristieken hebben.

5.4.1. Soevereiniteit van het volk: De macht wordt gedefinieerd als uitgeoefend door alle burgers.

5.4.2. Initiatiefrecht: Het recht om wetten voor te stellen.

5.4.3. Isonomia: Politieke gelijkheid, iedere burger moet dezelfde kansen hebben om zijn politieke rechten uit te oefenen.

5.4.4. Isegoria: Gelijkheid om zichzelf uit te drukken. Iedere burger heeft het recht om zichzelf uit te drukken en om voorstellen in te dienen bij politieke instanties. Wanneer een groep leden het oneens zijn met de meerderheid van de partij kunnen zij vrij hun standpunt verkondigen.

5.4.5. Scheiding van de macht: alle types van macht (wetgevend, rechterlijk, uitvoerend, media, financieel, etc...), worden uitgeoefend binnen verschillende instituten.

5.4.6. Imperatief mandaat: Alle gemandateerde officials voeren een opdracht uit de duidelijk gedefinieerd is in termen van inhoud en duur en moet zich daar aan houden. Deze mandaten zijn herroepbaar en impliceren volledige aansprakelijkheid op hun voorwaarden.

5.4.7. Anti-professionalisatie: Politiek is een burgerlijke zaak, en niet enkel voor professionals of experten. Debatten en wetten moeten uitgedrukt worden in een taal die verstaanbaar is voor zo veel mogelijk mensen.

5.5. Creativiteit : Piraten zijn creatief, nieuwsgierig en niet tevreden met de status quo. Ze dagen het systeem uit, zoeken haar zwakheden en zoeken en vinden manieren om die te corrigeren. Piraten leren van hun fouten.

5.6. Sharing van kennis, technologie en cultuur: dit moet gezien worden als een fundamenteel recht.

De huidige wetten op copyright en patenten leggen artificiële grenzen aan de stroom van kennis, technologische innovatie, software en cultuur. Dus copyright en patenten hebben radicale hervormingen nodig.

5.7 Ecologisch : Piraten zorgen voor een behoud van natuurlijke bronnen en willen een vrije stroom van virtuele bronnen. Ze aanvaarden geen eigendom van leven.

5.8. Gelijkwaardigheid:

5.8.1. Piraten onderhouden banden onderling zijn gelijkwaardigen onder elkaar en tussen burgers.

5.8.2. Omdat iedereen hetzelfde potentieel heeft, maakt de Piraten van digitale inclusie een prioriteit.

5.8.3. Piraten zijn aandacht naar werkelijke, echte gelijkwaardigheid tussen genders, zonder hokjesdenken.

5.9 Objectiviteit:

5.9.1. Piraten verkiezen beslissingen gebaseerd op wetenschap en op argumenten, eerder dan redenen gebaseerd op wetgeving, gewoonten of individuele mogelijkheden.

5.9.2. Piraten zijn positief, we zijn liever ergens voor, dan tegen.
}}

Statutes/Art. 4

2015-01-03T19:54:12Z

Manu: Created page with "{{Statutes paragraph |number=4 |FR=Le Parti Pirate et ses membres s'engagent à promouvoir les droits et libertés garantis par la Convention pour la protection des droits de ..."

{{Statutes paragraph
|number=4
|FR=Le Parti Pirate et ses membres s'engagent à promouvoir les droits et libertés garantis par la Convention pour la protection des droits de l'homme et des libertés fondamentales du 4 Novembre 1950.
|NL=De Piratenpartij en haar leden verbinden er zich toe de rechten en vrijheden, zoals gewaarborgd door het Verdrag tot bescherming van de Rechten van de Mens en de Fundamentele Vrijheden van 4 november 1950, te bevorderen.
}}

Statutes/Art. 3

2015-01-03T19:53:42Z

Manu: Created page with "{{Statutes paragraph |number=3 |FR=L'association est une organisation politique. |NL=De vereniging is een politieke organisatie. }}"

{{Statutes paragraph
|number=3
|FR=L'association est une organisation politique.
|NL=De vereniging is een politieke organisatie.
}}

Statutes/Art. 2

2015-01-03T19:53:03Z

Manu: Created page with "{{Statutes paragraph |number=2 |FR=La dénomination de l’association est "Piratenpartij" en néerlandais, "Parti Pirate" en français, "Piratenpartei" en allemand, "Pirate P..."

{{Statutes paragraph
|number=2
|FR=La dénomination de l’association est "Piratenpartij" en néerlandais, "Parti Pirate" en français, "Piratenpartei" en allemand, "Pirate Party" en anglais.
|NL=De naam van de vereniging is "Piratenpartij" in het Nederlands, "Parti Pirate" in het Frans, "Piratenpartei" in het Duits, "Pirate Party" in het Engels.
}}

Template:Display statutes paragraph

2015-01-03T19:52:18Z

Manu:

<noinclude>
This template is used to display paragraphs from the [[statutes]] in both languages (FR and NL). See [[Special:RunQuery/Statutes query|here]].
</noinclude>

<includeonly>
'''Art. {{{?Paragraph number}}}''' [{{formedit|{{{?}}}}}]
{{Bilingual
|fr={{{?FR|}}}
|nl={{{?NL|}}}
}}
</includeonly>

Template:Statutes paragraph

2015-01-03T19:50:51Z

Manu:

<noinclude>
This template is used to display a statutes paragraph on its own page. To create such a paragraph, use [[Special:FormEdit/Statutes paragraph|this form]].
</noinclude>

<includeonly>{{Bilingual
|fr=[[FR::{{{FR|''Traduction manquante.''}}}]]
|nl=[[NL::{{{NL|''Ontbrekende vertaling.''}}}]]
}}
{{#set:Paragraph number={{{number|''?''}}}}}
[[Category:Statutes paragraph]]
</includeonly>

Statutes/Art. 1

2015-01-03T19:48:28Z

Manu: Created page with "{{Statutes paragraph |number=1 |FR=Le Parti Pirate est une association de fait, créée pour une durée indéterminée. |NL=De vereniging de Piratenpartij is een feitelijke ve..."

{{Statutes paragraph
|number=1
|FR=Le Parti Pirate est une association de fait, créée pour une durée indéterminée.
|NL=De vereniging de Piratenpartij is een feitelijke vereniging, opgericht voor onbepaalde duur.
}}

Statutes

2015-01-03T19:47:37Z

Manu: New statutes browsing system. First sections.

Statutes/Help

2015-01-03T19:45:30Z

Manu: Created page with "=== How to add a new paragraph in the statutes === Use this form. Note that the number should be an integer or a number of between x.2 ..."

=== How to add a new paragraph in the statutes ===
Use [[Special:FormEdit/Statutes_paragraph|this form]]. Note that the number should be an integer or a number of between x.2 and x.9. A paragraph labeled x.10 would be sorted before x.2, which is not what is intended.

Don't forget to adjust the range of the corresponding section on the [[statutes]] page (see next section).

=== How to manage sections ===
Sections are directly written on the main page. The deepest sections should include a link to the range of paragraphs contained in it.
Such a link has the following form. The red text need to be changed and correspond to the bold text just before.

<nowiki>{{#queryformlink:form=Statutes query
|query string=Statutes%20query%5B</nowiki>'''from'''<nowiki>%5D=</nowiki><span style="color:red;">15</span><nowiki>&Statutes%20query%5B</nowiki>'''to'''<nowiki>%5D=</nowiki><span style="color:red;">54</span><nowiki>&Statutes%20query%5B</nowiki>'''lang'''<nowiki>%5D=</nowiki><span style="color:red;">FR</span><nowiki>&wpRunQuery=true
|</nowiki>'''link text'''<nowiki>=</nowiki><span style="color:red;">Voir les articles en français</span><nowiki>
}}</nowiki>

* <code>from</code> is the number of the first paragraph included;
* <code>to</code> is the number of the last paragraph included;
* <code>lang</code> is the language in which the paragraphs will be displayed. The allowed values are <code>FR, NL</code> and <code>FR-NL</code>.
* <code>link text</code> is the text to be displayed on the link.
[[Category:Statutes]]

Property:Paragraph number

2015-01-03T19:45:00Z

Manu: Created page with "This is a property of type Has type::Number, used to number the paragraphs of the statutes. It should only contain integer numbers or numbers between x.2 and x.9."

This is a property of type [[Has type::Number]], used to number the paragraphs of the [[statutes]].
It should only contain integer numbers or numbers between x.2 and x.9.

Form:Statutes query

2015-01-03T19:44:23Z

Manu: Created page with "<noinclude> This form is used to query paragraphs of the statutes. Use it through this page. </noinclude><includeonly> {{{info|query fo..."

<noinclude>
This form is used to query paragraphs of the [[statutes]]. Use it through [[Special:RunQuery/Statutes query|this page]].
</noinclude><includeonly>
{{{info|query form at top}}}
Which paragraphs whould you like to display?
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|Statutes query}}}
{| class="formtable"
! From:
| {{{field|from}}}
|-
! To:
| {{{field|to}}}
|-
! Language:
| {{{field|lang|input type=dropdown|values=FR-NL,FR,NL|default=FR-NL}}}
|}
{{{end template}}}
{{{standard input|run query}}}
</includeonly>

Form:Statutes paragraph

2015-01-03T19:43:48Z

Manu: Created page with "<noinclude> Use this link to make a new statutes paragraph with this form. </noinclude> <includeonly> {{{info|page name=Statutes/Art. <..."

<noinclude>
Use this [[Special:FormEdit/Statutes paragraph|link]] to make a new statutes paragraph with this form.
</noinclude>
<includeonly>
{{{info|page name=Statutes/Art. <Statutes paragraph[number]>}}}
<div id="wikiPreview" style="display: none; padding-bottom: 25px; margin-bottom: 25px; border-bottom: 1px solid #AAAAAA;"></div>
{{{for template|Statutes paragraph}}}
{| class="formtable"
! Paragraph number<nowiki>*</nowiki>:
| {{{field|number|mandatory|input type=text}}}
|-
! FR:
| {{{field|FR}}}
|-
! NL:
| {{{field|NL}}}
|}
{{{end template}}}
<nowiki>*</nowiki> It should be of the following type: 23, 34.2...

{{{standard input|summary}}}

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

{{{standard input|save}}} {{{standard input|preview}}} {{{standard input|changes}}} {{{standard input|cancel}}}
</includeonly>

Template:Statutes query

2015-01-03T19:43:21Z

Manu: Created page with "<noinclude> This template is used to query paragraphs in the statutes. See this page. </noinclude> <includeonly> {{#ask: Category:Sta..."

<noinclude>
This template is used to query paragraphs in the [[statutes]]. See [[Special:RunQuery/Statutes query|this page]].
</noinclude>
<includeonly>
{{#ask: [[Category:Statutes paragraph]] [[Paragraph number::≥{{{from|1}}}]] [[Paragraph number::≤{{{to|1000}}}]]
|?FR
|?NL
|?Paragraph number
|format=template
|named args=yes
|template={{#switch: {{{lang|}}}
| FR = Display statutes paragraph/FR
| NL = Display statutes paragraph/NL
| FR-NL = Display statutes paragraph
| Display statutes paragraph
}}
|link=none}}
[[Category:Statutes]]
</includeonly>

Template:Display statutes paragraph/NL

2015-01-03T19:42:53Z

Manu: Created page with "<noinclude> Dit template dient om artikels van de statuten weer te geven in het Nederlands. Zie hier. </noinclude> <includeon..."

<noinclude>
Dit template dient om artikels van de [[statutes|statuten]] weer te geven in het Nederlands.
Zie [[Special:RunQuery/Statutes query|hier]].
</noinclude>

<includeonly>
'''Art. {{{?Paragraph number}}}''' [{{formedit|{{{?}}}}}]

{{{?NL|}}}
</includeonly>

Template:Display statutes paragraph/FR

2015-01-03T19:42:09Z

Manu: Created page with "<noinclude> Ce modèle sert à afficher les articles de statuts en français. Voir cette page. </noinclude> <includeonly> '''..."

<noinclude>
Ce modèle sert à afficher les articles de [[statutes|statuts]] en français. Voir [[Special:RunQuery/Statutes query|cette page]].
</noinclude>

<includeonly>
'''Art. {{{?Paragraph number}}}''' [{{formedit|{{{?}}}}}]

{{{?FR|}}}
</includeonly>

Template:Display statutes paragraph

2015-01-03T19:41:42Z

Manu: Created page with "<noinclude> This template is used to display paragraphs from the statutes in both languages (FR and NL). See here. </noinclude> <inclu..."

<noinclude>
This template is used to display paragraphs from the [[statutes]] in both languages (FR and NL). See [[Special:RunQuery/Statutes query|here]].
</noinclude>

<includeonly>
'''Art. {{{?Paragraph number}}}''' [{{formedit|{{{?}}}}}]
{{col-float}}
{{{?FR|}}}
{{col-float-break}}
{{{?NL|}}}
{{col-float-end}}
</includeonly>

Template:Statutes paragraph

2015-01-03T19:40:30Z

Manu: Created page with "<noinclude> This template is used to display a statutes paragraph on its own page. To create such a paragraph, use this form. </noinclu..."

<noinclude>
This template is used to display a statutes paragraph on its own page. To create such a paragraph, use [[Special:FormEdit/Statutes paragraph|this form]].
</noinclude>

<includeonly>{{col-float}}
[[FR::{{{FR|''Traduction manquante.''}}}]]
{{col-float-break}}
[[NL::{{{NL|''Ontbrekende vertaling.''}}}]]
{{col-float-end}}

{{#set:Paragraph number={{{number|''?''}}}}}
[[Category:Statutes paragraph]]
</includeonly>

Category:Statutes paragraph

2015-01-03T19:39:21Z

Manu: Created page with "This category uses the form Has default form::Statutes paragraph. Category:Statutes"

This category uses the form [[Has default form::Statutes paragraph]].

[[Category:Statutes]]

Category:Statutes

2015-01-03T19:38:46Z

Manu: Created page with "This category contains everything related to the statutes of the pirate party."

This category contains everything related to the [[statutes]] of the pirate party.

User:ZeFredz/AmendmentsTool

2014-07-30T09:35:32Z

Manu: add co-ment in the list

==Coals and motivation==

Set up a tool to manage proposals and amendments for parliamentary/legislative/judiciary texts. This tool or set of tools will have to provide an intuitive user-friendly interface and handle history and translations. The goal here is to list the existing solutions, to analyse them and to create a list of requirements for such a platform.

'''Motivation''' : We are currently using several tools to manage our GA preparation process but none of theme is currently meeting the requirements to create a complete eDemocracy online platform that anybody can use. This platform will have to work in a multi-language environment which will be a real challenge to solve !

http://movecommons.org/mc/0.1/images/np-rp-rc.to-gr-88x31-0.1.png
[http://movecommons.org/en/np-rp-rc.to-gr/0.1/ Move Commons Non-Profit, Reproducible, Reinforcing the Town/community/society Commons, Grassroots]

==State of the art==

* MediaWiki (libre & open source GPL) - example : [[Events/EGA:2014-08/Amendments]]
* GetOpinionated : http://opinion.pirateparty.be (libre & open source GPL)
* AT4AM : http://www.at4am.org tool developped for EU (libre & open source EUPL)
* Wirite : http://main.wirite.org/ (proprietary, source not available at this time)
* Co-ment : http://www.co-ment.org/ Descendant of the software used to write GPL V3.
* Git
** German Laws on GitHub : https://github.com/bundestag/gesetze
* Pads (etherpad-lite)

===Standards & data structures===

* http://www.akomantoso.org/ : "Akoma Ntoso (“linked hearts” in Akan language of West Africa) defines a “machine readable” set of simple technology-neutral electronic representations (in XML format) of parliamentary, legislative and judiciary documents."
* Markdown + structure of documents (German laws on GitHub)

===Other tools to look at===

* iMio.be (ex-communesplone) : http://www.imio.be/

==Analysis of existing tools==

Template :

===Tool name===
====ToolName - Good for====

====ToolName - Lacks of====

===MediaWiki===

The Wiki has been used for the Amendments for the August 2014 GA

The main issue with the Wiki is that it's a generalistic tool. It can do nearly anything, but it's not specialized in anything. So using it to do something alse than creating a collaborative web site can be tricky or take a lot of time to enforce structural conventions. In addition, it requires a good communication on how the structuration has to be done by the end users.

====MediaWiki - Good for====

* Collaborative editing
* Versioning and history
* Easy to use if you now how to use the Wiki
* Flexible

====MediaWiki - Lacks of====

* Clarity when mixing proposals and amendments on a page
* Support for translations
* History on sections of a page (i.e. Amendments and Proposals)
* Easier way to debate/discuss on amendments and proposals
* Parliamentary/Legislative/Judiciary specific structures of documents
* User-friendliness if your are not a fan of the Wiki tool
* Seing amendments/questions/discussions in the page flow can be tricky
* Voting/decision system (OK? done at the GA, but should be possible to do it online for a more generalized usage)

===GetOpinionated===

Is a great tool for Liquid Democracy, for simpler than Liquid Feedback. But this is not a proposal/amendment managment tool.

====GetOp - Good for====

* Liquid democracy
* Discussion
* "liking" comments
* Voting on proposals
* Proxy voting

====GetOp - Lacks of====

As far as I know :

* A way to add argumentation to a proposal
* A way to handle amendments on proposals
* A way to create new proposals from amendments
* Versionning and history on proposals
* Translation system on proposals/amendments
* A way to add references (links, documents...) on proposals
* Collaborative proposals/amendments writing

=== Co-ment===
==== Co-ment - Good for ====
* text annotation by multiple users.
* discussion
* ?

==== Co-ment - Lacks of====
* ?

==Requirements for an Proposals/Amendments management tool==

working on it...

Events/EGA:2014-08/Amendments

2014-07-22T10:14:19Z

Manu: /* Traduction à vérifier */

= Intro =

==== EN ====
This is the page dedicated to the preparation of the texts that will be voted during our next G.A.
We have received these proposals according to our protocol, available there: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

==== FR ====
Ceci est la page dédiée à la préparation des textes qui seront votés en Assemblée Générale.
Nous avons reçu ces propositions en conformité avec notre protocole, disponible ici: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

= Existing Statutes =

[[Statutes|Existing Statutes - Statuten - Statuts]]

= Proposals to amend =

== Intro ==

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Translation :'''

In the context of translating the statutes, here is the convention to respect in order to keep the work clear :

The translations are made in '''bold'''.

The corrections of the text are made in ''italic''.

The finalisation after proofreading is made in normal.

'''Amendments :'''

Every amendment is written under the proposal to amend, with sub(-sub)-bullet and signature (name and date) of the pirate who's amending.

Example :
* Every pirate can start a project that respects the statutes and the general goals of the party.
** Every pirate can start a project that respects the statutes and the general goals of the party, except during an eclipse of sun. [[User:Alexis|Alexis]] ([[User talk:Alexis|talk]]) 12:30, 20 July 2014 (CEST)

Code :

<nowiki>** Amendment. ~~~~</nowiki>

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Traduction :'''

Dans le cadre de la traduction des statuts, voici la convention à respecter afin de garder une certaine visibilité :

Les traductions se font en '''gras'''.

Les corrections à un texte se font en ''italique''.

La finalisation après relecture se fait en normal.

'''Amendements :'''

Chaque amendement se fait sous l'article à amender, en sous(-sous)-point, avec signature (nom et date) du pirate qui a amendé.

Exemple :
* Every pirate can start a project that respects the statutes and the general goals of the party.
** Every pirate can start a project that respects the statutes and the general goals of the party, except during an eclipse of sun. [[User:Alexis|Alexis]] ([[User talk:Alexis|talk]]) 12:30, 20 July 2014 (CEST)

Code :

<nowiki>** Amendement. ~~~~</nowiki>
|}

== Set n°1 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set1
<eplite id=ga201408-amendments-set1></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
=== Original ===
* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction à vérifier ===

* '''Les escouades responsables de la communication numérique du parti, ont le droit de modérer les canaux et ''de'' refuser, le cas échéant, l'accès à ces canaux.'''

*''' Pour tous les mandats, la rétrocession au parti s'élève à 22,5% de la rémunération brute. Si l'élu en question ''ne dispose'' pas de revenu''s'' ''émanant d'une autre activité'', ''d'une'' pension ou ''d'un'' revenu de remplacement, le montant des rétrocessions ''s'élève'' à 17,5% de la rémunération brute.'''

*''' La cotisation ''des membres'' est de 2,5 € par mois. La coreteam peut, ''à titre'' exceptionnel, décider qu'une personne n'a pas à payer les frais d'adhésion.'''

*''' A chaque assemblée générale, la coreteam est élue lors d'un vote de confiance. Tous les candidats de la coreteam sont placés sur une liste. Ensuite les membres votent secrètement ''l'approbation'' ou non de chacun des candidats. Tous les candidats ayant reçu la confiance de la majorité du parti sont élus. S'il y a plus de 10 élus, les membres ayant reçu le plus de votes de confiance rejoignent la coreteam, ensuite les candidats ayant le moins d'années d'expérience.'''

*''' Nous allons retravailler les statuts, pour que le Parti Pirate, devienne une a.s.b.l. Les éléments importants pour les tiers sont déplacés dans les statuts de l'association, et tous les éléments du fonctionnement interne dans un règlement interne. Ce changement radical dans la structure sera ensuite présenté concrètement à l'assemblée générale.'''

'''Commission de conciliation et de discipline'''

'''§X. L'autorité de l'Assemblée Générale doit être reconnue et respectée par tous les membres. Les personnes qui sapent l'autorité de l'Assemblée Générale, qui refusent de se soumettre aux décisions établies, ou qui par leur comportement ou attitude causent du trouble ou des dommages au parti, peuvent être suspendus de leurs fonctions.'''

'''§X. Les organes qui refusent de reconnaître l'autorité de l'Assemblée Générale, ou qui entreprennent des actions qui causent du trouble ou des dommages au parti, peuvent être suspendus de manière collective.'''

'''§X. La suspension d'organes ou de membres est le fait d'une procédure de conciliation et de discipline, qui elle-même est initiée par une entité à l'encontre de cet organe ou de ce membre.'''

'''Durant toute période de 6 mois précédant des élections politiques ou une élection de la coreteam, une suspension ne peut être prononcée que sous l'approbation de la coreteam en fonction. Si elle n'a pas été prise, cette décision est reportée après lesdites élections.'''

'''La coreteam détermine les partis impliqués lors d'une procédure de conciliation et de discipline.'''

'''§X. Toute décision de suspension ou de réprimande doit être déposée dans la semaine sous dossier auprès de la coreteam.'''

'''Toute suspension ne peut excéder une durée de 6 mois après dépôt.'''

'''Le conseil ayant émis la suspension doit évaluer la situation avant le terme de terme de celle-ci. Un dossier de conciliation et de discipline doit être déposé en cas d'évaluation négative. La suspension reste d'application pendant la période de traitement de ce nouveau dossier.'''

'''§X. Toutes les plaintes et éléments en cours sont traités de manière publique et transparente, mais ''sous'' respect de la vie privée des personnes concernées.'''

'''§X. La commission nationale de conciliation et discipline est composée de 5 membres tirés au sort ''pour l'affaire concernée'' parmi les membres ayant pris part ''à'' l'assemblée générale précédente, éventuellement par procuration.'''

'''Pour chaque membre, un remplaçant est également tiré au sort.'''

'''Au cas où un membre effectif ne pourrait être présent, le secrétariat contactera un remplaçant. Il ne peut y avoir maximum que 1 membre représentant une province. Il sera assuré qu'au moins 2 personnes parlant la même langue que les parties concernées seront présentes.'''

'''Le secrétaire de la coreteam est un membre supplémentaire de la commission de conciliation et discipline, le sixième, et sans droit de vote. Il décide lui-même de la nécessité de sa présence.'''

'''§X. Un membre de la commission de conciliation et discipline qui serait lui-même impliqué dans une procédure ne peut pas y sièger. Les membres de la coreteam, à l'exception du secrétaire, ne peuvent pas faire partie de la commission.'''

'''§X. Une réunion de la commission n'est considérée comme valide que si au moins la moitié de ses membres sont présents.'''

'''§X. La commission est renouvelée pour chaque nouveau cas.'''

'''§X. Tout diffrend au sein du parti et toute violation grave du règlement du parti peut être présenté à la commission de conciliation et discipline par la coreteam elle-même ou par tout autre pirate.'''

'''Cet acte doit être annoncé lors de la prochaine réunion de la coreteam.'''

'''§X. La commission de conciliation et discipline se réunit endéans les 2 mois sous invitation de son président afin d'examiner le problème soumis. Elle peut entendre les différentes parties, recevoir leur dossier et des notes, ainsi que rédiger un rapport reprenant les points de vue respectifs. Ce rapport est remis au secrétaire de la coreteam.'''

'''§X. La coreteam peut à titre exceptionnel décider de suspendre provisoirement un membre pour une durée de 2 mois. Cette suspension prend fin lorsque la commission de conciliation et discipline prononce sa décision.'''

'''§X. La commission de conciliation et discipline peut lever cette suspension si cela peut contribuer à résoudre le conflit.'''

'''§X. La commission de conciliation et discipline cherchera toujours en premier lieu la conciliation. Elle peut également proposer ou astreindre les mesures suivantes, par ordre d'importance :'''

'''A. la réprimande, en avisant les membres de l'organe concerné;'''

'''B. le blâme, en avisant les membres du parti;'''

'''C. la suspension dans une fonction, pour une durée maximale de 12 mois;'''

'''D. la suspension en tant que membre du parti, pour une durée maximale de 12 mois;'''

'''E. l'exclusion.'''

'''Les sanctions A, B et C peuvent être prononcées et instituées par la commission de conciliation et discipline elle-même.'''

'''Les sanctions D et E ne peuvent qu'être proposées par la commission et doivent être entérinées par la coreteam.'''

'''Les décisions de la commission de conciliation et discipline sont prises par majorité simple.'''

'''§X. Un membre de la commission de conciliation et discipline fait rapport de l'affaire lors de la prochaine réunion de la coreteam. En cas de sanction D ou E, celui-ci expose la proposition, à la suite de quoi la coreteam se prononce immédiatement.'''

'''Une autre mesure de conciliation peut être proposée en cas de rejet.'''

'''§X. Toute décision de la commission de conciliation et discipline ou du conseil du parti doit être annoncée aux parties concernées dans la semaine par le secrétaire général.'''

'''§X. Un élu exclu par une mesure de conciliation remettra son ou ses mandats immédiatement à la disposition du parti. En cas de suspension, un élu reste tenu de respecter ses obligations envers le parti.'''

'''§X. Un membre auparavant exclu du parti fera part par écrit à l'assemblée générale de son souhait de réintégrer le parti. L'assemblée générale peut décider de s'occuper de l'affaire. Dans ce cas, elle entend le membre exclu et les éventuelles autres parties concernées et prend une décision.'''

|-
|}

== Set n°2 ==

=== Discussion pad ===

Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set2
<eplite id=ga201408-amendments-set2></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Original'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squad organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidence.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-center:5px; border-radius:5px" |
'''Translation ongoing (David L.)'''
==== Crews ====
Zie huidige statuten.
* De rol van kapitein richt zich op de leden van de crew en de groepsdynamiek.
* De rol van navigator richt zich op administratieve taken.

==== Projecten ====

* Elke piraat kan een project dat de statuten en de algemene doelen van de partij respecteert starten.
* Elke piraat die een project start moet de coördinatie-squad contacteren met de volgende informatie: een beschrijving van het project en een contactpersoon.
* De coördinatie-squad registreert het project formeel na verificatie dat het de statuten en de waarden van de partij respecteert.
* Elk project dat niet aangegeven werd aan de coördinatie-squad is de facto niet onderschreven door de partij.
* Als het project beëindigd of in stand-by is, moet de contactpersoon van het project dit melden aan de coördinatie-squad.
* (OPT) Elk project moet publiek worden voorgesteld op een webpagina.

==== Resource centers ====
* Een resource center is een repertorium dat piraten met specifieke vaardigheden of kennis rond een specifiek onderwerp oplijst. Het kan andere informatie gerelateerd met zijn thema bevatten, zoals doumentatie, een lijst van experten, enz.

==== Squads ====
* De volgende entiteiten, gerefereerd door squads moeten als volgt worden benoemd:
** squads
** ?

* Er zijn exact 9 squads in de partij. Dit zijn:
** Coaching
** Coördinatie
** Coreteam
** Financiën
** AV
** IT
** Pers
** Secretariaat
** Wiki

De rollen van elke squad worden beschreven in de volgende secties.

* Er zijn twee manieren voor een piraat om lid te worden van een squad:
*# Goedgekeurd worden door een motie van vertrouwen op een AV.
*# Unaniem goedgekeurd worden door de huidige leden van de squad. In dit geval moet deze beslissing actief aangekondigd worden naar alle piraten.
* Er zijn twee manieren voor een lid van een squad om deze te verlaten:
*# Aftreden.
*# Falen in een motie van vertrouwen op een AV.
* Elke squad bestaat uit minstens twee leden.
* Op de eerste AV van elk jaar presenteert elke squad een activiteitenraport en er wordt opgeroepen tot een motie van vertrouwen. Indien de motie faalt voor een bepaalde squad wordt er opgeroepen tot een een motie van vertrouwen voor elk van zijn leden.
* Elke kandidaat voor een squad moet een nog te bepalen procedure volgen.

===== Coaching =====
* De Coaching-squad heeft de volgende exclusieve bevoegdheden:
** Verwelkomen van nieuwe leden.
** Richtlijnen verspreiden.
** Documentatie en middelen aanbieden aan nieuwe leden.
** ''Aan te vullen''

===== Coördinatie =====
* De Coördinatie-squad heeft de volgende exclusieve bevoegdheden:
** Inkomende email op het contactadres contact@pirateparty.be beheren. Onder "beheren" wordt verstaan het forwarden naar de juiste persoon die kan antwoorden.
** Beheren van een publieke lijst van crews, inclusief een contactpersoon.
** Beheren van een publieke lijst van lopende projecten, inclusief een contactpersoon.
** Beheren van een publieke lijst van resource centers.
** Oproepen van elke piraat, squad, crew, coreteam of projectvertegenwoordiger om naar informatie over hun activiteiten te vragen.
* De Coördinatie-squad dient als een "orakel" voor piraten. Hiermee wordt bedoeld dat iedere piraat met een bepaalde behoefte of vraag contact kan opnemen met de Coördinatie-squad. Er wordt dan van de Coördinatie-squad verwacht hem/haar in contact te brengen met de juiste piraat om hem/haar te helpen.
* De Coördinatie-squad deelt zijn kennis van de interne werking van de partij actief en regelmatig met de piraten.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-left:5px; border-radius:5px" |
'''Translation needed'''
==== Équipages ====
Voir les statuts actuels.
* '''Le rôle du capitaine est centré autour des membres de l'équipage et de la dynamique du groupe.'''
* '''Le rôle du navigateur est centré autour des tâches administratives.'''

==== Projets ====

* '''Chaque pirate peut lancer un projet qui respecte les statuts et les buts généraux du parti.'''
* '''Chaque pirate lançant un projet doit contacter la squad de coordination avec les informations suivantes : une description du projet et une personne de contact.'''
* '''La squad de coordination enregistre dans les faits le projet après avoir vérifié qu'il respecte les statuts et les valeurs du parti.'''
* '''Tout projet qui n'a pas été déclaré à la squad de coordination n'est, de facto, pas pris en charge par le parti.'''
* '''Si le projet s'achève ou si il est en pause, la personne de contact du projet doit en informer la squad de coordination.'''
* '''(OPT) Tout projet doit être publiquement présenté sur une page web.'''

==== Resource centers ====
* '''Un centre de ressource est un annuaire listant des pirates ayant des compétences particulières ou des connaissances sur un sujet en particulier. Il pourrait contenir d'autres informations en relation avec ses thèmes, tels qu'une documentation, une liste d'experts, etc.'''

==== Squads ====
* '''Les entités suivantes, désignées par le nom de squads, devraient être nommées comme suit:'''
** squad
** ?

* '''Il existe exactement 9 squads au sein du parti. Lesquelles sont:'''
** Coaching
** Coordination
** Coreteam
** Finance
** AG
** IT
** Presse
** Secrétariat
** Wiki

'''Les rôles de chaque squad sont décrits dans les sections suivantes.'''

* '''Il y a deux moyens pour un pirate de devenir membre d'une squad.'''
*# '''Être approuvé par une motion de confiance lors d'une AG.'''
*# '''Être unanimement approuvé par les membres actuels de la squad. Dans ce cas, cette décision doit être clairement annoncée à tous les pirates.'''
* '''Il y a deux moyens pour un membre d'une squad d'en sortir:'''
*# '''Démission.'''
*# '''Une motion de confiance lors de l'AG échoue.'''
* '''Chaque squad contient un minimum de deux membres.'''
* '''Lors de la première AG de l'année, chaque squad présentes un rapport d'activité et une motion de confiance est votée. Si elle échoue pour une squad donnée, une motion de confiance est votée pour chacun des membres à la fois.'''
* '''Chaque candidature à une squad doit suivre une procédure encore à définir.'''

===== Coaching =====
*''' La squad Coaching a les compétences exclusives qui suivent :'''
**''' Accueillir les nouveaux membres.'''
**''' Diffuser les lignes directrices.'''
**''' Fournir la documention et les ressources aux nouveaux venus.'''
**''' ''À compléter.'' '''

===== Coordination =====
*''' La squad de coordination a les compétences exclusives qui suivent :'''
**''' Gérer les courriels entrant de l'adresse de contact contact@pirateparty.be. « Gérer » signifie transférer à la bonne personne pour réponse.'''
**''' Maintenir une liste publique des équipages, y compris une personne de contact.'''
**''' Maintenir une liste publique des projets en cours, y compris une personne de contact.'''
**''' Maintenir une liste publique des centres de ressource.'''
**''' Convoquer n'importe quel pirate, squad, équipage, coreteam ou représentant de projet afin de demander des informations sur leur activités.
*''' La squad de coordination sert d' « oracle » pour les pirates. Cela signifie que chaque pirate ayant un besoin particulier ou une question peut contacter la squad de coordination. On attend ensuite de la squad de coordination de le/la mettre en contact avec le pirate qui saura l'aider.'''
*''' La squad de coordination partage activemment et régulièrement sa connaissance des affaires internes du parti aux pirates.'''

===== Coreteam =====
* '''Toute décision de la coreteam doit être communiquée à tous les pirates.'''
* '''La coreteam possède les compétences exclusives qui suivent:'''
** '''Gérer le budget du parti. La mise en œuvre du budget est laissée à la squad finance.'''
** '''Désigner les délégués pour l'international.'''
** '''''À compléter'''''

===== Finance =====
*''' Les membres et seulement les membres de la squad Finance ont accès aux comptes bancaires du parti.'''
*''' La squad Finance a les compétences exclusives qui suivent :'''
**''' Mettre en oeuvre le budget approuvé par l'Assemblée Générale.'''
*''' Les finances seront surveillées par un groupe de contrôle.'''
*''' Les revenu et dépense doivent être visibles à n'importe quel moment et par n'importe quand.'''

===== AG =====
*''' La squad AG organise les assemblées générales.'''
*''' La squad AG a les compétences exclusives qui suivent :'''
**''' S'assurer que le protocole de l'AG est correctement suivi.'''
**''' Rassembler toutes les propositions et amendements faites par les membres.'''
**''' Préparer tous les documents relatifs au vote.'''
***''' S'assurer que les documents sont traduits.'''
**''' Publier les statusts.'''
**''' Recueillir la motion de confiance.'''

===== IT =====
*''' Les membres et seulements les membres de la squad IT ont accès aux serveurs du parti, à l'exception des membres de la squad Wiki, qui a un accès limité à ceux-ci, comme décrit dans la section correspondante.'''
*''' ''À détailler.'' '''

===== Presse =====
*''' La squad Presse a les compétences exclusives qui suivent :'''
**''' Parler au nom du parti à la presse.'''
**''' Réagir aux nouvelles en publiant des communiqués de presse.'''
**''' ''À détailler.'' '''

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
|}

= Set n°3 =
* (as discussed in the refactoring lab of 5/07).

A thinking process has to be implemented between the present and the next GA in order to discuss,
amongst all pirates, about a possible change of the name of our "Pirate Party" and our goals (a manifesto).

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set3
<eplite id=ga201408-amendments-set3></eplite>

= Set n°4 =

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

'''Original'''

Teneinde de ground-up filosofie van de partij nog beter in haar organisatiestruktuur te weerspiegelen en de transparantie te verhogen, stellen wij voor om het coreteam af te schaffen en te vervangen door twee nieuwe, duidelijk van elkaar ondescheiden, instanties: het secretariaat en het coördinatie comité.

=== Het secretariaat ===
==== Functieomschrijving ====
*Het (nationaal) secretariaat is een louter administratief orgaan dat enkel instaat voor secretariaatstaken zoals: het ledenbeheer, de administratie, de (nationale) financiën, het beheer van de vzw, ed.
*Het is een louter uitvoerende instantie, zonder beslissingsbevoegdheid.
*Het secretariaat neemt van het oude coreteam de taken schatbewaarder, secretaris en IT over.

==== Leden ====
* Het (nationaal) secretariaat bestaat uit piraten die zich daarvoor op de GA kandidaat stellen, en uit piraten die, op grond van hun specifieke expertise, gevraagd worden om bepaalde taken uit te voeren.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het secretariaat intern over haar werking en de acties die ze uitvoert.

=== Het coördinatie-comité ===
==== Functieomschrijving ====
* Het coördinatie comité is in de eerste plaats een overlegorgaan tussen de verschillende crews (een raad van de crews).
* Het coördinatie comité bevordert de communicatie tussen de verschillende crews, verzamelt en verspreidt partijinformatie tussen de crews onderling en tussen de crews en het nationale en internationale niveau, stimuleert de discussie over de werking en toekomst van de partij, stelt de agenda voor de GA voor en staat in voor het dringend dagelijks bestuur van de partij.
* Het coördinatie comité is geen “leidende” instantie, het is een overlegorgaan tussen de crews, dat enkel bevoegd is om dringende beslissingen te nemen in functie van het dagelijks bestuur van de partij.
* Het coördinatie comité heeft geen beslissingsbevoegdheid mbt de inhoudelijke oriëntatie of organisatie van de partij, die bevoegdheden heeft enkel de GA.
* Het coördinatiecomité neemt van het oude coreteam de taken integratie, coördinatie, internationale betrekkingen en pers over.

==== Leden ====
* Het coördinatie comité bestaat uit één afgevaardigde van elke crew.
* De crews duiden op de GA hun vertegenwoordiger aan, deze blijft in functie tot de volgende GA. Indien nodig kan een crew zich door iemand anders laten vertegenwoordigen.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het comité intern over haar werking en de acties die ze uitvoert.
*De vergaderingen van het coördinatie comité zijn open voor elk lid van de partij, maar bij een eventuele stemming in functie van het dringend dagelijks bestuur, hebben enkel de vertegenwoordigers van een crew stemrecht.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

'''FR translation (complete)'''

Dans le souci d'accroître la transparence du parti et de mieux refléter la philosophie "ground-up" dans sa structure, nous proposons de supprimer la coreteam et de la remplacer par deux nouvelles instances, clairement distinctes l'une de l'autre : le secrétariat et le comité de coordination.

=== Le secrétatiat ===
==== Description des fonctions ====
* Le secrétariat (national) est un organe purement administratif traitant exclusivement de tâches de secrétariat telles que la gestion des membres, l'administration, les finances (nationales), la gestion de l'asbl, etc.
* C'est une instance purement exécutive, sans compétence décisionnelle.
* Le secrétariat reprend de la coreteam actuelle les tâches de trésorier, secrétaire et gestion de l'IT.

==== Membres ====
* Le secrétariat (national) se compose de pirates se présentant comme candidat à l'AG ainsi que de pirates qui, du fait de leur expertise, sont invités à exécuter certaines tâches déterminées.

==== Fonctionnement ====
* Le secrétariat décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.

=== Le comité de coordination ===
==== Description des fonctions ====
* Le comité de coordination est avant tout un organe de concertation entre les équipages (un conseil d'équipage).
* Le comité de coordination favorise la communication entre les équipages, collecte et répand toute information relative au parti entre les équipages et entre les équipages et les niveaux nationaux et internationaux, stimule les discussions relatives au fonctionnement et à l'avenir du parti, propose l'agenda de l'AG et traite des affaires courantes du parti.
* Le comité de coordination n'est pas une instance dirigeante mais un organe de concertation entre équipages, uniquement autorisé à prendre des décisions urgentes concernant la gestion quotidienne du parti.
* Le comité de coordination n'a aucune compétence décisionnelle concernant l'orientation idéologique ou l'organisation du parti. Seule l'AG dispose de ces compétences.
* Le comité de coordination reprend de la coreteam actuelle les tâches d'intégration et de coordination, les relations internationales et la presse.

==== Membres ====
* Le comité de coordination se compose d'un délégué issu de chaque équipage.
* Les équipages font part de leur délégué à l'AG. Ceux-ci restent en fonction jusqu'à la prochaine AG. En cas de nécessité, un équipage peut se faire représenter par quelqu'un d'autre.

==== Fonctionnement ====
* Le comité de coordination décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.
* Les réunions du comité de coordination sont ouvertes à tout membre du parti, bien que seuls les représentants de chaque équipage peuvent participer aux votes organisés dans le cadre de la gestion des affaires courantes.
|-
|}

=== Discussion pad ===

Direct link to the pad: http://www.piratepad.be/p/voorstel

<eplite id=voorstel></eplite>

== Set n°5 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/coreteam_GA_proposals
<eplite id=coreteam_GA_proposals></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

=== Original ===

In case of an internal conflict which may harm the party, the coreteam may start a conflict resolution procedure with a simple majority vote. The conflict resolution procedure consists of:
* The coreteam may temporarily suspend one or more parties involved for a maximum of two months or until the procedure has ended, whichever comes first.
* The coreteam shall determine the intially involved parties in the conflict.
* The coreteam shall assemble a conflict resolution group, consisting of:
** 5 randomly selected Pirate party members which were present during the last GA. If a selected Pirate declines the invitation, a replacement will be found.
** Coreteam members and parties involved in the conflict are automatically excluded.
** The conflict resolution group shall contain a minimum of 2 speakers of the language of the involved parties.
* The conflict resolution group may decide to not address the conflict, in case it is deemed frivolous or otherwise has become irrelevant.
* The conflict resolution group may attempt to resolve the conflict in mediation with the involved parties. Mediation is considered succesful if all involved parties agree.
* The conflict resolution group may ultimately decide to:
** Formally reprimand one or more parties, either internally (with the involved parties) or publically within the party.
** Eject one or more parties from any of their currently held Pirate functions.
** Suspend one or more parties, for a maximum duration of 12 months.
** Exclude one or more party from the Pirate Party Belgium and any of its activities.
* In case of suspension or exclusion, the coreteam has to confirm the sanction by simple majority.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction à vérifier ===

'''Au cas où un conflit interne pouvant nuire au parti surgit, la Coreteam peut entamer une procédure de résolution de conflit avec un simple vote à la majorité. Cette procédure de résolution de conflit consiste en ceci :

*La Coreteam peut suspendre une ou plusieurs des parties impliquées durant deux mois maximum ou jusqu’à ce que la procédure prenne fin, selon ce qui advient en premier.
*La Coreteam déterminera les parties initialement impliquées dans le conflit.
*La Coreteam réunira un groupe de résolution de conflit, qui consiste en ceci :
**5 membres pirates pris au hasard parmi les membres présents durant la dernière AG. Si un pirate sélectionné décline l’invitation, un remplaçant doit être trouvé.
**Les personnes impliquées dans le conflit sont automatiquement exclus
**Le groupe de résolution de conflit contiendra au minimum deux locuteurs de la langue des parties impliquées.
*Le groupe de résolution de conflit peut décider de ne pas s’occuper du conflit, dans la mesure où il est jugé frivole ou aucunement important.
*Le groupe de résolution de conflit peut essayer de résoudre le conflit par la médiation des parties impliquées. La médiation est considérée comme réussie si toutes les parties sont d’accord.
*Le groupe de résolution de conflit peut, en dernier recours, décider de :
*Réprimander formellement une ou plusieurs parties, aussi bien en interne (avec les parties impliquées) que publiquement au sein du parti.
**Retirer une ou plusieurs parties de ses fonctions au sein du parti
**Suspendre une ou plusieurs parties, pour une durée de 12 mois.
**Exclure une ou plusieurs parties du Parti Pirate de Belgique et de ses activités.
*En cas de suspension ou d’exclusion, la Coreteam doit confirmer la sanction par vote à simple majorité.'''
|-
|}

Events/EGA:2014-08/Amendments

2014-07-21T19:01:06Z

Manu: /* Fonctionnement */ ortho

= Intro =

==== EN ====
This is the page dedicated to the preparation of the texts that will be voted during our next G.A.
We have received these proposals according to our protocol, available there: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

==== FR ====
Ceci est la page dédiée à la préparation des textes qui seront votés en Assemblée Générale.
Nous avons reçu ces propositions en conformité avec notre protocole, disponible ici: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

= Existing Statutes =

[[Statutes|Existing Statutes - Statuten - Statuts]]

= Proposals to amend =

== Intro ==

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Translation :'''

In the context of translating the statutes, here is the convention to respect in order to keep the work clear :

The translations are made in '''bold'''.

The corrections of the text are made in ''italic''.

The finalisation after proofreading is made in normal.

'''Amendments :'''

Every amendment is written under the proposal to amend, with sub(-sub)-bullet and signature (name and date) of the pirate who's amending.

Example :
* Every pirate can start a project that respects the statutes and the general goals of the party.
** Every pirate can start a project that respects the statutes and the general goals of the party, except during an eclipse of sun. [[User:Alexis|Alexis]] ([[User talk:Alexis|talk]]) 12:30, 20 July 2014 (CEST)

Code :

<nowiki>** Amendment. ~~~~</nowiki>

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Traduction :'''

Dans le cadre de la traduction des statuts, voici la convention à respecter afin de garder une certaine visibilité :

Les traductions se font en '''gras'''.

Les corrections à un texte se font en ''italique''.

La finalisation après relecture se fait en normal.

'''Amendements :'''

Chaque amendement se fait sous l'article à amender, en sous(-sous)-point, avec signature (nom et date) du pirate qui a amendé.

Exemple :
* Every pirate can start a project that respects the statutes and the general goals of the party.
** Every pirate can start a project that respects the statutes and the general goals of the party, except during an eclipse of sun. [[User:Alexis|Alexis]] ([[User talk:Alexis|talk]]) 12:30, 20 July 2014 (CEST)

Code :

<nowiki>** Amendement. ~~~~</nowiki>
|}

== Set n°1 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set1
<eplite id=ga201408-amendments-set1></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
=== Original ===
* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction à vérifier ===

* '''Les escouades responsables de la communication numérique du parti, ont le droit de modérer les canaux et ''de'' refuser, le cas échéant, l'accès à ces canaux.'''

*''' Pour tous les mandats, la rétrocession au parti s'élève à 22,5% de la rémunération brute. Si l'élu en question n'a pas de revenu de toute autre profession, une pension ou un revenu de remplacement, le montant des rétrocessions est à 17,5% de la rémunération brute.'''

*''' La cotisation ''des membres'' est de 2,5 € par mois. La coreteam peut, dans des cas exceptionnels, décider qu'une personne n'a pas à payer les frais d'adhésion.'''

*''' A chaque assemblée générale, la coreteam est élue lors d'un vote de confiance. Tous les candidats de la coreteam sont placés sur une liste. Ensuite les membres votent secrètement ''l'approbation'' ou non de chacun des candidats. Tous les candidats ayant reçu la confiance de la majorité du parti sont élus. S'il y a plus de 10 élus, les membres ayant reçu le plus de votes de confiance rejoignent la coreteam, ensuite les candidats ayant le moins d'années d'expérience.'''

*''' Nous allons retravailler les statuts, pour que le Parti Pirate, devienne une a.s.b.l. Les éléments importants pour les tiers sont déplacés dans les statuts de l'association, et tous les éléments du fonctionnement interne dans un règlement interne. Ce changement radical dans la structure sera ensuite présenté concrètement à l'assemblée générale.'''

'''Commission de conciliation et de discipline'''

'''§X. L'autorité de l'Assemblée Générale doit être reconnue et respectée par tous les membres. Les personnes qui sapent l'autorité de l'Assemblée Générale, qui refusent de se soumettre aux décisions établies, ou qui par leur comportement ou attitude causent du trouble ou des dommages au parti, peuvent être suspendus de leurs fonctions.'''

'''§X. Les organes qui refusent de reconnaître l'autorité de l'Assemblée Générale, ou qui entreprennent des actions qui causent du trouble ou des dommages au parti, peuvent être suspendus de manière collective.'''

'''§X. La suspension d'organes ou de membres est le fait d'une procédure de conciliation et de discipline, qui elle-même est initiée par une entité à l'encontre de cet organe ou de ce membre.'''

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

'''§X. Toutes les plaintes et éléments en cours sont traités de manière publique et transparente, mais avec le respect de la vie privée des personnes concernées.'''
'''
§X. La commission nationale de conciliation et discipline est composée de 5 membres tirés au sort pour le cas parmi les membres ayant pris part l'assemblée générale précédente, éventuellement par procuration.'''

'''Pour chaque membre, un remplaçant est également tiré au sort.'''

'''Au cas où un membre effectif ne pourrait être présent, le secrétariat contactera un remplaçant. Il ne peut y avoir maximum que 1 membre représentant une province. Il sera assuré qu'au moins 2 personnes parlant la même langue que les parties concernées seront présentes.'''

'''Le secrétaire de la coreteam est un membre supplémentaire de la commission de conciliation et discipline, le sixième, et sans droit de vote. Il décide lui-même de la nécessité de sa présence.'''

'''§X. Un membre de la commission de conciliation et discipline qui serait lui-même impliqué dans une procédure ne peut pas y sièger. Les membres de la coreteam, à l'exception du secrétaire, ne peuvent pas faire partie de la commission.'''

'''§X. Une réunion de la commission n'est considérée comme valide que si au moins la moitié de ses membres sont présents.'''

'''§X. La commission est renouvelée pour chaque nouveau cas.'''

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

|-
|}

== Set n°2 ==

=== Discussion pad ===

Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set2
<eplite id=ga201408-amendments-set2></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Original'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squad organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidence.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-center:5px; border-radius:5px" |
'''Translation ongoing (David L.)'''
==== Crews ====
Zie huidige statuten.
* De rol van kapitein richt zich op de leden van de crew en de groepsdynamiek.
* De rol van navigator richt zich op administratieve taken.

==== Projecten ====

* Elke piraat kan een project dat de statuten en de algemene doelen van de partij respecteert starten.
* Elke piraat die een project start moet de coördinatie-squad contacteren met de volgende informatie: een beschrijving van het project en een contactpersoon.
* De coördinatie-squad registreert het project formeel na verificatie dat het de statuten en de waarden van de partij respecteert.
* Elk project dat niet aangegeven werd aan de coördinatie-squad is de facto niet onderschreven door de partij.
* Als het project beëindigd of in stand-by is, moet de contactpersoon van het project dit melden aan de coördinatie-squad.
* (OPT) Elk project moet publiek worden voorgesteld op een webpagina.

==== Resource centers ====
* Een resource center is een repertorium dat piraten met specifieke vaardigheden of kennis rond een specifiek onderwerp oplijst. Het kan andere informatie gerelateerd met zijn thema bevatten, zoals doumentatie, een lijst van experten, enz.

==== Squads ====
* De volgende entiteiten, gerefereerd door squads moeten als volgt worden benoemd:
** squads
** ?

* Er zijn exact 9 squads in de partij. Dit zijn:
** Coaching
** Coördinatie
** Coreteam
** Financiën
** AV
** IT
** Pers
** Secretariaat
** Wiki

De rollen van elke squad worden beschreven in de volgende secties.

* Er zijn twee manieren voor een piraat om lid te worden van een squad:
*# Goedgekeurd worden door een motie van vertrouwen op een AV.
*# Unaniem goedgekeurd worden door de huidige leden van de squad. In dit geval moet deze beslissing actief aangekondigd worden naar alle piraten.
* Er zijn twee manieren voor een lid van een squad om deze te verlaten:
*# Aftreden.
*# Falen in een motie van vertrouwen op een AV.
* Elke squad bestaat uit minstens twee leden.
* Op de eerste AV van elk jaar presenteert elke squad een activiteitenraport en er wordt opgeroepen tot een motie van vertrouwen. Indien de motie faalt voor een bepaalde squad wordt er opgeroepen tot een een motie van vertrouwen voor elk van zijn leden.
* Elke kandidaat voor een squad moet een nog te bepalen procedure volgen.

===== Coaching =====
* De Coaching-squad heeft de volgende exclusieve bevoegdheden:
** Verwelkomen van nieuwe leden.
** Richtlijnen verspreiden.
** Documentatie en middelen aanbieden aan nieuwe leden.
** ''Aan te vullen''

===== Coördinatie =====
* De Coördinatie-squad heeft de volgende exclusieve bevoegdheden:
** Inkomende email op het contactadres contact@pirateparty.be beheren. Onder "beheren" wordt verstaan het forwarden naar de juiste persoon die kan antwoorden.
** Beheren van een publieke lijst van crews, inclusief een contactpersoon.
** Beheren van een publieke lijst van lopende projecten, inclusief een contactpersoon.
** Beheren van een publieke lijst van resource centers.
** Oproepen van elke piraat, squad, crew, coreteam of projectvertegenwoordiger om naar informatie over hun activiteiten te vragen.
* De Coördinatie-squad dient als een "orakel" voor piraten. Hiermee wordt bedoeld dat iedere piraat met een bepaalde behoefte of vraag contact kan opnemen met de Coördinatie-squad. Er wordt dan van de Coördinatie-squad verwacht hem/haar in contact te brengen met de juiste piraat om hem/haar te helpen.
* De Coördinatie-squad deelt zijn kennis van de interne werking van de partij actief en regelmatig met de piraten.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-left:5px; border-radius:5px" |
'''Translation needed'''
==== Équipages ====
Voir les statuts actuels.
* '''Le rôle du capitaine est centré autour des membres de l'équipage et de la dynamique du groupe.'''
* '''Le rôle du navigateur est centré autour des tâches administratives.'''

==== Projets ====

* '''Chaque pirate peut lancer un projet qui respecte les statuts et les buts généraux du parti.'''
* '''Chaque pirate lançant un projet doit contacter la squad de coordination avec les informations suivantes : une description du projet et une personne de contact.'''
* '''La squad de coordination enregistre dans les faits le projet après avoir vérifié qu'il respecte les statuts et les valeurs du parti.'''
* '''Tout projet qui n'a pas été déclaré à la squad de coordination n'est, de facto, pas pris en charge par le parti.'''
* '''Si le projet s'achève ou si il est en pause, la personne de contact du projet doit en informer la squad de coordination.'''
* '''(OPT) Tout projet doit être publiquement présenté sur une page web.'''

==== Resource centers ====
* '''Un centre de ressource est un annuaire listant des pirates ayant des compétences particulières ou des connaissances sur un sujet en particulier. Il pourrait contenir d'autres informations en relation avec ses thèmes, tels qu'une documentation, une liste d'experts, etc.'''

==== Squads ====
* '''Les entités suivantes, désignées par le nom de squads, devraient être nommées comme suit:'''
** squad
** ?

* '''Il existe exactement 9 squads au sein du parti. Lesquelles sont:'''
** Coaching
** Coordination
** Coreteam
** Finance
** AG
** IT
** Presse
** Secrétariat
** Wiki

'''Les rôles de chaque squad sont décrits dans les sections suivantes.'''

* '''Il y a deux moyens pour un pirate de devenir membre d'une squad.'''
*# '''Être approuvé par une motion de confiance lors d'une AG.'''
*# '''Être unanimement approuvé par les membres actuels de la squad. Dans ce cas, cette décision doit être clairement annoncée à tous les pirates.'''
* '''Il y a deux moyens pour un membre d'une squad d'en sortir:'''
*# '''Démission.'''
*# '''Une motion de confiance lors de l'AG échoue.'''
* '''Chaque squad contient un minimum de deux membres.'''
* '''Lors de la première AG de l'année, chaque squad présentes un rapport d'activité et une motion de confiance est votée. Si elle échoue pour une squad donnée, une motion de confiance est votée pour chacun des membres à la fois.'''
* '''Chaque candidature à une squad doit suivre une procédure encore à définir.'''

===== Coaching =====
*''' La squad Coaching a les compétences exclusives qui suivent :'''
**''' Accueillir les nouveaux membres.'''
**''' Diffuser les lignes directrices.'''
**''' Fournir la documention et les ressources aux nouveaux venus.'''
**''' ''À compléter.'' '''

===== Coordination =====
*''' La squad de coordination a les compétences exclusives qui suivent :'''
**''' Gérer les courriels entrant de l'adresse de contact contact@pirateparty.be. « Gérer » signifie transférer à la bonne personne pour réponse.'''
**''' Maintenir une liste publique des équipages, y compris une personne de contact.'''
**''' Maintenir une liste publique des projets en cours, y compris une personne de contact.'''
**''' Maintenir une liste publique des centres de ressource.'''
**''' Convoquer n'importe quel pirate, squad, équipage, coreteam ou représentant de projet afin de demander des informations sur leur activités.
*''' La squad de coordination sert d' « oracle » pour les pirates. Cela signifie que chaque pirate ayant un besoin particulier ou une question peut contacter la squad de coordination. On attend ensuite de la squad de coordination de le/la mettre en contact avec le pirate qui saura l'aider.'''
*''' La squad de coordination partage activemment et régulièrement sa connaissance des affaires internes du parti aux pirates.'''

===== Coreteam =====
* '''Toute décision de la coreteam doit être communiquée à tous les pirates.'''
* '''La coreteam possède les compétences exclusives qui suivent:'''
** '''Gérer le budget du parti. La mise en œuvre du budget est laissée à la squad finance.'''
** '''Désigner les délégués pour l'international.'''
** '''''À compléter'''''

===== Finance =====
*''' Les membres et seulement les membres de la squad Finance ont accès aux comptes bancaires du parti.'''
*''' La squad Finance a les compétences exclusives qui suivent :'''
**''' Mettre en oeuvre le budget approuvé par l'Assemblée Générale.'''
*''' Les finances seront surveillées par un groupe de contrôle.'''
*''' Les revenu et dépense doivent être visibles à n'importe quel moment et par n'importe quand.'''

===== AG =====
*''' La squad AG organise les assemblées générales.'''
*''' La squad AG a les compétences exclusives qui suivent :'''
**''' S'assurer que le protocole de l'AG est correctement suivi.'''
**''' Rassembler toutes les propositions et amendements faites par les membres.'''
**''' Préparer tous les documents relatifs au vote.'''
***''' S'assurer que les documents sont traduits.'''
**''' Publier les statusts.'''
**''' Recueillir la motion de confiance.'''

===== IT =====
*''' Les membres et seulements les membres de la squad IT ont accès aux serveurs du parti, à l'exception des membres de la squad Wiki, qui a un accès limité à ceux-ci, comme décrit dans la section correspondante.'''
*''' ''À détailler.'' '''

===== Presse =====
*''' La squad Presse a les compétences exclusives qui suivent :'''
**''' Parler au nom du parti à la presse.'''
**''' Réagir aux nouvelles en publiant des communiqués de presse.'''
**''' ''À détailler.'' '''

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
|}

= Set n°3 =
* (as discussed in the refactoring lab of 5/07).

A thinking process has to be implemented between the present and the next GA in order to discuss,
amongst all pirates, about a possible change of the name of our "Pirate Party" and our goals (a manifesto).

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set3
<eplite id=ga201408-amendments-set3></eplite>

= Set n°4 =

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

'''Original'''

Teneinde de ground-up filosofie van de partij nog beter in haar organisatiestruktuur te weerspiegelen en de transparantie te verhogen, stellen wij voor om het coreteam af te schaffen en te vervangen door twee nieuwe, duidelijk van elkaar ondescheiden, instanties: het secretariaat en het coördinatie comité.

=== Het secretariaat ===
==== Functieomschrijving ====
*Het (nationaal) secretariaat is een louter administratief orgaan dat enkel instaat voor secretariaatstaken zoals: het ledenbeheer, de administratie, de (nationale) financiën, het beheer van de vzw, ed.
*Het is een louter uitvoerende instantie, zonder beslissingsbevoegdheid.
*Het secretariaat neemt van het oude coreteam de taken schatbewaarder, secretaris en IT over.

==== Leden ====
* Het (nationaal) secretariaat bestaat uit piraten die zich daarvoor op de GA kandidaat stellen, en uit piraten die, op grond van hun specifieke expertise, gevraagd worden om bepaalde taken uit te voeren.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het secretariaat intern over haar werking en de acties die ze uitvoert.

=== Het coördinatie-comité ===
==== Functieomschrijving ====
* Het coördinatie comité is in de eerste plaats een overlegorgaan tussen de verschillende crews (een raad van de crews).
* Het coördinatie comité bevordert de communicatie tussen de verschillende crews, verzamelt en verspreidt partijinformatie tussen de crews onderling en tussen de crews en het nationale en internationale niveau, stimuleert de discussie over de werking en toekomst van de partij, stelt de agenda voor de GA voor en staat in voor het dringend dagelijks bestuur van de partij.
* Het coördinatie comité is geen “leidende” instantie, het is een overlegorgaan tussen de crews, dat enkel bevoegd is om dringende beslissingen te nemen in functie van het dagelijks bestuur van de partij.
* Het coördinatie comité heeft geen beslissingsbevoegdheid mbt de inhoudelijke oriëntatie of organisatie van de partij, die bevoegdheden heeft enkel de GA.
* Het coördinatiecomité neemt van het oude coreteam de taken integratie, coördinatie, internationale betrekkingen en pers over.

==== Leden ====
* Het coördinatie comité bestaat uit één afgevaardigde van elke crew.
* De crews duiden op de GA hun vertegenwoordiger aan, deze blijft in functie tot de volgende GA. Indien nodig kan een crew zich door iemand anders laten vertegenwoordigen.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het comité intern over haar werking en de acties die ze uitvoert.
*De vergaderingen van het coördinatie comité zijn open voor elk lid van de partij, maar bij een eventuele stemming in functie van het dringend dagelijks bestuur, hebben enkel de vertegenwoordigers van een crew stemrecht.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

'''FR translation (complete)'''

Dans le souci d'accroître la transparence du parti et de mieux refléter la philosophie "ground-up" dans sa structure, nous proposons de supprimer la coreteam et de la remplacer par deux nouvelles instances, clairement distinctes l'une de l'autre : le secrétariat et le comité de coordination.

=== Le secrétatiat ===
==== Description des fonctions ====
* Le secrétariat (national) est un organe purement administratif traitant exclusivement de tâches de secrétariat telles que la gestion des membres, l'administration, les finances (nationales), la gestion de l'asbl, etc.
* C'est une instance purement exécutive, sans compétence décisionnelle.
* Le secrétariat reprend de la coreteam actuelle les tâches de trésorier, secrétaire et gestion de l'IT.

==== Membres ====
* Le secrétariat (national) se compose de pirates se présentant comme candidat à l'AG ainsi que de pirates qui, du fait de leur expertise, sont invités à exécuter certaines tâches déterminées.

==== Fonctionnement ====
* Le secrétariat décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.

=== Le comité de coordination ===
==== Description des fonctions ====
* Le comité de coordination est avant tout un organe de concertation entre les équipages (un conseil d'équipage).
* Le comité de coordination favorise la communication entre les équipages, collecte et répand toute information relative au parti entre les équipages et entre les équipages et les niveaux nationaux et internationaux, stimule les discussions relatives au fonctionnement et à l'avenir du parti, propose l'agenda de l'AG et traite des affaires courantes du parti.
* Le comité de coordination n'est pas une instance dirigeante mais un organe de concertation entre équipages, uniquement autorisé à prendre des décisions urgentes concernant la gestion quotidienne du parti.
* Le comité de coordination n'a aucune compétence décisionnelle concernant l'orientation idéologique ou l'organisation du parti. Seule l'AG dispose de ces compétences.
* Le comité de coordination reprend de la coreteam actuelle les tâches d'intégration et de coordination, les relations internationales et la presse.

==== Membres ====
* Le comité de coordination se compose d'un délégué issu de chaque équipage.
* Les équipages font part de leur délégué à l'AG. Ceux-ci restent en fonction jusqu'à la prochaine AG. En cas de nécessité, un équipage peut se faire représenter par quelqu'un d'autre.

==== Fonctionnement ====
* Le comité de coordination décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.
* Les réunions du comité de coordination sont ouvertes à tout membre du parti, bien que seuls les représentants de chaque équipage peuvent participer aux votes organisés dans le cadre de la gestion des affaires courantes.
|-
|}

=== Discussion pad ===

Direct link to the pad: http://www.piratepad.be/p/voorstel

<eplite id=voorstel></eplite>

== Set n°5 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/coreteam_GA_proposals
<eplite id=coreteam_GA_proposals></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

=== Original ===

In case of an internal conflict which may harm the party, the coreteam may start a conflict resolution procedure with a simple majority vote. The conflict resolution procedure consists of:
* The coreteam may temporarily suspend one or more parties involved for a maximum of two months or until the procedure has ended, whichever comes first.
* The coreteam shall determine the intially involved parties in the conflict.
* The coreteam shall assemble a conflict resolution group, consisting of:
** 5 randomly selected Pirate party members which were present during the last GA. If a selected Pirate declines the invitation, a replacement will be found.
** Coreteam members and parties involved in the conflict are automatically excluded.
** The conflict resolution group shall contain a minimum of 2 speakers of the language of the involved parties.
* The conflict resolution group may decide to not address the conflict, in case it is deemed frivolous or otherwise has become irrelevant.
* The conflict resolution group may attempt to resolve the conflict in mediation with the involved parties. Mediation is considered succesful if all involved parties agree.
* The conflict resolution group may ultimately decide to:
** Formally reprimand one or more parties, either internally (with the involved parties) or publically within the party.
** Eject one or more parties from any of their currently held Pirate functions.
** Suspend one or more parties, for a maximum duration of 12 months.
** Exclude one or more party from the Pirate Party Belgium and any of its activities.
* In case of suspension or exclusion, the coreteam has to confirm the sanction by simple majority.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction à vérifier ===

'''Au cas où un conflit interne pouvant nuire au parti surgit, la Coreteam peut entamer une procédure de résolution de conflit avec un simple vote à la majorité. Cette procédure de résolution de conflit consiste en ceci :

*La Coreteam peut suspendre une ou plusieurs des parties impliquées durant deux mois maximum ou jusqu’à ce que la procédure prenne fin, selon ce qui advient en premier.
*La Coreteam déterminera les parties initialement impliquées dans le conflit.
*La Coreteam réunira un groupe de résolution de conflit, qui consiste en ceci :
**5 membres pirates pris au hasard parmi les membres présents durant la dernière AG. Si un pirate sélectionné décline l’invitation, un remplaçant doit être trouvé.
**Les personnes impliquées dans le conflit sont automatiquement exclus
**Le groupe de résolution de conflit contiendra au minimum deux locuteurs de la langue des parties impliquées.
*Le groupe de résolution de conflit peut décider de ne pas s’occuper du conflit, dans la mesure où il est jugé frivole ou aucunement important.
*Le groupe de résolution de conflit peut essayer de résoudre le conflit par la médiation des parties impliquées. La médiation est considérée comme réussie si toutes les parties sont d’accord.
*Le groupe de résolution de conflit peut, en dernier recours, décider de :
*Réprimander formellement une ou plusieurs parties, aussi bien en interne (avec les parties impliquées) que publiquement au sein du parti.
**Retirer une ou plusieurs parties de ses fonctions au sein du parti
**Suspendre une ou plusieurs parties, pour une durée de 12 mois.
**Exclure une ou plusieurs parties du Parti Pirate de Belgique et de ses activités.
*En cas de suspension ou d’exclusion, la Coreteam doit confirmer la sanction par vote à simple majorité.'''
|-
|}

Events/EGA:2014-08/Amendments

2014-07-13T14:41:14Z

Manu: /* Set n°4 */ translation completed

= Intro =

==== EN ====
This is the page dedicated to the preparation of the texts that will be voted during our next G.A.
We have received these proposals according to our protocol, available there: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

==== FR ====
Ceci est la page dédiée à la préparation des textes qui seront votés en Assemblée Générale.
Nous avons reçu ces propositions en conformité avec notre protocole, disponible ici: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

= Existing Statutes =

[[Statutes|Existing Statutes - Statuten - Statuts]]

= Proposals to amend =

== Set n°1 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set1
<eplite id=ga201408-amendments-set1></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
=== Original ===
* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction nécessaire ===

* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

|-
|}

== Set n°2 ==

=== Discussion pad ===

Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set2
<eplite id=ga201408-amendments-set2></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Original'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-center:5px; border-radius:5px" |
'''Translation ongoing (David L.)'''
==== Crews ====
Zie huidige statuten.
* De rol van kapitein richt zich op de leden van de crew en de groepsdynamiek.
* De rol van navigator richt zich op administratieve taken.

==== Projecten ====

* Elke piraat kan een project dat de statuten en de algemene doelen van de partij respecteert starten.
* Elke piraat die een project start moet de coördinatie-squad contacteren met de volgende informatie: een beschrijving van het project en een contactpersoon.
* De coördinatie-squad registreert het project formeel na verificatie dat het de statuten en de waarden van de partij respecteert.
* Elk project dat niet aangegeven werd aan de coördinatie-squad is de facto niet onderschreven door de partij.
* Als het project beëindigd of in stand-by is, moet de contactpersoon van het project dit melden aan de coördinatie-squad.
* (OPT) Elk project moet publiek worden voorgesteld op een webpagina.

==== Resource centers ====
* Een resource center is een repertorium dat piraten met specifieke vaardigheden of kennis rond een specifiek onderwerp oplijst. Het kan andere informatie gerelateerd met zijn thema bevatten, zoals doumentatie, een lijst van experten, enz.

==== Squads ====
* De volgende entiteiten, gerefereerd door squads moeten als volgt worden benoemd:
** squads
** ?

* Er zijn exact 9 squads in de partij. Dit zijn:
** Coaching
** Coördinatie
** Coreteam
** Financiën
** AV
** IT
** Pers
** Secretariaat
** Wiki

De rollen van elke squad worden beschreven in de volgende secties.

* Er zijn twee manieren voor een piraat om lid te worden van een squad:
*# Goedgekeurd worden door een motie van vertrouwen op een AV.
*# Unaniem goedgekeurd worden door de huidige leden van de squad. In dit geval moet deze beslissing actief aangekondigd worden naar alle piraten.
* Er zijn twee manieren voor een lid van een squad om deze te verlaten:
*# Aftreden.
*# Falen in een motie van vertrouwen op een AV.
* Elke squad bestaat uit minstens twee leden.
* Op de eerste AV van elk jaar presenteert elke squad een activiteitenraport en er wordt opgeroepen tot een motie van vertrouwen. Indien de motie faalt voor een bepaalde squad wordt er opgeroepen tot een een motie van vertrouwen voor elk van zijn leden.
* Elke kandidaat voor een squad moet een nog te bepalen procedure volgen.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-left:5px; border-radius:5px" |
'''Translation needed'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
|}

= Set n°3 =
* (as discussed in the refactoring lab of 5/07).

A thinking process has to be implemented between the present and the next GA in order to discuss,
amongst all pirates, about a possible change of the name of our "Pirate Party" and our goals (a manifesto).

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set3
<eplite id=ga201408-amendments-set3></eplite>

= Set n°4 =

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

'''Original'''

Teneinde de ground-up filosofie van de partij nog beter in haar organisatiestruktuur te weerspiegelen en de transparantie te verhogen, stellen wij voor om het coreteam af te schaffen en te vervangen door twee nieuwe, duidelijk van elkaar ondescheiden, instanties: het secretariaat en het coördinatie comité.

=== Het secretariaat ===
==== Functieomschrijving ====
*Het (nationaal) secretariaat is een louter administratief orgaan dat enkel instaat voor secretariaatstaken zoals: het ledenbeheer, de administratie, de (nationale) financiën, het beheer van de vzw, ed.
*Het is een louter uitvoerende instantie, zonder beslissingsbevoegdheid.
*Het secretariaat neemt van het oude coreteam de taken schatbewaarder, secretaris en IT over.

==== Leden ====
* Het (nationaal) secretariaat bestaat uit piraten die zich daarvoor op de GA kandidaat stellen, en uit piraten die, op grond van hun specifieke expertise, gevraagd worden om bepaalde taken uit te voeren.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het secretariaat intern over haar werking en de acties die ze uitvoert.

=== Het coördinatie-comité ===
==== Functieomschrijving ====
* Het coördinatie comité is in de eerste plaats een overlegorgaan tussen de verschillende crews (een raad van de crews).
* Het coördinatie comité bevordert de communicatie tussen de verschillende crews, verzamelt en verspreidt partijinformatie tussen de crews onderling en tussen de crews en het nationale en internationale niveau, stimuleert de discussie over de werking en toekomst van de partij, stelt de agenda voor de GA voor en staat in voor het dringend dagelijks bestuur van de partij.
* Het coördinatie comité is geen “leidende” instantie, het is een overlegorgaan tussen de crews, dat enkel bevoegd is om dringende beslissingen te nemen in functie van het dagelijks bestuur van de partij.
* Het coördinatie comité heeft geen beslissingsbevoegdheid mbt de inhoudelijke oriëntatie of organisatie van de partij, die bevoegdheden heeft enkel de GA.
* Het coördinatiecomité neemt van het oude coreteam de taken integratie, coördinatie, internationale betrekkingen en pers over.

==== Leden ====
* Het coördinatie comité bestaat uit één afgevaardigde van elke crew.
* De crews duiden op de GA hun vertegenwoordiger aan, deze blijft in functie tot de volgende GA. Indien nodig kan een crew zich door iemand anders laten vertegenwoordigen.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het comité intern over haar werking en de acties die ze uitvoert.
*De vergaderingen van het coördinatie comité zijn open voor elk lid van de partij, maar bij een eventuele stemming in functie van het dringend dagelijks bestuur, hebben enkel de vertegenwoordigers van een crew stemrecht.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

'''FR translation (complete)'''

Dans le souci d'accroître la transparence du parti et de mieux refléter la philosophie "ground-up" dans sa structure, nous proposons de supprimer la coreteam et de la remplacer par deux nouvelles instances, clairement distinctes l'une de l'autre : le secrétariat et le comité de coordination.

=== Le secrétatiat ===
==== Description des fonctions ====
* Le secrétariat (national) est un organe purement administratif traitant exclusivement de tâches de secrétariat telles que la gestion des membres, l'administration, les finances (nationales), la gestion de l'asbl, etc.
* C'est une instance purement exécutive, sans compétence décisionnelle.
* Le secrétariat reprend de la coreteam actuelle les tâches de trésorier, secrétaire et gestion de l'IT.

==== Membres ====
* Le secrétariat (national) se compose de pirates se présentant comme candidat à l'AG ainsi que de pirates qui, du fait de leur expertise, sont invités à exécuter certaines tâches déterminées.

==== Fonctionnement ====
* Le secrétariat décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.

=== Le comité de coordination ===
==== Description des fonctions ====
* Le comité de coordination est avant tout un organe de concertation entre les équipages (un conseil d'équipage).
* Le comité de coordination favorise la communication entre les équipages, collecte et répand toute information relative au parti entre les équipages et entre les équipages et les niveaux nationaux et internationaux, stimule les discussions relatives au fonctionnement et à l'avenir du parti, propose l'agenda de l'AG et traite des affaires courantes du parti.
* Le comité de coordination n'est pas une instance dirigeante mais un organe de concertation entre équipages, uniquement autorisé à prendre des décisions urgentes concernant la gestion quotidienne du parti.
* Le comité de coordination n'a aucune compétence décisionnelle concernant l'orientation idéologique ou l'organisation du parti. Seule l'AG dispose de ces compétences.
* Le comité de coordination reprend de la coreteam actuelle les tâches d'intégration et de coordination, les relations internationales et la presse.

==== Membres ====
* Le comité de coordination se compose d'un délégué issu de chaque équipage.
* Les équipages font part de leur délégué à l'AG. Ceux-ci restent en fonction jusqu'à la prochaine AG. En cas de nécessité, un équipage peut se faire représenter par quelqu'un d'autre.

==== Fonctionnement ====
* Le comité de coordination décide en interne de son fonctionnement et des actions qu'il exécute, sans porter préjudice aux statuts et en respectant les objectifs généraux du parti.
* Les réunions du comité de coordination sont ouvertes à tout membre du parti, bien que seuls les représentants de chaque équipage peuvent participer aux votes organisé dans le cadre de la gestion des affaires courantes.
|-
|}

=== Discussion pad ===
Direct link to the pad: http://www.piratepad.be/p/voorstel
<eplite id=voorstel></eplite>

Events/EGA:2014-08/Amendments

2014-07-13T14:01:49Z

Manu: /* Set n°4 */ new layout

= Intro =

==== EN ====
This is the page dedicated to the preparation of the texts that will be voted during our next G.A.
We have received these proposals according to our protocol, available there: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

==== FR ====
Ceci est la page dédiée à la préparation des textes qui seront votés en Assemblée Générale.
Nous avons reçu ces propositions en conformité avec notre protocole, disponible ici: http://wiki.pirateparty.be/index.php/Events/EGA:2014-08

= Existing Statutes =

[[Statutes|Existing Statutes - Statuten - Statuts]]

= Proposals to amend =

== Set n°1 ==

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set1
<eplite id=ga201408-amendments-set1></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
=== Original ===
* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

=== Traduction nécessaire ===

* Squads die verantwoordelijk zijn voor de digitale communicatiekanalen van de partij, hebben het recht om die kanalen te modereren, en indien nodig, mensen de toegang tot die kanalen te ontzeggen.

* Voor alle mandaten bedraagt de afdracht 22,5% van de brutovergoedingen. Indien de betrokken mandataris geen inkomsten heeft uit een ander beroep, een pensioen of een vervangingsinkomen bedraagt de afdracht 17,5% van de brutovergoedingen.

*Het lidgeld bedraagt €2,5 per maand. Het coreteam kan in uitzonderlijke gevallen beslissen dat iemand het lidgeld niet hoeft te betalen.

* Iedere algemene vergadering wordt het coreteam gestemd bij vertrouwensstemming. Alle kandidaten voor het coreteam worden op een lijst geplaatst, waarna de leden in het geheim met approval voting kunnen beslissen. Alle kandidaten met het vertrouwen van de meerderheid van de partij zijn verkozen. Als er meer dan 10 verkozenen zouden zijn, komen de 10 verkozenen met het meeste vertrouwen in het coreteam, en vervolgens de kandidaat met de minste jaren ervaring in het coreteam.

* We zullen de statuten herwerken, om van de Piratenpartij een v.z.w. te kunnen maken. Daarbij plaatsen we alle elementen voor derden in de statuten van de v.z.w., en alle elementen voor de interne werking in een huishoudelijk reglement. Deze drastische structuurwijziging gaat later concreet voorgelegd worden aan de algemene vergadering.

Verzoenings- en tuchtcommissie

§X. Het gezag van de algemene vergadering moet door alle leden worden aanvaard en geëerbiedigd. Personen die het gezag van de algemene vergadering ondermijnen, die weigeren zich neer te legen bij definitieve bestuursbeslissingen of door hun gedrag of houding de partij in opspraak brengen of schade berokkenen, kunnen in hun functies geschorst worden.

§X. Organen die het gezag van de algemene vergadering niet kunnen accepteren of die acties ondernemen die de partij in opspraak brengen of schade berokkenen, kunnen collectief geschorst worden.

§X. Een schorsing van organen of personen kan door een verzoenings- en tuchtprocedure, die door een entiteit gestart worden tegen dit bestuur en die persoon.

Alleen met goedkeuring van het coreteam kan een schorsing uitgesproken worden tijdens de periode van zes maanden die voorafgaat aan de datum van politieke verkiezingen of bestuursverkiezingen. Anders wordt die beslissing over de verkiezingen getild.

Het coreteam bepaald de betrokken partijen bij een verzoenings- en tuchtprocedure.

§X. De beslissing tot schorsing of berisping moet samen met het dossier binnen de week worden neergelegd bij het coreteam.

Een schorsing geldt voor een termijn voor ten hoogste zes maanden vanaf de indiening.

Voor het einde van de schorsing moet het schorsend bestuur een evaluatie maken van de situatie. Bij een negatieve evaluatie moet een verzoenings- en tuchtdossier ingediend worden. Gedurende de periode dat het nieuwe verzoenings- en tuchtdossier behandeld wordt, loopt de schorsing door.

§X. Alle aanhangig gemaakte klachten en elementen worden publiek en transparant behandeld, maar met respect voor de privacy van de betrokkenen.

§X. De nationale verzoenings- en tuchtcommissie bestaat uit 5 leden, per zaak uitgeloot onder de leden die deelgenomen hebben aan de laatste algemene vergadering, eventueel via een volmacht.

Voor elk verkozen lid van de verzoenings- en tuchtcommissie wordt een plaatsvervangend lid uitgeloot.

Indien een vast lid niet aanwezig kan zijn wordt door het secretariaat een plaatsvervanger gecontacteerd. Er blijven per zitting van de verzoenings- en tuchtcommissie echter maximum 1 lid per provincie. Er wordt gezorgd dat er minstens 2 sprekers van de talen van de betrokken partijen bij zijn.

De secretaris uit het coreteam is een bijkomend, zesde lid van de verzoenings- en tuchtcommissie zonder stemrecht. Hij oordeelt of zijn aanwezigheid noodzakelijk is.

§X. Een lid van de verzoenings- en tuchtcommissie dat zelf betrokken is in een procedure kan niet zetelen. Leden van het coreteam, behalve de secretaris, kunnen geen deel uitmaken van de nationale verzoenings- en tuchtcommissie.

§X. De verzoenings- en tuchtcommissie kan slechts geldig vergaderen als minstens de helft van de leden aanwezig is.

§X. De verzoenings- en tuchtcommissie wordt voor iedere zaak vernieuwd.

§X. Een geschil binnen de partij en elke grove inbreuk op de partijtucht kan aan de nationale verzoenings- en tuchtcommissie worden voorgelegd door het coreteam zelf, of door een piraat.

In dit geval moet hiervan melding worden gedaan op de eerstvolgende vergadering van het coreteam.

§X. Binnen twee maanden komt de verzoenings- en tuchtcommissie samen op uitnodiging van haar voorzitter om het voorgelegde probleem te onderzoeken. Zij kan de verschillende betrokken partijen horen, hun dossier en nota’s in ontvangst nemen en een rapport opstellen met de respectieve standpunten. Dit rapport wordt bezorgd aan de secretaris van het coreteam.

§X. Het coreteam kan in uitzonderlijke gevallen beslissen om een lid voorlopig te schorsen tot 2 maanden of tot de beslissing van de verzoenings- en tuchtcommissie, welke eerst afloopt.

§X. De verzoenings- en tuchtcommissie kan de beslissing tot schorsing bedoeld opheffen indien dit tot een eventuele verzoening kan bijdragen.

§X. De verzoenings- en tuchtcommissie zal steeds in eerste instantie verzoening nastreven. Zij kan echter ook volgende tuchtmaatregelen opleggen of voorstellen, dit in orde van belangrijkheid:

A. de berisping, met kennisgeving aan de leden van de betrokken organen;

B. de blaam, met kennisgeving aan de leden van de partij;

C. de schorsing in een functie, voor ten hoogste 12 maanden;

D. de schorsing als lid van de partij, voor ten hoogste 12 maanden;

E. de uitsluiting.

De sancties A, B en C kunnen door de nationale verzoenings- en tuchtcommissie zelf worden uitgesproken en ingesteld.

De sancties D en E kunnen door de commissie slechts worden voorgesteld en dienen ter bekrachtiging worden voorgelegd aan het coreteam.

De verzoenings- en tuchtcommissie beslist bij eenvoudige meerderheid.

§X. Op de eerstvolgende vergadering van het coreteam brengt een lid van de nationale verzoenings- en tuchtcommissie verslag uit over het geheel en licht het voorstel toe in geval van sanctie D of E, waarna het coreteam zich onmiddellijk uitspreekt.

Bij verwerping kan steeds een minder vérstrekkende tuchtmaatregel worden voorgesteld.

§X. De beslissing van de verzoenings- en tuchtcommissie of de partijraad moet binnen de week door de algemeen secretaris worden bekend gemaakt aan de betrokken partijen.

§X. Een mandataris, bij tuchtmaatregel uitgesloten, zal zijn mandaat of mandaten onmiddellijk ter beschikking stellen van de partij. In geval van schorsing blijft de mandataris ertoe gehouden zijn verplichtingen ten overstaan van de partij na te leven.

§X. De vraag tot wederopneming van een eerder uitgesloten lid wordt door het uitgesloten lid zelf via schrijven aan de algemene vergadering voorleggen. De algemene vergadering kan beslissen om de zaak aan te nemen, hoort vervolgens het uitgesloten lid en eventueel andere betrokken partijen en neemt de beslissing.

|-
|}

== Set n°2 ==

=== Discussion pad ===

Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set2
<eplite id=ga201408-amendments-set2></eplite>


{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="3" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">

{| width="100%"

| width="33%" style="padding-right:5px; border-radius:5px" | EN
| width="33%" style="padding-left:5px; border-radius:5px" | NL
| width="33%" style="padding-left:5px; border-radius:5px" | FR

|}</h3>

|-

| width="33%" style="vertical-align:top; padding-right:5px; border-radius:5px" |
'''Original'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-center:5px; border-radius:5px" |
'''Translation ongoing (David L.)'''
==== Crews ====
Zie huidige statuten.
* De rol van kapitein richt zich op de leden van de crew en de groepsdynamiek.
* De rol van navigator richt zich op administratieve taken.

==== Projecten ====

* Elke piraat kan een project dat de statuten en de algemene doelen van de partij respecteert starten.
* Elke piraat die een project start moet de coördinatie-squad contacteren met de volgende informatie: een beschrijving van het project en een contactpersoon.
* De coördinatie-squad registreert het project formeel na verificatie dat het de statuten en de waarden van de partij respecteert.
* Elk project dat niet aangegeven werd aan de coördinatie-squad is de facto niet onderschreven door de partij.
* Als het project beëindigd of in stand-by is, moet de contactpersoon van het project dit melden aan de coördinatie-squad.
* (OPT) Elk project moet publiek worden voorgesteld op een webpagina.

==== Resource centers ====
* Een resource center is een repertorium dat piraten met specifieke vaardigheden of kennis rond een specifiek onderwerp oplijst. Het kan andere informatie gerelateerd met zijn thema bevatten, zoals doumentatie, een lijst van experten, enz.

==== Squads ====
* De volgende entiteiten, gerefereerd door squads moeten als volgt worden benoemd:
** squads
** ?

* Er zijn exact 9 squads in de partij. Dit zijn:
** Coaching
** Coördinatie
** Coreteam
** Financiën
** AV
** IT
** Pers
** Secretariaat
** Wiki

De rollen van elke squad worden beschreven in de volgende secties.

* Er zijn twee manieren voor een piraat om lid te worden van een squad:
*# Goedgekeurd worden door een motie van vertrouwen op een AV.
*# Unaniem goedgekeurd worden door de huidige leden van de squad. In dit geval moet deze beslissing actief aangekondigd worden naar alle piraten.
* Er zijn twee manieren voor een lid van een squad om deze te verlaten:
*# Aftreden.
*# Falen in een motie van vertrouwen op een AV.
* Elke squad bestaat uit minstens twee leden.
* Op de eerste AV van elk jaar presenteert elke squad een activiteitenraport en er wordt opgeroepen tot een motie van vertrouwen. Indien de motie faalt voor een bepaalde squad wordt er opgeroepen tot een een motie van vertrouwen voor elk van zijn leden.
* Elke kandidaat voor een squad moet een nog te bepalen procedure volgen.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
| width="33%" style="vertical-align:top; padding-left:5px; border-radius:5px" |
'''Translation needed'''
==== Crews ====
See current statutes.
* The role of captain is centered around crew members and group dynamics.
* The role of navigator is centered around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends or is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centers ====
* A resource center is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad are described in the following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

===== Coaching =====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centers.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

===== Coreteam =====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

===== Finance =====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

===== GA =====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

===== IT =====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

===== Press =====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

===== Secretary =====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

===== Wiki =====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

==== Procedures ====
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.
|}

= Set n°3 =
* (as discussed in the refactoring lab of 5/07).

A thinking process has to be implemented between the present and the next GA in order to discuss,
amongst all pirates, about a possible change of the name of our "Pirate Party" and our goals (a manifesto).

=== Discussion pad ===
Direct link to the pad: http://piratepad.be/p/ga201408-amendments-set3
<eplite id=ga201408-amendments-set3></eplite>

= Set n°4 =

{| id="mp-left" cellpadding="2" cellspacing="5" style="margin:10px 0 0 0; width:100%; border:1px solid #A7D7F9; vertical-align:top; background:#F6F6F6; text-align: justify; border-radius:5px"
! colspan="2" | <h3 id="mp-itn-h2" style="margin:0; background:#733594; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em; border-radius:5px">
{| width="100%"
| width="50%" style="padding-right:5px; border-radius:5px" | NL
| width="50%" style="padding-left:5px; border-radius:5px" | FR
|}</h3>
|-
| width="50%" style="vertical-align:top; padding-right:5px; border-radius:5px" |

'''Original'''

Teneinde de ground-up filosofie van de partij nog beter in haar organisatiestruktuur te weerspiegelen en de transparantie te verhogen, stellen wij voor om het coreteam af te schaffen en te vervangen door twee nieuwe, duidelijk van elkaar ondescheiden, instanties: het secretariaat en het coördinatie comité.

=== Het secretariaat ===
==== Functieomschrijving ====
*Het (nationaal) secretariaat is een louter administratief orgaan dat enkel instaat voor secretariaatstaken zoals: het ledenbeheer, de administratie, de (nationale) financiën, het beheer van de vzw, ed.
*Het is een louter uitvoerende instantie, zonder beslissingsbevoegdheid.
*Het secretariaat neemt van het oude coreteam de taken schatbewaarder, secretaris en IT over.

==== Leden ====
* Het (nationaal) secretariaat bestaat uit piraten die zich daarvoor op de GA kandidaat stellen, en uit piraten die, op grond van hun specifieke expertise, gevraagd worden om bepaalde taken uit te voeren.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het secretariaat intern over haar werking en de acties die ze uitvoert.

=== Het coördinatie-comité ===
==== Functieomschrijving ====
* Het coördinatie comité is in de eerste plaats een overlegorgaan tussen de verschillende crews (een raad van de crews).
* Het coördinatie comité bevordert de communicatie tussen de verschillende crews, verzamelt en verspreidt partijinformatie tussen de crews onderling en tussen de crews en het nationale en internationale niveau, stimuleert de discussie over de werking en toekomst van de partij, stelt de agenda voor de GA voor en staat in voor het dringend dagelijks bestuur van de partij.
* Het coördinatie comité is geen “leidende” instantie, het is een overlegorgaan tussen de crews, dat enkel bevoegd is om dringende beslissingen te nemen in functie van het dagelijks bestuur van de partij.
* Het coördinatie comité heeft geen beslissingsbevoegdheid mbt de inhoudelijke oriëntatie of organisatie van de partij, die bevoegdheden heeft enkel de GA.
* Het coördinatiecomité neemt van het oude coreteam de taken integratie, coördinatie, internationale betrekkingen en pers over.

==== Leden ====
* Het coördinatie comité bestaat uit één afgevaardigde van elke crew.
* De crews duiden op de GA hun vertegenwoordiger aan, deze blijft in functie tot de volgende GA. Indien nodig kan een crew zich door iemand anders laten vertegenwoordigen.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het comité intern over haar werking en de acties die ze uitvoert.
*De vergaderingen van het coördinatie comité zijn open voor elk lid van de partij, maar bij een eventuele stemming in functie van het dringend dagelijks bestuur, hebben enkel de vertegenwoordigers van een crew stemrecht.

| width="50%" style="vertical-align:top; padding-left:5px; border-radius:5px" |

'''FR translation (todo)'''

Teneinde de ground-up filosofie van de partij nog beter in haar organisatiestruktuur te weerspiegelen en de transparantie te verhogen, stellen wij voor om het coreteam af te schaffen en te vervangen door twee nieuwe, duidelijk van elkaar ondescheiden, instanties: het secretariaat en het coördinatie comité.

=== Het secretariaat ===
==== Functieomschrijving ====
*Het (nationaal) secretariaat is een louter administratief orgaan dat enkel instaat voor secretariaatstaken zoals: het ledenbeheer, de administratie, de (nationale) financiën, het beheer van de vzw, ed.
*Het is een louter uitvoerende instantie, zonder beslissingsbevoegdheid.
*Het secretariaat neemt van het oude coreteam de taken schatbewaarder, secretaris en IT over.

==== Leden ====
* Het (nationaal) secretariaat bestaat uit piraten die zich daarvoor op de GA kandidaat stellen, en uit piraten die, op grond van hun specifieke expertise, gevraagd worden om bepaalde taken uit te voeren.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het secretariaat intern over haar werking en de acties die ze uitvoert.

=== Het coördinatie-comité ===
==== Functieomschrijving ====
* Het coördinatie comité is in de eerste plaats een overlegorgaan tussen de verschillende crews (een raad van de crews).
* Het coördinatie comité bevordert de communicatie tussen de verschillende crews, verzamelt en verspreidt partijinformatie tussen de crews onderling en tussen de crews en het nationale en internationale niveau, stimuleert de discussie over de werking en toekomst van de partij, stelt de agenda voor de GA voor en staat in voor het dringend dagelijks bestuur van de partij.
* Het coördinatie comité is geen “leidende” instantie, het is een overlegorgaan tussen de crews, dat enkel bevoegd is om dringende beslissingen te nemen in functie van het dagelijks bestuur van de partij.
* Het coördinatie comité heeft geen beslissingsbevoegdheid mbt de inhoudelijke oriëntatie of organisatie van de partij, die bevoegdheden heeft enkel de GA.
* Het coördinatiecomité neemt van het oude coreteam de taken integratie, coördinatie, internationale betrekkingen en pers over.

==== Leden ====
* Het coördinatie comité bestaat uit één afgevaardigde van elke crew.
* De crews duiden op de GA hun vertegenwoordiger aan, deze blijft in functie tot de volgende GA. Indien nodig kan een crew zich door iemand anders laten vertegenwoordigen.

==== Werking ====
* Onverminderd de statuten en met respect voor de algemene doelen van de partij, beslist het comité intern over haar werking en de acties die ze uitvoert.
*De vergaderingen van het coördinatie comité zijn open voor elk lid van de partij, maar bij een eventuele stemming in functie van het dringend dagelijks bestuur, hebben enkel de vertegenwoordigers van een crew stemrecht.
|-
|}

=== Discussion pad ===
Direct link to the pad: http://www.piratepad.be/p/voorstel
<eplite id=voorstel></eplite>

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T14:12:21Z

Manu:

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.
== Proposals ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

'''Short presentation (not to be included in the statutes) :'''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. The other squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and other squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

==== Coaching ====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

== Resources ==

=== What squads are ===
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

=== What squads should be ===

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T14:08:35Z

Manu: /* Draft */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

'''Short presentation (not to be included in the statutes) :'''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. The other squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and other squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

==== Coaching ====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T14:07:21Z

Manu: /* Draft */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

'''Short presentation (not to be included in the statutes) :'''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

==== Coaching ====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T14:04:03Z

Manu: /* Structure */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

==== Coaching ====
* The Coaching squad has the following exclusive competencies :
** Welcome new members.
** Spread guidelines.
** Provide documentation and resources to newcomers.
** ''To complete''

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
* The Press squad has the following exclusive competencies :
** Speak in the name of the party to press.
** React to news by publishing press releases.
** ''To detail''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T13:58:50Z

Manu: /* Squads */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.
* Every candidacy to a squad has to follow a procedure still to define.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T13:57:20Z

Manu: /* Crews */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.
* The role of captain is centred around crew members and group dynamics.
* The role of navigator is centred around administrative tasks.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T13:54:11Z

Manu: /* Draft */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive. The 4G squad can be integrated in them.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T12:56:02Z

Manu: /* Squads */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails for a given squad, a motion of confidence is called for each of its members in turn.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T12:53:08Z

Manu: /* Squads */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad contains a minimum of two members.
* At the first GA of each year, each squad presents an activity report and a motion confidence is called for it. If it fails, a motion of confidence is called for each member in turn.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T12:24:22Z

Manu: /* Structure */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 9 squads in the party. Those are :
** Coaching
** Coordination
** Coreteam
** Finance
** GA
** IT
** Press
** Secretary
** Wiki

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Coreteam ====
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T10:31:50Z

Manu: /* Squads */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Coreteam ====
* The coreteam is made up of the captains of each crew.
* A captain can delegate his/her coreteam duties to any member of his/her crew.
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 8 squads in the party. Those are :
** Coordination
** Finance
** GA
** IT
** Press
** Secretary
** Wiki
** Coaching

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

==== Coaching ====

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T10:30:22Z

Manu: /* Draft */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Coreteam ====
* The coreteam is made up of the captains of each crew.
* A captain can delegate his/her coreteam duties to any member of his/her crew.
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* The following entities, referred by squads should be named as follows :
** squads
** ?

* There are exactly 8 squads in the party. Those are :
** Coordination
** Finance
** GA
** IT
** Press
** Secretary
** Wiki
** Coaching

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T10:25:57Z

Manu: /* Procedures */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Coreteam ====
* The coreteam is made up of the captains of each crew.
* A captain can delegate his/her coreteam duties to any member of his/her crew.
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* There are exactly 8 squads in the party. Those are :
** Coordination
** Finance
** GA
** IT
** Press
** Secretary
** Wiki
** Coaching

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed by the persons calling it.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T10:23:41Z

Manu: /* GA */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Coreteam ====
* The coreteam is made up of the captains of each crew.
* A captain can delegate his/her coreteam duties to any member of his/her crew.
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* There are exactly 8 squads in the party. Those are :
** Coordination
** Finance
** GA
** IT
** Press
** Secretary
** Wiki
** Coaching

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated.
** Publish the statutes.
** Collect the motion of confidences.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed.

EGA:2014/08 Uccle-Ukkel/Resquad

2014-07-05T10:13:54Z

Manu: /* Squads */

'''Goal''' : Produce an amendment to chapter II.2. of the statutes governing squads in order to clarify their purpose and their functioning.

== What squads are ==
* '''43.''' Les Squads sont les groupes de travail du parti.
* '''44.''' Les Squads ne sont pas liées à une ville ou région.
* '''45.''' Les squads sont de 2 types : par thème et par projet (limitée dans le temps).
* '''46.''' Les squads de projet se composent d’au moins 3 pirates.
* '''47.''' Les squads thématiques se composent d’au moins 3 pirates issus d’au moins deux équipages différents.
* '''48.''' Un Pirate peut faire partie d’autant de Squads qu’il le souhaite.
* '''49.''' Les seules conditions pour rejoindre une Squad sont l’intention et la capacité de participer.
* '''50.''' Les postes spécifiques d’une Squad sont un Responsable de projet dans une Squad de projet, pas de postes spécifiques pour les Squads thématiques.
* '''51.''' La Squad est le groupe de travail d’oùprovient les impulsions, les positions et les actions du Parti.
* '''52.''' Les Squads formalisent les impulsions, initiatives et idées fournies par les Pirates.
* '''53.''' Un projet est défini par un échéancier (début/ fin), un produit final et un Responsable.
* '''54.''' Le Responsable du projet est responsable du respect des délais et de l’adéquation avec le Projet Pirate.
* '''55.''' Le Responsable de Projet entre en relation avec les instances concernées pour faire connaître l’initiative, vérifier son originalité (pas de doublons) et rassembler des ressources humaines.
* '''56.''' Pour valider le travail d’une Squad, les critères suivants doivent être rencontrés :
** a) le référencement (tout élément de proposition et/ou d’argumentation doit être appuyé d’une documentation) et la transparence (ladite documentation doit être accessible à tous);
** b) le travail doit être adopté par l’Assemblée Générale ou par une instance désignée par l’Assemblée générale ;
** c) la production passera par des outils de travail collaboratif (wiki, lqfb, jegouverne, forums, pad, irc, mumble,...);
** d) la Squad tient à jour une page wiki (infos, PV, ...) et diffuse ses infos (mailing list, ...);
** e) la Squad doit présenter un rapport de son activité au moins une fois par an ;
** f) la Squad a pris contact avec la Coreteam.

== What squads should be ==

* Les squads doivent permettre de remplir les missions que les pirates se sont assignées lors des assemblées générales => Squad obligatoire
** La coreteam a la responsabilité de trouver des gens pour ces travaux qui doivent répondre à un cahier de charge (collaboratif, transparence, vie privée,...)

* Les squads doivent permettre aux membres de prendre connaissance des travaux des autres pirates => Squad émergent
** Le travail peut être commencé de manière informelle puis transformé en squad de projet. Des projets récurrents ou semblables peuvent devenir des composants d'un squad thématique.
** La coreteam a la responsabilité d'aider les groupes de travail à évoluer vers un squad formalisé (templates wiki, encadrement,...)

== Draft ==
''Add stuff freely, but discuss any change on the [[Talk:Resquad project|Talk page]].''

The idea is to split the current squads into different entities :
* Projects : formerly known as project squads. They are temporary, less constraints are imposed.
* Resource centres : formerly known as thematic squads. They are now inherently passive.
* Squads : those are the crucial units we need to make the party function as a whole. A control procedure is introduced.

The coreteam is defined as the place where day-to-day decisions are made. It consists of the captains of every crews by default. The squads are there (among others) to implement decisions taken by the coreteam.

For example, if the coreteam decides on the amount to give to each crew for election campaign, the finance squad has to ask for receipts and proceed reimbursements. Coreteam members stay out of the process.

So basically, coreteam should talk and meet, and squads should do.

=== Structure ===

==== Conflict resolution ====
''To define''

==== Coreteam ====
* The coreteam is made up of the captains of each crew.
* A captain can delegate his/her coreteam duties to any member of his/her crew.
* Every decision of the coreteam must be communicated to all pirates.
* The coreteam has the following exclusive competencies :
** Manage the budget of the party. The implementation of the budget is left to the finance squad.
** Nominate international delegates.
** ''To complete''

==== Crews ====
See current statutes.

==== Projects ====

* Every pirate can start a project that respects the statutes and the general goals of the party.
* Every pirate starting a project has to contact the coordination squad with the following information : a description of the project and a contact person.
* The coordination squad formally records the project after verifying that it respects the statutes and the values of the party.
* Any project that hasn't been declared to the coordination squad is de facto not endorsed by the party.
* If the project ends of is in stand-by, the contact person of the project has to tell the coordination squad.
* (OPT) Any project has to be publicly presented on a webpage.

==== Resource centres ====
* A resource centre is a directory listing pirates having particular skills or knowledge about a particular subject. It may contain other information related to its theme such as documentation, a list of experts, etc.
* 4G and thematic squads could be integrated.

==== Squads ====
* There are exactly 8 squads in the party. Those are :
** Coordination
** Finance
** GA
** IT
** Press
** Secretary
** Wiki
** Coaching

The roles of each squad is described in following sections.

*There are two ways for a pirate to become member of a squad :
*# Get approved by a motion of confidence at a GA.
*# Get unanimously approved by the current members of the squad. In this case, this decision has to be actively announced to all pirates.
* There are two ways for a member of a squad to get out :
*# Resign.
*# Fail a motion of confidence at a GA.
* Any squad should contain a minimum of two members.

===== Coordination =====
* The coordination squad has the following exclusive competencies :
** Manage incoming email from the contact address contact@pirateparty.be. By "manage" is meant : forwarding to the right person to answer.
** Maintaining a public list of crews, including a contact person.
** Maintaining a public list of ongoing projects, including a contact person.
** Maintaining a public list of resource centres.
** Convoke any pirate, squad, crew, coreteam or project representative to ask for information on their activities.
* The coordination squad serves as an "oracle" for pirates. By this is meant that every pirate having a particular need or question can contact the coordination squad. The coordination squad is then expected to put him/her in touch with the right pirate to help him/her.
* The coordination squad shares actively and regularly its knowledge of the party's internal businesses to pirates.

==== Finance ====
* The members and only the members of the finance squad have access to the bank accounts of the party.
* The Finance squad has the following exclusive competencies :
** Implementing the budget approved by the General Assembly.
* The finances will be monitored by a control group.
*Income and outcome have to be visible at anytime by anyone.

==== GA ====
* The GA squads organizes general assemblies.
* The GA squad has the following exclusive competencies :
** Ensure that the GA protocol is correctly followed.
** Collect all proposals and amendments made by members.
** Prepare all voting documents.
*** Ensures that the documents are translated
** Publish the statutes.

==== IT ====
* The members and only the members of the IT squad have access to the servers of the party, with exception for the members of the wiki squad, who have a limited access to them, as described in the corresponding section.
* ''To detail''

==== Press ====
''To define''.

==== Secretary ====
* The members and only the members of the secretary squad have access to the database of members of the party.
* The Secretary squad has the following exclusive competencies :
** Ensure the party meets all legal requirements.
**...

==== Wiki ====
* The wiki squad maintains the wiki.
* The members and only the members of the Wiki squad have administrator rights on the wiki.
* The members of the wiki squad have also access to the wiki installation through a special SSH access.

=== Procedures ===
* A motion of confidence requires 60% of the expressed votes to pass.
* It takes 3 pirates to call a motion of confidence.
* Before a vote is taken, the reasons for the motion have to be clearly exposed.