Differences

This shows you the differences between two versions of the page.

--- fuel_opnfv_governance [2015/10/02 19:21]
Jonas Bjurel created
+++ fuel_opnfv_governance [2015/10/04 19:46] (current)
Jonas Bjurel [Fuel@OPNFV participation]
@@ Line 1: / Line 1: @@
-====== Governance of project Fuel@OPNFV ======
+======= Governance of project Fuel@OPNFV =======
 Participants in project Fuel@OPNFV agree to the following governance:
-==== Fuel@OPNFV governance====
+=====Fuel@OPNFV participation=====
-  * Fuel@OPNFV participation:
     * Anyone can join the Fuel@OPNFV project as a contributor
-    * Anyone can nominate him/her self to become a Fuel@OPNFV committer approved by an absolute majority vote result from all existing Fuel@OPNFV committers.
+    * Anyone can nominate him/her self to become a Fuel@OPNFV committer pending approval by an absolute majority vote result from Fuel@OPNFV committers, prior merits in OPNFV or other open source initiatives counts a lot!
-  *
-  * Fuel Project lead
-    * Projects which provide/create a deployment tool for OPNFV can choose to participate in Genesis requirements definition. A project which plans to join Genesis needs to formally apply for participation (see "procedure to join Genesis" below). The filled-in application form has to be signed by the project lead of the applying project and will be stored in the genesisreq repository for reference.
-    * Projects which choose to participate in Genesis have to support the requirements defined by Genesis. "Support of a requirement" means that the required functionality is supported in the target release identified.
-    * A project which participates in Genesis, but fails to support the requirements defined by Genesis for an upcoming release will be excluded from Genesis. Support of defined requirements by the participating projects will be assessed by the committers of the Genesis project in a dedicated review meeting at the RC0 milestone of an upcoming OPNFV release. Failure to support the requirements defined by Genesis for the upcoming release results in removal of the project from Genesis; committers can overrule exclusion by a majority vote of all committers.
-    * A project can choose to stop participating in Genesis at any time. If a project withdraws its participation in Genesis, the committer representing the participating deployment tool project will also be removed from the list of committers of Genesis.
-  * Genesis committers:
-    * Projects which participate in Genesis are represented by their lead committer/project lead in the Genesis project.
-    * Committers of the Genesis project will elect a committer from the newly joined project to become a committer on the Genesis project following the usual OPNFV procedures. It is expected that typically the lead committer/project lead of a participating project will be the primary choice to become a committer on the Genesis project.
-    * Genesis' list of committers is defined as the set of lead committers of the participating project and the Genesis project lead; i.e. there are no other committers than the individual lead committers of the participating project leads as well as the Genesis project lead.
-    * The Genesis project intends to have at most one committer per company represented on the project.
-  * Genesis contributors:
-    * Contribution to Genesis is open to everyone.
-==== Documenting requirements and finding agreement ====
-  * All requirements defined by Genesis will be documented in the genesisreq repository.
-    * Requirements will be associated with a specific target release of OPNFV.
-    * Requirements have to be supported by all projects participating in Genesis.
-  * New contributions (provided through a patch) will only be merged into the genesisreq repository if an *absolute majority** of all committers of the Genesis project have reviewed the patch in Gerrit and responded with a "+1". Note that all committers are expected to vote on all patches (+1 = agree, 0 = abstain, -1 = disagree).
-==== Procedure to join Genesis ====
-A deployment project, referred to as "deployment tool" below, can join "Genesis" as follows:
+=====Fuel@OPNFV Project lead=====
+     * Fuel@OPNFV project leads must be a project committer during his/her time as project lead - thus the nomination/election of a project lead inherently means nomination/election of a project committer, including the merit requirements that comes with a committer approval.
+     * The OPNFV@Fuel project leadership is a one year assignment, the project leadership assignment period spans from June 1 to June 1 the following year. Project lead nomination candidates shall be at hand one calendar month before the assignment period ends.
+     * A project lead must receive a relative majority in respect to the nominees, all committers MUST vote.
+     * A project lead nominee candidature is not valid unless the nominee agrees and confirms his/her nomination.
+     * There is no restriction on number of assignment periods for a project leader.
+     * Only project committers are eligible for project lead voting/election.
+     * The voting/election is open/non-anonymized and takes place in a regular weekly project meeting.
+     * In case a project lead wants to step down prior to his/her assignment period ends, it is advisable to do so 2 month prior to effect, this to give time for a thorough nomination and election process.
-The project lead/lead-committer of project "deployment tool" sends a signed email to the Genesis project leadership, copying the opnfv-tsc@lists.opnfv.org mailing list. The email needs to include the following:
+=====Fuel@OPNFV rules of arbitration=====
+Although Fuel@OPNFV is an Open-source project with the lead-star of Meritocracy, the expectation of the project lead is that, in consensus with the project committers - steer the project into sound future prospects, keeping project and architectural goals in mind. A well respected OPNFV@Fuel project lead should under normal conditions be able to do that by finding consensus - only in extraordinary cases should formal voting be used.
-//Herewith project "deplo    * Requirements will be associated with a specific target release of OPNFV.
+Formal voting on decisions can be requested if an absolute majority of the project committers request this. In this case, only committers are eligible to vote, and the result should follow the single majority vote outcome.
-    * Requirements have to be supported by all projects participating in Genesis.
-  * New contributions (provided through a patch) will only be merged into the genesisreq repository if an *absolute majority** of all committers of the Genesis project have reviewed the patch in Gerrit and responded with a "+1". Note that all committers are expected to vote on all patches (+1 = agree, 0 = abstain, -1 = disagree).yment tool" requests to join the Genesis project. The "deployment tool" project agrees to the principles of the Genesis project and the associated project governance defined in wiki.opnfv.org/genesis/governance. Specifically, the "deployment tool" project will participate in requirements definition and implement the requirements jointly defined by the Genesis project.//
-The Genesis project (the project lead or any other committer) will acknowledge receiving the application and initiate a vote selecting a committer for the newly joining project. A copy of the application will be stored for future reference in the genesisreq repository. The newly elected committer representing the newly added "deployment tool" will be added to the list of Genesis committers.

Wiki

User Tools

Site Tools

Differences

Page Tools