Confirm
394
edits
Changes
→Map Contribution Paths
Every new coding contributor should be pointed to the [https://developer.mozilla.org/En/Developer_Guide MDN developer guide]. A couple first goals should be to get familiar with Bugzilla and to build the source code.
* 0. [https://bugzilla.mozilla.org/createaccount.cgi Create Open a bugzilla new Bugzilla account].
* 1. Verify bugs that are already posted, post comments to indicate your findings.
* 9. Ticket Closed
You should also [https://wiki.mozilla.org/IRC join IRC] in the #developers and #introduction channels.
Once you are ready, [http://www.gerv.net/hacking/before-you-mail-gerv.html contact gerv for editbugs privileges]
Suggestion: In addition to just documenting these steps, look for a simple 5-minute task that someone can take to get started (for example, signing up for Bugzilla if they are interested in coding) and also figure out where in the process you can add a mentor to help people.
