This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 83c424b Updated asf-site from master at
4297d38d91603ea38c25f44aac4879c3653aa79a using
https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/105/
83c424b is described below
commit 83c424b4ab52abb88a3ae99dd1d35925974e6c78
Author: jenkins <bui...@apache.org>
AuthorDate: Mon Jul 12 08:02:24 2021 +0000
Updated asf-site from master at 4297d38d91603ea38c25f44aac4879c3653aa79a
using
https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/105/
---
content/index.xml | 2 +-
content/newcommitter.html | 106 +++++++++++++++++++++++-----------------------
content/sitemap.xml | 2 +-
3 files changed, 54 insertions(+), 56 deletions(-)
diff --git a/content/index.xml b/content/index.xml
index 6643731..34f97de 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -433,7 +433,7 @@ Overview Projects are defined by the students tutor in
consultation with the TLP
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/newcommitter.html</guid>
- <description>Identifying potential new committers, calling a vote for
their recognition as a committer and processing the relevant documents is
something to which the whole community can contribute.
+ <description>Identifying potential new committers, calling a vote for
their recognition 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
describes a common process found in many Apache projects. It also provides
drafts for the various communications that are necessary.
Guidelines for assessing new candidates for committership Ability to work
cooperatively with peers.</description>
</item>
diff --git a/content/newcommitter.html b/content/newcommitter.html
index 081e690..e07903c 100644
--- a/content/newcommitter.html
+++ b/content/newcommitter.html
@@ -7,13 +7,13 @@
<meta name="keywords" content="apache, apache community, community
development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1,
maximum-scale=1" />
<meta property="og:title" content="New Committer" />
-<meta property="og:description" content="Identifying potential new committers,
calling a vote for their recognition as a committer and processing the relevant
documents is something to which the whole community can contribute.
+<meta property="og:description" content="Identifying potential new committers,
calling a vote for their recognition 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
describes a common process found in many Apache projects. It also provides
drafts for the various communications that are necessary.
Guidelines for assessing new candidates for committership Ability to work
cooperatively with peers." />
<meta property="og:type" content="article" />
<meta property="og:url"
content="https://community.apache.org/newcommitter.html"; />
<meta property="og:image"
content="https://community.apache.org/images/aceu19_1.jpg"/>
-<meta property="article:modified_time" content="2020-09-23T00:32:47+02:00"
/><meta property="og:site_name" content="Apache Community Development" />
+<meta property="article:modified_time" content="2021-07-05T18:43:33+05:30"
/><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - New Committer</title>
@@ -186,7 +186,7 @@ Each project has a different approach to managing new
committers. This page desc
<hr>
<p>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.</p>
<p>Each project has a different approach to managing new committers. This page
describes a common process found in many Apache projects. It also provides
@@ -227,7 +227,7 @@ drafts for the various communications that are
necessary.</p>
<h2 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines
for assessing new candidates for committership</h2>
<p>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.</p>
+how the candidate interacts with others, and the contributions (code or doc
patches, suggestions, engagement in conversation) they have made.</p>
<p>All new committers <strong>must</strong> adhere to the <a
href="https://www.apache.org/foundation/policies/conduct.html";>Apache Code of
Conduct</a>.</p>
<p>Each PMC may want to create their own supplemental committer guidelines;
here are the <a href="https://forrest.apache.org/committed.html";>Apache Forrest
committer guidelines</a>.</p>
<p>The following are some points to consider when assessing a
candidate’s qualifications for committership.</p>
@@ -235,7 +235,7 @@ how the candidate interacts.</p>
<h3 id="ability-to-work-cooperatively-with-peers">Ability to work
cooperatively with peers.</h3>
<p>How do we evaluate?</p>
<ul>
-<li>By the interactions they have through mail.</li>
+<li>By the interactions they have through email.</li>
<li>By how they respond to criticism.</li>
<li>By how they participate in the group decision-making process.</li>
</ul>
@@ -243,15 +243,15 @@ how the candidate interacts.</p>
<h3 id="ability-to-be-a-mentor">Ability to be a mentor.</h3>
<p>How do we evaluate?</p>
<ul>
-<li>By the interactions they have through mail.</li>
-<li>By how clear they are and how willing they are to point at appropriate
background
-materials (or even create them).</li>
+<li>By the interactions they have through email.</li>
+<li>By how clear they are and how willing they are to identify or even create
appropriate background
+materials.</li>
</ul>
<p><a name="NewCommitter-Community"></a></p>
<h3 id="community">Community</h3>
<p>How do we evaluate?</p>
<ul>
-<li>By the interactions they have through mail.</li>
+<li>By the interactions they have through email.</li>
<li>Do they help to answer questions raised on the mailing list; do they show
a helpful
attitude and respect for other people’s ideas?</li>
</ul>
@@ -259,38 +259,38 @@ attitude and respect for other people’s ideas?</li>
<h3 id="commitment">Commitment</h3>
<p>How do we evaluate?</p>
<ul>
-<li>By time given to the project already</li>
-<li>By sticking through tough issues</li>
-<li>By helping on not-so-fun tasks as well</li>
+<li>By time already given to the project.</li>
+<li>By how well they stick with the process through tough issues.</li>
+<li>By how they help on not-so-fun tasks.</li>
</ul>
<p><a name="NewCommitter-Personalskill/ability"></a></p>
<h3 id="personal-skillability">Personal skill/ability</h3>
<p>How do we evaluate?</p>
<ul>
<li>A solid general understanding of the project.</li>
-<li>Quality of discussion in mail.</li>
-<li>Patches (where applicable) easy to apply with only a cursory review.</li>
+<li>Quality of discussion in email.</li>
+<li>Whether their patches (where applicable) are easy to apply with only a
cursory review.</li>
</ul>
<p><a name="NewCommitter-NewCommitterProcess"></a></p>
<h2 id="new-committer-process">New Committer Process</h2>
<p>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.</p>
<p><a name="NewCommitter-Summary"></a></p>
<h3 id="summary">Summary</h3>
<ol>
<li>Call a vote (templates/committerVote.txt)</li>
<li>Close the vote</li>
-<li>Invite the new committer (templates/committerInvite.txt)</li>
+<li>If the result is positive, invite the new committer
(templates/committerInvite.txt)</li>
</ol>
-<p>If they accept, then do:</p>
+<p>If they accept, then:</p>
<ol>
<li>Accept the committer (templates/committerAccept.txt)</li>
<li>Wait until we see that receipt of CLA is recorded</li>
<li>Request creation of the committer account (template/committerCreate.txt)
<ol>
-<li>now wait until root says it is done</li>
-<li>PMC Chair to enable svn and other access</li>
+<li>Wait until root says it is done</li>
+<li>PMC Chair enables svn and other access</li>
<li>Add committer to the appropriate groups in JIRA and CWiki</li>
</ol>
</li>
@@ -301,10 +301,10 @@ later in this document.</p>
</ol>
<p><a name="NewCommitter-Discussion"></a></p>
<h3 id="discussion">Discussion</h3>
-<p>We do the vote on the private mailing list to enable a frank discussion.</p>
+<p>We do the vote on the <code>private@</code> mailing list to enable a frank
discussion.</p>
<p>Start a separate [VOTE] thread for each new person. This makes it much
easier
-to review the mail archives.</p>
-<p>We need to be sure that they are committed people that we can work with.
+to review the email archives.</p>
+<p>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.</p>
<p>Don’t wait too long before proposing and don’t be too hasty.
There is a
@@ -312,31 +312,31 @@ trade-off and something about timeliness. A point is
reached where it
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.</p>
-<p>On the PMC list we can each say exactly what we feel about each person,
+<p>On the <code>private@</code> 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.</p>
<p>Let the Vote thread run for one week.</p>
-<p>A positive result is achieved by <strong>Consensus Approval</strong>: i.e.
at least 3 +1
+<p>A positive result is achieved by <strong>Consensus Approval</strong>: at
least 3 +1
votes and no vetoes.</p>
<p>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.</p>
+Other members can attempt to encourage them to change their mind.</p>
<p>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.</p>
<p>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.</p>
-<p>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
+<p>After we reach a decision on the <code>private@</code> list, and after the
steps above, we
+announce the new committer on the <code>dev</code> list. We can then each
follow up with
our praise in public.</p>
-<p>Other notes about the process are available on the main <a
href="https://www.apache.org/dev/pmc.html#newcommitter";>Apache site</a></p>
+<p>Other notes about the process are available on the main <a
href="https://www.apache.org/dev/pmc.html#newcommitter";>Apache site</a>.</p>
<p><a name="NewCommitter-EmailTemplates"></a></p>
<h2 id="email-templates">Email Templates</h2>
<h3 id="committer-vote-template">Committer Vote Template</h3>
-<p>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)</p>
+<p>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).</p>
<pre><code>------------------------------------------------------------
To: private@[PROJECT].apache.org
Subject: [VOTE] New committer: Joe Bloggs
@@ -354,7 +354,7 @@ https://community.apache.org/newcommitter.html
<h3 id="pmc-vote-template">PMC Vote Template</h3>
<p>This is the email to commence a vote for a new <strong>PMC
candidate</strong>. 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).</p>
+(or Incubator PMC for incubating projects).</p>
<pre><code>------------------------------------------------------------
To: private@[PROJECT].apache.org
Subject: [VOTE] New PMC candidate: Joe Bloggs
@@ -368,9 +368,8 @@ See voting guidelines at
https://community.apache.org/newcommitter.html
</code></pre>
<h3 id="close-vote">Close Vote</h3>
-<pre><code>This is the email ends the vote and reports the result to the
project.
-
-------------------------------------------------------------
+<p>This email ends the vote and reports the result to the project.</p>
+<pre><code>------------------------------------------------------------
To: private@[PROJECT].a.o
Subject: [RESULT] [VOTE] New committer (or PMC candidate): Joe Bloggs
@@ -431,34 +430,34 @@ B. If you accept, the next step is to register an iCLA:
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.
</code></pre>
<h3 id="committer-accept-template">Committer Accept Template</h3>
-<p>This is the followup email after the new committer has accepted the
invitation</p>
+<p>This is the followup email after the new committer has accepted the
invitation.</p>
<pre><code>------------------------------------------------------------------------
To: joeblo...@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
@@ -471,7 +470,7 @@ After that is done, please make followup replies to the
[PROJECT]-dev list.
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/
@@ -496,20 +495,20 @@ The Apache [PROJECT] PMC
<p>Follow the instructions
<a href="https://www.apache.org/dev/pmc.html#newcommitter";>here</a>.</p>
<p>In summary:</p>
-<p>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
+<p>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.</p>
<p>Otherwise, the new account request should be made by the
PMC Chair (or any <a
href="https://www.apache.org/foundation/glossary.html#Member";>ASF Member</a> if
the chair is unavailable).</p>
<p>The PMC chair needs to use the <a
href="https://id.apache.org/acreq/pmc-chairs/";>ASF New Account Request</a> form
to
send a new account request. Members may use <a
href="https://id.apache.org/acreq/members/";>ASF New Account
-Request</a> page for ASF members to use.</p>
+Request</a> page.</p>
<p>For elections held on public lists, please supply the
<a href="https://mail-archives.apache.org/";>mail-archives.apache.org</a> url.
For private lists, you can
use the <a href="https://mail-search.apache.org/";>Mail Search tool</a> to
locate the appropriate url.</p>
<h3 id="committer-announce-template">Committer Announce Template</h3>
-<p>This is the email to announce to [PROJECT]-dev once the account has been
created.</p>
+<p>This is the email to announce the new committer to
<code>[PROJECT]-dev</code> once the account has been created.</p>
<pre><code>------------------------------------------------------------
To: dev@[PROJECT].apache.org
Subject: new committer: ###Joe Bloggs
@@ -523,8 +522,7 @@ to announce that he has accepted.
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.
</code></pre>
<h3 id="committer-done-template">Committer Done Template</h3>
<pre><code>After the committer account is established.
@@ -534,10 +532,10 @@ To: private@[PROJECT].a.o, ###joeblo...@foo.net
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]
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 695f56a..9c86548 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -244,7 +244,7 @@
<url>
<loc>https://community.apache.org/newcommitter.html</loc>
- <lastmod>2020-09-23T00:32:47+02:00</lastmod>
+ <lastmod>2021-07-05T18:43:33+05:30</lastmod>
</url>
<url>
![https://community.apache.org/images/aceu19_1.jpg"/](https://community.apache.org/images/aceu19_1.jpg"/){kind=link}