Changes

Jump to: navigation, search

WebExtensions/Contribution Onramp

270 bytes added, 19:59, 10 September 2018
formatting changes
* To make sure your comment in Bugzilla is seen, please “needinfo” the bug’s mentor by checking the box that says “Needs more information from” and then selecting “mentor” from the drop down box.
== Introduction & Setting Up Developer Environment Getting Started == *If you haven’t done haven't already done so, create an account on https://bugzilla.mozilla.org. * Pick a bug you want to work on from the [https://mzl.la/2yq1XA8 good-first-bugs list]. * Comment on the bug that you would like to work on it and proceed to set up your developer environment.  == Setting Up Developer Environment == * Now, you need to set up your development environment by [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build building Firefox]. There are two ways to do this:
** [recommended] Build Firefox using [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds Firefox Artifact builds]. If the issue only requires changes to privileged JavaScript code, we recommend you use this method. Artifact builds saves time because it downloads a pre-built version of Firefox sources and applies your local changes on it, instead of rebuilding all of the C++ and Rust pieces from scratch.
** [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build Build Firefox from scratch]. Note: doing this can take some time. After the initial build, you can build Firefox using the “mach build” command.
1,698
edits

Navigation menu