If a developer has contributed a significant number of - high-quality patches, is interested in continuing the - contribution, and has demonstrated the ability to work well with +
If a person has made significant contributions of + high-quality, is interested in continuing to + contribute, and works well with others under the Apache guidelines, the project might vote to - grant that developer commit access. See the ASF How it Works document, - which explains + grant that person + commit access. See the ASF How it Works document, + which explains meritocracy and roles.
-Discussion of a potential new committer should take place on - the podling project's private list; normally it would take place on a - project's private list. After vetting the new candidate, the vote can - be called on either one of the two places listed below (notice the - balance between private and public lists):
--
-
- The podling's private list, with notice posted to the - Incubator private list. -
- The developer list, with notice posted to the Incubator - general list. -
The practice of a private discussion followed by a public, - pro-forma, vote is re-emerging as a Best Practice for ASF projects - (see this comprehensive discussion - about these practices).
-Only votes cast by Incubator PMC members are binding. If the vote is - positive, and the contributor accepts the responsibility of a - committer for the project, the contributor formally becomes an Apache - committer. An Incubator PMC member should then follow the - documented procedures - to complete the process, and CC both the Incubator PMC - and the PPMC when sending the necessary e-mails to root.
-Please direct the new committer to the Apache developer's pages, to - the Apache Incubator - site and to the Incubator Committers Guide for important additional - information.
+One of the PPMC members should lead the process of accepting + a new committer. For the purposes of this document, the proposing + PPMC member is referred to as the proposer, and the proposed + committer is referred to as the nominee. Discussion of a + nominee should take place on the podling project's private (PPMC) + list [in a Top Level Project it would take place on the project's + private list]. If there are any concerns raised during the + discussion, these need to be resolved so that there is consensus + among the PPMC members as to the suitability of the nominee for + the project and for Apache. Many projects adopt an approach where, + if there are any concerns, the nomination is delayed + for a few months. Many concerns go away with continued participation + by the nominee in the project. +
+After vetting the nominee, the vote can be called on either + one of the two places listed below (notice the difference between + private and public lists): +
-
+
-
+ The podling's private (PPMC) list, with notice posted to the
+ Incubator private list. The notice is a separate email forwarding
+ the vote email with a cover statement that this vote is underway
+ on the podling's private list. Many consider this approach to be
+ best practice. After completing the vote on the PPMC list, if
+ there are not three +1 votes from Incubator PMC members, the proposer
+ should call a vote on the Incubator PMC private list, summarizing
+ the discussion and vote, with a reference to the archived discussion
+ and vote threads by the PPMC. Note that only the Incubator PMC
+ members can see this discussion, and the podling's Mentors should
+ review all Incubator PMC feedback with the PPMC. Moreover, only
+ Apache members may review the private PPMC list (this is normally
+ not an issue since most Incubator PMC members are Apache members).
+
Many projects then follow the Incubator PMC vote with a pro forma + vote on the public project dev list, or have a welcome thread on the + public dev list. These are intended to make the new committer feel + welcome.
+ - The podling's developer list, with notice posted to the + Incubator general list. The notice is a separate email forwarding + the vote email with a cover statement that this vote is underway + on the podling's developer list. This approach is considered + inferior by many because it is a source of discord to have a + public vote like this fail or take a very long time. +
Only votes cast by Incubator PMC members are binding, but votes + by the PPMC are very important. The entire PPMC should show support + for the nominee. If the vote is positive (three or more binding +1 + votes and no binding -1 votes), the proposer offers committership + to the nominee. If the nominee accepts the responsibility of being + a committer for the project, the nominee formally becomes an + Apache committer.
+The proposer then asks an Incubator PMC member + to follow the documented procedures + to complete the process. + Normally, the Incubator PMC member is a Mentor on the podling's PPMC + but if the Mentors are temporarily unavailable, the proposer can ask + any Incubator PMC member.
+-
+
- If the nominee is already an Apache committer on another project, + the Incubator PMC member simply updates the authorization file + to include the nominee as a committer on the podling. +
- If the nominee is not already an Apache committer, the Incubator + PMC member CC's both the Incubator PMC and the PPMC when sending + the necessary e-mails to root.
The proposer then directs the new committer to the Apache developer's pages, + to the Apache Incubator site + and to the Incubator Committers Guide for important additional + information. +
