The page defines a rule-of-thumb guidance on when a contributor should be considered for committership in Ignite. It's not a strict rule to follow but rather a formal recommendation that really helps to exclude a lot of guesses and arguings in every case.
Once a contributor gets a green light for 1 and 2 (optionally, depends on the PMC consensus) his/her candidacy will be reviewed by PMC members:
- Code contribution (features, improvements, bug fixes and optimizations):
- 10 tasks of moderate complexity on average or
- 1 outstanding tasks such as a big feature or significant improvements.
- A candidate needs to have a good presence and visibility on the dev list. At least, he/she has to drive the topics related to his/her contributions.
- Community engagement (optional for the committership but essential for those candidates who want to get to the PMC):
- Active involvement in Ignite features and future discussions on the dev list. Can be checked with Nabble (http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=222)
- Ignite users support via the user list and Stackoverflow. Total number of messages sent to the user list can be checked via Nabble: http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=1269
- Presenting Ignite at various events (meetups, conferences, webinars).
- Blog posts about Ignite: https://ignite.apache.org/blogs.html
I would like to also mention http://community.apache.org/newcommitter.html guide here.
And more Apache links related to committership :
Discussion on community developers mailing list to find out opinions about committership for a developer is not visible on the mailing list:
And one more discussion about off-list development (large code drops) impact on a community: