Differences between revisions 3 and 4
Revision 3 as of 2012-03-23 19:50:50
Size: 402
Editor: brianleroux
Comment:
Revision 4 as of 2012-07-16 18:53:55
Size: 1339
Editor: FilMaj
Comment: Working out the committer guidelines based on mailing list thread
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 * [[http://incubator.apache.org/cordova/|Read up on how to contribute.]] You can't become a committer with having contributed code!
 * Send a message to the Cordova mailing list asking to become a committer once you have successfully contributed.
 * The community will vote on making you a committer in the private list.
 * If no -1 votes come up you will be notified!
 * Sign up for the Cordova dev mailing list. See http://cordova.io.
 * Sign up for the Cordova issue tracker (JIRA). See http://issues.cordova.io.
 * Become active on the mailing list! It's important to keep up-to-date on the latest issues the developer community is dealing with.
 * Ask on the mailing list (optionally check out the issue tracker) about where you can help out. Some of the most appreciated contributions include:
  * Documentation. Under the issue tracker, do a search for issues and filter by Component: Docs. These are usually simple, text-editing issues that are a good introduction to the project!
  * Tests. There is a mobile-spec repository (Component: Mobile-spec under the issue tracker) containing the HTML5-based tests for the Cordova API.
  * Code. Each platform is filed as a Component in the issue tracker. If you have a platform preference, have a look at the outstanding issues for that platform.
 * Send a message to the Cordova mailing list asking to become a committer once you have successfully contributed code and it has been merged in.
 * The committers will start a private vote thread discussing and voting on your potential committership, based on these guidelines and any other concerns the committers have.
 * If no -1 votes come up, you will be notified!

Becoming A Committer

  • Sign up for the Cordova dev mailing list. See http://cordova.io.

  • Sign up for the Cordova issue tracker (JIRA). See http://issues.cordova.io.

  • Become active on the mailing list! It's important to keep up-to-date on the latest issues the developer community is dealing with.
  • Ask on the mailing list (optionally check out the issue tracker) about where you can help out. Some of the most appreciated contributions include:
    • Documentation. Under the issue tracker, do a search for issues and filter by Component: Docs. These are usually simple, text-editing issues that are a good introduction to the project!
    • Tests. There is a mobile-spec repository (Component: Mobile-spec under the issue tracker) containing the HTML5-based tests for the Cordova API.
    • Code. Each platform is filed as a Component in the issue tracker. If you have a platform preference, have a look at the outstanding issues for that platform.
  • Send a message to the Cordova mailing list asking to become a committer once you have successfully contributed code and it has been merged in.
  • The committers will start a private vote thread discussing and voting on your potential committership, based on these guidelines and any other concerns the committers have.
  • If no -1 votes come up, you will be notified!