Index: site-author/guides/ppmc.xml
===================================================================
--- site-author/guides/ppmc.xml (revision 670744)
+++ site-author/guides/ppmc.xml (working copy)
@@ -161,41 +161,56 @@
by the nominee in the project.
After vetting the nominee, the vote can be called using either
one of the two approaches listed below (notice the difference between
- private and public lists):
-
+ private and public lists). And note that binding votes are those
+ cast by Incubator PMC members.
+
-
Vote on 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, the
- proposer calls a vote on the Incubator PMC private list, summarizing
+ proposer takes the results to the Incubator PMC.
+
+ - if there are three binding +1 votes, and no binding -1 votes,
+ the proposer asks for lazy consensus by the Incubator
+ PMC by sending email to the Incubator PMC private list, summarizing
the discussion and vote, with a reference to the archived discussion
- and vote threads by the PPMC. The Incubator vote is done even if
- there are three +1 votes from Incubator PMC members during the PPMC
- vote, in order to give all Incubator PMC members a chance to express
- their support or disapproval after seeing the PPMC discussion and
- vote results. Note that only the Incubator PMC members can see
+ and vote threads by the PPMC. Any member of the Incubator PMC can ACK
+ the receipt of the vote. This starts a 72-hour window for lazy
+ consensus. After 72 hours and no requests by any Incubator PMC member
+ for a full vote by the Incubator PMC, the committer request is
+ considered approved by the Incubator PMC and the PPMC can start
+ the committer invitation process.
+
+ - if there are not three binding +1 votes in the PPMC vote,
+ or there are any -1 votes, or if any Incubator PMC member requests
+ a full vote, the proposer calls for a vote by the Incubator PMC.
+ Note that only the Incubator PMC members can see
the Incubator private 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.
+ welcome.
+
- Vote on 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
+ on the podling's developer list. Incubator PMC members vote on
+ the public developer list. Three binding +1 votes and no binding
+ -1 votes are required for a successful vote. 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
+
+ If the vote is positive, 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.