From Fedora Project Wiki

< Env and Stacks

Revision as of 17:12, 5 November 2013 by Toshio (talk | contribs) (Initial Env and Stacks import from the cloud governance.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. This is an unratified draft document

Fedora Environment and Stacks Working Group Governance Structure

This document describes the governing structure for the Fedora Environment and Stacks Working Group.

Will be re-evaluated after Fedora 21
This document is based on the Cloud Working Groups Governance document. However, the Environment and Stack WG is very different. The Cloud WG has a mission of creating a specific Fedora Product. The Environments and Stacks Working Group is more of a research and development group that may end up launching wholly new products or helping to build technologies and procedures that help the other WGs produce their products. As such, we're going to re-evaluate whether the governance we've adopted here is a good fit for what we do in practice after we've had a little time to see what work we actually do.


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.

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.

Current Members

  • James Antill
  • Robyn Bergeron
  • Joe Brockmeier
  • Haïkel Guémar
  • Sam Kottler
  • Sandro Mathys
  • Matthew Miller (FESCo Liaison)
  • Frankie Onuonga
  • Mattias Runge

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