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 63c0825e Updated asf-site from main at
e6932cd06f18b5938a24135be169803833e6f5de
63c0825e is described below
commit 63c0825e0f864278320f73a2c13fe5d576c21f6f
Author: jenkins <[email protected]>
AuthorDate: Mon Oct 28 19:58:16 2024 +0000
Updated asf-site from main at e6932cd06f18b5938a24135be169803833e6f5de
Built from
https://ci-builds.apache.org/job/Community%20Development/job/site/job/main/148/
---
content/_pagefind/fragment/en_33c8d45.pf_fragment | Bin 0 -> 4253 bytes
content/_pagefind/fragment/en_4d32193.pf_fragment | Bin 6416 -> 0 bytes
content/_pagefind/index/en_1959cc4.pf_index | Bin 29780 -> 0 bytes
content/_pagefind/index/en_22ae8e6.pf_index | Bin 31715 -> 0 bytes
content/_pagefind/index/en_245e56d.pf_index | Bin 0 -> 29139 bytes
content/_pagefind/index/en_3eb5fa7.pf_index | Bin 28167 -> 0 bytes
content/_pagefind/index/en_56c2da9.pf_index | Bin 28617 -> 0 bytes
content/_pagefind/index/en_68c77d8.pf_index | Bin 0 -> 31217 bytes
content/_pagefind/index/en_79fafdc.pf_index | Bin 0 -> 27490 bytes
content/_pagefind/index/en_938651f.pf_index | Bin 32025 -> 0 bytes
content/_pagefind/index/en_97357ad.pf_index | Bin 30386 -> 0 bytes
content/_pagefind/index/en_a0a73c5.pf_index | Bin 0 -> 28801 bytes
content/_pagefind/index/en_a2254ad.pf_index | Bin 31402 -> 0 bytes
content/_pagefind/index/en_b6db8ca.pf_index | Bin 0 -> 31428 bytes
content/_pagefind/index/en_be14f24.pf_index | Bin 0 -> 29578 bytes
content/_pagefind/index/en_ca77320.pf_index | Bin 0 -> 31179 bytes
content/_pagefind/index/en_cc7521b.pf_index | Bin 29167 -> 0 bytes
content/_pagefind/index/en_cfb7bcc.pf_index | Bin 0 -> 28385 bytes
content/_pagefind/pagefind-entry.json | 2 +-
content/_pagefind/pagefind.en_7739171e2d.pf_meta | Bin 1299 -> 0 bytes
content/_pagefind/pagefind.en_ad90895d67.pf_meta | Bin 0 -> 1292 bytes
content/css/main.css | 2 +-
content/index.xml | 2 +-
content/newcommitter.html | 403 ++++++----------------
content/templates/committer-announce.txt | 13 +
content/templates/committer-discuss.txt | 13 +
content/templates/committer-invite.txt | 76 ++++
content/templates/committer-pmc-announce.txt | 13 +
content/templates/committer-pmc-results.txt | 16 +
content/templates/committer-pmc-vote.txt | 27 ++
content/templates/committer-results.txt | 15 +
content/templates/committer-vote.txt | 19 +
content/templates/committer-welcome.txt | 69 ++++
33 files changed, 362 insertions(+), 308 deletions(-)
diff --git a/content/_pagefind/fragment/en_33c8d45.pf_fragment
b/content/_pagefind/fragment/en_33c8d45.pf_fragment
new file mode 100644
index 00000000..09559dcf
Binary files /dev/null and b/content/_pagefind/fragment/en_33c8d45.pf_fragment
differ
diff --git a/content/_pagefind/fragment/en_4d32193.pf_fragment
b/content/_pagefind/fragment/en_4d32193.pf_fragment
deleted file mode 100644
index d3484bd5..00000000
Binary files a/content/_pagefind/fragment/en_4d32193.pf_fragment and /dev/null
differ
diff --git a/content/_pagefind/index/en_1959cc4.pf_index
b/content/_pagefind/index/en_1959cc4.pf_index
deleted file mode 100644
index 12ad7ef7..00000000
Binary files a/content/_pagefind/index/en_1959cc4.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_22ae8e6.pf_index
b/content/_pagefind/index/en_22ae8e6.pf_index
deleted file mode 100644
index 6e3d74af..00000000
Binary files a/content/_pagefind/index/en_22ae8e6.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_245e56d.pf_index
b/content/_pagefind/index/en_245e56d.pf_index
new file mode 100644
index 00000000..1a4e415c
Binary files /dev/null and b/content/_pagefind/index/en_245e56d.pf_index differ
diff --git a/content/_pagefind/index/en_3eb5fa7.pf_index
b/content/_pagefind/index/en_3eb5fa7.pf_index
deleted file mode 100644
index c11e7590..00000000
Binary files a/content/_pagefind/index/en_3eb5fa7.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_56c2da9.pf_index
b/content/_pagefind/index/en_56c2da9.pf_index
deleted file mode 100644
index d7fd61f9..00000000
Binary files a/content/_pagefind/index/en_56c2da9.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_68c77d8.pf_index
b/content/_pagefind/index/en_68c77d8.pf_index
new file mode 100644
index 00000000..b9eb6d82
Binary files /dev/null and b/content/_pagefind/index/en_68c77d8.pf_index differ
diff --git a/content/_pagefind/index/en_79fafdc.pf_index
b/content/_pagefind/index/en_79fafdc.pf_index
new file mode 100644
index 00000000..934e54ae
Binary files /dev/null and b/content/_pagefind/index/en_79fafdc.pf_index differ
diff --git a/content/_pagefind/index/en_938651f.pf_index
b/content/_pagefind/index/en_938651f.pf_index
deleted file mode 100644
index 6be4b617..00000000
Binary files a/content/_pagefind/index/en_938651f.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_97357ad.pf_index
b/content/_pagefind/index/en_97357ad.pf_index
deleted file mode 100644
index 765be398..00000000
Binary files a/content/_pagefind/index/en_97357ad.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_a0a73c5.pf_index
b/content/_pagefind/index/en_a0a73c5.pf_index
new file mode 100644
index 00000000..03a759c0
Binary files /dev/null and b/content/_pagefind/index/en_a0a73c5.pf_index differ
diff --git a/content/_pagefind/index/en_a2254ad.pf_index
b/content/_pagefind/index/en_a2254ad.pf_index
deleted file mode 100644
index 2668bc2e..00000000
Binary files a/content/_pagefind/index/en_a2254ad.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_b6db8ca.pf_index
b/content/_pagefind/index/en_b6db8ca.pf_index
new file mode 100644
index 00000000..78bcfb01
Binary files /dev/null and b/content/_pagefind/index/en_b6db8ca.pf_index differ
diff --git a/content/_pagefind/index/en_be14f24.pf_index
b/content/_pagefind/index/en_be14f24.pf_index
new file mode 100644
index 00000000..9d953d97
Binary files /dev/null and b/content/_pagefind/index/en_be14f24.pf_index differ
diff --git a/content/_pagefind/index/en_ca77320.pf_index
b/content/_pagefind/index/en_ca77320.pf_index
new file mode 100644
index 00000000..4d96f9b0
Binary files /dev/null and b/content/_pagefind/index/en_ca77320.pf_index differ
diff --git a/content/_pagefind/index/en_cc7521b.pf_index
b/content/_pagefind/index/en_cc7521b.pf_index
deleted file mode 100644
index bb9ae6cd..00000000
Binary files a/content/_pagefind/index/en_cc7521b.pf_index and /dev/null differ
diff --git a/content/_pagefind/index/en_cfb7bcc.pf_index
b/content/_pagefind/index/en_cfb7bcc.pf_index
new file mode 100644
index 00000000..74b47358
Binary files /dev/null and b/content/_pagefind/index/en_cfb7bcc.pf_index differ
diff --git a/content/_pagefind/pagefind-entry.json
b/content/_pagefind/pagefind-entry.json
index ed77c6a9..36f8edc1 100644
--- a/content/_pagefind/pagefind-entry.json
+++ b/content/_pagefind/pagefind-entry.json
@@ -1 +1 @@
-{"version":"1.0.3","languages":{"en":{"hash":"en_7739171e2d","wasm":"en","page_count":145}}}
\ No newline at end of file
+{"version":"1.0.3","languages":{"en":{"hash":"en_ad90895d67","wasm":"en","page_count":145}}}
\ No newline at end of file
diff --git a/content/_pagefind/pagefind.en_7739171e2d.pf_meta
b/content/_pagefind/pagefind.en_7739171e2d.pf_meta
deleted file mode 100644
index 1b3fcc83..00000000
Binary files a/content/_pagefind/pagefind.en_7739171e2d.pf_meta and /dev/null
differ
diff --git a/content/_pagefind/pagefind.en_ad90895d67.pf_meta
b/content/_pagefind/pagefind.en_ad90895d67.pf_meta
new file mode 100644
index 00000000..a078b639
Binary files /dev/null and b/content/_pagefind/pagefind.en_ad90895d67.pf_meta
differ
diff --git a/content/css/main.css b/content/css/main.css
index 72b14988..c1de8cc3 100644
--- a/content/css/main.css
+++ b/content/css/main.css
@@ -104,4 +104,4 @@ volunteers-list li {
.bg-bright {
background: white;
-}
\ No newline at end of file
+}
diff --git a/content/index.xml b/content/index.xml
index ec75f52f..7c4da045 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -712,7 +712,7 @@ Talk to the project first Make sure it&rsquo;s
wanted/welcome See if there&a
<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 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.
+Each project has a different approach to managing new committers. This page
describes a common process found in many Apache projects. It also provides
draft templates for the various communications that are necessary.
Some of the PMCs automatically make committers PMC members. The templates
below have conditional [if] clauses for that.</description>
</item>
diff --git a/content/newcommitter.html b/content/newcommitter.html
index ef26cb75..38de4ece 100644
--- a/content/newcommitter.html
+++ b/content/newcommitter.html
@@ -8,7 +8,7 @@
<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 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.
+Each project has a different approach to managing new committers. This page
describes a common process found in many Apache projects. It also provides
draft templates for the various communications that are necessary.
Some of the PMCs automatically make committers PMC members. The templates
below have conditional [if] clauses for that." />
<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:section" content="" />
@@ -227,7 +227,7 @@ 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
-drafts for the various communications that are necessary.</p>
+draft templates for the various communications that are necessary.</p>
<p>Some of the PMCs automatically make committers PMC members. The templates
below
have conditional <code>[if]</code> clauses for that.</p>
<p>If the PMC has separate process for approving PMC members, see
@@ -235,6 +235,11 @@ have conditional <code>[if]</code> clauses for that.</p>
The <a href="https://community.apache.org/contributor-ladder.html">Contributor
Ladder</a> helps explain different roles.</p>
<nav id="TableOfContents">
<ul>
+ <li>
+ <ul>
+ <li><a href="#tldr---inviting-a-new-committer">TL;DR - Inviting a new
Committer</a></li>
+ </ul>
+ </li>
<li><a
href="#guidelines-for-assessing-new-candidates-for-committership">Guidelines
for assessing new candidates for committership</a>
<ul>
<li><a href="#ability-to-work-cooperatively-with-peers">Ability to
work cooperatively with peers.</a></li>
@@ -246,29 +251,60 @@ The <a
href="https://community.apache.org/contributor-ladder.html">Contributor L
</li>
<li><a href="#new-committer-process">New Committer Process</a>
<ul>
- <li><a href="#summary">Summary</a></li>
<li><a href="#discussion">Discussion</a></li>
- </ul>
- </li>
- <li><a href="#email-templates">Email Templates</a>
- <ul>
- <li><a href="#committer-vote-template">Committer Vote Template</a></li>
- <li><a
href="#committer-and-pmc-member-candidate-vote-template">Committer and PMC
member candidate Vote Template</a></li>
- <li><a href="#committer-close-vote">Committer Close Vote</a></li>
- <li><a
href="#committer-and-new-pmc-member-candidate-close-vote">Committer and New PMC
member candidate close Vote</a></li>
- <li><a href="#committer-invite-template">Committer Invite
Template</a></li>
+ <li><a href="#vote">Vote</a></li>
+ <li><a href="#announcing-results">Announcing results</a></li>
<li><a href="#committer-account-creation">Committer Account
Creation</a></li>
- <li><a href="#committer-announce-template">Committer Announce
Template</a></li>
- <li><a href="#committer-and-pmc-member-announce-template">Committer
and PMC member Announce Template</a></li>
- <li><a href="#committer-done-template">Committer Done Template</a></li>
</ul>
</li>
+ <li><a href="#email-templates">Email Templates</a></li>
</ul>
</nav>
+<p><a name="NewCommitter-Summary"></a></p>
+<h3 id="tldr---inviting-a-new-committer">TL;DR - Inviting a new Committer <a
class="headerlink" title="Permalink"
href="#tldr---inviting-a-new-committer">¶</a></h3>
+<ol>
+<li>Discuss the proposed committer (and optionally PMC member). (Use
+<a href="templates/committer-discuss.txt">this template</a>.)
+If the discussion seems to be going positively,
+call a vote. (Use <a href="templates/committer-vote.txt">this template</a> for
+committer, <a href="templates/committer-pmc-vote.txt">this template</a> for
+committer and PMC member.)</li>
+<li>Close the vote. (Use <a href="templates/committer-results.txt">this
template</a> for a committer vote, or <a
href="templates/committer-pmc-results.txt">this template</a> for a committer +
PMC member vote.)</li>
+<li>If the result is positive, invite the new committer. (Use <a
href="templates/committer-invite.txt">this
+template</a>.)</li>
+</ol>
+<p>If they accept, then:</p>
+<ol>
+<li>If they already have an Apache id, grant appropriate commit privileges.
+Use the Whimsy tool to update the roster via <a
href="https://whimsy.apache.org/roster/committee/">Comitee Roster</a> or
+<a href="https://whimsy.apache.org/roster/ppmc/">PPMC Roster</a></li>
+<li>If they have already filed an ICLA, request creation of the committer
account.
+If they need to change anything in a previously filed ICLA, wait until the new
ICLA is filed,
+then request the account.
+<ol>
+<li>Wait until root says it is done</li>
+<li>PMC Chair updates LDAP group membership which enables svn, gitbox and
other access.
+If the committer uses GitHub, let them know that they are responsible for
linking
+it to their ASF account.</li>
+<li>Add committer to the appropriate access groups for any services
+that your project uses, which are not tied to ASF LDAP.</li>
+</ol>
+</li>
+<li>Notify the committer of completion. (Use <a
href="templates/committer-welcome.txt">this
+template</a></li>
+<li>If committer is also to be a PMC member, the PMC Chair or other PMC
+members must <a href="https://whimsy.apache.org/roster/committee/">update the
PMC roster</a>
+See <a href="https://www.apache.org/dev/pmc.html#newpmcmember">new PMC
member</a> for more detail.</li>
+<li>Announce the new committer. (Use <a
href="templates/committer-announce.txt">this
+template</a>.</li>
+</ol>
<p><a
name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a></p>
<h2 id="guidelines-for-assessing-new-candidates-for-committership">Guidelines
for assessing new candidates for committership <a class="headerlink"
title="Permalink"
href="#guidelines-for-assessing-new-candidates-for-committership">¶</a></h2>
+<p>Frequently inviting new committers (and PMC members) to your project
+helps to ensure the sustainability of the project, and brings new ideas
+into the discussion.</p>
<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
+should be approved to become a committer. They might search mailing lists and
issue trackers to see
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,
@@ -320,48 +356,20 @@ attitude and respect for other people’s ideas?</li>
<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
later in this document.</p>
-<p><a name="NewCommitter-Summary"></a></p>
-<h3 id="summary">Summary <a class="headerlink" title="Permalink"
href="#summary">¶</a></h3>
-<ol>
-<li>Discuss the proposed committer (and optionally PMC member). If the
discussion seems to be going positively,
-call a vote following the template below.</li>
-<li>Close the vote following the template below</li>
-<li>If the result is positive, invite the new committer following the template
below.</li>
-</ol>
-<p>If they accept, then:</p>
-<ol>
-<li>If they already have an Apache id, grant appropriate commit privileges.
-Use the Whimsy tool to update the roster via <a
href="https://whimsy.apache.org/roster/committee/">Comitee Roster</a> or
-<a href="https://whimsy.apache.org/roster/ppmc/">PPMC Roster</a></li>
-<li>If they have already filed an ICLA, request creation of the committer
account.
-If they need to change anything in a previously filed ICLA, wait until the new
ICLA is filed,
-then request the account.
-<ol>
-<li>Wait until root says it is done</li>
-<li>PMC Chair updates LDAP group membership which enables svn, gitbox and
other access.
-If the committer uses GitHub, they are responsible for linking it to their ASF
account.</li>
-<li>Add committer to the appropriate groups in Jira and CWiki</li>
-</ol>
-</li>
-<li>Notify the committer of completion following the template below</li>
-<li>If committer is also to be a PMC member, PMC Chair or another PMC member
sends email to board@ notifying
-about the PMC member. See [new PMC member](<a
href="https://www.apache.org/dev/pmc.html#newpmcmember%5D">https://www.apache.org/dev/pmc.html#newpmcmember]</a></li>
-<li>Announce the new committer following the template below.</li>
-</ol>
<p><a name="NewCommitter-Discussion"></a></p>
<h3 id="discussion">Discussion <a class="headerlink" title="Permalink"
href="#discussion">¶</a></h3>
<p>We do the discussion and vote on the <code>private@</code> mailing list to
enable a frank
discussion. Any PMC member may propose a potential committer or PMC
member. This is <strong>not</strong> the sole responsibility or right of the
PMC
chair.</p>
+<p>You can use <a href="templates/committer-discuss.txt">this template to
start the
+discussion</a>.</p>
<p>We invite people to join as committers/PMC members, not github ids. It is
fine to refer to the candidate’s github id for context, but the person
should
be referred to by their name. It is not necessary to have their full legal
name (that will be kept private) but it is important to use their name, as
they refer to themselves in email. If a person is known only by their github
id, it is ok to ask them for their real name prior to holding a VOTE.</p>
-<p>Start a separate [VOTE] thread for each new person. This makes it much
easier
-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>
@@ -374,166 +382,34 @@ disillusioned.</p>
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>: 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 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 the project
can take steps
-to retire them.</p>
+<h3 id="vote">Vote <a class="headerlink" title="Permalink"
href="#vote">¶</a></h3>
+<p>If the proposed candidate seems to be received positively by a majority
+of those responding, it’s time to <a
href="templates/committer-vote.txt">start a vote</a>.</p>
+<p>In some projects, new committers are automatically also made PMC members.
+If this is the case in your project, use <a href="committer-pmc-vote.txt">this
template to start the
+vote</a> instead.</p>
+<p>Start a separate [VOTE] thread for each new person. This makes it much
easier
+to review the email archives.</p>
+<p>Let the Vote thread run for one week. A positive result is achieved by
+more positive votes than negative ones, as per the <a
href="https://apache.org/foundation/voting">ASF voting process
+document</a>.</p>
+<h3 id="announcing-results">Announcing results <a class="headerlink"
title="Permalink" href="#announcing-results">¶</a></h3>
<p>After a positive result, record the result on the PMC list with a
<code>[RESULT][VOTE]</code> 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>
+and then invite the candidate, using <a
href="templates/committer-results.txt">this template</a>
+for a new committer, or <a href="templates/committer-pmc-results.txt">this
template</a>
+for a committer and PMC member.</p>
+<p>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 <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><a name="NewCommitter-EmailTemplates"></a></p>
-<h2 id="email-templates">Email Templates <a class="headerlink"
title="Permalink" href="#email-templates">¶</a></h2>
-<h3 id="committer-vote-template">Committer Vote Template <a class="headerlink"
title="Permalink" href="#committer-vote-template">¶</a></h3>
-<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,
-use the following one (Committer and PMC member candidate Vote Template).</p>
-<pre><code>------------------------------------------------------------
-To: private@[PROJECT].apache.org
-Subject: [VOTE] New committer: Jo Bloggs
-
-[ add the reasons behind your nomination here ]
-
-Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
-https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
-
-See voting guidelines at
-https://community.apache.org/newcommitter.html
-
-------------------------------------------------------------
-</code></pre>
-<h3 id="committer-and-pmc-member-candidate-vote-template">Committer and PMC
member candidate Vote Template <a class="headerlink" title="Permalink"
href="#committer-and-pmc-member-candidate-vote-template">¶</a></h3>
-<p>This is the email to commence a vote for new committer that is also
candidate for a PMC member.</p>
-<pre><code>------------------------------------------------------------
-To: private@[PROJECT].apache.org
-Subject: [VOTE] New Committer and PMC member candidate: Jo Bloggs
-
-[ add the reasons behind your nomination here ]
-
-Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
-https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
-
-See voting guidelines at
-https://community.apache.org/newcommitter.html
-</code></pre>
-<h3 id="committer-close-vote">Committer Close Vote <a class="headerlink"
title="Permalink" href="#committer-close-vote">¶</a></h3>
-<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: Jo Bloggs
-
-The vote has now closed. The results are:
-
-Binding Votes:
-
-+1 [TOTAL BINDING +1 VOTES]
- 0 [TOTAL BINDING +0/-0 VOTES]
--1 [TOTAL BINDING -1 VOTES]
-
-The vote is ***successful/not successful***
-</code></pre>
-<h3 id="committer-and-new-pmc-member-candidate-close-vote">Committer and New
PMC member candidate close Vote <a class="headerlink" title="Permalink"
href="#committer-and-new-pmc-member-candidate-close-vote">¶</a></h3>
-<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 and PMC member candidate: Jo Bloggs
-
-The vote has now closed. The results are:
-
-Binding Votes:
-
-+1 [TOTAL BINDING +1 VOTES]
- 0 [TOTAL BINDING +0/-0 VOTES]
--1 [TOTAL BINDING -1 VOTES]
-
-The vote is ***successful/not successful***
-</code></pre>
-<h3 id="committer-invite-template">Committer Invite Template <a
class="headerlink" title="Permalink"
href="#committer-invite-template">¶</a></h3>
-<p>This is the suggested invitation email to send to the newly elected
committer,
-sent after a positive result from the vote for a new committer.</p>
-<pre><code>------------------------------------------------------------
-To: [email protected]
-Cc: private@[PROJECT].apache.org
-Subject: Invitation to become [PROJECT] committer: Jo Bloggs
-
-Hello [invitee name],
-
-The [Project] Project Management Committee (PMC)
-hereby offers you committer privileges to the project
-[If your project automatically adds committers as PMC members]
-as well as membership in the PMC
-[/if]
-These privileges are offered on the understanding that you'll use them
-reasonably and with common sense. We like to work on trust
-rather than unnecessary constraints.
-
-Being a committer enables you to more easily make
-changes without needing to go through the patch
-submission process. [Being a PMC member enables you
-to guide the direction of the project.]
-
-Being a committer does not require you to
-participate any more than you already do. It does
-tend to make one even more committed. You will
-probably find that you spend more time here.
-
-Of course, you can decline and instead remain as a
-contributor, participating as you do now.
-
-This personal invitation is a chance for you to accept or decline in private.
-Please let us know in reply to this message whether you accept or decline.
-
-If you accept, you will need an Apache account (id) with privileges.
-Please follow these instructions.
-
-A. If you already have an ICLA on file:
-
- 1. If you already have an Apache account, let us know your id and we
-will grant you privileges on the project repositories.
-
- 2. If you have previously sent an ICLA, let us know the email address
-and public name used on the ICLA and your preferred Apache id, and
-we will request your account.
-
- 3. If the email address on the previously submitted ICLA is no longer
-valid, let us know the email address and public name used on the new ICLA,
-and your preferred Apache id. Continue to step B below and file your new ICLA.
-
-Look to see if your preferred ID is already taken at
-https://people.apache.org/committer-index.html
-
-B. If there is not already an ICLA on file, you need to submit an ICLA:
-
- 1. Details of the ICLA and the forms are found
- through this link: https://www.apache.org/licenses/#clas
-
- 2. Instructions for its completion and return to
- the Secretary of the ASF are found at
- https://www.apache.org/licenses/contributor-agreements.html#submitting
-
- Do not copy the project or any other individual on your message
- to Secretary, as the form contains Personally Identifiable Information
- that should be kept private.
-
- 3. When you complete the ICLA form, be sure to include in the form
- the Apache [Project] 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
- This will allow the Secretary to notify the PMC
- when your ICLA has been recorded.
-
-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>
+<a href="template/committer-announce.txt">announce the new committer on the
<code>dev</code> list</a></p>
+<p>Alternately, use <a href="templates/committer-pmc-announce.txt">this
template</a> for new
+committer + PMC member.</p>
+<p>You can use <a href="templates/committer-welcome.txt">this template</a> to
welcome
+the new committer to your project community. You are, however,
+encouraged to create your own version of this template, customized to
+your particular project community.</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>
<h3 id="committer-account-creation">Committer Account Creation <a
class="headerlink" title="Permalink"
href="#committer-account-creation">¶</a></h3>
<p>Please see the <a
href="https://www.apache.org/dev/pmc.html#newcommitter">account creation
instructions</a>.</p>
<p>In summary:</p>
@@ -546,107 +422,24 @@ PMC Chair (or any <a
href="https://www.apache.org/foundation/glossary.html#Membe
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.</p>
-<p>For elections held on public lists, please supply the
-<a href="https://mail-archives.apache.org/">Mail archives</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 <a
class="headerlink" title="Permalink"
href="#committer-announce-template">¶</a></h3>
-<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: ###Jo Bloggs
-
-The Project Management Committee (PMC) for Apache [PROJECT]
-has invited Jo Bloggs to become a committer and we are pleased
-to announce that they have accepted.
-
-### add specific details here ###
-
-Being a committer enables easier contribution to the
-project since the committer has write access to the repository
-This should enable better productivity.
-</code></pre>
-<h3 id="committer-and-pmc-member-announce-template">Committer and PMC member
Announce Template <a class="headerlink" title="Permalink"
href="#committer-and-pmc-member-announce-template">¶</a></h3>
-<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 and PMC member: ###Jo Bloggs
-
-The Project Management Committee (PMC) for Apache [PROJECT]
-has invited Jo Bloggs to become a committer and a PMC member
-and we are pleased to announce that they have accepted.
-
-### add specific details here ###
-
-Being a committer enables easier contribution to the
-project since the committer has write access to the repository
-This should enable better productivity.
-
-A PMC member helps manage and guide the direction of the project.
-</code></pre>
-<h3 id="committer-done-template">Committer Done Template <a class="headerlink"
title="Permalink" href="#committer-done-template">¶</a></h3>
-<pre><code>After the committer account is established.
-
-------------------------------------------------------------
-To: private@[PROJECT].a.o, ###[email protected]
-Subject: account request: ###Jo Bloggs
-
-####, as you know, the ASF Infrastructure has set up your
-committer account with the username '####'.
-
-Please follow the instructions to set up your SSH,
-svn password, svn configuration, email forwarding, etc.
-https://www.apache.org/dev/#committers
-
-[If your project automatically adds committers as PMC members]
-Please subscribe to the [PROJECT] Project Management
-Committee mailing list private@[PROJECT].apache.org.
-[/If]
-
-You have commit access to specific sections of the
-ASF repository, as follows:
-
-[PROJECT] has various resources at:
- https://svn.apache.org/repos/asf/[PROJECT]
- https://gitbox.apache.org
-
-The general "committers" at:
-https://svn.apache.org/repos/private/committers
-
-If using svn, you will probably need to 'svn switch" previous checkouts
to now use https,
-for example:
-
-svn switch --relocate https://svn.apache.org/repos/asf/[PROJECT]
https://svn.apache.org/repos/asf/[PROJECT]
-
-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/
-
-The incubator also has some useful information for new committers
-in incubating projects:
- https://incubator.apache.org/guides/committer.html
- https://incubator.apache.org/guides/ppmc.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.]
- https://forrest.apache.org/guidelines.html
-
-If you have any questions during this phase, then please
-see the following resources:
-
-Apache developer's pages: https://www.apache.org/dev/
-Incubator committer guide: https://incubator.apache.org/guides/committer.html
-
-Naturally, if you don't understand anything be sure to ask us on the [PROJECT]
dev mailing list.
-Documentation is maintained by volunteers and hence can be out-of-date and
incomplete - of course
-you can now help fix that.
-
-A PMC member will announce your election to the dev list soon.
-</code></pre>
+<p>Please supply the <a href="https://lists.apache.org/">mail archives</a> URL
as
+proof of the vote results.</p>
+<p><a name="NewCommitter-EmailTemplates"></a></p>
+<h2 id="email-templates">Email Templates <a class="headerlink"
title="Permalink" href="#email-templates">¶</a></h2>
+<p>The following templates are recommended ways to phrase your email
+communications around inviting a new committer, to ensure that everyone
+understands your intent.</p>
+<ul>
+<li><a href="templates/committer-discuss.txt">Committer discussion
template</a></li>
+<li><a href="templates/commiter-vote.txt">Committer vote template</a></li>
+<li><a href="templates/commiter-pmc-vote.txt">Committer + PMC vote
template</a></li>
+<li><a href="templates/committer-results.txt">Committer vote results
template</a></li>
+<li><a href="templates/committer-pmc-results.txt">Committer + PMC vote results
template</a></li>
+<li><a href="templates/committer-invite.txt">Committer invite template</a></li>
+<li><a href="templates/committer-announce.txt">New committer
announcement</a></li>
+<li><a href="templates/committer-pmc-announce.txt">New committer and PMC
member announcement</a></li>
+<li><a href="templates/committer-welcome.txt">Welcome the new committer to
your community</a></li>
+</ul>
</div>
diff --git a/content/templates/committer-announce.txt
b/content/templates/committer-announce.txt
new file mode 100644
index 00000000..119d9155
--- /dev/null
+++ b/content/templates/committer-announce.txt
@@ -0,0 +1,13 @@
+To: dev@[PROJECT].apache.org
+Subject: New committer: [Committer Name]
+
+The Project Management Committee (PMC) for Apache [PROJECT]
+has invited [Committer Name] to become a committer and we are pleased
+to announce that they have accepted.
+
+Please join us in welcoming [Committer Name] to their new role and
+responsibility in our project community.
+
+[Your Name]
+On behalf of the [Project] PMC
+
diff --git a/content/templates/committer-discuss.txt
b/content/templates/committer-discuss.txt
new file mode 100644
index 00000000..012d5a9c
--- /dev/null
+++ b/content/templates/committer-discuss.txt
@@ -0,0 +1,13 @@
+To: [email protected]
+Subject: [DISCUSS] New committer: [Candidate Name]
+
+I propose to add [Candidate Name] as a committer.
+
+[State reasons that you believe they are a good candidate.]
+
+[State contribution statistics, if available and relevant.]
+
+Please remember that should this candidate be elected, they will have
+access to our archives, and be able to read this, so phrase your
+comments constructively with this in mind.
+
diff --git a/content/templates/committer-invite.txt
b/content/templates/committer-invite.txt
new file mode 100644
index 00000000..582a1049
--- /dev/null
+++ b/content/templates/committer-invite.txt
@@ -0,0 +1,76 @@
+To: [email protected]
+Cc: private@[PROJECT].apache.org
+Subject: Invitation to become [PROJECT] committer: [Candidate Name]
+
+Hello [Candidate Name],
+
+The [Project] Project Management Committee (PMC)
+hereby offers you committer privileges to the project
+[If your project automatically adds committers as PMC members]
+as well as membership in the PMC
+[/if]
+These privileges are offered on the understanding that you'll use them
+reasonably and with common sense. We like to work on trust
+rather than unnecessary constraints.
+
+Being a committer enables you to more easily make
+changes without needing to go through the patch
+submission process. [Being a PMC member enables you
+to guide the direction of the project.]
+
+Being a committer does not require you to
+participate any more than you already do. It does
+tend to make one even more committed. You will
+probably find that you spend more time here.
+
+Of course, you can decline and instead remain as a
+contributor, participating as you do now.
+
+This personal invitation is a chance for you to accept or decline in private.
+Please let us know in reply to this message whether you accept or decline.
+
+If you accept, you will need an Apache account (id) with privileges.
+Please follow these instructions.
+
+A. If you already have an ICLA on file:
+
+ 1. If you already have an Apache account, let us know your id and we
+will grant you privileges on the project repositories.
+
+ 2. If you have previously sent an ICLA, let us know the email address
+and public name used on the ICLA and your preferred Apache id, and
+we will request your account.
+
+ 3. If the email address on the previously submitted ICLA is no longer
+valid, let us know the email address and public name used on the new ICLA,
+and your preferred Apache id. Continue to step B below and file your new ICLA.
+
+Look to see if your preferred ID is already taken at
+https://people.apache.org/committer-index.html
+
+B. If there is not already an ICLA on file, you need to submit an ICLA:
+
+ 1. Details of the ICLA and the forms are found
+ through this link: https://www.apache.org/licenses/#clas
+
+ 2. Instructions for its completion and return to
+ the Secretary of the ASF are found at
+ https://www.apache.org/licenses/contributor-agreements.html#submitting
+
+ Do not copy the project or any other individual on your message
+ to Secretary, as the form contains Personally Identifiable Information
+ that should be kept private.
+
+ 3. When you complete the ICLA form, be sure to include in the form
+ the Apache [Project] 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
+ This will allow the Secretary to notify the PMC
+ when your ICLA has been recorded.
+
+When recording of your ICLA is noted, you will
+receive a follow-up message with the next steps for
+establishing you as a committer.
+
+
diff --git a/content/templates/committer-pmc-announce.txt
b/content/templates/committer-pmc-announce.txt
new file mode 100644
index 00000000..c22c28ac
--- /dev/null
+++ b/content/templates/committer-pmc-announce.txt
@@ -0,0 +1,13 @@
+To: dev@[PROJECT].apache.org
+Subject: New committer and PMC member: [Committer Name]
+
+The Project Management Committee (PMC) for Apache [PROJECT]
+has invited [Committer Name] to become a committer and a PMC member
+and we are pleased to announce that they have accepted.
+
+Please join us in welcoming [Committer Name] to their new role and
+responsiblity in our project community.
+
+[Your Name]
+On behalf of the [Project] PMC
+
diff --git a/content/templates/committer-pmc-results.txt
b/content/templates/committer-pmc-results.txt
new file mode 100644
index 00000000..d9d44bc4
--- /dev/null
+++ b/content/templates/committer-pmc-results.txt
@@ -0,0 +1,16 @@
+To: private@[PROJECT].a.o
+Subject: [RESULT] [VOTE] New committer and PMC member candidate: [Candiate
Name]
+
+The vote has now closed. The results are:
+
+Binding Votes:
+
++1 N binding, M non-binding
+ 0 N binding, M non-binding
+-1 N binding, M non-binding
+
+[Considering listing the names of who voted which way]
+
+The vote is ***successful/not successful***
+
+
diff --git a/content/templates/committer-pmc-vote.txt
b/content/templates/committer-pmc-vote.txt
new file mode 100644
index 00000000..a3038a8c
--- /dev/null
+++ b/content/templates/committer-pmc-vote.txt
@@ -0,0 +1,27 @@
+To: private@[PROJECT].apache.org
+Subject: [VOTE] New Committer and PMC member: [Candidate Name]
+
+[ add the reasons behind your nomination here ]
+
+Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
+https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
+
+See voting guidelines at
+https://community.apache.org/newcommitter.html
+
+This is a VOTE to add [Candidate Name] as a committer and PMC member
+
+This has been discussed here: [Link to DISCUSS thread on
+lists.apache.org] If you have more to add to the discussion, please do
+so there, rather than in this VOTE thread.
+
+[+1] Yes, add this committer and PMC member
+[0] Abstain
+[-1] No, do not add this committer and PMC member
+
+Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
+https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
+
+See voting guidelines at
+https://community.apache.org/newcommitter.html
+
diff --git a/content/templates/committer-results.txt
b/content/templates/committer-results.txt
new file mode 100644
index 00000000..88755c16
--- /dev/null
+++ b/content/templates/committer-results.txt
@@ -0,0 +1,15 @@
+To: private@[PROJECT].a.o
+Subject: [RESULT] [VOTE] New committer: [Candidate Name]
+
+The vote has now closed. The results are:
+
+Binding Votes:
+
++1 N binding, M non-binding
+ 0 N binding, M non-binding
+-1 N binding, M non-binding
+
+[Considering listing the names of who voted which way]
+
+The vote is ***successful/not successful***
+
diff --git a/content/templates/committer-vote.txt
b/content/templates/committer-vote.txt
new file mode 100644
index 00000000..7dcee141
--- /dev/null
+++ b/content/templates/committer-vote.txt
@@ -0,0 +1,19 @@
+To: private@[PROJECT].apache.org
+Subject: [VOTE] New committer: [Candidate Name]
+
+This is a VOTE to add [Candidate Name] as a committer.
+
+This has been discussed here: [Link to DISCUSS thread on
+lists.apache.org] If you have more to add to the discussion, please do
+so there, rather than in this VOTE thread.
+
+[+1] Yes, add this committer
+[0] Abstain
+[-1] No, do not add this committer
+
+Voting ends one week from today, i.e. midnight UTC on YYYY-MM-DD
+https://www.timeanddate.com/counters/customcounter.html?year=YYYY&month=MM&day=DD
+
+See voting guidelines at
+https://community.apache.org/newcommitter.html
+
diff --git a/content/templates/committer-welcome.txt
b/content/templates/committer-welcome.txt
new file mode 100644
index 00000000..2749e710
--- /dev/null
+++ b/content/templates/committer-welcome.txt
@@ -0,0 +1,69 @@
+To: private@[PROJECT].a.o, [email protected]
+Subject: Welcome, [First Name], New Committer!
+
+Hello, [Committer Name]
+
+As you know, the ASF Infrastructure has set up your committer account
+with the username `[apacheID]`
+
+[If your project uses GitHub]
+You will now be able to merge approved PRs on GitHub for this project.
+(You'll need to associate your GitHub account with your Apache email
+address.)
+
+You can manage your account settings at https://id.apache.org/
+[/If GitHub]
+
+[If your project uses SVN]
+svn password, svn configuration, email forwarding, etc.
+https://www.apache.org/dev/#committers
+
+[PROJECT] has various resources at:
+ https://svn.apache.org/repos/asf/[PROJECT]
+[/If SVN]
+
+[If your project automatically adds committers as PMC members]
+Please subscribe to the [PROJECT] Project Management
+Committee mailing list private@[PROJECT].apache.org.
+[/If PMC]
+
+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/
+
+The incubator also has some useful information for new committers
+in incubating projects:
+ https://incubator.apache.org/guides/committer.html
+ https://incubator.apache.org/guides/ppmc.html
+
+You now have expanded access to portions of the Whimsy toolset
+specific to committers: https://whimsy.apache.org/
+
+As an ASF committer, you now also have commit access to specific
+sections of the ASF Foundation repository, as follows:
+
+The general "committers" at:
+https://svn.apache.org/repos/private/committers
+
+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
+
+If you have any questions during this phase, then please
+see the following resources:
+
+Apache developer's pages: https://www.apache.org/dev/
+Incubator committer guide: https://incubator.apache.org/guides/committer.html
+
+Naturally, if you don't understand anything be sure to ask us on the
+[PROJECT] dev mailing list. Documentation is maintained by volunteers
+and hence can be out-of-date and incomplete - of course you can now
+help fix that.
+
+A PMC member will announce your election to the dev list, and we
+encourage you to introduce yourself there.
+
+[Your Name]
+On behalf of the [Project] PMC
+