Becoming a committer

Apache HAWQ committers are those who have the right to directly commit changes to HAWQ git repositories.

To become a committer, there are no hard and fast rules, but here are a few things that typically would prompt considering somebody a candidate for a committer

• Code contributions (patches submitted to JIRA or PRs) committed 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

The process

After someone has successfully contributed a few non-trivial contributions, a committer proposes him as a committer. 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. Usually it is the committer who has reviewed and applied the most patches from that contributor starts the proposal. The proposal should at least include the contributions the committer has made. And the proposal is sent only to the list of committers, which ensures that discussion is private and everyone can feel comfortable speaking their minds. The decision is made by consensus.