Confirm
1,605
edits
Changes
amo codebase
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:
*https://bugzilla.mozilla.org/
**Be sure to set a [:nick] for your account. Go to https://bugzilla.mozilla.org/userprefs.cgi?tab=account and in the "Your real name" field, add it next to your name. Example: Amy Tsay [:amyt]
*http://github.com
==Step 2: Tell us a little about yourself==
Please fill out a short survey (TBD) so we can better connect you to the right opportunities.
==Step 3: Familiarize yourself with the on-boarding materials==
# Setting up the frontend development environment: http://olympia.readthedocs.org/en/latest/
# Working with Marketplace code: (TBD - Notes: https://etherpad.mozilla.org/how-to-work-with-mp-code)
# Working with Marketplace developers: (TBD - Notes: https://etherpad.mozilla.org/how-to-work-with-mp-devs)
# Coding styleguide: http://olympia.readthedocs.org/en/latest/topics/hacking/style.html
# Review checklist--pass your code review: https://developer.mozilla.org/docs/Mozilla/Developer_guide/Reviewer_Checklist
==Step 4: Set up a development environment on your local machine==
If you run into any issues or have questions, please go here for help: https://discourse.mozilla-community.org/c/add-ons/contribute. Or, jump into the #Addons channel on irc.mozilla.org.
==Step 5: Select a "goodfirstbug" to work on==
Once your dev environment is set up, go to [http://mzl.la/1Vc7bUQ this link] to see a list of bugs that are marked as good for first time contributors. 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! https://wiki.mozilla.org/Add-ons/Contribute/Recognition
==Pick another bug==
Select another “goodfirstbug” to get more practice, or move on to a “goodsecondbug”!
==Need guidance?==
Please feel free to reach out to one of our community mentors! The two best ways to reach out are:
* irc.mozilla.com - #amo channel; mentors are given "voice" in the #marketplace channel, so should float to the top in most clients
* Code contributor forum: https://discourse.mozilla-community.org/c/add-ons/contribute
Volunteer code mentors
*TBD
=Steps to Onboard=
==Step 1: Create some accounts==
Please create accounts on the following sites, if you haven't already:
*https://bugzilla.mozilla.org/
**Be sure to set a [:nick] for your account. Go to https://bugzilla.mozilla.org/userprefs.cgi?tab=account and in the "Your real name" field, add it next to your name. Example: Amy Tsay [:amyt]
*http://github.com
==Step 2: Tell us a little about yourself==
Please fill out a short survey (TBD) so we can better connect you to the right opportunities.
==Step 3: Familiarize yourself with the on-boarding materials==
# Setting up the frontend development environment: http://olympia.readthedocs.org/en/latest/
# Working with Marketplace code: (TBD - Notes: https://etherpad.mozilla.org/how-to-work-with-mp-code)
# Working with Marketplace developers: (TBD - Notes: https://etherpad.mozilla.org/how-to-work-with-mp-devs)
# Coding styleguide: http://olympia.readthedocs.org/en/latest/topics/hacking/style.html
# Review checklist--pass your code review: https://developer.mozilla.org/docs/Mozilla/Developer_guide/Reviewer_Checklist
==Step 4: Set up a development environment on your local machine==
If you run into any issues or have questions, please go here for help: https://discourse.mozilla-community.org/c/add-ons/contribute. Or, jump into the #Addons channel on irc.mozilla.org.
==Step 5: Select a "goodfirstbug" to work on==
Once your dev environment is set up, go to [http://mzl.la/1Vc7bUQ this link] to see a list of bugs that are marked as good for first time contributors. 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! https://wiki.mozilla.org/Add-ons/Contribute/Recognition
==Pick another bug==
Select another “goodfirstbug” to get more practice, or move on to a “goodsecondbug”!
==Need guidance?==
Please feel free to reach out to one of our community mentors! The two best ways to reach out are:
* irc.mozilla.com - #amo channel; mentors are given "voice" in the #marketplace channel, so should float to the top in most clients
* Code contributor forum: https://discourse.mozilla-community.org/c/add-ons/contribute
Volunteer code mentors
*TBD
