Second Charter Draft

The eglug.org charter

The Bahram Document

Article 1 - Title

The title of the group is The Egyptian GNU/Linux Users Group - مجموعة مستخدمى جنو/لينكس فى مصر.

The lug shall be referred to as EGLUG - جنو/لينكس مصر

the domain name of the group shall be eglug.org

Article 2 - Why Does EGLUG.org exist

  • To promote the use of Free/Open Source Software in general and GNU/Linux in particular within Egypt
  • To provide support for GNU/Linux and Free/Open Source Software users and contributors in Egypt
  • To build a thriving, proactive and friendly community of GNU/Linux and Free/Open Source Software users.
  • To communicate and cooperate with other Free/Open Source groups and organization and be part of the international Free/Open source community.

Article 3 - Membership

There are no costs for membership. Membership shall be open to all, Only requirement is accepting this charter, anyone who has an account in the eglug.org website is considered a member.

All members are bound by this charter.

Active members will be designated Senior Members through a transparent, fair, objective and preferably automated process

Senior Members don't have more rights, but are empowered with direct access to more eglug.org resources without having to go through moderators and administrators.

Article 4 - Basic Principles

  1. EGLUG is a democratic community; all members have the right to voice their opinion and give input and feedback, and to contribute to the decision making process, all members are equal and have equal rights to be heard.
  2. EGLUG is a transparent community; All members have the right to know each and every detail about EGLUG and its activities, no secret decisions shall be made and no secret process shall be used to reach any decision. All EGLUG rules and policies shall be public, well known in advance and reached to through an open democratic process, Members have the right to monitor all actions taken by moderators and administrators.
  3. EGLUG is a volunteer community and it lives by personal initiative. The members have the right to propose ideas and activities concerning Free/Open Source Software to the community and to develop these ideas and lead projects which the community finds useful, productive and interesting.
  4. EGLUG has no imposed leaders; the administrators and moderators exist only to provide technical support for keeping the website up and functioning smoothly. If leadership is required at any point it is to be temporary and with a strictly defined duration and purpose.
  5. No rule, activity decision or moderation action shall violate, contradict or compromise this charter.

Article 5 - Moderators

The moderator's primary responsibility is to ensure the content of the order to ensure that eglug.org remains accessible and useful to all its members.

Moderators shall also interfere in disputes arising between members to ensure the dispute never becomes hostile.

Moderators are expected to facilitate and encourage member contribution and to empower members to participate in all aspects of the eglug.org website.

The composition of the moderators team shall be determined through a

Article 6 - Administrators

The administrator is a person who has the ultimate responsibility for the eglug.org website, administrators hold the keys and passwords to the website account and are responsible for implementing and maintaining the technical requirements of the community.

The duties and responsibilities of administrators include the duties of moderators as described in Article 5 of this document.

Administrators shall not implement changes that affect the existing core functionality of the eglug website without first seeking the approval of the community through an open and democratic process as described in Article 7 of this document.

The composition of the administrators team shall be determined through

Article 7 - Voting and decision making

Voting is the fundamental process that ensures the democratic nature of EGLUG an administrator's or moderator's failure to implement this process is considered a violation of their mandate and shall be

All members are eligible to vote on all decisions, except small decisions concerning a single event or activity, in that case only members participating in the event/activity are eligible to vote.

What gets voted on

Voting matters shall initially be discussed within the community, a matter is approved for voting if it is presented on the website with 27 approvals, to simplify the process each senior user approval counts as 3 approvals, and each moderator/administrator approval counts as 9 approvals.

Minimum Votes

Minimum number of votes for a poll to be considered valid shall be 51% the number of senior users, moderators and administrators.

Polling

When a matter is approved for vote, it will be posted as a poll by an administrator or moderator within 48 hours of approval> All eglug members will be alerted to the poll through reasonable means, an announcement shall be published on the eglug.org homepage, and the poll will remain open for at least 10 days.

A request for vote can include within a request for a longer polling period, approval of the request shall be taken to mean approval of the proposed polling period.

If the minimum number of votes is not reached by the end of the polling period, the poll remains open for another polling period.

If after the second polling period the minimum number of votesis not reached yet, this shall be considered a sign that active members are being alienated, the whole community shall embark on a discussion of the roots of the problem.

if throught eh discussion the community agrees on the importance of reaching a descision on the voting matter, the poll remains open for a third voting period the result of the poll after the 3 periods is sufficient.

Results

A two third majority in the poll will be considered conclusive. All votes are equal.

In case polling period passes without reaching a two third majority the option with the least votes is removed from the poll and the poll is repeated, when the number of choices is down to two. failure to reach majority shall be considered a sign of discord within the community, the whole community shall then embark on a discussion to resolve the differences.

through the discussion the community may agree to repeat the last poll as is with no changes using the voting approval procedure, if after the repeat two third majority is not reached a simple majoprity is sufficient.

Article 8 - Amendments

The charter will come up for optional review once every year.

The procedure shall be as follows.

  1. A discussion is started on the 10th of July where members can voice issues and problems with the charter along with proposed amendments.
  2. The discussion is closed on the 20th of July and a poll is opened to determine whether any issues raised warrant a charter review.
  3. After the poll is over, the administrators, moderators and senior users are responsible for producing alternate versions of the amended charter in an open and inclusive process, they shall solicit feedback from the rest of the community.
  4. When an ammended charter is ready a poll is opened to ratify the charter.
  5. if by the end of August no new charter has been proposed for ratification the old version is preserved for another year.

Appendix A - Versions of this document

The Charter is expected to evolve slowly over time. The different versions are given names of individuals whom the community feels have contributed meaningfully to the existence of the group specifically and Free/Open Source Software in particular in Egypt. Acting administrators and moderators shall not be considered for naming.

Versions

  1. Bahram: Mr Hesham Bahram is considered the spiritual founder of Linux Egypt and provided the initial impetus to organize.
    • First draft issued on the 3th of May 2004.
    • Second draft issued on the 5th of June 2004.

AcceptableUsePolicy

My suggestion for the AUP is to adopt what NewComer proposed and to revisit the AUP again as soon as we get a sizable number of members.

The current poll shows the community is divided by half on allowing profanity, but almost all agree on no personal attacks and hate speech, at the moment we shall adopt the more conservative choice (since it got a majority of sorts) but obviously the topic needs to be reconsidered again.


The Acceptable Use Policy

Purpose

The Acceptable Use Policy is a simple set of guidelines determining behavior in eglug. The intention is not to restrict, but rather to provide the barest possible protection for members in order to provide a respectable and constructive working environment for the site. The AUP is as follows.

The Policy

The following kinds of speech will not be allowed on the eglug.org website:

  1. No content violating the laws of Egypt.
  2. No Hate speech against individuals or groups.
  3. No personal attacks.
  4. No Profanity or sexualy explicit content.
  5. No off topic content.

Topic

This LUG was founded to promote the ideals of Free/Open Source Software and GNU/Linux. Members are expected to keep the topic of work and discussion in this area as much as they can. It is understood that the line between on-topic and off-topic is sometimes not too clear, and the benefit of the doubt will be given as often as possible. Only clear violations of this rule will be considered a violation of the Acceptable Use Policy.

Blogs

Blogs are a special area of the eglug.org website, their goal is to foster community and to enable social interaction between members.

The rule about off topic content is relaxed fully when it comes to blogs, blog writers can write about anything they want as long as they don't violate the rest of the rules.

When it comes to religion and philosophy, you have the right to express your believes even if it contradicts other religions as long as it doesn't insult/attack them, there's a very fine line between both.

Moderation

It is moderators duty to ensure that content published on the eglug.org website does not violate the rules stated above.

Moderators are to avoid editing members posts, they should instead unpublish the post and ask the author to edit the post till it complies with the rules.

Moderators shall not delete content from the website permenantly, posts violating the rules shall be unpublished and moved to a locked location, any member has the right to request monitoring moderation descisions and looking at moderated posts.

A public trail of the moderation descision citing the author of the violating post, the name of the moderator and the reason for moderation shall be provided, failure to do so will be considered violation of the moderators mandate.

Any moderation descision can be revoked through the consensus of 3 moderators.


I did not actualy give this much thought, and I'd like to hear feedback about it.

MemberClassAssignmentPolicy

Proposal

hmm can we use a better word than class, you know class carries alot of baggage.

the main changes from MadFarmAnimalz suggestions are an automated process for promoting to senior user.

And a concorde voting system for choosing people.

And a very complicated method for choosing administrators, my worry is that administrators have ultimate powers they should be able to trust each other and work together with no tension at all and with minimal disagreements.

Administrators should also trust each others technical abilities and each others embrace of agreed procedures.

which is why I suggest current administrator team must approve candidates.

Rationale

Since quorum is caclulated in terms of Senior Users and since basic resources don't start oppening up until you're senior user this practicaly means that the community is composed of senior users and above. We cannot have an open and democratic community if entery into the community is tied to acceptance of a certain class of members, this renders the right for gratis membership and member equiality void.

Seniority is just a measure of commitment and activity afterall.

I'm not sure if it should be completly automated though, I think moderators should have the right to bypass the system in order to promote some members (but not the opposite). essentialy to empower those who can contribute alot.

the numbers I chose for the scoring system are arbitirary please consider them as just place holders.

I chose a concorde voting method when selecting people for several reasons.

  • IMO it works better for voting among relativly small numbers
  • it works better for choices that are very much similar to each other
  • concorde minimizes the impact of personal relationships in the choosing
  • elegantly resolves the small majority results, since members clearly state the order of preferences
  • minimizes tension, when voting among tight group like moderators individual relations may come to play, an open voting method as opposed to an anonymous one resolves some of these problems but may add tension among friends for not selecting each other, a concorde method eases these pains abit.
  • No gaming, gaming is more likely to appear when choosing people than when choosing policies, an anonymous poll system can not be practicaly secured without too much trouble, an open voting method resolves this.
  • It seems to work quite well for others (debian).

Member Class Assignment Policy

Purpose

This document details the process of selecting Administrators, Moderators and Senior Users.

It also covers the procedure for dealing with members who violate their mandates or abuse their positions.

Senior Members

Senior members shall be choosen from among new members in an auotmated fashion.

A score will be kept to measure each members activity in the LUG, any member who reaches a score of 100 points will be automaticaly promoted to senior member.

Only contributions in the in topic areas of the eglug.org website and activities will be scored, moderated/unpublished contributions will not be counted at all.

  • Each comment gets 1 point.
  • Each New Forum topic gets 2 points.
  • Each New non minor revision to an existing book page (WIKI) gets 1 point.
  • Each New WikiPage gets 3 points.
  • Each New form based article gets 5 points.
  • Each New article gets 10 points.
  • Volunteering in an Event gets 20 points.
  • Helping in organizing an Event gets 40 points.
  • Leading an Event gets 80 points.
  • Moderators can grant up to 30 points, consensus of three moderators is needed for this.

Moderators

Moderators are chosen from the pool of senior users.

The Number of moderators shall be 20% the number of senior users and the procedure to choose moderators shall be as follows

  • Twice a year near the end of February and the end of August the number of new moderators needed will be calculated and a call for candidates from among senior members will be anounced.
  • If the number of candidates is less than or equal to th number needed, candidates will be automaticaly promoted to moderators.
  • Otherwise a concorde voting poll will be used and the highest ranked candidates are choosen.
  • Canidates are not allowed to campaign at all, violating this rule will be a violation of their mandate.
  • The community may choose to change the perscentage of moderators instead, a vote is proposed, if the vote is approved the moderator choosing process is suspended until the new number is determined.
  • If the new percentage is less than the current one moderators vote using a concorde method among themselves to choose who will leave and become senior user unless enough moderators resign.

A moderator may resign at any point from her duties.

Administrators

Administrators are chosen from the pool of moderators. An administrator is nothing more than a moderator with additional strictly technical responsibilities which means that technical competence is a prerequisite.

Due to technical details administrators have to function as once entity, there is no place for disagreement at all between administrators.

Number of Administrators shall be 4 or 20% the number of moderators (whichever is larger).

Once a year after reviewing the charter the number of Administrators needed is calculated and new administrators are chosen according to the following procedure:

  • A call for candidates is anounced among moderators.
  • Candidates shall present their technical capabilities in web development and administration, but otherwise are not allowed to campaign.
  • Administrators are then charged with approving candidates , a candidate is approved unanimously or not.
  • The community votes on approved candidates using a concorde method, an extra choice will be provided to show disagreement with the administrators approvals and disaprovals.
  • If the disagree with administrators approvals choice ranks anywhere other higher than the last quarter of the ranking it will be taken as a sign of great discord in the community, the vote will be void and a discussion shall start to address the roots of the issue.
  • In case of discord the administration team is disbanded, a new call for candidates is anounced and a direct concorde voting method is used to rank candidates.
  • This time campaigning will be allowed.
  • The top candidates are chosen.

An administrator may resign at any point, but must stick around until a replacement is voted upon.

Violation of Mandate

In case of administrators or moderators violating their mandate the community may vote on demoting the them.

Violation of mandate represent a breech of social contract, the member is demoted to new user with 0 score.

Membership revocation

Only administrators can propose membership revocation.

Membership may only be revoked if a member:

  • Persists in violation of the AUP
  • Persists in unethical behavior not covered by the AUP

Since both these criteria are subjective, membership revocation must be approved by the community through 27 votes:

  • A New user's vote will count as 1 vote.
  • A Senior user's vote will count as 3 votes.
  • A Moderators or Administrator's vote will count as 9 votes.

Where a user has his/her membership revoked, and where all 27 votes are senior or new user ballots it can be understood that there is a significant disconnect between the administrators/moderators and the community at large.

ResourcesUsagePolicy

The Resource Usage Policy

Purpose

This document details how resources owned by eglug.org shall be used and what are the rights of the members in relation to these resources.

Disclaimer

Ownership here is a social contract not legal ownership, legal ownership would typicaly be to the one who payed for the resource, in case of payment by electronic means as in credit cards legal ownership will be to the owner of the account used to pay. while this in theory may give one person power over the whole community there is no practical means to avoid this problem, trust and peer pressure are the only thing the only guarantees we could have.

At the moment all eglug.org resources are donated by Alaa, MadFarmAnimalz, Uniball, WhirlPool and ezabi, later to avoid concentrating too much power a wider group of members should contribute in paying.

Resources

The resources controlled by eglug.org are the eglug.org and eglug.net domains and and hosting space.

The details of how these resources can be used very much depends on the details of the hosting package, this policy shall change everytime the hosting provider or package changes.

As of the time of writing this version (5th of June 2004) the resources can be distributed as:

  1. Webspace (we have around 600MB).
  2. FTPspace (shared with webspace).
  3. eglug.org/net Subdomains (sharing storage with webspace).
  4. unlimited eglug.org/net Subdomain redirects.
  5. eglug.org/net POP or IMAP email boxes (shares space with webspace).
  6. unlimited eglug.org/net email forwarding addresses.
  7. 20GB of bandwidth per month.
  8. 5 mailing lists.
  9. The core eglug.org space and the drupal installation.
  10. Blogs under the drupal installation.

Policy

Administrators are responsible for maintaining and allocating these resources as described in the charter.

Only Administratos hold the passwords to all resources, abuse of these resurces will be considred violation of their mandate.

The community shall work hard to ensure that changes in this policy are for better distribution and more access to members, changes to less resources or more restrictive usage shall only happen when it is extremly nessecary.

In case of running out of resources administrators will investigate if one area or person is using excess amounts of resources, or if some resources are allocated to an unactive area, if no resource waste is found this will b taken to mean the community has grown enough to justify acquiring new resources.

Resource Distribution

  1. Main purpose of the webspace is to serve the core eglug.org website.
  2. Due to the unsecure nature of FTP, FTP space will be allocated for anonymous access to Free/Open Source Software related packages developed as part of eglug.org activities.
    • it must be realised that in most cases a LUG is not the correct place to host files.
  3. All moderators and Administrators will be granted eglug.org email boxes.
    • the boxes are to remain valid as long as the owner is still considered a member of EGLUG.
    • mailbox quota may be changed by administrators according to circumstances as long as they provide adequate notice.
  4. All Senior members get an eglug.org forward address.
    • The addresses remain valid as long as the owner is considered a member of EGLUG
  5. Members are enocuraged to use their eglug.org emails in all matters relating to eglug.org, they're of course free to use it for personal uses.
  6. Upon request moderators can have a limited space and a subdomain for personal use.
    • The subdomain will be fashioned after the members nick in the eglug.org website.
    • All rules applying to blogs apply to these personal spaces.
    • Administrators may at any point anounce they can no longer grant such requests, they're not however to pick and choose between requests, requests are honored on a first come first serve basis.
  7. Upon request senior users and moderators can have space and a subdomain for use in their personal Free/Open Source related projects as long as the project does not fit another section of the eglug.org website.

  • A visible link to this project will be provided in the eglug.org website.
  • Administrators may at any point anounce they can no longer grant such requests, they're not however to pick and choose between requests, requests are honored on a first come first server basis.
  1. All senior members and above are granted blogs on the eglug.org website and a limited image gallery to use as they see fit.

The rest of the resources are to be used by the administrators to server the needs of the community, Administrators are required to utilize these resources to implement any features or ideas the community agrees on.


we should add language to describe a formal process for collecting money for annual payments.

we should also add language to describe a formal process for dealing with running out of resources.

we should also add language to the effect that hosting provider should not be changed except under very extreme conditions to minimize dns instability and the pain of migrating emails boxes and stuff like that.

cheers, Alaa