genesis:governance
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
genesis:governance [2015/06/30 11:05] Frank Brockners |
genesis:governance [2015/08/03 14:56] (current) Frank Brockners |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * Genesis participation: | * Genesis participation: | ||
| - | * 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 Genesis repository for reference. | + | * 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. | * 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 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. | ||
| Line 20: | Line 20: | ||
| ==== Documenting requirements and finding agreement ==== | ==== Documenting requirements and finding agreement ==== | ||
| - | * All requirements defined by Genesis will be documented in the genesis repository. | + | * All requirements defined by Genesis will be documented in the genesisreq repository. |
| * Requirements will be associated with a specific target release of OPNFV. | * Requirements will be associated with a specific target release of OPNFV. | ||
| * Requirements have to be supported by all projects participating in Genesis. | * Requirements have to be supported by all projects participating in Genesis. | ||
| - | * New contributions (provided through a patch) will only be merged into the genesis repository if an *absolute majority** of all committers of the Genesis project have reviewed the patch in Gerrit and responded with a "+1". | + | * 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 ==== | ==== Procedure to join Genesis ==== | ||
| Line 33: | Line 33: | ||
| //Herewith project "deployment 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.// | //Herewith project "deployment 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 Genesis repository. The newly elected committer representing the newly added "deployment tool" will be added to the list of Genesis committers. | + | 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. |
genesis/governance.1435662332.txt.gz ยท Last modified: 2015/06/30 11:05 by Frank Brockners
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
