Confirm
251
edits
Changes
→Hacking
If you are already familiar with Mozilla development and want to help work on mobile bugs, see the [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3Aandroid%20blocking-fennec%3A%2B%20%40nobody&list_id=6141094 list of "tracking-fennec" bugs] for high-priority bugs. Or browse through any of our open bugs!
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.
''Useful links:''
