You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tinkerpop.apache.org by sp...@apache.org on 2016/08/24 11:11:17 UTC
tinkerpop git commit: Clean up references to "PPMC" and add a new PMC
section
Repository: tinkerpop
Updated Branches:
refs/heads/master 4daefb37a -> c9e2f4160
Clean up references to "PPMC" and add a new PMC section
Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/c9e2f416
Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/c9e2f416
Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/c9e2f416
Branch: refs/heads/master
Commit: c9e2f4160cc32b6ace351081602561e45abc0de7
Parents: 4daefb3
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Wed Aug 24 07:10:34 2016 -0400
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Wed Aug 24 07:10:34 2016 -0400
----------------------------------------------------------------------
docs/src/dev/developer/administration.asciidoc | 95 +++++++++++++++------
1 file changed, 68 insertions(+), 27 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/c9e2f416/docs/src/dev/developer/administration.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/dev/developer/administration.asciidoc b/docs/src/dev/developer/administration.asciidoc
index e1eb352..0a18811 100644
--- a/docs/src/dev/developer/administration.asciidoc
+++ b/docs/src/dev/developer/administration.asciidoc
@@ -20,8 +20,8 @@ Administration
New Committers
--------------
-When a candidate is identified by a PPMC member as someone who might be a good official committer to TinkerPop, the
-PPMC member should open a DISCUSS thread on the private TinkerPop mailing list. The thread should provide some
+When a candidate is identified by a PMC member as someone who might be a good official committer to TinkerPop, the
+PMC member should open a DISCUSS thread on the private TinkerPop mailing list. The thread should provide some
background and reasoning for why that member believes the candidate would be a good committer. Given enough time for
feedback on the candidate and presuming there is still positive interest in doing so, a VOTE thread on the private
TinkerPop mailing list is started to get the official stance. As per usual, the VOTE will be made open for no less
@@ -36,36 +36,45 @@ SUBJECT: Invitation to become TinkerPop committer: [candidate name]
Hello,
-The TinkerPop Podling Project Management Committee (PPMC) hereby offers you committer privileges to the project.
-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.
+The TinkerPop Project Management Committee (PMC) hereby offers you committer
+privileges to the project. 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 committer enables you to more easily make changes without needing to
+go through the patch submission process.
-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.
+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.
+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@tinkerpop.apache.org address only.
+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@tinkerpop.apache.org address only.
-B. If you are accepting, the next step is to register an iCLA with the Apache Software Foundation:
- 1. Details of the iCLA and the forms are found through this link: http://www.apache.org/licenses/#clas.
+B. If you are accepting, the next step is to register an iCLA with the Apache
+Software Foundation:
+ 1. Details of the iCLA and the forms are found through this link:
+ http://www.apache.org/licenses/#clas.
- 2. The form (text or PDF version) provides instructions for its completion and return to the Secretary of the ASF
- at secretary@apache.org.
+ 2. The form (text or PDF version) provides instructions for its completion
+ and return to the Secretary of the ASF at secretary@apache.org.
- 3. When you transmit the completed iCLA, request to notify Apache TinkerPop and choose a unique Apache id.
- Look to see if your preferred id is already taken at http://people.apache.org/committer-index.html This will
- allow the Secretary to notify the PMC when your iCLA has been recorded.
+ 3. When you complete iCLA ensure that you include "Apache TinkerPop" in the
+ "notify project" project field and choose a preferred unique Apache id.
+ Look to see if your preferred id is already taken at
+ http://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 receive a follow-up message with the next steps for establishing you
-as a committer.
+When recording of your iCLA is noticed, you will receive a follow-up message
+with the next steps for establishing you as a committer.
----
-Assuming the individual accepts, the next step is to get their account created. As we are in incubation, we will
-need to contact a mentor for help with this step.
+Assuming the iCLA included items from step 3, the secretary will handle account creation, otherwise it will be up to
+the PMC chair to link:http://www.apache.org/dev/pmc.html#newcommitter[handle such things].
Upon confirming with the new committer that their account is established, send an announcement email to the
developer and user mailing lists:
@@ -74,14 +83,46 @@ developer and user mailing lists:
----
SUBJECT: New Committer: [committer name]
-The Podling Project Management Committee (PPMC) for Apache TinkerPop has asked [committer name] to become a committer
-and we are pleased to announce that he has accepted.
+The Project Management Committee (PMC) for Apache TinkerPop has asked
+[committer name] to become a committer and we are pleased to announce their
+acceptance.
-[describe the nature of the committers work in the community]
+[describe the nature of the committer's work in the community]
-Being a committer enables easier contribution to the project since there is no need to work via the patch submission
-process. This should enable better productivity.
+Being a committer enables easier contribution to the project since there is no
+need to work via the patch submission process. This should enable better
+productivity.
----
+Finally, new committers should be sent an email that covers some of the administrative elements of their new role:
+* link:http://www.apache.org/dev/committers.html[Apache Committer Gu]ide]
+* link:http://www.apache.org/dev/committers.html[Apache Committer FAQ]
+* link:http://tinkerpop.apache.org/docs/current/dev/developer/[TinkerPop Developer Documentation]
+** Bring specific attention to the "committer" section which describes our general policies.
+New PMC Members
+---------------
+
+The process for bringing on new PMC members is not so different from the one for new committers. The process begins
+with a DISCUSS thread to the private mailing list for building consensus followed by a VOTE thread to confirm.
+Presuming the new PMC member is a committer already (which is mostly likely for TinkerPop), there should be no need for
+any additional paperwork. On successful vote however, a NOTICE should be sent to the board@apache.org (copying
+private@tinkerpop.apache.org):
+
+[source,text]
+----
+Subject [NOTICE] [name of PMC new member] for Apache TinkerPop PMC
+
+Apache TinkerPop proposes to invite [name of PMC new member] ([ApacheId]) to join the PMC.
+
+The vote result is available here:
+
+[include the link to the vote result thread from private]
+----
+
+If the candidate does not (yet) have an Apache account, then please note that fact in the notification email. Provide
+the board 72 hours to respond with objection before extending the invite to the new PMC member. Once that time has
+elapsed, the invite may be sent to the new PMC member. If they accept, then the PMC chair should refer to the
+link:http://www.apache.org/dev/pmc.html#newpmc[How to Add a New PMC Member] section in the Apache docs for ho to
+complete the process.
\ No newline at end of file