Env and Stacks/Governance Charter
m (Fixed two more typos.)
m (Petersen moved page User:Toshio/Env and Stacks Governance to Env and Stacks/Governance Charter: final place)
Revision as of 01:15, 5 February 2014
This document describes the governing structure for the Fedora Environments and Stacks Working Group.
The Fedora Environments and Stacks Working Group has nine voting members, one selected by the Fedora Engineering Steering Committee as the liaison to FESCo, and the others initially selected by the FESCo liaison.
Continuity is not as important with the Environments and Stacks Working Group as other Working Groups since we are incubating fresh new ideas so we choose our voting members via election.
- Elections for half the seats will be held after every fedora release (approximately 6 months) to match with FESCo. Elected members serve for two releases before needing to stand for re-election
- Both candidates and the electorate must have signed the FPCA and be in one other non-cla group to show that they are Fedora Contributors. This is the same group of people as the FESCo electorate but broader than the FESCo candidate pool.
- Other details of the election policy match the FESCo election policy.
- John Dulaney
- Honza Horak
- Tadej Janež
- Slavek Kabrda
- Sam Kottler
- Petr Kovar
- Toshio Kuratomi
- Marcela Mašláňová (FESCo Liaison)
- Jens Petersen
- Debi Rieden
Because Fedora is a global project, members of the working group may be distributed across multiple timezones. It may be possible to have real-time IRC meetings, but in general we will conduct business on the Environments and Stacks mailing list.
Many of our decisions can be made through "lazy consensus". Under this model, an intended action is announced on the mailing list, discussed, and if there is no controversy or dissenting views within three days, simply done.
For bigger issues (where there is disagreement, a long-term impact, or where an action may not easily be undone) we will have more formal voting. Working group members can vote +1 to approve, -1 to disagree, or 0 to abstain. Abstentions serve to remove one person from being counted towards pass or failure. So, with no abstentions, a simple majority of five members is necessary to pass a measure. With two abstentions, four +1 votes are necessary, and so forth. Note that neglecting to vote is not equivalent to abstaining. You must explicitly cast a +0 vote if you wish to remove yourself from being counted towards pass or fail.
We will use the ticketing system at  to record our votes. Non-members may comment on the ticket (and, of course, discuss on the mailing list) but are asked to refrain from putting votes in the ticket. Working Group Members should add their +1, 0, or -1 votes as comments to the ticket.
Changing These Rules
This document will be approved by consensus of the initial Working Group members and approved by FESCo. After initial ratification, any substantive changes can be approved by majority vote and sent to FESCo for acceptance.