Committership Bar Guidance

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 for either 2 or 3 his 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-2 outstanding tasks such as a big feature or significant improvements.
2. Community engagement:
   1. Active involvement in Ignite features and future discussions on the dev list. 20 comments/suggestions/proposals have to be left on average. Can be checked with Nabble (http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=user_nodes&user=222)
   2. Ignite users support via the user list and Stackoverflow. Assistance should be provided for 10 users inquiries on average. A 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
3. or Evangelism:
   1. Bragging about Ignite at various events (meetups, conferences, webinars). At least 1 event is needed to cross out this requirement.
   2. Blog posts about Ignite. At least 3 are required and they will be listed here: https://ignite.apache.org/blogs.html