This document provides:
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.
The general process is as follows:
If they accept, then do:
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.
To: private@juneau.apache.org I'd like to discuss adding Jane Doe as a PMC member. State reason why. |
If there is consensus that the proposed member is suitable, then there should be a formal vote in the PMC private alias:
To: private@juneau.apache.org I'm pleased to be calling this vote for inviting [Jane Doe] to be a member of the Juneau PMC. State reason why. |
If the vote is successful, the proposer should send a message to the PMC private alias.
To: private@juneau.apache.org Voting for PMC membership for [Jane Doe] is now closed. The vote has passed with the following tally: John Smith, PMC, +1 |
Adding a new PMC member requires sending an email notification to the Board's mailing list copying 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 Juneau proposes to invite [Jane Doe](janedoe) to join the PMC. (include if a vote was held) |
It should noted that there is a grace period of 72 hours from when the above NOTICE is sent to the board 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 embarrassing situation for people involved.
After 72 hours, Jane Doe should be invited to join the PMC. Check to see if the proposed committer already has an Apache id.
Sample message for proposed committers without an Apache id:
To: janedoe@gmail.com 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 if you do not have an Apache id. If you have an Apache id, let the PMC know by return email what your id is. 1. If you do not have an Apache id, details of the iCLA and the forms are found here: 2. Instructions for its completion and return to the Secretary of the ASF are found here: 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. |
Sample message for existing Apache committers:
To: janedoe@apache.org 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. 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. |
To: janedoe@gmail.com Welcome. Here are the next steps. After that we will make an announcement to the juneau-dev list. You need to have an Apache id. If you do not already have one, you will need to send an individual Contributor License Agreement to the ASF. If you also make contributions done in work time or using work resources then consult with your company to see if they want to file a corporate CLA. Ask us (the PMC) if you have any questions. 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 iCLA 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 iCLA has been recorded. After that is done, please make followup replies to the dev@juneau.apache.org list. We generally discuss everything there and keep the private@juneau.apache.org list for occasional matters which must be private. Most important links for developers can be found here: http://juneau.apache.org/index.html#community.html The developer section of the Apache website describes the roles and provides otherresources: http://www.apache.org/foundation/how-it-works.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 Best regards, |
For new Apache committers:
Request new account for new committer:
https://whimsy.apache.org/officers/acreq
Follow the instructions here.
For new and existing Apache committers:
After the committer account is established, send the following message:
Message for new Apache committers:
To: private@juneau.apache.org, janedoe@foo.net 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. Please subscribe to the Juneau Project Management Committee mailing list You have commit access to specific sections of the ASF repository, as follows: If you haven't done so already, you'll need to use the GitBox Account Linking Utility to get write access to these repositories. The general "committers" at: If you have any questions during this phase, then please see the following resources: 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. |
Message for existing Apache committers:
To: private@juneau.apache.org, janedoe@apache.org Welcome to Apache Juneau! 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: The general "committers" at: If you have any questions during this phase, then please see the following resources: 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. |
This is the email to announce to juneau-dev once the account has been created.
To: dev@juneau.apache.org The Project Management Committee (PMC) for Apache Juneau has invited [Jane Doe] to become a PMC member 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. |