Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In the interest of having a transparent and objective nomination process, the following criteria will be applied when evaluating new committer nominations. 

...

 1. History of sustained contributions to the project

A factor that will be considered is the duration for which the person is associated with the project. The association can either be in form of code contributions or participation in community discussions on technical topics or project governance. A minimum of 3 months is needed before someone can be nominated to become a committer. The evidence of sustained contributions should provide an assurance to the community that the nominee will continue the contributions even after becoming a committer.

...

2. Quality of contributions to the project

New committers should have a history of code contributions to MXNet in the form of accepted pull requests to master branch. The substance and value of pull requests will be considered when evaluating new committer nominations. The following are some examples of contributions that will make a strong case. Having one of the following is sufficient:

...

When it comes to code contributions, quality is more important than quantity. While all contributions are welcome and highly appreciated, certain guidelines will be applied when it comes to committer nominations, e.g. clean, documented and maintainable code, including unit tests if applicable. Updating license text or fixing indentation in hundreds of source files for instance is case of quantity trumping quality.

3. Community Involvement

Potential committers should have a record of participating in discussions related to MXNet code and features. They should have a history of providing constructive inputs on PRs and github issues. Answering user questions on forums such as stackoverflow, slack channel and apache dev@ list are also considered valuable contributions. Potential committers can demonstrate community involvement by having an additional responsibility to mentor new contributors and enhancing MXNet documentation related to APIs, architecture/design, etc.

...