From Fedora Project Wiki

< Server

Revision as of 15:35, 31 October 2013 by Duffy (talk | contribs)

This is a draft document!
This document is a work-in-progress draft and has not been agreed upon yet.


Fedora Server WG Governance

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


The Fedora Server WG has nine voting members with the members of the Server Work Group being made up from a single indvidual representive from the following compositon group Docs, Rel-Eng, QA, Ambassadors, Infrastructure, Design, Marketing followed by the remaining two members coming from the Server Community itself.

Each composition group is responsabile for chosing their member to appoint to their respective seat by.

In the event that a current member relinquishes their seat, each composition group is responsabile for chosing another member to appoint to their respective seat by.

If there are no candidates available, the existing remaining members of the Server WG will fill the seat by selecting a candidate and approving by majority consensus.

Each representing person from compositon group will be responsible for the Server Working Group's interaction and other duty's within their group.

Current Members

  • Stephen Gallagher: Representing Server Community and the initial FESCo Liaison
  • David Strauss: Representing Server Community
  • Jim Perrin: Representing Server Community
  • Jóhann B. Guðmundsson: Representing the Fedora QA team
  • Kevin Fenzi: Representing Fedora Infrastructure
  • Miloslav Trmač: Representing Server Community
  • Máirín Duffy: Representative the Fedora Design Team
  • Simo Sorce: Representing Server Community
  • Truong Anh. Tuan: Representing the Fedora Ambassadors

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

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 WG itself where the necessary quorum is not reach (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 and do the vote live, with participating individual in that meeting having the right to put down vote.

Changing these Rules

This document will be approved by consensus of the initial Server WG members and approved by FESCo. After initial ratification, any substantive changes can be approved by majority vote and sent to FESCo for acceptance.