From Fedora Project Wiki
mNo edit summary
(Remove redundant membership list)
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{admon/warning | This is a draft document! | This document is a work-in-progress draft and has not been agreed upon yet.
{{admon/tip | 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.
'''Discussion'''
}}
* [https://lists.fedoraproject.org/pipermail/server/2013-October/000223.html 'Discussion of Server Working Group governance' mailing list thread]
* [http://blog.linuxgrrl.com/2013/10/30/fedora-server-working-group-initial-meeting-minutes/ 30 Oct 2013 Meeting]}}
* [https://lists.fedoraproject.org/pipermail/server/2013-October/000315.html 'The "Membership" section of the governance charter draft' mailing list thread]


== Fedora Server WG Governance ==
== Fedora Server WG Governance ==
Line 11: Line 8:
=== Membership ===
=== Membership ===


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.
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 composition group is responsabile for chosing their member to appoint to their respective seat by.
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.


In the event that a current member relinquishes their seat, each composition group is responsabile for chosing another member to appoint to
The current composition of the Server Working Group can usually be found at the [[Server]] landing page.
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 ===
=== 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.
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.
 
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.  
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 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.
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.


=== Changing these Rules ===
=== Changing these Rules ===


This document will be approved by consensus of the initial Server WG members and approved by FESCo.  
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.
After initial ratification, any substantive changes can be approved by majority vote and sent to FESCo for acceptance.

Revision as of 00:33, 7 September 2016

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.

Fedora Server WG Governance

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

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.

The current composition of the Server Working Group can usually be found at the Server landing page.

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.

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.