|
|
| (21 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| | __NOTOC__ | | __NOTOC__ |
| − | = Technical committee = | + | = OpenStack Technical Committee = |
| | | | |
| − | Status: RFC
| + | The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters. |
| | | | |
| − | === Mission ===
| + | The Technical Committee is formally defined in the [http://www.openstack.org/legal/bylaws-of-the-openstack-foundation/ OpenStack Foundation bylaws] (in particular article 4.1(b), article 4.13 and Appendix 4) and further refined in the [https://governance.openstack.org/tc/reference/charter.html OpenStack Technical Committee Charter]. |
| | | | |
| − | The Technical Committee ("TC") is tasked with providing the technical leadership for the OpenStack project as a whole (including core projects, library projects, gating projects and supporting projects). It enforces OpenStack core projects ideals (Openness, Transparency, Commonality, Integration, Quality...), decides on issues affecting multiple projects, and generally forms an ultimate appeals board for technical decisions within OpenStack projects. | + | The TC governance website at https://governance.openstack.org/tc/ contains all reference documents and resolutions voted by the OpenStack Technical Committee (which are openly managed via [https://review.openstack.org/#/q/status:open+project:openstack/governance,n,z proposed changes] to the [http://git.openstack.org/cgit/openstack/governance openstack/governance git repository]). |
| | | | |
| − | The TC has control over which projects are considered OpenStack projects, including those in core incubation status. It recommends projects for final OpenStack Core addition, combination, split or deletion to the Board of Directors, which has sole authority to approve them.
| |
| | | | |
| − | === Members === | + | === Current members === |
| − | Two options:
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| − | or
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| | | | |
| − | === Chair ===
| + | You can find a list of the current Technical Committee members [https://governance.openstack.org/tc/ here]. |
| | | | |
| − | After each election, the TC proposes one of its members to act as the TC chair. In case of multiple candidates, it may use a single-winner election method to decide the result (see below). The Board of Directors has the authority to approve the TC chair and shall approve the proposition, unless otherwise justified by its bylaws. The TC chair is responsible for making sure meetings are held according to the rules described below, and for communicating the decisions taken during those meetings to the Board of Directors and the OpenStack community at large. It may be revoked under the conditions described in the Foundation bylaws.
| |
| | | | |
| − | === Meeting === | + | === Technical Committee Charter === |
| | | | |
| − | TC meetings happen publicly, weekly on IRC. The meeting time should be decided among TC members after each election. If there isn't consensus on a meeting time, the option of rotating the time weekly should be explored. The TC maintains an open agenda on the wiki. A TC meeting is automatically called if anything is posted to that wiki by one of its members at least one day before the meeting time. For a meeting to be actually held, at least half of the members need to be present. Non-members affected by a given discussion are strongly encouraged to participate to the meeting and voice their opinion, though only elected TC members can ultimately cast a vote.
| + | You can find an up-to-date copy of the Technical Committee Charter [https://governance.openstack.org/tc/reference/charter.html here]. |
| | | | |
| − | === Motions ===
| |
| | | | |
| − | Before being put to a vote, motions presented before the TC should be discussed publicly on the development mailing-list for a minimum of 5 business days to give a chance to the wider community to express their opinion. TC members can vote positively, negatively, or abstain. Decisions need more positive votes than negative votes, and a minimum of positive votes of at least one fourth of the total number of TC members.
| + | === Mailing-list === |
| | | | |
| − | === Proxying ===
| + | The [http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc openstack-tc mailing-list] is used for communication within the Technical Committee. Posting is moderated for non-members. |
| | | | |
| − | When a TC member is unable to make a meeting, he is encouraged to name a proxy that will represent his opinion and vote on his behalf during the meeting. Only members really present at the meeting (directly or proxied) can vote.
| + | [[Category:OpenStackFoundation]] |
| − | | |
| − | === Election ===
| |
| − | Depending on the option chosen above:
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| − | or
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| − | | |
| − | === Voters ===
| |
| − | | |
| − | The Technical committee represents the active technical contributors to OpenStack projects. The TC members are therefore elected by the Active Technical Contributors ("ATC"), which are a subset of the Foundation Individual Members. Individual Members who committed a change to any of the official OpenStack projects (over which the TC has final authority) in the past 18 months before an election are automatically considered ATC. Specific technical contributors who did not have a change recently accepted in one of the OpenStack projects but nevertheless feel their contribution to the OpenStack project is technical (bug triagers, technical documentation writers...) can exceptionally apply for ATC by sending an email to the TC chair. Final approval on the exception is decided by the TC itself, and lasts one year.
| |
| − | | |
| − | === Candidates ===
| |
| − | | |
| − | Any ATC can propose his candidacy for an available TC seat.
| |
| − | | |
| − | === Initial committee ===
| |
| − | | |
| − | Depending on the option chosen above:
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| − | or
| |
| − | {| border="1" cellpadding="2" cellspacing="0"
| |
| − | |}
| |
| − | | |
| − | === Election systems ===
| |
| − | | |
| − | For single-winner elections, the Condorcet Schulze algorithm shall be used.
| |
| − | | |
| − | For multiple-winner elections, a system ensuring representativity of smaller groups and resistant to vote management shall be used. Options considered include [http://www.cs.cornell.edu/w8/~andru/civs/ CIVS]'s Schulze with [http://www.cs.cornell.edu/w8/~andru/civs/proportional.html proportional representation] enabled, traditional STV or Schulze STV.
| |
| − | | |
| − | === Amendment ===
| |
| − | | |
| − | Amendment to those Technical Committee rules shall only be proposed by a motion accepted by at least two-thirds of the TC members. The Foundation Board of Directors has final authority to approve them.
| |
The OpenStack Technical Committee is one of the governing bodies of the OpenStack project. It is an elected group that represents the contributors to the project, and has oversight on all technical matters.
