Changes between Version 4 and Version 5 of TachankaMembershipProcess

Timestamp:

02/06/11 17:29:18 (15 years ago)

Author:

garcon du monde

Comment:

additional links to other wiki pages

TachankaMembershipProcess

@@ -30 +30 @@
  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 [wiki:DecisionMaking decision-making process]. All individuals are strongly encouraged to express their position on the issue.
+ 3. The expelled member may appeal. This is done by sending an email to the tachanka-collective list which decides using the regular [wiki:Organization/DecisionMaking decision-making process]. 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.
@@ -36 +36 @@
 == 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.  
+ * Periodically, members may be asked to [TachankaMembershipInfo 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 [TachankaMembershipInfo 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)