Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Information on adding new Committers/PPMC PMC members to Apache Juneau.

The Apache Juneau team does not differentiate between Committers and PMC members.  Any member of the PMC can propose a new member of the PMC.

Summary

The general process is as follows:

  1. Discussion
  2. Call a vote
  3. Close the vote
  4. Invite the new committer

If they accept, then do:

  1. Accept the committer
  2. Wait until we see that receipt of CLA is recorded
  3. Request creation of the committer account
  4. Now wait until root says it is done
  5. PMC Chair to enable svn and other access
  6. Add committer to the appropriate groups in JIRA and CWiki
  7. Notify the committer of completion
  8. If committer is also to be a PMC member, PMC Chair sends email to board@ asking for acknowledgement of new PMC member
  9. Announce the new committer

Discussion

Before approving membership, it's assumed that the person has actively contributed through this process:
https://cwiki.apache.org/confluence/display/JUNEAU/Contributing+for+Non-committers

Once it's been shown that the member submits good work, the team can invite them to be a full member.

The Apache Juneau team does not differentiate between Committers and PPMC members.  However, PPMC membership must undergo an additional lazy consensus vote to the IPMC to become official.

Any member of the PPMC can propose a new member of the PPMC. The proposal should be discussed in private on the PPMC private alias:

To: private@juneau.apache.org
[DISCUSS]

Joe Bob PPMC

Jane Doe PMC membership

I'd like to discuss adding Joe Bob as a

PPMC

PMC member.

State reason why.

Call for vote

If there is consensus that the proposed member is suitable, then there should be a formal vote in the PPMC PMC private alias:

To: private@juneau.apache.org
[VOTE] Joe Bob PPMC Jane Doe PMC membership

I'm pleased to be calling this vote for inviting Joe Bob [Jane Doe] to be a member of the Juneau PPMCPMC.

This vote will be open at least until 04-May-2016 1:30pm and passes if a majority of at least three +1 Apache Juneau PPMC PMC votes are cast. 
(needs to be at least 72 weekday hours)


[ ] +1 Approve invitation
[ ] 0 I don't feel strongly about it, but don't object 
[ ] -1 Do not approve invitation because...

State reason why.

Close the vote

If the vote is successful, the proposer should send a message to the PPMC PMC private alias.

To: private@juneau private@juneau.apache.org
[VOTE][RESULT] Joe Bob PPMC Jane Doe PMC membership

Voting for PPMC PMC membership for Joe Bob [Jane Doe] is now closed. The vote has passed with the following tally:

John Smith, PPMCPMC, +1
... 

The message id of the [VOTE][RESULT] message should be preserved for notifying the Incubator PMC. 

The nominating PPMC member should send a message to the IPMC (private@incubator.apache.org) with a reference to the vote result's message id of the following form:

Board notification

Adding a new PMC member requires sending an email notification to the Board's mailing list and the PMC's private mailing list and waiting 72 hours. Once the notification appears in the archives, an invitation may be sent out 72 hours later (unless a Director objects to the nomination). The detailed process can be found in the June 2013 board minutes under section "7 G. Amend the Procedure for PMC Membership Changes"

Do NOT send an unconditional invite to the potential member before the 72 hour NOTICE period has expired! It would be very awkward if the invite has to be withdrawn if the board objects.

This notification may be sent by the PMC Chair, or by any other PMC member if they include a link to the formal PMC decision or vote on their private@ list.

Ensure the PMC private list is copied - but do not Cc the potential member. For example:


To: board@apache.org
Cc: private@juneau.apache.org

[NOTICE] Jane Doe for Juneau PMC

Juneau proposes to invite [Jane Doe](janedoe) to join the PMC.

(include if a vote was held)
The vote result is available here: https://lists.apache.org/...

To: private@incubator.apache.org
New member of Juneau PPMC Joe Bob

Joe Bob has been voted as a new member of the Juneau PPMC.

The vote result is at: <reference to RESULT VOTE above>

It should noted that there is a grace period of 72 hours from when the above NOTICE is sent to the Incubator PMC to when the proposed member is formally invited. This is an important part of the overall process. Failure to do this can result in an embarassing situation embarrassing situation for people involved.

Committer Invite

After 72 hours, Joe Bob should be invited to join the PPMCPMC, using a sample message like this:

To:

 joebob@apache

 janedoe@apache.org
CC: private@juneau.apache.org
You're

invited

to

join

the

Juneau

PPMC!Dear Joe Bob In recognition of your demonstrated commitment to, and alignment with, the goals of the Apache Juneau project, the Juneau PPMC has voted to offer you membership in the Juneau PPMC ("Podling Project Management Committee"). Please let us know if you accept by subscribing to the private alias [by sending mail to private-subscribe@juneau.incubator.apache.org], and posting a message to private@juneau.incubator.apache.org. The PPMC is the Incubator podling version of a project PMC ("Project Management Committee") that for every top-level project is tasked by the Apache Board of Directors with official oversight and binding votes in that project. When Juneau graduates from the Incubator to a top-level project, the project PMC is usually formed from the membership of the PPMC. Note that while participation in the PMC after graduation is not guaranteed, simply continuing your constructive and active participation is usually sufficient. As a PPMC member, and later as a PMC member, you are responsible for continuing the general project, code, and community oversight that you have exhibited so far. The votes of the PPMC are not legally binding; votes of the Incubator PMC are. However, many of the PPMC members are also Incubator PMC members, so they implicitly cast binding votes when we vote on PPMC issues. While this is an important legal distinction, it shouldn't enter your thinking when working on the PPMC - members should treat every decision as if it were legally binding for the ASF. Also, in day-to-day activities, the Incubator PMC member vs PPMC member distinction should be invisible -- we are peers. All PPMC members are subscribed to the project's private mail list, which is used to discuss issues unsuitable for an open, public forum, such as people issues (e.g. new committers, problematic community members, etc.), security issues, and the like. It can't be emphasized enough that care should be taken to minimize the use of the private list, discussing everything possible on the appropriate public list. The private PPMC list is *private* - it is strictly for the use of the PPMC. Messages are not to be forwarded to anyone else without the express permission of the PPMC. Also note that any Member of the Foundation has the right to review and participate in any PPMC or PMC list, as a PMC and PPMC are acting on behalf of the Membership. Finally, the PPMC (and assuming graduation, the PMC) is not meant to create a hierarchy within the committership or the community. In fact, a goal is to add all committers over time to the PPMC/PMC, as our belief is that those who do the work should get a binding vote. Therefore, in our day-to-day interactions with the rest of the community, we continue to interact as peers, where every reasonable opinion is considered, and all community members are invited to participate in our public voting. If there ever is a situation where the PMC/PPMC's view differs significantly from that of the rest of the community, this is a symptom of a problem that needs to be addressed. With the expectation of your acceptance, welcome! The Apache Juneau PPMC
p.s. Additional information on Committers and PPMC membership information here:
 
http://www.apache.org/dev/new-committers-guide.html
http://www.apache.org/dev/committers.html
http://incubator.apache.org/guides/ppmc.html
Once the proposed member has accepted, the moderator for the PPMC mail alias will accept the new member's subscription request.

The nominating member should also update the PPMC membership section of the Podling's status file. For projects which choose to always make new committers also PPMC members, simply updating the committer list and ensuring that a statement such as "The PPMC consists of all the committers and mentors listed here" is generally sufficient.

PMC!

Hello [Jane Doe],

The Juneau 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
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.

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@juneau.apache.org
address only.

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: http://www.apache.org/licenses/#clas

2. Instructions for its completion and return to
the Secretary of the ASF are found at
http://www.apache.org/licenses/#submitting

3. When you transmit the completed iCLA, request
to notify the Apache Juneau 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.

When recording of your iCLA is noticed, you will
receive a follow-up message with the next steps for
establishing you as a committer.


Committer Accept

This is the followup email after the new committer has accepted the invitation:

To: janedoe@foo.net
Cc: private@juneau.apache.org
Subject: Re: invitation to become Juneau committer

Welcome. Here are the next steps. After that we will make
an announcement to the juneau-dev list.

You need to send a Contributor License Agreement to the ASF.
Normally you would send an Individual CLA. If you also make
contributions done in work time or using work resources then
see the Corporate CLA. Ask us if you have any issues.
http://www.apache.org/licenses/#clas

You need to choose a preferred ASF user name and alternatives.
In order to ensure it is available you can view a list of taken ids at
http://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.

After that is done, please make followup replies to the juneau-dev list.
We generally discuss everything there and keep the
private@juneau.apache.org list for occasional matters which must be private.

The developer section of the website describes the roles and provides other
resources:
http://www.apache.org/foundation/how-it-works.html
http://www.apache.org/dev/

The incubator also has some useful information for new committers
in incubating projects:
http://incubator.apache.org/guides/committer.html
http://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

Yours,
The Apache Juneau PMC

Committer Account Creation

Follow the instructions here.

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, then the account creation request is made by the secretary or assistant who files the ICLA. Otherwise, the new account request should be made by the PMC Chair (or any ASF Member if the chair is unavailable).

The PMC chair needs to use the ASF New Account Request form to send a new account request. Members may use ASF New Account Request page for ASF members to use.  For elections held on public lists, please supply the mail-archives.apache.org url. For private lists, you can use the Mail Search tool to locate the appropriate url.

Committer Done 

After the committer account is established.

To: private@juneau.apache.org, janedoe@foo.net
Account request: Jane Doe

As you know, the ASF Infrastructure has set up your
committer account as the username '[janedoe]'.

Please follow the instructions to set up your SSH,
svn password, svn configuration, mail forwarding, etc.
http://www.apache.org/dev/#committers

Please subscribe to the Juneau Project Management
Committee mailing list private@juneau.apache.org.

You have commit access to specific sections of the
ASF repository, as follows:

Juneau has various resources at:
https://gitbox.apache.org/repos/asf/juneau.git
https://gitbox.apache.org/repos/asf/juneau-website.git

The general "committers" at:
https://svn.apache.org/repos/private/committers

If you have any questions during this phase, then please

see the following resources:

Apache developer's pages: http://www.apache.org/dev/
Naturally, if you don't understand anything be sure to ask us on the Juneau 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.


Committer Announce

This is the email to announce to juneau-dev once the account has been created.

To: dev@juneau.apache.org
New committer: Jane Doe

The Project Management Committee (PMC) for Apache Juneau
has invited [Jane Doe] to become a committer and we are pleased
to announce that he has 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.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

...