This is an automated email from the ASF dual-hosted git repository.
tison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/main by this push:
new 4f764bb6 Clarify and split new committer / new PMC member templates
(#183)
4f764bb6 is described below
commit 4f764bb68b4a628001d50538c12cf237672f3998
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Wed Jul 17 04:58:50 2024 +0200
Clarify and split new committer / new PMC member templates (#183)
Since we are now reaching out to projects about PMC vs. PMC member,
I looked at the source of some of the templates that are used and
clarified, unified them and fixed a few errors in those templates,
also replaced the link to anchor in www-site about new PMC member
with #newpmcmember instead of #newpmc, which could be confusing
and one of the reasons why people use New PMC rather than New PMC
member.
The problem with those templates were that they did not provide
correct templates for inviting (and following up) in case the
PMC member was invited separately from committer - the templates
required manual modifications of Commiter to "PMC member" and
manually modifying text of the template, which could be onoe of
the reasons why people replaced "Committer" with "PMC member" in
their invitations.
The change splits the process out of inviting PMC member separately
(while leaving the optional process where committer is immediately
a PMC member in the original place).
This PR also unifies the way how links are added to the page, there
was a mixture of `[n]` references and `md` way of inlining links.
Another part of this change is introducing "PMC member" everywhere
where "PMC" could be confused with person. For example the
"PMC candidate" - while technically correct ("candidate to the PMC")
is another reason why people could confuse "PMC" with person.
Replacing it with "PMC member candidate" removes the confusion while
being also techincally correct.
The last part of it that in a few places the documentation was
wrongly referring to "asking the board" when inviting PMC member,
where this process have been changed last year to "notifying the board".
All those places have been corrected.
---
layouts/partials/navbar.html | 4 +-
source/newcommitter.md | 252 ++++++++++++++++++++++++-------------------
source/newpmcmember.md | 169 +++++++++++++++++++++++++++++
source/pmc/chair.md | 24 ++---
4 files changed, 325 insertions(+), 124 deletions(-)
diff --git a/layouts/partials/navbar.html b/layouts/partials/navbar.html
index 930c8271..fa8bb5d4 100644
--- a/layouts/partials/navbar.html
+++ b/layouts/partials/navbar.html
@@ -53,7 +53,7 @@
<a class="dropdown-item" href="/newcomers/">Getting Started at
Apache</a>
<a class="dropdown-item"
href="https://www.apache.org/dev/";>Technical Developer FAQs</a>
<div class="dropdown-divider"></div>
- <a class="dropdown-item text-uppercase disabled"
href="#">Commiters and PMCs</a>
+ <a class="dropdown-item text-uppercase disabled"
href="#">Committers and PMCs</a>
<a class="dropdown-item" href="/committers/">Committer Tips</a>
<a class="dropdown-item"
href="/committers/decisionMaking.html">Decision Making</a>
<a class="dropdown-item"
href="/committers/funding-disclaimer.html">Funding Campaign Disclaimer</a>
@@ -90,7 +90,7 @@
</li>
<li class="nav-item dropdown">
<a class="nav-link dropdown-toggle" href="#" id="conversDropdown"
role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Working Groups
+ Working Groups
</a>
<div class="dropdown-menu" aria-labelledby="wgDropdown">
<a class="dropdown-item" href="/workinggroups/">Working Groups</a>
diff --git a/source/newcommitter.md b/source/newcommitter.md
index 8ea96d0c..11271628 100644
--- a/source/newcommitter.md
+++ b/source/newcommitter.md
@@ -11,6 +11,12 @@ 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.
+Some of the PMCs automatically make committers PMC members. The templates below
+have conditional `[if]` clauses for that.
+
+If the PMC has separate process for approving PMC members, see
+[new PMC member](https://community.apache.org/newpcmember.html)
+
{{% toc %}}
<a name="NewCommitter-Guidelinesforassessingnewcandidatesforcommittership"></a>
@@ -29,7 +35,7 @@ the project. We encourage you to not make this bar
artificially high.
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.
+### Ability to work cooperatively with peers.
How do we evaluate?
- By the interactions they have through email.
@@ -49,7 +55,7 @@ materials.
How do we evaluate?
- By the interactions they have through email.
- - Do they help to answer questions raised on the mailing list; do they show
a helpful
+ - 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>
@@ -64,7 +70,7 @@ How do we evaluate?
### Personal skill/ability
How do we evaluate?
- - A solid general understanding of the project.
+ - A solid general understanding of the project.
- Quality of discussion in email.
- Whether their patches (where applicable) are easy to apply with only a
cursory review.
@@ -78,25 +84,27 @@ later in this document.
<a name="NewCommitter-Summary"></a>
### Summary
-1. Discuss the proposed committer or PMC member. If the discussion seems to be
going positively, call a vote (templates/committerVote.txt)
-1. Close the vote (templates/closeVote.txt)
-1. If the result is positive, invite the new committer
(templates/committerInvite.txt)
+1. Discuss the proposed committer (and optionally PMC member). If the
discussion seems to be going positively,
+ call a vote following the template below.
+1. Close the vote following the template below
+1. If the result is positive, invite the new committer following the template
below.
If they accept, then:
1. If they already have an Apache id, grant appropriate commit privileges.
-Use the Whimsy tool to update the roster via
https://whimsy.apache.org/roster/committee/ or
https://whimsy.apache.org/roster/ppmc/
+ Use the Whimsy tool to update the roster via [Comitee
Roster](https://whimsy.apache.org/roster/committee/) or
+ [PPMC Roster](https://whimsy.apache.org/roster/ppmc/)
1. 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.
1. Wait until root says it is done
1. 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.
+ If the committer uses GitHub, they are responsible for linking it to
their ASF account.
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)
+1. Notify the committer of completion following the template below
+1. 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](https://www.apache.org/dev/pmc.html#newpmcmember]
+1. Announce the new committer following the template below.
<a name="NewCommitter-Discussion"></a>
### Discussion
@@ -143,7 +151,7 @@ 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.
-After a positive result, record the result on the PMC list with a
[RESULT][VOTE] subject
+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.
@@ -159,96 +167,110 @@ Other notes about the process are available on the main
[Apache site](https://ww
### Committer 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).
-
+use the following one (Committer and PMC member candidate Vote Template).
+
------------------------------------------------------------
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
-
+
------------------------------------------------------------
-### 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).
-
+### Committer and PMC member candidate Vote Template
+This is the email to commence a vote for new committer that is also candidate
for a PMC member.
+
------------------------------------------------------------
To: private@[PROJECT].apache.org
- Subject: [VOTE] New PMC candidate: Jo Bloggs
-
+ 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
-
-### Close Vote
+
+### Committer Close Vote
This email ends the vote and reports the result to the project.
-
+
------------------------------------------------------------
To: private@[PROJECT].a.o
- Subject: [RESULT] [VOTE] New committer (or PMC candidate): Jo Bloggs
-
+ 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***
-### Notify Board of new PMC member
-See [https://www.apache.org/dev/pmc.html#newpmc][1]
+### Committer and New PMC member candidate close Vote
+This email ends the vote and reports the result to the project.
+
+ ------------------------------------------------------------
+ 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***
### Committer Invite Template
-This is the suggested invitation email to send to the newly elected committer,
+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.
-
+
------------------------------------------------------------
To: joblo...@foo.net
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
- [as well as membership in the PMC]. These privileges are
- offered on the understanding that you'll use them
+ 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.
+ 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
+ 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
+ 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
+ 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
@@ -256,21 +278,21 @@ sent after a positive result from the vote for a new
committer.
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.
+ 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
+
+ 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
+
+ 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
+ 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
@@ -279,95 +301,113 @@ sent after a positive result from the vote for a new
committer.
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
+ 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
+ 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
+ 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 Account Creation
Please see the [account creation
instructions](https://www.apache.org/dev/pmc.html#newcommitter).
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,
-the account creation request is made by the
+`[RESULT][VOTE]` message has been posted to the PMC private list,
+the account creation request is made by the
secretary or assistant secretary who files the ICLA.
Otherwise, the new account request should be made by the
-PMC Chair (or any [ASF Member][6] if the chair is unavailable).
+PMC Chair (or any [ASF
Member](https://www.apache.org/foundation/glossary.html#Member)
+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.
+The PMC chair needs to use the [ASF New Account
Request](https://id.apache.org/acreq/pmc-chairs/) form to
+send a new account request. Members may use [ASF New Account
Request](https://id.apache.org/acreq/members/) 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.
+For elections held on public lists, please supply the
+[Mail archives](https://mail-archives.apache.org/) url. For private lists, you
can
+use the [Mail Search tool](https://mail-search.apache.org/) to locate the
appropriate url.
### Committer Announce Template
This is the email to announce the new committer to `[PROJECT]-dev` once the
account has been created.
-
+
------------------------------------------------------------
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
+ 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.
+
+### Committer and PMC member Announce Template
+This is the email to announce the new committer to `[PROJECT]-dev` once the
account has been created.
+
+ ------------------------------------------------------------
+ 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 there is no need to go via the patch
- submission process. This should enable better productivity.
+ 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.
### Committer Done Template
After the committer account is established.
-
+
------------------------------------------------------------
To: private@[PROJECT].a.o, ###joblo...@foo.net
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 to the PMC]
- Please subscribe to the [PROJECT] Project Management
+
+ [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,
+
+ 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
@@ -376,27 +416,19 @@ This is the email to announce the new committer to
`[PROJECT]-dev` once the acco
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.
+
+ 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.
-
- [1]: https://www.apache.org/dev/pmc.html#newpmc
- [2]: https://id.apache.org/acreq/pmc-chairs/
- [3]: https://id.apache.org/acreq/members/
- [4]: https://mail-archives.apache.org/
- [5]: https://mail-search.apache.org/
- [6]: https://www.apache.org/foundation/glossary.html#Member
+ A PMC member will announce your election to the dev list soon.
diff --git a/source/newpmcmember.md b/source/newpmcmember.md
new file mode 100644
index 00000000..3c754b59
--- /dev/null
+++ b/source/newpmcmember.md
@@ -0,0 +1,169 @@
+---
+title: New PMC member
+tags: ["pmc", "pmcmembers", "election"]
+---
+
+## New PMC member process
+
+This section describes a typical Apache project's process for handling the
+vote to add a new PMC member - when it is separate from becoming committer.
+Templates mentioned in the process appear later in this document. If your PMC
+adds automatically committers as PMC members, the process for doing both at the
+same time is described in the [New
committer](https://community.apache.org/newcommitter.html)
+
+<a name="NewPMCMember-Summary"></a>
+### Summary
+
+1. Discuss the proposed PMC member. If the discussion seems to be going
positively, call a vote following
+ the template below.
+1. Close the vote following the template below.
+1. If the result is positive, invite the new committer following the template
below.
+
+If they accept, then:
+
+1. In case the new PMC member is already is already a committer, they have
Apache id,
+ you should grant them appropriate PMC privileges. Use the Whimsy tool to
update the roster via
+ https://whimsy.apache.org/roster/committee/ or
https://whimsy.apache.org/roster/ppmc/
+1. Announce the new PMC member following the template below.
+
+<a name="NewPMCMember-Discussion"></a>
+### Discussion
+
+We do the discussion and vote on the `private@` mailing list to enable a frank
+discussion. Any PMC member may propose a potential PMC member.
+This is **not** the sole responsibility or right of the PMC chair.
+
+We invite people to join as 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.
+
+Start a separate [VOTE] thread for each new person. This makes it much easier
+to review the email archives.
+
+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.
+
+Don't wait too long before proposing and don't be too hasty. There is a
+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.
+
+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**: 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 mind.
+
+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 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 PMC
membership in private.
+They can post a reply to the PMC mailing list.
+
+After we reach a decision on the `private@` list, and after the steps above, we
+announce the new PMC member 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#newpmcmember).
+
+<a name="NewCommitter-EmailTemplates"></a>
+## Email Templates
+
+### PMC member Vote Template
+This is the email to commence a vote for a new PMC member.
+
+ ------------------------------------------------------------
+ To: private@[PROJECT].apache.org
+ Subject: [VOTE] New 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/newpmcmember.html
+
+ ------------------------------------------------------------
+
+### Close Vote
+This email ends the vote and reports the result to the project.
+
+ ------------------------------------------------------------
+ To: private@[PROJECT].a.o
+ Subject: [RESULT] [VOTE] New 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***
+
+### PMC member Invite Template
+This is the suggested invitation email to send to the newly elected PMC member
candidate,
+sent after a positive result from the vote for a new PMC member.
+
+ ------------------------------------------------------------
+ To: joblo...@foo.net
+ Cc: private@[PROJECT].apache.org
+ Subject: Invitation to become [PROJECT] PMC member: Jo Bloggs
+
+ Hello [invitee name],
+
+ The [Project] Project Management Committee (PMC)
+ hereby offers you membership in the PMC. 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.
+
+ 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.
+
+### PMC member Announce Template
+
+This is the email to announce the new committer to `[PROJECT]-dev` once the
account has been created.
+
+ ------------------------------------------------------------
+ To: dev@[PROJECT].apache.org
+ Subject: new PMC member: ###Jo Bloggs
+
+ The Project Management Committee (PMC) for Apache [PROJECT]
+ has invited Jo Bloggs to become a PMC member and we are pleased
+ to announce that they have accepted.
+
+ ### add specific details here ###
+
+ A PMC member helps manage and guide the direction of the project.
+
+### PMC Member Done Template
+ After the PMC member account is established.
+
+ ------------------------------------------------------------
+ To: private@[PROJECT].a.o, ###joblo...@foo.net
+ Subject: account request: ###Jo Bloggs
+
+ Please subscribe to the [PROJECT] Project Management
+ Committee mailing list private@[PROJECT].apache.org.
+
+ A PMC member will announce your election to the dev list soon.
diff --git a/source/pmc/chair.md b/source/pmc/chair.md
index 86e6158f..6c84fcc3 100644
--- a/source/pmc/chair.md
+++ b/source/pmc/chair.md
@@ -18,12 +18,12 @@ duties](https://www.apache.org/dev/pmc.html#chair) of the
role.
## Secretarial duties
The Chair is responsible for completing the necessary "paperwork" when
-new committers and PMC members are added.
+new committers and PMC members are added.
-See the [process for adding new
+See the [process for adding new
committers](https://www.apache.org/dev/pmc.html#committer-management),
-and the [process for adding new PMC
-members](https://www.apache.org/dev/pmc.html#newpmc), for details of
+and the [process for adding new PMC
+members](https://www.apache.org/dev/pmc.html#newpmcmember), for details of
these requirements.
## Reporting
@@ -35,18 +35,18 @@ the board of directors.
As the name implies, the Chair may occasionally need to step in to
moderate discussion, to ensure that a community is conducting itself
-with decorum, and not straying into divisive discussion.
+with decorum, and not straying into divisive discussion.
-The Chair has been selected because they are a respected member of the
-community, and so should not be hesitant to step in and state what the
-community standards are, and enforce the expectation that community members
+The Chair has been selected because they are a respected member of the
+community, and so should not be hesitant to step in and state what the
+community standards are, and enforce the expectation that community members
behave in appropriate ways on official communication channels.
## Selecting a new Chair
-A project may periodically select a new Chair.
+A project may periodically select a new Chair.
-Some projects do this every year or two, while others keep the same Chair
+Some projects do this every year or two, while others keep the same Chair
for many years. A Chair might step down because they no longer have time
for the role, or simply to give someone else an opportunity.
@@ -60,10 +60,10 @@ success in the role.
## See also:
-Newly Chairs are sent [this
+Newly Chairs are sent [this
advice](https://svn.apache.org/repos/private/foundation/officers/advice-for-new-pmc-chairs.txt),
and you're encouraged to read that thoroughly. They should also be
-familiar with [published
+familiar with [published
policies](https://www.apache.org/dev/pmc.html#policy) for PMCs.
