Confirm
1,111
edits
Changes
→Hacking
Before starting to work on a bug, you should make sure you have your development environment set up. When you're ready to start hacking, it's a good idea to add a comment to the bug report letting the mentor know that you want to work on it. Ideally, the bug report should already have relevant source code links to help you get started. If you're unsure whether to take a certain bug or not, you can always [[#Communication|contact us]] for clarification. If the bug you're working on involves UI changes, request feedback from the UX team (see contact list [[#Communication|below]]) before landing.
=== Resources ===Here''Useful linkss a list of resources that you may find useful for hacking on Fennec. Feel free to add more if you find things are missing!* [http:''//mxr.mozilla.org/mozilla-central/ MXR]* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ Mercurial FAQ]* [Mobilehttps:/Fennec/Android|Build instructions]developer.mozilla.org/en-US/docs/Developer_Guide/mach mach] * [http://wwwblog.joshmatthewsmargaretleibovic.netcom/bugsahoypost/?mobile=1 List of mentor bugs36893756730/bugzilla-101 Bugzilla 101]
== Testing ==
