Confirmed users
92
edits
Contribute/Firefox: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Quick guide to contributing to Firefox) |
No edit summary |
||
| Line 1: | Line 1: | ||
Contributing to Mozilla Firefox | =Contributing to Mozilla Firefox= | ||
Step 0: Download and install the prerequisites | ==Step 0: Download and install the prerequisites== | ||
https://developer.mozilla.org/en-US/docs/Simple_Firefox_build | https://developer.mozilla.org/en-US/docs/Simple_Firefox_build | ||
Step 1: Download the code | ==Step 1: Download the code== | ||
1.1 Mozilla Firefox development uses Mercurial for code management. | ===1.1 Mozilla Firefox development uses Mercurial for code management.=== | ||
hg clone https://hg.mozilla.org/mozilla-central | hg clone https://hg.mozilla.org/mozilla-central | ||
| Line 13: | Line 13: | ||
This will create a folder called mozilla-central which holds all the necessary code to build firefox. | This will create a folder called mozilla-central which holds all the necessary code to build firefox. | ||
1.2 Create a config file | ===1.2 Create a config file=== | ||
cd /path/to/mozilla-central | cd /path/to/mozilla-central | ||
| Line 22: | Line 22: | ||
https://developer.mozilla.org/en/docs/Configuring_Build_Options | https://developer.mozilla.org/en/docs/Configuring_Build_Options | ||
1.3 Build the code | ===1.3 Build the code=== | ||
make -f client.mk build | make -f client.mk build | ||
| Line 30: | Line 30: | ||
./mach build | ./mach build | ||
1.4 Run Firefox | ===1.4 Run Firefox=== | ||
./obj-[...]/dist/bin/firefox | ./obj-[...]/dist/bin/firefox | ||
2. Create a Bugzilla account | ==2. Create a Bugzilla account== | ||
Go to https://bugzilla.mozilla.org/createaccount.cgi | Go to https://bugzilla.mozilla.org/createaccount.cgi | ||
Enter your email address. Confirm it, and login to bugzilla. | Enter your email address. Confirm it, and login to bugzilla. | ||
3. Search for bugs / File bugs | ==3. Search for bugs / File bugs== | ||
For first timers, the best bugs are fixing warnings. | For first timers, the best bugs are fixing warnings. | ||
| Line 46: | Line 46: | ||
If a bug doesn't exist, file one. | If a bug doesn't exist, file one. | ||
4. Fix the bug | ==4. Fix the bug== | ||
This might tricky, especially for newbies. | This might tricky, especially for newbies. | ||
| Line 52: | Line 52: | ||
The fastest way to get some information is to ask on the #developers channel on irc.mozilla.org | The fastest way to get some information is to ask on the #developers channel on irc.mozilla.org | ||
5. Post the patch on bugzilla | ==5. Post the patch on bugzilla== | ||
https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch | https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch | ||
6. Get feedback | ==6. Get feedback== | ||
Make sure you follow the Coding Style: | Make sure you follow the Coding Style: | ||
https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style | https://developer.mozilla.org/en-US/docs/Developer_Guide/Coding_Style | ||
7. Mark the bug with Checkin needed | ==7. Mark the bug with Checkin needed== | ||
The patch will be merged by someone else as soon as possible. | The patch will be merged by someone else as soon as possible. | ||