Add-ons/Contribute/Code: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
Line 13: Line 13:


==Step 3: Familiarize yourself with the on-boarding materials==
==Step 3: Familiarize yourself with the on-boarding materials==
 
[http://mozweb.readthedocs.org/en/latest/ Webdev Bootcamp]
# [http://mozweb.readthedocs.org/en/latest/ Webdev Bootcamp]
# [https://docs.google.com/document/d/1EFE6beSAxcR5SHhx6nrNMjQiLBeIrohyEZD5B1FMsl8/edit GitHub Best Practices]
# [https://docs.google.com/document/d/1s5PuZB-YkK6iP-e3u_QrUzAQUQbsWpvVnuHudA9E6BA/edit Working with AMO developers]


==Step 4: Set up a development environment on your local machine==
==Step 4: Set up a development environment on your local machine==

Revision as of 15:23, 13 October 2015

We love contributions to the addons.mozilla.org (AMO) codebase! We have a formal onboarding process to ensure you are getting the most out of your experience, and to help you work well with other staff and volunteer developers.

Steps to Onboard

Step 1: Create some accounts

Please create accounts on the following sites, if you haven't already:

Step 2: Tell us a little about yourself

Please fill out a short survey so we can better connect you to the right opportunities. We may reach out to you if there is a particular project that fits your skills, but in the meantime please move on to step #3.

Step 3: Familiarize yourself with the on-boarding materials

Webdev Bootcamp

Step 4: Set up a development environment on your local machine

Our documentation provides step-by-step instructions on how to set up your local development environment. If you run into any issues or have questions, please go here for help. Or, jump into the #amo channel on irc.mozilla.org.

Step 5: Select a "good first bug" to work on

Once your development environment is set up, go to this link to see a list of bugs that are marked as good for first time contributors. Have a look at the "Assignee" field. If no one else is working on the bug, please leave a comment to let the mentor know you are going to work on it. If someone is working on it but there hasn't been activity for a while, feel free to ask permission by leaving a comment.

Alternatively, we may reach out to you to suggest a bug for you to work on, based on what you indicated in the contributor survey.

What's Next?

Get recognized

When your first pull request is merged, please report it here so we can properly celebrate your first contribution!

Pick another bug

Select another “good first bug” to get more practice, or move on to a “good second bug”!

Need guidance?

Please feel free to reach out to one of our community mentors! The two best ways to reach out are:

Volunteer code mentors

  • TBD