community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woh...@apache.org
Subject svn commit: r1757932 - /comdev/site/trunk/content/newcommitter.mdtext
Date Fri, 26 Aug 2016 23:13:49 GMT
Author: wohali
Date: Fri Aug 26 23:13:49 2016
New Revision: 1757932

URL: http://svn.apache.org/viewvc?rev=1757932&view=rev
Log:
CMS commit to community by wohali

Modified:
    comdev/site/trunk/content/newcommitter.mdtext

Modified: comdev/site/trunk/content/newcommitter.mdtext
URL: http://svn.apache.org/viewvc/comdev/site/trunk/content/newcommitter.mdtext?rev=1757932&r1=1757931&r2=1757932&view=diff
==============================================================================
--- comdev/site/trunk/content/newcommitter.mdtext (original)
+++ comdev/site/trunk/content/newcommitter.mdtext Fri Aug 26 23:13:49 2016
@@ -1,10 +1,10 @@
 Title: NewCommitter
 
 Identifying potential new committers, calling a vote for their recognition
-as a committer and processing the relevant documents is something that the
-whole community can contribute to.
+as a committer and processing the relevant documents is something to which
+the whole community can contribute.
 
-Each project has different approaches to managing new committers, this page
+Each project has a different approach to managing new committers. This page
 describes a common process found in many Apache projects. It also provides
 drafts for the various communications that are necessary.
 
@@ -13,63 +13,80 @@ drafts for the various communications th
 <a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
 # Guidelines for assessing new candidates for committership
 
-When voting, all PMC members need to make up your own mind, perhaps search
-mailing lists and Jira, etc. The following are some tips that we developed.
-Also consider the Apache Forrest [committer guidelines](http://forrest.apache.org/committed.html).
+When voting, all PMC members need to make up their own minds as to whether a candidate
+should be approved to become a committer. They might search mailing lists and JIRA to see
+how the candidate interacts.
+
+All new committers **must** adhere to the [Apache Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).
+
+Each PMC may want to create their own supplemental committer guidelines; here are the [Apache
Forrest committer guidelines](http://forrest.apache.org/committed.html).
+
+The following are some points to consider when assessing a candidate's qualifications for
committership.
 
 <a name="NewCommitter-Abilitytoworkco-operativelywithpeers."></a>
 ## Ability to work cooperatively with peers. 
-How do we evaluate?  By the interactions they have through mail. By how
-they respond to criticism. By how they participate in decision-making
-process.
+How do we evaluate?
+
+  - By the interactions they have through mail.
+  - By how they respond to criticism.
+  - By how they participate in the group decision-making process.
 
 <a name="NewCommitter-Abilitytobeamentor."></a>
 ## Ability to be a mentor.
-How do we evaluate?  By the interactions they have through mail. By how
-clear they are and how willing they are to point at appropriate background
+How do we evaluate?
+
+  - By the interactions they have through mail.
+  - By how clear they are and how willing they are to point at appropriate background
 materials (or even create them).
 
 <a name="NewCommitter-Community"></a>
 ## Community
-How do we evaluate?  By the interactions they have through mail. Do they 
-help to answer questions raised on the mailing list; do they show a helpful 
-attitude and respect for other's ideas.
+How do we evaluate?
+
+  - By the interactions they have through mail.
+  - Do they help to answer questions raised on the mailing list; do they show a helpful 
+attitude and respect for other people's ideas?
 
 <a name="NewCommitter-Committment"></a>
 ## Committment
-How do we evaluate?  By time, by sticking through tough issues, by helping
-on not-so-fun tasks as well.
+How do we evaluate?
+
+  - By time given to the project already
+  - By sticking through tough issues
+  - By helping on not-so-fun tasks as well
 
 <a name="NewCommitter-Personalskill/ability"></a>
 ## Personal skill/ability
-How do we evaluate?  A solid general understanding of the project. 
-Quality of discussion in mail.	Patches (where applicable) easy to apply with only
-a cursory review.
+How do we evaluate?
+
+  - A solid general understanding of the project. 
+  - Quality of discussion in mail.
+  - Patches (where applicable) easy to apply with only a cursory review.
 
 <a name="NewCommitter-NewCommitterProcess"></a>
 # New Committer Process
 
-This section describes a typical Apache projects process for handling the
-voting of a new committer. Templates mentioned in the process appear at
+This section describes a typical Apache project's process for handling the
+vote to add a new committer. Templates mentioned in the process appear at
 later in this document.
 
 <a name="NewCommitter-Summary"></a>
 ## Summary
 
-1. Call a vote: templates/committerVote.txt
-1. If candidate PMC member, notify board and wait three days for lazy approval
-1. Invite the new committer/PMC member: templates/committerInvite.txt
+1. Call a vote (templates/committerVote.txt)
+1. Invite the new committer (templates/committerInvite.txt)
 
 If they accept, then do:
 
-1. Accept the committer - note this assumes the committer is also to be a
-PMC member (templates/committerAccept.txt)
-1. wait until we see that receipt of CLA is recorded
+1. Accept the committer (templates/committerAccept.txt)
+1. Wait until we see that receipt of CLA is recorded
 1. Request creation of the committer account (template/committerCreate.txt)
    1. now wait until root says it is done
-   1. chair to enable their svn access
-   1. add committer to the appropriate groups in Jira and CWiki
+   1. PMC Chair to enable svn and other access
+   1. Add committer to the appropriate groups in JIRA and CWiki
 1. Notify the committer of completion (template/committerDone.txt)
+1. If committer is also to be a PMC member, PMC Chair sends email to board@ asking for acknowledgement
of new PMC member
+(templates/email-member-ack.txt)
 1. Announce the new committer (template/committerAnnounce.txt)
 
 <a name="NewCommitter-Discussion"></a>
@@ -77,14 +94,9 @@ PMC member (templates/committerAccept.tx
 
 We do the vote on the private mailing list to enable a frank discussion.
 
-Start a separate Vote thread for each new person. This makes it much easier
+Start a separate [VOTE] thread for each new person. This makes it much easier
 to review the mail archives.
 
-In most cases, we will be inviting people to go straight from developer to
-PMC member. However, there may be extraordinary cases where we want
-limited work-related commit access. This will be resolved during the vote
-discussion. 
-
 We need to be sure that they are committed people that we can work with.
 They will be our peers. We will have already observed that they are
 committed to the project and graceful toward users and other developers.
@@ -97,22 +109,22 @@ disillusioned.
 
 On the PMC list we can each say exactly what we feel about each person,
 with no holds barred. Keep the discussion concise. The praise part can
-be done later in public. Remember that if electing a new PMC member,
-if successful they can see the discussion in the archives.
-
-See the end of this document for some guidelines to help you to assess a
-candidate.
+be done later in public. Keep in mind, however, that if the member becomes
+a PMC member later, they will have access to this discussion.
 
 Let the Vote thread run for one week.
 
-In general, committer elections are majority approval votes, as described on 
-the [Apache Voting Process](https://www.apache.org/foundation/voting.html) page.
+A positive result is achieved by **Consensus Approval**: i.e. at least 3 +1
+votes and no vetoes.
 
-New PMC members can be either quiet or active as they choose. If we find
-that certain people lapse and don't ever contribute, then we can take steps
+Any veto must be accompanied by reasoning and the vetoer must be prepared to defend it.
+Other members can attempt to encourage them to change their minds.
+
+New committers can be either quiet or active as they choose. If we find
+that certain people lapse and don't ever contribute, then each project can take steps
 to retire them.
 
-After a positive result, we give them a chance to decline in private. They
+After a positive result, we give candidates a chance to decline committership in private.
They
 can post a reply to the PMC mailing list.
 
 After we reach a decision on the PMC list, and after the steps above, we
@@ -131,7 +143,7 @@ merge this with the following template (
       
     ------------------------------------------------------------
     To: private@[PROJECT].apache.org
-    Subject: [Vote] new committer: Joe Bloggs
+    Subject: [VOTE] New committer: Joe Bloggs
     
     [ add the reasons behind your nomination here ]
     
@@ -139,19 +151,18 @@ merge this with the following template (
     http://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
     
     See voting guidelines at
-    https://svn.apache.org/repos/private/pmc/forrest/pmc-member-vote.txt
-    (yes, this links to the Apache Forrest Guidelines, we don't have our own yet)
+    https://community.apache.org/newcommitter.html
     
     ------------------------------------------------------------
 
 ## PMC Vote Template
-This is the email to commence a vote for a new PMC candidate. New PMC members need
-to be voted for by the existing PMC members and (lazily) approved by the Board
+This is the email to commence a vote for a new **PMC candidate**. New PMC members need
+to be voted for by the existing PMC members and subsequently approved by the Board
 (or Incubator PMC for Incubating projects).
     
     ------------------------------------------------------------
     To: private@[PROJECT].apache.org
-    Subject: [Vote] new PMC candidate: Joe Bloggs
+    Subject: [VOTE] New PMC candidate: Joe Bloggs
     
     [ add the reasons behind your nomination here ]
     
@@ -159,15 +170,14 @@ to be voted for by the existing PMC memb
     http://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
     
     See voting guidelines at
-    https://svn.apache.org/repos/private/pmc/forrest/pmc-member-vote.txt
-    (yes, this links to the Apache Forrest Guidelines, we don't have our own yet)
+    https://community.apache.org/newcommitter.html
     
 ## Close Vote
     This is the email ends the vote and reports the result to the project.
     
     ------------------------------------------------------------
     To: private@[PROJECT].a.o
-    Subject: [RESULT] [Vote] new PMC candidate: Joe Bloggs
+    Subject: [RESULT] [VOTE] New committer (or PMC candidate): Joe Bloggs
     
     The vote has now closed. The results are:
     
@@ -179,7 +189,7 @@ to be voted for by the existing PMC memb
     
     The vote is ***successful/not successful***
 
-##Board Lazy Approval of new PMC member 
+##Board Approval of new PMC member 
 See [http://www.apache.org/dev/pmc.html#newpmc][1]
 
 ## Committer Invite Template
@@ -218,10 +228,10 @@ sent after a positive result from the vo
     let us know in reply to the [private@project.apache.org] 
     address only.
 
-    B. If you accept, the next step is to register 
+    B. If you are accepting, the next step is to register 
     an iCLA with the Apache Software Foundation:
         1. Details of the iCLA and the forms are found 
-        through this link: <http://www.apache.org/licenses/#submitting>.
+        through this link: <http://www.apache.org/licenses/#clas>.
 
         2. The form (text or PDF version) provides 
         instructions for its completion and return to 
@@ -279,10 +289,14 @@ This is the followup email after the new
     in incubating projects:
       http://incubator.apache.org/guides/committer.html
       http://incubator.apache.org/guides/ppmc.html
-    
-    In the absence of our own guidelines document we are currently 
-    using those developed at Apache Forrest:
-    http://forrest.apache.org/guidelines.html
+
+    Just as before you became a committer, participation in any ASF community
+    requires adherence to the ASF Code of Conduct:
+      https://www.apache.org/foundation/policies/conduct.html
+    
+    [PROJECT should insert its own guidelines here; if none are available,
+     the Apache Forrest guidelines are available as a template.]
+      http://forrest.apache.org/guidelines.html
     
     Yours,
     The Apache [PROJECT] PMC



Mime
View raw message