You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by gi...@apache.org on 2023/02/16 03:06:14 UTC
[comdev-site] branch asf-site updated: Updated asf-site from master at 6ce919ffd9f69069c43c5669851c8ad3aa658fc5 using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/192/
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 60e9bc0 Updated asf-site from master at 6ce919ffd9f69069c43c5669851c8ad3aa658fc5 using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/192/
60e9bc0 is described below
commit 60e9bc0ef7c379bfee7e2c1f22cc82386f8469ec
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Feb 16 03:06:11 2023 +0000
Updated asf-site from master at 6ce919ffd9f69069c43c5669851c8ad3aa658fc5 using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/192/
---
content/newcommitter.html | 146 +++++++++++++++++++++++-----------------------
content/sitemap.xml | 2 +-
2 files changed, 73 insertions(+), 75 deletions(-)
diff --git a/content/newcommitter.html b/content/newcommitter.html
index f26a730..74f60e7 100644
--- a/content/newcommitter.html
+++ b/content/newcommitter.html
@@ -13,7 +13,7 @@ Each project has a different approach to managing new committers. This page desc
<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="2022-06-13T22:07:12+01:00" /><meta property="og:site_name" content="Apache Community Development" />
+<meta property="article:modified_time" content="2023-02-09T07:53:15-08:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - New Committer</title>
@@ -221,9 +221,8 @@ drafts for the various communications that are necessary.</p>
<li><a href="#committer-vote-template">Committer Vote Template</a></li>
<li><a href="#pmc-vote-template">PMC Vote Template</a></li>
<li><a href="#close-vote">Close Vote</a></li>
- <li><a href="#board-approval-of-new-pmc-member">Board Approval of new PMC member</a></li>
+ <li><a href="#notify-board-of-new-pmc-member">Notify Board of new PMC member</a></li>
<li><a href="#committer-invite-template">Committer Invite Template</a></li>
- <li><a href="#committer-accept-template">Committer Accept Template</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-done-template">Committer Done Template</a></li>
@@ -287,18 +286,21 @@ 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>Discuss the proposed committer/PMC member. If positive, call a vote (templates/committerVote.txt)</li>
+<li>Close the vote (templates/closeVote.txt)</li>
<li>If the result is positive, invite the new committer (templates/committerInvite.txt)</li>
</ol>
<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)
+<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/">https://whimsy.apache.org/roster/committee/</a> or <a href="https://whimsy.apache.org/roster/ppmc/">https://whimsy.apache.org/roster/ppmc/</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 enables svn and other access</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>
@@ -309,7 +311,13 @@ 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 <code>private@</code> mailing list to enable a frank discussion.</p>
+<p>We do the discussion and vote on the <code>private@</code> mailing list to enable a frank discussion.</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.
@@ -391,7 +399,7 @@ Binding Votes:
The vote is ***successful/not successful***
</code></pre>
-<h3 id="board-approval-of-new-pmc-member">Board Approval of new PMC member</h3>
+<h3 id="notify-board-of-new-pmc-member">Notify Board of new PMC member</h3>
<p>See <a href="https://www.apache.org/dev/pmc.html#newpmc">https://www.apache.org/dev/pmc.html#newpmc</a></p>
<h3 id="committer-invite-template">Committer Invite Template</h3>
<p>This is the suggested invitation email to send to the newly elected committer,
@@ -423,81 +431,52 @@ probably find that you spend more time here.
Of course, you can decline and instead remain as a
contributor, participating as you do now.
-A. This personal invitation is a chance for you to
-accept or decline in private. Either way, please
-let us know in reply to the private@[PROJECT].apache.org
-address only.
+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.
-B. If you accept, the next step is to register 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/#submitting
+If you accept, you will need an Apache account (id) with privileges.
+Please follow these instructions.
- 3. When you transmit the completed iCLA, request
- to notify 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.
+A. If you already have an ICLA on file:
-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>
-<pre><code>------------------------------------------------------------------------
-To: JoBloggs@foo.net
-Cc: private@[PROJECT].apache.org
-Subject: Re: invitation to become [PROJECT] committer
+ 1. If you already have an Apache account, let us know your id and we
+will grant you privileges on the project repositories.
-Welcome. Here are the next steps in becoming a project committer. After that we will make
-an announcement to the [PROJECT]-dev list.
+ 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.
-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,
-see the Corporate CLA. Ask us if you have any issues.
-https://www.apache.org/licenses/#clas.
+ 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.
-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
+Look to see if your preferred ID is already taken at
https://people.apache.org/committer-index.html
-Please notify us when you have submitted the CLA and by what means
-you did so. This will enable us to monitor its progress.
-
-We will arrange for your Apache user account when the CLA has
-been recorded.
+B. If there is not already an ICLA on file, you need to submit an ICLA:
-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 roles within the ASF and provides other
-resources:
- https://www.apache.org/foundation/how-it-works.html
- https://www.apache.org/dev/
+ 1. Details of the ICLA and the forms are found
+ through this link: https://www.apache.org/licenses/#clas
-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
+ 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
-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
+ 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.
-[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
+ 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.
-Yours,
-The Apache [PROJECT] PMC
+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-account-creation">Committer Account Creation</h3>
<p>Follow the instructions
@@ -556,15 +535,34 @@ 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
-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
+ 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:
diff --git a/content/sitemap.xml b/content/sitemap.xml
index e5ed8bf..8b61449 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -244,7 +244,7 @@
<url>
<loc>https://community.apache.org/newcommitter.html</loc>
- <lastmod>2022-06-13T22:07:12+01:00</lastmod>
+ <lastmod>2023-02-09T07:53:15-08:00</lastmod>
</url>
<url>