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.
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.
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:
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.
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