|
|
| Line 1: |
Line 1: |
| '''This is an unratified draft document'''
| | #REDIRECT [[Cloud]] |
| | |
| = Fedora Cloud Working Group Governance Structure =
| |
| | |
| This document describes the governing structure for the Fedora Cloud Working Group.
| |
| | |
| == Mission ==
| |
| | |
| The Fedora Cloud Working group leads the design and production of Fedora's cloud product.
| |
| | |
| ''Question: do we want to clarify the pets-vs-cattle distinction right up front here? Does anyone have (or prefer) a less cutesy way of putting it?''
| |
| | |
| == Role in Fedora ==
| |
| | |
| The Fedora Cloud Working Group is a subset of the Fedora Cloud SIG, one of the many teams working on Fedora.
| |
| | |
| The Working Group is responsible for initial and ongoing development of the ''Product Requirements Document'', and for coordinating production of the Fedora Cloud operating system.
| |
| | |
| We work with existing groups across the greater Fedora Project, and may delegate particular members to take responsibility for working with certain other teams. For example, a working group member may act as a coordinator for quality assurance or for release engineering.
| |
| | |
| == Membership ==
| |
| | |
| The Fedora Cloud 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.
| |
| | |
| ''Decision time! Do we want option A or option B, or something else?''
| |
| | |
| '''Option A''' ''Members of the Working Group serve two year terms. At the end of the two year period, FESCo will either renew the FESCo liaison or appoint a new one. The other positions will be filled by general election every two years. As a special exception, four seats will be filled in one year, with those positions chosen at random (unless some number of members decide to step down). Voting will follow the standard Fedora election process and be open to all contributors in the CLA+1 group.''
| |
| | |
| '''Option B''' ''Because continuity is important, Working Group members serve as long as they are able and willing. When a position in the group becomes available, that position will be filled by unanimous consent of the existing members.'' (n.b. this is how the Fedora Packaging Committee operates).
| |
| | |
| == Current Members ==
| |
| | |
| * James Antill
| |
| * Robyn Bergeron
| |
| * Joe Brockmeier
| |
| * Haïkel Guémar
| |
| * Sam Kottler
| |
| * Sandro Mathys
| |
| * Matthew Miller (FESCo Liaison)
| |
| * Frankie Onuonga
| |
| * Mattias Runge
| |
| | |
| == Communications ==
| |
| | |
| It is our policy to default to open; wherever possible, all communications will be held in the open and archived for future public reference. In some rare cases, it may necessary for some members of the group to enter into non-disclosure agreements (for example, when working with public cloud vendors) but such circumstances should be minimal and not impact core decisions of the group.
| |
| | |
| Our primary forum for discussion is the Cloud SIG mailing list, https://lists.fedoraproject.org/mailman/listinfo/cloud. Members also regularly are available in the <tt>#fedora-cloud</tt> IRC channel on FreeNode.
| |
| | |
| ''Q: insert something here about communications with FESCo, QA, RelEng, Marketing, Ambassadors, Websites, etc., etc.?''
| |
| | |
| == 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, but in general we will conduct business on the Fedora Cloud 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 with a few days, simply done.
| |
| | |
| For bigger issues, where there may be disagreement, or where there is long-term impact, or where an action may not easily be undone, we will use a ticketing system for voting https://fedorahosted.org/cloud/. Working group members can vote +1 to approve, -1 to disagree, or 0 to abstain; five +1 votes are necessary for a measure to pass. 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.
| |
| | |
| == 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.
| |
