Re: [jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer

Craig L Russell Sun, 03 Jun 2007 22:15:09 -0700


On Jun 3, 2007, at 9:38 PM, Craig Russell (JIRA) wrote:

[ https://issues.apache.org/jira/browse/INCUBATOR-57? page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Russell updated INCUBATOR-57:
-----------------------------------

    Attachment: smime.p7s
                incubator-57.patch
                ppmc.html

And for those of you who read offline, I've attached the patch and
resulting .html file to this message.


Which Apache promptly removed. Hmmm.

Here's the sources for the patch and html.

Voting in a new committer

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 person commit access. See the ASF How it Works document, which explains meritocracy and roles.

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 [normally it would take place on a 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 balance 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 with a reference to the archived discussion and vote by the PPMC. Note that only the incubator PMC members can see this discussion, and the podling's Mentors should review any incubator PMC feedback with the PPMC. 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 good 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.

If the nominee is already an Apache committer on another project, the proposer asks a member of the incubator PMC to update 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. 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.

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.




Index: site-author/guides/ppmc.xml
===================================================================
--- site-author/guides/ppmc.xml (revision 544016)
+++ site-author/guides/ppmc.xml (working copy)
@@ -134,53 +134,38 @@
     <section id="Voting+in+a+new+committer">
       <title>Voting in a new committer</title>
-      <p>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
+      <p>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 <a
+      grant that person <a

href="http://www.apache.org/foundation/ glossary.html#CommitAccess"

       >commit access</a>. See the ASF <em>How it Works</em> document,
       which explains <a
-      href="http://www.apache.org/foundation/how-it-works.html#roles";>

+ href="http://www.apache.org/foundation/how-it- works.html#meritocracy">

       meritocracy</a> and <a
       href="http://www.apache.org/foundation/how-it-works.html#roles";>
       roles</a>.</p>

-      <p>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):</p>
+<p>

+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 [normally it would take place on a 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.

+</p><p>

+After vetting the nominee, the vote can be called on either one of the two places listed below (notice the balance between private and public lists):

-      <ul>
-        <li> The podling's private list, with notice posted to the
-             Incubator private list.</li>
-        <li> The developer list, with notice posted to the Incubator
-             general list.</li>
-      </ul>
+<ul><li>

+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 with a reference to the archived discussion and vote by the PPMC. Note that only the incubator PMC members can see this discussion, and the podling's Mentors should review any incubator PMC feedback with the PPMC. 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 good to make the new committer feel welcome.

+</li><li>

+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.

+</li></ul>
+</p><p>

+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.

-      <p>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 <a

- href="http://marc.theaimsgroup.com/? t=112033720600002">discussion</a>

-      about these practices). </p>
-

- 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 <a

-      href="http://www.apache.org/foundation/glossary.html#Committer";>
-      committer</a>. An Incubator PMC member should then follow the

- <a href="http://www.apache.org/dev/pmc.html";>documented procedures

-      </a>to complete the process, and CC both the Incubator PMC
-      and the PPMC when sending the necessary e-mails to root.</p>
+</p><p>

+If the nominee is already an Apache committer on another project, the proposer asks a member of the incubator PMC to update 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. 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.

-      <p>Please direct the new committer to the <a

- href="http://www.apache.org/dev/";>Apache developer's pages</ a>, to

-      the  <a href="http://incubator.apache.org/";>Apache Incubator
-      site</a> and to the Incubator <a

- href="committer.html">Committers</a> Guide for important additional

-      information.</p>
+</p><p>

+The proposer then directs the new committer to the <a href="http:// www.apache.org/dev/">Apache developer's pages</a>, to the <a href="http://incubator.apache.org/";>Apache Incubator site</a> and to the Incubator <a href="committer.html">Committers Guide</a> for important additional information.

+</p>
     </section>
     <section id="Voting+in+a+new+PPMC+member">
       <title>Voting in a new PPMC member</title>
Index: site-publish/guides/ppmc.html
===================================================================
--- site-publish/guides/ppmc.html       (revision 544016)
+++ site-publish/guides/ppmc.html       (working copy)
@@ -204,40 +204,37 @@
    <a name="Voting+in+a+new+committer">Voting in a new committer</a>
</h2>
<div class="section-content">
-<p>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
+<p>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 <a href="http://www.apache.org/foundation/ glossary.html#CommitAccess">commit access</a>. See the ASF How it Works document, - which explains <a href="http://www.apache.org/foundation/how- it-works.html#roles"> + grant that person <a href="http://www.apache.org/foundation/ glossary.html#CommitAccess">commit access</a>. See the ASF How it Works document, + which explains <a href="http://www.apache.org/foundation/how- it-works.html#meritocracy"> meritocracy</a> and <a href="http://www.apache.org/foundation/ how-it-works.html#roles">

       roles</a>.</p>
-<p>Discussion of a potential new committer should take place on

-      balance between private and public lists):</p>
-<ul>
-        <li> The podling's private list, with notice posted to the
-             Incubator private list.</li>
-        <li> The developer list, with notice posted to the Incubator
-             general list.</li>
-      </ul>
-<p>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 <a href="http://marc.theaimsgroup.com/? t=112033720600002">discussion</a>

-      about these practices). </p>
-<p>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 <a href="http://www.apache.org/foundation/ glossary.html#Committer">

-      committer</a>. An Incubator PMC member should then follow the

- <a href="http://www.apache.org/dev/pmc.html";>documented procedures

-      </a>to complete the process, and CC both the Incubator PMC
-      and the PPMC when sending the necessary e-mails to root.</p>

-Please direct the new committer to the <a href="http:// www.apache.org/dev/">Apache developer's pages</a>, to

-      the  <a href="http://incubator.apache.org/";>Apache Incubator

- site</a> and to the Incubator <a href="committer.html">Committers</a> Guide for important additional

-      information.</p>
+<p>

+</p>
+<p>

+After vetting the nominee, the vote can be called on either one of the two places listed below (notice the balance between private and public lists):

+
+<ul><li>

+</li><li>

+</li></ul>
+</p>
+<p>

+
+</p>
+<p>

+
+</p>
+<p>

+</p>
</div>
            <h2><img src="/images/redarrow.gif" />

<a name="Voting+in+a+new+PPMC+member">Voting in a new PPMC member</a>

Craig
In the PPMC guide, clarify how to vote in a new committer
---------------------------------------------------------

                Key: INCUBATOR-57
URL: https://issues.apache.org/jira/browse/ INCUBATOR-57
            Project: Incubator
         Issue Type: Improvement
         Components: site
           Reporter: Craig Russell
Attachments: incubator-57.patch, incubator-57.patch, ppmc.html, ppmc.html, ppmc.xml, smime.p7s
There are two issues in this section.
The first is the meaning of the term (P)PMC. I'd like to get rid of that term and replace it with PPMC or IPMC as appropriate. The second is how many votes are needed to vote in a new committer, and who should follow up to create the account.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature

Re: [jira] Updated: (INCUBATOR-57) In the PPMC guide, clarify how to vote in a new committer

Reply via email to