Skip to content
Permalink
Browse files
Merge remote-tracking branch 'cottage/patch-26' into cottage14-patch-26
  • Loading branch information
swapnilmmane committed Jul 5, 2021
2 parents bed7a04 + 8cd2697 commit 3eb0defffb9a008f2adfe2a3bec9e2099ab174f4
Showing 1 changed file with 52 additions and 53 deletions.
@@ -3,7 +3,7 @@ title: New Committer
---

Identifying potential new committers, calling a vote for their recognition
as a committer and processing the relevant documents is something to which
as a committer and processing the relevant documents are tasks to which
the whole community can contribute.

Each project has a different approach to managing new committers. This page
@@ -17,7 +17,7 @@ drafts for the various communications that are necessary.

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.
how the candidate interacts with others, and the contributions (code or doc patches, suggestions, engagement in conversation) they have made.

All new committers **must** adhere to the [Apache Code of Conduct](https://www.apache.org/foundation/policies/conduct.html).

@@ -29,63 +29,63 @@ The following are some points to consider when assessing a candidate's qualifica
### Ability to work cooperatively with peers.
How do we evaluate?

- By the interactions they have through mail.
- By the interactions they have through email.
- 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
materials (or even create them).
- By the interactions they have through email.
- By how clear they are and how willing they are to identify or even create appropriate background
materials.

<a name="NewCommitter-Community"></a>
### Community
How do we evaluate?

- By the interactions they have through mail.
- By the interactions they have through email.
- 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>
### Commitment
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
- By time already given to the project.
- By how well they stick with the process through tough issues.
- By how they help on not-so-fun tasks.

<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.
- Quality of discussion in email.
- Whether their patches (where applicable) are easy to apply with only a cursory review.

<a name="NewCommitter-NewCommitterProcess"></a>
## New Committer Process

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
vote to add a new committer. Templates mentioned in the process appear
later in this document.

<a name="NewCommitter-Summary"></a>
### Summary

1. Call a vote (templates/committerVote.txt)
1. Close the vote
1. Invite the new committer (templates/committerInvite.txt)
1. If the result is positive, invite the new committer (templates/committerInvite.txt)

If they accept, then do:
If they accept, then:

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. PMC Chair to enable svn and other access
1. Wait until root says it is done
1. PMC Chair enables 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
@@ -95,12 +95,12 @@ If they accept, then do:
<a name="NewCommitter-Discussion"></a>
### Discussion

We do the vote on the private mailing list to enable a frank discussion.
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
to review the mail archives.
to review the email archives.

We need to be sure that they are committed people that we can work with.
We need to be sure that they are committed people with whom we can work.
They will be our peers. We will have already observed that they are
committed to the project and graceful toward users and other developers.

@@ -110,40 +110,40 @@ becomes obvious that we should invite them. This encourages them and keeps
them enthusiastic. If we leave it too long, then we risk them becoming
disillusioned.

On the PMC list we can each say exactly what we feel about each person,
On the `@private` 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. 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.

A positive result is achieved by **Consensus Approval**: i.e. at least 3 +1
A positive result is achieved by **Consensus Approval**: at least 3 +1
votes and no vetoes.

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.
Other members can attempt to encourage them to change their mind.

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
that certain people lapse and don't ever contribute, then the project can take steps
to retire them.

After a positive result, record the result on the PMC list with a [RESULT][VOTE] subject
and then invite the candidate. 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
will announce it on the dev list. We can then each follow up with
After we reach a decision on the `@private` list, and after the steps above, we
announce the new committer on the `dev` list. We can then each follow up with
our praise in public.

Other notes about the process are available on the main [Apache site](https://www.apache.org/dev/pmc.html#newcommitter)
Other notes about the process are available on the main [Apache site](https://www.apache.org/dev/pmc.html#newcommitter).

<a name="NewCommitter-EmailTemplates"></a>
## Email Templates

### Committer Vote Template
This is the email to commence a vote for a new committer member.
Some projects make committers PMC members automatically, if this is the case then
merge this with the following template (PMC Vote Template)
This is the email to commence a vote for a new committer.
Some projects make committers PMC members automatically. If this is the case,
merge this template with the following one (PMC Vote Template).

------------------------------------------------------------
To: private@[PROJECT].apache.org
@@ -162,7 +162,7 @@ merge this with the following template (PMC Vote Template)
### 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 subsequently approved by the Board
(or Incubator PMC for Incubating projects).
(or Incubator PMC for incubating projects).

------------------------------------------------------------
To: private@[PROJECT].apache.org
@@ -177,7 +177,7 @@ to be voted for by the existing PMC members and subsequently approved by the Boa
https://community.apache.org/newcommitter.html

### Close Vote
This is the email ends the vote and reports the result to the project.
This email ends the vote and reports the result to the project.

------------------------------------------------------------
To: private@[PROJECT].a.o
@@ -242,35 +242,35 @@ sent after a positive result from the vote for a new committer.

3. When you transmit the completed iCLA, request
to notify the Apache [Project] and choose a
unique Apache id. Look to see if your preferred
id is already taken at
https://people.apache.org/committer-index.html
unique Apache ID. Look to see if your preferred
ID is already taken at
https://people.apache.org/committer-index.html.
This will allow the Secretary to notify the PMC
when your iCLA has been recorded.

When recording of your iCLA is noticed, you will
When recording of your iCLA is noted, you will
receive a follow-up message with the next steps for
establishing you as a committer.

### Committer Accept Template
This is the followup email after the new committer has accepted the invitation
This is the followup email after the new committer has accepted the invitation.

------------------------------------------------------------------------
To: JoeBloggs@foo.net
Cc: private@[PROJECT].apache.org
Subject: Re: invitation to become [PROJECT] committer

Welcome. Here are the next steps. After that we will make
Welcome. Here are the next steps in becoming a project committer. After that we will make
an announcement to the [PROJECT]-dev list.

You need to send a Contributor License Agreement to the ASF.
Normally you would send an Individual CLA. If you also make
contributions done in work time or using work resources then
contributions done in work time or using work resources,
see the Corporate CLA. Ask us if you have any issues.
https://www.apache.org/licenses/#clas
https://www.apache.org/licenses/#clas.

You need to choose a preferred ASF user name and alternatives.
In order to ensure it is available you can view a list of taken ids at
In order to ensure it is available you can view a list of taken IDs at
https://people.apache.org/committer-index.html

Please notify us when you have submitted the CLA and by what means
@@ -283,7 +283,7 @@ This is the followup email after the new committer has accepted the invitation
We generally discuss everything there and keep the
private@[PROJECT].apache.org list for occasional matters which must be private.

The developer section of the website describes the roles and provides other
The developer section of the website describes roles within the ASF and provides other
resources:
https://www.apache.org/foundation/how-it-works.html
https://www.apache.org/dev/
@@ -295,11 +295,11 @@ This is the followup email after the new committer has accepted the invitation

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
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.]
https://forrest.apache.org/guidelines.html
the Apache Forrest guidelines are available as a template.
https://forrest.apache.org/guidelines.html.]

Yours,
The Apache [PROJECT] PMC
@@ -310,8 +310,8 @@ Follow the instructions

In summary:

If the ICLA identifies the project and a valid Apache id, and the
[RESULT][VOTE] message has been posted to the PMC private list, then
If the ICLA identifies the project and a valid Apache ID, and the
[RESULT][VOTE] message has been posted to the PMC private list,
the account creation request is made by the
secretary or assistant who files the ICLA.

@@ -320,14 +320,14 @@ PMC Chair (or any [ASF Member][6] if the chair is unavailable).

The PMC chair needs to use the [ASF New Account Request][2] form to
send a new account request. Members may use [ASF New Account
Request][3] page for ASF members to use.
Request][3] page.

For elections held on public lists, please supply the
[mail-archives.apache.org][4] url. For private lists, you can
use the [Mail Search tool][5] to locate the appropriate url.

### Committer Announce Template
This is the email to announce to [PROJECT]-dev once the account has been created.
This is the email to announce the new committer to `[PROJECT]-dev` once the account has been created.

------------------------------------------------------------
To: dev@[PROJECT].apache.org
@@ -342,8 +342,7 @@ This is the email to announce to [PROJECT]-dev once the account has been created
Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.
A PMC member helps manage and guide the direction of the project.

### Committer Done Template
After the committer account is established.
@@ -353,10 +352,10 @@ This is the email to announce to [PROJECT]-dev once the account has been created
Subject: account request: ###Joe Bloggs

####, as you know, the ASF Infrastructure has set up your
committer account as the username '####'.
committer account with the username '####'.

Please follow the instructions to set up your SSH,
svn password, svn configuration, mail forwarding, etc.
svn password, svn configuration, email forwarding, etc.
https://www.apache.org/dev/#committers

[If your project automatically adds committers to the PMC]

0 comments on commit 3eb0def

Please sign in to comment.