developer:committer_promotions
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
developer:committer_promotions [2015/02/04 09:39] Christopher Price created |
developer:committer_promotions [2015/09/10 08:39] (current) Ulrich Kleber [After a successful nomination] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| While the initial committers on a project are nominated at project formation, it is expected that community members will emerge as willing committers over time. | While the initial committers on a project are nominated at project formation, it is expected that community members will emerge as willing committers over time. | ||
| - | Committer nomination and promotion must take place according to [http://www.opendaylight.org/project/tsc/charter Section 7 of the TSC Charter]. This page intends to describe how the charter shall be interpreted in a practical step by step manner. | + | Committer nomination and promotion must take place according to Section 8 of the [[https://www.opnfv.org/developers/technical-project-governance/tsc-charter|TSC Charter]]. This page intends to describe how the charter shall be interpreted in a practical step by step manner. |
| ==== Prior to nomination ==== | ==== Prior to nomination ==== | ||
| Line 16: | Line 16: | ||
| ==== Nomination for committer promotion ==== | ==== Nomination for committer promotion ==== | ||
| - | The nomination for committer promotion begins with the project lead or delegate sending an e-mail to the <project>-dev list requesting the committers on the project vote on the nomination. | + | The nomination for committer promotion begins with the project lead or delegate sending an e-mail to the opnfv-tech-discuss mailing list with the appropriate project identified in the subject line %%[project-name]%% requesting the committers on the project vote on the nomination. |
| The nomination e-mail should begin with a clear topic name and be followed by a statement of motivation. The statement of motivation should describe any achievements or activities the contributor has performed of notable value for the project and may include a link to a git-log of the nominees activity history. More than one contributor may be nominated in one nomination e-mail. | The nomination e-mail should begin with a clear topic name and be followed by a statement of motivation. The statement of motivation should describe any achievements or activities the contributor has performed of notable value for the project and may include a link to a git-log of the nominees activity history. More than one contributor may be nominated in one nomination e-mail. | ||
| The e-mail may take the following form: | The e-mail may take the following form: | ||
| * From: <project lead> | * From: <project lead> | ||
| - | * To: <project>-dev@lists.opendaylight.org | + | * To: opnfv-tech-discuss@lists.opnfv.org |
| - | * Nomination for new Committer(s): <contributors name(s)> | + | * Subject: [project-name] Nomination of Committer(s) promotion for: <contributors name(s)> |
| - | * The motivation for nominating <contributors name> to committer on the <project> project is due to a long history of providing value to the project through consistent high quality and valuable contributions. <refer to relevant contributions and the value they provided to the project> I provide a link to the relevant contributions. <link> | + | * Body: The motivation for nominating <contributors name> to committer on the <project> project is due to a long history of providing value to the project through consistent high quality and valuable contributions. <refer to relevant contributions and the value they provided to the project> I provide a link to the relevant contributions. <link> |
| - | Once the e-mail has been sent the nomination stands until a clear majority vote for or against the nomination has been met, or the nominator withdraws the nomination. Voting shall take place according to the Condorcet or single transferable vote methods outlined in [http://www.opendaylight.org/project/tsc/charter Section 6 of the TSC charter]. | + | Once the e-mail has been sent the nomination stands until a clear majority vote for or against the nomination has been met, or the nominator withdraws the nomination. Voting shall take place according to the Condorcet or single transferable vote methods outlined in Section 7 of the [[https://www.opnfv.org/developers/technical-project-governance/tsc-charter|TSC charter]]. |
| - | ==== Addressing the TSC with a successful nomination ==== | + | ==== After a successful nomination ==== |
| - | At the completion of a nomination process, if the nominee was successful, the nominator should address the TSC via the TSC mailing list tsc@lists.opendylight.org by forwarding the nomination e-mail along with a summary of the outcome of the committer votes. The TSC Chair should be contacted to identify a suitable time-slot at the available opportunity for the TSC to take a formal vote on the nomination. | + | At the completion of a nomination process, if the nominee was successful, the Project lead should inform the TSC via the TSC mailing list opnfv-tsc@lists.opnfv.org by forwarding the nomination e-mail along with a summary of the outcome of the committer votes. |
| - | The TSC will consider the following as relevant to the decision: | + | |
| - | * The nomination process and the outcome as captured by the project lead or delegate | + | |
| - | * The number of committers on the project and the need for an increase in committers | + | |
| - | * Any community feedback received around the nomination or nominee | + | |
| - | The TSC will vote on the nomination according to the voting methods outlined in [http://www.opendaylight.org/project/tsc/charter Section 6 of the TSC charter]. The outcome of the vote will be recorded in the minutes of the meeting and any associated reasoning for the decision that has been taken. | + | |
| - | If the vote on the TSC is successful the OpenDaylight administrative team will be informed and the nominee will be promoted to project committer. | + | |
| - | If the vote on the TSC was not successful the reasoning and motivations for the decision will be captured in the meeting minutes. The project lead may choose to act to redress the captured reasoning and once ready nominate the contributor once more following the above described process. | + | The Project leader should additionally update the "Key Project Facts" section of the project WiKi page as well as the INFO file in the project repository and inform the LinuxFoundation facilities team of the individuals change in status. This should be done by sending an update e-mail to opnfv-helpdesk@rt.linuxfoundation.org with the new committers e-mail and LinuxFoundation ID. This e-mail should either contain a link to the meeting minutes or relevant specific email archive recording the vote. |
| + | ==== Contesting a nomination or promotion ==== | ||
| + | |||
| + | The TSC is responsible for overseeing the committer nomination and promotion processes. In the case that any member of the OPNFV community would like to raise discussion or has concerns over a committer promotion, nomination, or the committer promotion process they should reach out to the TSC via the TSC mailing list opnfv-tsc@lists.opnfv.org, or if preferred the TSC Chair Person directly to identify if further action or intervention by the TSC is needed. | ||
developer/committer_promotions.1423042748.txt.gz · Last modified: 2015/02/04 09:39 by Christopher Price
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
