Changes between Initial Version and Version 1 of TachankaMembershipProcess

Timestamp:

09/21/10 23:25:15 (15 years ago)

Author:

garcon du monde

Comment:

my first draft :-)

TachankaMembershipProcess

@@ +1 @@
+[[PageOutline]]
+
+= Membership of Tachanka =
+
+All members of the main Tachanka collective should meet the following criteria:
+ 1. Should have personally met and exchanged GPG key fingerprints with at least 2 other members of the collective.
+ 2. Should have been involved in online, political tech work with at least 2 other members of the collective for a minimum of 2 years. 
+Note: the two members listed in parts 1. and 2. need not be the same two members. 
+
+All such members will be added to the tachanka-collective mailing list (encrypted) and active members will be eligible to hold root access on all host servers.
+
+Anyone who is considered for membership but doesn't meet these criteria is eligible to participate in the [MentorsIndex mentoring scheme] (to be developed). 
+
+== Inviting a new member into Tachanka ==
+
+A person who meets the membership criteria may be proposed as a new member of the Tachanka collective based on the following: 
+
+ 1. They agree with the [PublicAbout#Principles principles of Tachanka].
+ 2. The possibility of them joining is first discussed on the list for a period, with particular emphasis on the following:
+    - suitability of the person for full membership;
+    - OR, suitability of the person for participation in mentors scheme.
+ 3. Discussing members should aim to come to consensus on whether the person should become a member or not.
+ 4. The person should then be formally proposed for a minimum period of 1 week. This is to allow collective members who have not participated in the discussion thus far a period in which to express their views. 
+ 5. For inclusion in the collective, the proposal requires no negative or abstaining collective members. 
+    - In the case of abstentions, the proposal is postponed for a minimum of 3 months.
+    - In the case of dissent, the proposal is blocked. 
+
+== Removing an existing member from Tachanka ==
+
+ 1. Any collective member may propose to expel another collective member
+ 2. The person is expelled from the collective and all privileges are revoked when the issue is supported by two ''other'' individuals (that is, ''not'' the member who initiated step 1).
+ 3. The expelled member may appeal. This is done by sending an email to the tachanka-collective list which decides using the regular decision-making process (defined below). All individuals are strongly encouraged to express their position on the issue.
+
+'''Note:''' This ejection process should be used only as a last resort or in breaches of confidentiality. We will develop a conflict resolution guide that can be used before the ejection process.
+
+== Membership in good standing ==
+
+ * Periodically, members may be asked to give an update to Tachanka on how they view Tachanka and their involvement (this is only likely to be every 6-12 months).
+ * If a member does not give a report with the specified time (usually, a minimum of 1 month), they are no longer considered to be active members of the Tachanka collective; root access privileges to host servers will be revoked.  
+   - They will be considered active members again as soon as a report is sent; it is not necessary to wait for the next round of reports.
+ * If 3 report cycles (or 2 years, whichever is the shorter) have passed without a member sending reports, then the member is no longer considered a member of Tachanka and access to all Tachanka facilities is removed (this includes the tachanka-collective mailing lists, the wiki, and collective resources such as git.tachanka.org)
+
+
+= Decision making =
+
+Most decisions are made by individuals working together on specific projects for Tachanka in the manner that is most appropriate for the situation. Those decisions that  affect the collective as a whole may be made by using the following process:
+
+ 1. All proposals are made to the tachanka-collective mailing list. The subject should begin with the word "proposal" followed by a numeric identifier and nothing else. The proposing member may withdraw the proposal at any time during the decision-making period.
+ 2. Our goal is to make decisions by consensus; we will do this by this process.
+    * The proposal is passed if it is approved by 1/3 (rounding up) of collective members; and,
+    * There are no negative votes.
+ 3. We have a time limit of two weeks for proposals, after this point the proposal is dropped if there not enough positive votes. 
+ 4. The decision-making time is automatically increased on the request of any member, if they give a reason for the extension and a specific date for the new deadline. 
+ 5. Only member groups who are active at the time that a proposal is made can support or block that proposal. 
+ 6. Proposals that have been accepted are posted onto the wiki with a brief summary of discussions, and numbers of abstentions and supporters. This is the responsibility of the original proposer. 
+