Server/Governance Charter

From FedoraProject

< Server(Difference between revisions)
Jump to: navigation, search
m
(Current Members)
 
Line 17: Line 17:
 
* [[User:Davidstrauss|David Strauss]]:        Representing Server Community
 
* [[User:Davidstrauss|David Strauss]]:        Representing Server Community
 
* [[User:Jperrin|Jim Perrin]]:            Representing Server Community
 
* [[User:Jperrin|Jim Perrin]]:            Representing Server Community
* [[User:Johannbg|Jóhann B. Guðmundsson]]: Representing the Fedora QA team
+
* [[User:adamw|Adam Williamson]]: Representing the Fedora QA team
 
* [[User:Kevin|Kevin Fenzi]]:          Representing Fedora Infrastructure
 
* [[User:Kevin|Kevin Fenzi]]:          Representing Fedora Infrastructure
 
* [[User:Mitr|Miloslav Trmač]]:        Representing Server Community
 
* [[User:Mitr|Miloslav Trmač]]:        Representing Server Community

Latest revision as of 17:34, 3 December 2013

Idea.png
This is an approved document.
This document was approved by the Server Working Group on November 5, 2013. It was approved by FESCo on November 6, 2013.

Contents

[edit] Fedora Server WG Governance

This document describes the governing structure for the Fedora Server WG.

[edit] Membership

The Fedora Server Working Group has nine voting members. We encourage involvement in the Server Working Group from all parts of the Fedora Project.

Each voting member of the working group will confirm their continued membership every six months. In the event that a current voting member relinquishes their seat, the remaining voting working group members are responsible for appointing a new voting member to fill the seat from the active Fedora Server community via majority consensus.

[edit] Current Members

[edit] Making Decisions

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 or Google+ hangouts, but in general we will conduct business on the mailing list or announce either IRC meetings or Google+ hangout events in advance should they take place.

The Server Working Group strives to work on consensus and only vote on things where it’s clear people aren’t going to be convinced to agree. 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 with a few days, simply done.

For bigger issues, where there may be disagreement within the Server Working Group itself where the necessary quorum is not reached (with 5 members being required for quorum,) or where there is long-term impact, or where an action may not easily be undone, we will schedule an IRC meeting during which a vote will be conducted. In the case where a voting member can not make a meeting, they can either pre-vote via the mailing list or abstain-by-default. Five positive votes will be required, regardless of the number of voting members present, for a proposal to be accepted.

[edit] Changing these Rules

This document will be approved by consensus of the initial Server 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.