Adding a committer while incubating:
Read Committer Criteria to see if the person you are proposing meets all of the criteria.
Send an email to private@impala.apache.org to discuss adding this committer.
Evaluate the discussion. If you decide to propose them, send an email to private@impala.apache.org with the subject "[VOTE] New committer: $NAME", making sure to substitute $NAME, $FIRSTNAME, $LASTNAME, $DURATION, $JIRANAME, $EMAIL_ADDR, $PRAISE, and $PROPOSER_TIMEZONE
$NAME has been actively contributing to Impala for $DURATION.
Their commits: https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=search;s=$FIRSTNAME+$LASTNAME;st=author
The bugs they filed: https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20reporter%20in%20($JIRANAME)
The code reviews for the patches they sent: https://gerrit.cloudera.org/#/q/owner:%22$FIRSTNAME+$LASTNAME%22
See also these code reviews by them: https://gerrit.cloudera.org/#/q/reviewer:%22$FIRSTNAME+$LASTNAME%22
Discussions on dev@: https://lists.apache.org/list.html?dev@impala.apache.org:lte=100M:$EMAIL_ADDR
$PRAISE
Voting ends in 72 hours, not counting weekends $PROPOSER_TIMEZONE, following https://impala.apache.org/bylaws.html
See voting guidelines at https://community.apache.org/newcommitter.htmlThe vote is successful if there are three +1 votes and no -1 votes.
Send the following email to private@apache.impala.org when the vote has ended, which is 72 hours from when it started, not counting weekends in the timezone of the proposer.
The vote has now closed. The results are:
Binding Votes:
+1: $PLUS_NUMBER
0: $ZERO_NUMBER
-1: $MINUS_NUMBER
The vote is ***[not] successful***
I will now follow https://community.apache.org/newcommitter.html to invite $NAME and get them set up with infra, should they accept.Send the following email to private@apache.impala.org and the contributor:
Hello $FIRSTNAME,
The Impala 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.
Being a committer enables you to +2 patches.
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@impala.incubator.apache.orgaddress only.
B. If you are accepting, the next step is to register an iCLA with the Apache Software Foundation:B.1. Details of the iCLA and the forms are found through this link: <http://www.apache.org/licenses/#clas>.
B.2. The form (text or PDF version) provides instructions for its completion and return to the Secretary of the ASF.
B.3. When you transmit the completed iCLA, request to notify Apache Impala 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 PPMC 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.
The process will follow the process described at <http://incubator.apache.org/guides/ppmc.html> and <https://community.apache.org/newcommitter.html>.Wait for the contributor to accept.
Send the following email to the user and private@impala.apache.org:
Welcome. Here are the next steps. After that we will make an announcement to the Impala-dev list.
You need to send a Contributor License Agreement to the ASF. Send an Individual 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 Impala-dev list. We generally discuss everything there and keep the private@impala.incubator.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
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 Impala PPMCWait to receive notice that their iCLA is on file from secretary@apache.org.
Ask the new committer to select a username that doesn't collide with any existing Apache username.
Email the project mentors to ask them to request the user account at https://id.apache.org/acreq/members/. Include the username the user has selected. cc private@impala.apache.org and the user.
Check that the username has been created by checking https://whimsy.apache.org/roster/committer/$USERNAME
Send this email to dev@impala.apache.org:
The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited $NAME to become a committer and we are pleased to announce that they have accepted.
Congratulations and welcome, $FIRST_NAME!Send the following email to the new committer and private@impala.apache.org:
$FIRST_NAME, as you know, the ASF Infrastructure has set up your committer account as the username "$USERNAME".
Please follow the instructions to set up your SSH, svn password, svn configuration, mail forwarding, etc.
http://www.apache.org/dev/#committers
If you have any questions during this phase, then please see the following resources:
Apache developer's pages: http://www.apache.org/dev/
Incubator committer guide: http://incubator.apache.org/guides/committer.html
Naturally, if you don't understand anything be sure to ask us on the Impala 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.- Add the person to the committers list in gerrit in People > List Groups > Apache Impala Committers.
- Add the person to the committers list on http://incubator.apache.org/projects/impala.html following the directions on http://incubator.apache.org/guides/website.html
- Set the new committer up with an account with "committer" privilege group on http://jenkins.impala.io:8080/.
- Add the person as a committer (but not a PPMC member) on https://whimsy.apache.org/roster/ppmc/impala by scrolling to the end of the committers list (or PPMC list, if there are no non-PPMC committers at the time) and clicking the big plus sign. The interface is unpleasant and may redirect you to that person's name when you mean to add them as a committer. Press back and then try again.
- Writing the wiki is restricted in order to prevent spam. Non-committers may have write access by just asking for it. If the new committer doesn't already have write access:
- Ask them to create an account and email you the username.
- On the wiki, in the lower left-hand corner, Space tools > Permissions > Individual Users > Edit Permissions
- Add the username with all permissions
Adding a PPMC member while incubating:
The following instructions assume the person is already a committer.
Send an email to private@impala.apache.org to discuss adding this person to the PPMC. The subject line should be "[DISCUSS] $FIRSTNAME $LASTNAME PPMC membership".
Evaluate the discussion. If you decide to propose them, send an email to private@impala.apache.org with the subject "[VOTE] $FIRSTNAME $LASTNAME PPMC membership", making sure to substitute $FIRSTNAME, $LASTNAME, $DURATION, $JIRANAME, $EMAIL_ADDR, $PRAISE, and $PROPOSER_TIMEZONE
$FIRSTNAME $LASTNAME has been actively contributing to Impala for $DURATION.
Their commits: https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=search;s=$FIRSTNAME+$LASTNAME;st=author
The bugs they filed: https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20reporter%20in%20($JIRANAME)
The code reviews for the patches they sent: https://gerrit.cloudera.org/#/q/owner:%22$FIRSTNAME+$LASTNAME%22
See also these code reviews by them: https://gerrit.cloudera.org/#/q/reviewer:%22$FIRSTNAME+$LASTNAME%22
Discussions on dev@: https://lists.apache.org/list.html?dev@impala.apache.org:lte=100M:$EMAIL_ADDR
$PRAISE
Voting ends in 72 hours, not counting weekends $PROPOSER_TIMEZONE, following https://impala.apache.org/bylaws.htmlThe vote is successful if there are three +1 votes and no -1 votes.
Send the following email to private@apache.impala.org when the vote has ended, which is 72 hours from when it started, not counting weekends in the timezone of the proposer. The subject line should be "[VOTE][RESULT] $FIRSTNAME $LASTNAME PPMC membership"
The vote has now closed. The results are:
Binding Votes:
+1: $PLUS_NUMBER
0: $ZERO_NUMBER
-1: $MINUS_NUMBER
The vote is ***[not] successful***
[I will now follow the next step, following http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+PPMC+member -- notifying the Incubator PMC of our intent to invite this new PPMC member, which gives the IPMC 72 hours to put a hold on the invitation. If they do not put a hold on it, I will formally invite them.]Find on https://lists.apache.org/list.html?private@impala.apache.org the vote thread and copy the "Permalink". It may take a few hours for the email to show up there. Email private@incubator.apache.org and private@impala.apache.org with the subject line "New member of Impala PPMC $FIRSTNAME $LASTNAME"
$FIRSTNAME $LASTNAME has been voted as a new member of the Impala PPMC.
the vote thread is at: $PERMALINK
Following http://incubator.apache.org/guides/ppmc.html#Voting+in+a+new+PPMC+member, I will wait 72 hours from now before sending them an invite.
Wait 72 hours. Follow the remaining directions only if there was no objection from the IPMC. If there was an objection, follow their directions.
Send the following email to private@apache.impala.org and the contributor:
Dear $FIRSTNAME $LASTNAME,
In recognition of your demonstrated commitment to, and alignment with, the
goals of the Apache Impala project, the Impala PPMC has voted to offer you
membership in the Impala PPMC ("Podling Project Management Committee").Please let us know if you accept by subscribing to the private alias [by
sending mail to private-subscribe@impala.incubator.apache.org], and posting
a message to private@impala.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 Impala 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. 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. 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 Impala PPMC
Wait for the person to accept.
Send this email to dev@impala.apache.org:
The Podling Project Management Committee (PPMC) for Apache Impala (incubating) has invited $FIRSTNAME $LASTNAME to become a PPMC member and we are pleased to announce that they have accepted.
Congratulations and welcome, $FIRSTNAME!Move the person from the committers list to the PPMC list on http://incubator.apache.org/projects/impala.html following the directions on http://incubator.apache.org/guides/website.html
- Make the person a PPMC member on https://whimsy.apache.org/roster/ppmc/impala