Add-ons/Contribute/Code: Difference between revisions

Add-ons/Contribute/Code (view source)

237 bytes added , 19 November 2015

m

Confirmed users

1,605

edits

@@ Line 19: / Line 19: @@
 ==Step 5: Select a "good first bug" to work on==
-Once your development 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. 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.
+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.
+*[http://mzl.la/1Vc7bUQ  Bugzilla Goodfirstbugs]
+**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 at least 14 days, feel free to ask permission by leaving a comment.
+*[https://waffle.io/mozilla/addons?label=good%20first%20bug Github Goodfirstbugs]
+**Skill needed for addons-validator: JavaScript
+**Skills needed for olympia: JavaScript, Python
 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.