Index: site-author/learn/newcommitters.html =================================================================== --- site-author/learn/newcommitters.html (revision 371423) +++ site-author/learn/newcommitters.html (working copy) @@ -30,6 +30,49 @@ is re-emerging as a Best Practice for ASF projects.

+

Process details

+

+ Below is a more detailed breakdown of the voting process from the + perspective of the committer who proposes the vote. +

+
    +
  1. + It is a good practice to first make an informal nomination on the + private project committer or PPMC list to check that there are no + objections to giving committer access to the nominated contributor. + If there are objections, then they can be resolved in private or the + committer vote can be postponed or cancelled without raising personal + issues on the public mailing list. +
    2. +
  2. + The formal vote is proposed by sending a [VOTE] message to the + developer mailing list and the general Incubator mailing list + (general@incubator.apache.org). The message subject should identify + the vote and the body should contain the nomination and brief voting + instructions. Good examples can be found in + the + archives. +
    3. +
  3. + Both the project committers and the Incubator PMC members are entitled + to vote. See the + voting page + for information on how to express votes. In a normal ASF project the + project PMC makes the decision on adding a new committer. In a podling + project it is the Incubator PMC that has formal right to accept + new committers. This is the reason for sending the committer vote also + to the Incubator mailing list. +
    4. +
  4. + A committer vote requires at least three positive votes (+1) and no + objections (-1) to pass. Because of the above, there needs to be at + least three positive votes from the Incubator PMC for the + vote to pass. For examples of how the vote can proceed, please see + the + archives. +
    5. +
+

Welcome!