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:

  1. Code contribution (features, improvements, bug fixes and optimizations):
    1. 10 tasks of moderate complexity on average or
    2. 1 outstanding tasks such as a big feature or significant improvements.
    3. 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. 

  2. Community engagement (optional for the committership but essential for those candidates who want to get to the PMC):
    1. Active involvement in Ignite features and future discussions on the dev list. Can be checked with Nabble (
    2. Ignite users support via the user list and Stackoverflow. Total number of messages sent to the user list can be checked via Nabble:
    3. Presenting Ignite at various events (meetups, conferences, webinars).
    1. Blog posts about Ignite:



  • No labels


  1. I would like to also mention guide here.

    This guide

    • contains a number of additional criteria for new committer nomination
    • confirms most of the existing criteria is not Apache Ignite-specific, but Apache-specific.
    • confirms PMC may want to set up an additional committer guidelines