This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Skip to end of metadata
Go to start of metadata

Steps and Criteria

To become a committer, there are no hard and fast rules, but here are a few considerations that influence the process.

  • Code contributions by the contributor (patches submitted to JIRA or PRs) merged by existing committers. 
  • Participation in the mailing list conversations
  • Documentation contributions
  • Wiki/social media contributions
  • Review of patches submitted by others
  • Reviews of release candidates
  • Bug reports
  • Work with peers collaboratively and potentially as a mentor to new contributors

It is not necessary for a committer to be an expert on all the areas of the system. Contributors that have contributed a lot to one area are welcomed as a committer.

  1. Participate and contribute via project's mailing lists, JIRA, wiki, documentation, sending patches and pull requests, and just generally evangelizing about the technology to the greater community.
  2. Contributors are nominated by a current Committer to be granted commit privileges by the Apache HAWQ PMC.
  3. Committers should nominate fellow contributors when a candidate has shown a consistent history of participating in the development process or community, and has demonstrated that they understand and follow the development process and community standards of the Apache HAWQ project.
  4. The members on the PMC will consider both the history and quality of the contributors' participation, and vote whether to grant commit privileges to the candidate, or provide feedback and mentoring to the candidate to help further groom them to become a Committer in the future.
  5. Contributors who have shown a consistent history of participating in the development process or community, and have demonstrated that they understand and follow the development process and community standards of the Apache HAWQ, and who show promise for future contributions should generally be accepted by the PMC as a new Committer.
  6. Newly voted Committers must download and print the Apache Contributor License Agreement (ICLA) from here. (For a company that will assign employees to work with Apache projects, please check the Corporate CLA)
  7. Sign and scan the ICLA and send to secretary@apache.org.
  8. Wait for your name to appear in the list of received CLA's.
  9. Once your account is provisioned you shall receive an e-mail from root@apache.org with details.
  10. Login at https://id.apache.org to test your account and update your profile if needed.

Nominating a Committer

The section is a quick guide through the process nominating committers for the Apache HAWQ project. For more in depth details please refer to the pmc guide. Any member of the PMC for Apache HAWQ can nominate someone to be a Apache HAWQ committer.

1. Send a VOTE email to private@hawq.apache.org with at least 72 hours of voting time indicating you would like to propose a new committer. The vote passes if there are at least 3 +1s and no -1 of any PMC members. Mentors votes are not required. Do separate vote for Committer and PMC membership. Example:

[VOTE] New committer: Sam Lee
to: private@hawq.apache.org

This is a VOTE email for promoting candidate Sam Lee (with github id sam_lee) from contributor to committer, who has been contributing to Apache HAWQ in last 6 months (from Apr. to Oct. 2016). Please give +1, 0 or -1 with reasons in this email thread.

His contribution includes (but not limited to):
List contributions to code base, documentation, code review, discussion in mailing list, JIRA, etc.

Voting ends one week from today, i.e., 12:00 AM UTC on 2016-10-23 or whenever we got enough votes from PPMC members.
[   ] +1 Approve
[   ] +0 No opinion
[   ] -1 Disapprove (and reason why)


2. Send the [VOTE][RESULT] email to private@hawq.apache.org. Example:

[RESULT][VOTE] New committer: Sam Lee
to: private@hawq.apache.org

This is the email ends the VOTE and reports the result to the project PPMC:

The VOTE has now closed. The results are:

+1: 13
 0: None
-1: None

The vote is ***successful***

I'll move forward to send him an invitation letter.
Thanks all for providing your opinions.
3. Invite the person to be a committer and get them to file an ICLA. CC the private@hawq.apache.org with the invitation. Example:
Invitation to become Apache HAWQ committer: Sam Lee
to: Sam Lee <sam_lee@email.com>
cc: private@hawq.apache.org

Hello Sam Lee,
The HAWQ 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 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@hawq.apache.org address only.
B. If you are accepting, the next step is to register an iCLA with the Apache Software Foundation:
Details of the iCLA and the forms are found through this link: <http://www.apache.org/licenses/#clas>.
The form (text or PDF version) provides instructions for its completion and return to the Secretary of the ASF.
When you transmit the completed iCLA, request to notify Apache HAWQ 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 committer.

4. Once the ICLA is filed, the PMC Chair will follow through with creating the account.

5. Send notice to dev@hawq.apache.org. Example:

new committer: Sam Lee
to: dev@hawq.apache.org

The Project Management Committee (PMC) for Apache HAWQ has invited Sam Lee to become a committer and we are pleased to announce that he has accepted.
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.
Please join us in congratulating him and we are looking forward to collaborating with him in the open source community.
His contribution includes (but not limited to):
List contributions to code base, documentation, code review, discussion in mailing list, JIRA, etc.


Nominating a PMC

The section is a quick guide through the process nominating PMC for the Apache HAWQ project. For more in depth details please refer to the pmc guide. Any member of the PMC for Apache HAWQ can nominate someone to be a Apache HAWQ PMC.

1. Send a DISCUSS email to private@hawq.apache.org indicating you would like to propose a new PMC. Example:

[DISCUSS] Sam Lee Apache HAWQ PPMC membership
to: private@hawq.apache.org

I would like to propose adding Sam Lee to PPMC.

He has been making significant contributions to all components of HAWQ including but not limited to QE, QP, External tables functionality etc.
The number of resolved JIRAs so far - 66, list - https://issues.apache.org/jira/browse/HAWQ-1361?jql=assignee%20in%20(%22Sam%20Lee%22)

Also, Sam Lee has been very engaged in HAWQ's graduation, so he definitely should be very valuable PPMC member.

Any thoughts?
2. If the DISCUSS email does not raise any objections after a couple of days, send a VOTE email to private@hawq.apache.org with at least 72 hours of voting time indicating you would like to propose a new PMC. The vote passes if there are at least 3 +1s and no -1 of any PMC members. Mentors votes are not required. Do separate vote for Committer and PMC membership. Example:

 

[VOTE] Sam Lee Apache HAWQ PPMC membership
to: private@hawq.apache.org

As a followup to a discuss thread, I would like to start voting thread for adding Sam Lee to PPMC.
JIRAs resolved by Sam Lee - https://issues.apache.org/jira/browse/HAWQ-1361?jql=assignee%20in%20(%22Sam%20Lee%22).

This vote will be open for the next 72 hours.

3. Send the [VOTE][RESULT] email to private@hawq.apache.org. Example:

[RESULT][VOTE] Sam Lee Apache HAWQ PPMC membership
to: private@hawq.apache.org

This is the email ends the VOTE and reports the result to the project PPMC:

The VOTE has now closed. The results are:

+1: 13
 0: None
-1: None

The vote is ***successful***

I'll move forward to send him an invitation letter.
Thanks all for providing your opinions.
4. Send invitation email to new PMC and CC private@hawq.apache.org. Example:

 

Invitation to join the HAWQ PPMC
to: Sam Lee <sam_lee@email.com>
cc: private@hawq.apache.org


Dear Sam Lee,

In recognition of your demonstrated commitment to, and alignment with, the
goals of the Apache HAWQ project, the HAWQ PPMC has voted to offer you
membership in the HAWQ PPMC ("Podling Project Management Committee").

Please let us know if you accept by subscribing to the private alias [by
sending mail to private-subscribe@hawq.apache.org], and posting 
a message to private@hawq.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 HAWQ 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 HAWQ PPMC
5. The new PMC accept or reject the membership.
  • No labels