Add-ons/Contribute/Code: Difference between revisions

m
overhaul
m (AmyT moved page Add-ons/Contribute/AMO/Code to Add-ons/Contribute/Code: add-on code contributions are not limited to AMO)
m (overhaul)
Line 1: Line 1:
Addons.mozilla.org, commonly known as "AMO," is Mozilla's official site for developers to list add-ons, and for users to discover them. We love contributions to the AMO codebase! Below is the 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.
We love code contributions to the add-ons ecosystem! Below you'll find ways to contribute code, and information on the onboarding process. Onboarding helps ensure you are getting the most out of your experience working with other staff and volunteer developers. Once you're familiar with the dev environments, please pick a "Good First Bug" to get started.


=Steps to Onboard=
=Step 1: Create some accounts=
 
==Step 1: Create some accounts==
Please create accounts on the following sites, if you haven't already:
Please create accounts on the following sites, if you haven't already:
*https://bugzilla.mozilla.org/
*https://bugzilla.mozilla.org/
**Be sure to set a [:nick] for your account, for example your IRC nick. 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]
**Be sure to set a [:nick] for your account, for example your IRC nick. Go to https://bugzilla.mozilla.org/userprefs.cgi?tab=account and in the "Your real name" field, add it next to your name. Example: Andreas Wagner [:theone]
*https://github.com
*https://github.com


==Step 2: Tell us a little about yourself==
=Step 2: Tell us a little about yourself=
Please fill out a [https://docs.google.com/a/mozilla.com/forms/d/1u5D7kVzuu7FMi7WKk6xL_4D8EX1MJN_CHh_5gjKEKLY/viewform 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.
Please fill out a [https://docs.google.com/a/mozilla.com/forms/d/1u5D7kVzuu7FMi7WKk6xL_4D8EX1MJN_CHh_5gjKEKLY/viewform 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==
=Step 3: Decide how you'd like to help=
[https://mozweb.readthedocs.org/en/latest/ Webdev Bootcamp]
 
==Improve add-ons in Firefox==
Add-ons make Firefox the most extensible browser available. Your contributions help support user freedom!
 
=====Develop Web Extensions APIs=====
[https://wiki.mozilla.org/WebExtensions WebExtensions] are becoming the standard for add-on development in Firefox. It seeks to unify the extension APIs and architecture with those of other browsers in the name of interoperability and modern architecture. We need your help extending the APIs to support the [https://wiki.mozilla.org/Add-ons/developer/communication needs] of add-on developers. You'll need to know some JavaScript.
 
#Familiarize yourself with the on-boarding materials: [http://areweeveryoneyet.org/onramp/desktop.html Onboard to Firefox codebase]
#Pick a [http://mzl.la/1I0i8my "Good First Bug"] to work on
#More [https://wiki.mozilla.org/WebExtensions/Hacking ways to hack]


==Step 4: Set up a development environment on your local machine==
=====Contribute to the Add-on Manager=====
Our [https://addons-server.readthedocs.org/en/latest/ 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 [https://discourse.mozilla-community.org/c/add-ons/contribute go here] for help. Or, jump into the #amo channel on irc.mozilla.org.
Description here.
#Familiarize yourself with the on-boarding materials: [http://areweeveryoneyet.org/onramp/desktop.html Onboard to Firefox codebase]
#Pick a [http://mzl.la/1JlF0hm "Good First Bug"] to work on


==Step 5: Select a "good first bug" to work on==
== Improve addons.mozilla.org (AMO) ==
Once your development environment is set up, pick a "goodfirstbug" to work on. Goodfirstbugs are mentored and they are a great way to get a feel for things.
[https://addons.mozilla.org addons.mozilla.org], commonly known as "AMO," is Mozilla's official site for developers to list add-ons, and for users to discover them.
*'''Goodfirstbugs''': https://waffle.io/mozilla/addons?label=good%20first%20bug
**Requirements: [https://wiki.mozilla.org/Add-ons/Contribute/AMO/Code Onboard to AMO]
**Skills needed for addons-server: Python, JavaScript
**Skill needed for addons-validator (linter): JavaScript
**Skill needed for command line tool (Web-Ext): JavaScript
*'''WebExtensions''': http://mzl.la/1I0i8my
**Requirements: [http://areweeveryoneyet.org/onramp/desktop.html Onboard to Firefox codebase]
**Skills needed: JavaScript
*'''Add-ons Manager''': http://mzl.la/1JlF0hm
**Requirements: [http://areweeveryoneyet.org/onramp/desktop.html Onboard to Firefox codebase]
**Skills needed: JavaScript
*'''SDK and JPM triage has been moved:''' https://wiki.mozilla.org/Add-ons/SDK#Monthly_community_meeting


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.
===== Contribute code to AMO =====
If you know JavaScript and/or Python, you can help make AMO better!
#Familiarize yourself with the on-boarding materials: [https://mozweb.readthedocs.org/en/latest/ Webdev Bootcamp]
#Set up a development environment on your local machine: Our [https://addons-server.readthedocs.org/en/latest/ 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 [https://discourse.mozilla-community.org/c/add-ons/contribute go here] for help. Or, jump into the #amo channel on irc.mozilla.org.
#Select a [https://waffle.io/mozilla/addons?label=good%20first%20bug "Good First Bug"] to work on. These bugs are mentored and they are a great way to get a feel for things.


=What's Next?=
=What's Next?=
Confirmed users
1,605

edits