Disclaimer: This text is an edited, by PepeAmpere, snapshot of the anonymous open etherpad offered in that thread.
This shortcut from discussion in: http://etherpad.springrts.com/p/organization
Details and Q/A are there.
Organizational hierarchy
- Spring Leader
- Board of Project Leaders
- Site administrator
- Lobby administrator
- Forum administrator
- Archives administrator (springfiles, replay pages)
- Wiki administrator (docu master, etc.)
- Finance administrator (care about accounts)
- + maintainers of different servers and services
Spring Leader
(doing decisions)
Person chosen by other developers and capable of appointing people to other roles.
- he makes the decisions which are forbbiden for Board of project leaders - decisions on field of engine, site rules, protocols, lobby, legal stuff, ... etc
- blog-like home page listing all important leaders actions (decisions, links to important dicussions, etc.)
(keeping stability of development environment)
- GENERAL RIGHTS:
- right of board to VETO any decision made on field of engine, site rules, protocols, lobby, legal stuff - if majority (50 % +) of board vote for VETO
- right of member of board to not be moderated (... specify better later)
- right of member to propose VETO voting
- SPECIFIC RIGHTS
- choose the leader
- IT DOESNT HAVE RIGHT:
- Not allowed to make any decision on field of engine, site rules, protocols, lobby, legal stuff (except specified field in "speicific rights") - and not allowed actively justify and enforce such decision
You become member of board by beeing in roles:
- appointed by Leader (max 20 % of total board vote weight)
- site administrator
- lobby administrator
- forum administrator
- archives administrator
- docu administrator
- developers (procedure of estabilishing dev board member is shortly described below)
- engine
- lobby
- autohost
- map
- animation (currently noone, yes)
- model
- AI
- verified game projects (details will be discussed on other place, like weight of vote or number of board members per project, etc..- if necessary)
- other verified spring related projects
- voting system
- archive of all votings + comments of all members if there were some voting
- blog-like home page listing all board-news
- separated forum section for board members where only board members are allowed to contribute
- administrator of board functionality (some bureaucratically skilled person)
- If person have right to become member board due satisfiing conditions of more classes listed above, it is member of board with one vote and hes considered as developer if he satisfies at least on condition of class developers.
- Appointed members are given by leader.
- somones right to become member of this board based on his work on given field (developers part of board):
- once a year board is expanded by supported devs: person become board member if it is supported by enough /specified later/ verified users (verfication based on minimal spring rank of ingame time))
- this right (once verified) cannot be canceled once it is approved
- right remains active for next 2 years