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!

Voting In a New Committer

• In general, Cordova follows community.apache.org's New Committer guidelines. This document covers the details of starting voting threads, making account creation requests, and all that fun stuff.

• If the vote passes and the new committer accepts, some Cordova-specific tasks are in order:

  • Add the committer to the Who's who wiki article.

  • If applicable, the committer should edit the Contributor Device List to reflect any mobile devices he or she has.

  • The committer should be added to the PMC list on JIRA.