Developer Organization

SMGL's contributors are organized into a team of Lead Developers and a team of General Developers. Leads are further divided into a Project Lead, identified Component Leads, and General Leads. The Project and Component Leads may also have Assistants.

General Developers:

• are defined as all non-Lead Developers listed at Developers

• can be added to the project and given repository access by any Lead Developer.

• have commit access to the various project components, at the discretion of the Lead over that component.

• have the option to cast a binding vote in all Lead Election votes.

• have the option to cast a non-binding vote in all other votes.

• can be removed by a super majority vote of the Lead Developers.

• can have a removal vote vetoed by a super majority vote of all Developers.

• are automatically nominated and seconded for a removal vote after one year of inactivity (defined as no committed changes to any part of the project's source code or documentation repositories (including web sites)).

  • Once someone is no longer considered a developer, their entry on the Developers page, all of their SCM accounts, @sourcemage.org aliases, @sourcemage IRC cloak, and special #sourcemage* IRC permissions must be removed.

Lead Developers:

• are elected from among the General Developers by a simple majority vote of the General + Lead Developers.

• have commit access to the various project components, at the discretion of the Lead over that component.

• are required to cast a binding vote in all Lead Election and other votes.

• serve an unlimited term as long as they are not removed by vote.

• can be removed as Leads by a super majority vote of the other Lead Developers.

• can have a removal vote vetoed by a super majority vote of all Developers.

• are automatically removed without vote or veto if they fail to cast any votes for two consecutive months or longer, provided there were at least two votes hold in that period.

• are automatically nominated and seconded for a removal vote after six months of inactivity (defined as no committed changes to any part of the project's source code or documentation repositories (including web sites)).

• revert to General Developers if removed.

Project and Component Leads:

• are elected from among the Lead Developers by a simple majority vote of the General + Lead Developers.

• remain Lead Developers.

• have primary responsibilty for and daily authority over one of the identified Project Components (or in the case of the Project Lead, the entire Project).

• are subject to the outcome of any votes affecting their Components.

• serve a one year term, with no limit on number of terms.

• can be removed as Project or Component Leads by a super majority vote of the other Lead Developers.

• can have a removal vote vetoed by a super majority vote of all Developers.

• remain Lead Developers if removed.

Assistants:

• can be any General or Lead Developer chosen by the individual Project and Component Leads.

• act on behalf of and with the authority of the Lead they are assisting, at the Lead's discretion.

• do not receive any extra binding or non-binding vote as an Assistant.

• can cast the Lead's binding vote in their place in any vote, at the Lead's discretion.

• retain their own binding or non-binding individual vote for all elections they would otherwise be involved in.

• revert to their regular, non-assistant status if the Lead they are assisting steps down or is otherwise removed as Lead.

For more information on Lead elections see the Voting Policy.