Confirm
1,111
edits
Changes
no edit summary
Setting up a development environment for Firefox Mobile is relatively easy. Just follow our [[Mobile/Fennec/Android|build instructions]] and you'll be ready to start hacking after a couple of hours—mostly waiting for everything to compile.
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.
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
=== Mentor Bugs ===
If you are looking for guidance, we have maintain a set of bugs that are marked with an assigned mentor (see "Whiteboard" field). The mentor will help you get the necessary information to understand the issue, point out relevant parts of the code to look at, etc. You can also browse these bugs on [http://www.joshmatthews.net/bugsahoy/?mobile=1 Bugs Ahoy!]
<bugzilla>
{
"product": "Firefox for Android",
"whiteboard": "mentor",
"resolution": "---",
"include_fields": "id, summary, whiteboard, assigned_to"
}
</bugzilla>
== Testing ==
