Changes

Jump to: navigation, search

Mobile/Get Involved

1,140 bytes removed, 17:48, 1 August 2017
no edit summary
This page is the place to learn how to start contributing to Mobile Firefox. The current products on mobile are Firefox and Focus, on both Android and iOS.
Firefox and Focus are developed by the Mozilla community. We're currently focused on making Firefox rock on Android and iOS phones and tablets. We hope this page will help you become an active member of our community! If you're looking for other ways to contribute to Mozilla, have a look at Mozilla's [http://www.mozilla.org/contribute/ global page] for new contributors. Either way, you should also take a look at the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines].
If you still feel that you don't know where to start after reading this page, feel free to [[#Communication|ping us]] on IRC, we can probably give you some ideas. We're always looking for ways to improve this page to make it easier to start contributing. Suggestions and general feedback are more than welcome.
== Hacking ==
Setting up a development environment for Mobile Firefox is relatively easy! All the projects have repos and either a setup script, or a READMEcan built in an IDE.
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.
=== Firefox for iOS Focus ===For Firefox Focus for iOS, you should follow the instructions in the [https://github.com/mozilla-mobile/firefoxfocus-ios Firefox Focus for iOS github repo]. We also have a list of [https://github.com/mozilla-mobile/focus-ios/labels/good%20first%20bug good first bugs].
=== For Focus for iOS ===For Firefox for iOSAndroid, you should have Android Studio installed and you can follow the instructions in the [https://github.com/mozilla-mobile/focus-ios android Focus for iOS Android github repo]. You can find a list of [https://github.com/mozilla-mobile/focus-android/labels/good%20first%20bug good first bugs here].
=== Firefox for Android ===For Firefox for iOS, you should follow the instructions in the [https://github.com/mozilla/firefox-ios Firefox for iOS github repo].
Just For Firefox for Android, follow our [https://developer.mozilla.org/en-US/docs/Simple_Firefox_for_Android_build build instructions] and you'll be ready to start hacking after a couple of hours—mostly waiting for everything to compile. Unfortunately, Firefox for Android is more complicated than a basic Android app, so we recommend that you're comfortable using a command line before getting started.
While you're waiting for your build, you can also take a look at our [[Mobile/Fennec/Android/Suggested workflow|suggested workflow]] page.
=== Focus for Android ===For Firefox for iOS, you should follow the instructions in the [https://github.com/mozilla-mobile/focus-android Focus for Android github repo].  Resources === Resources ===Here's a list of resources that you may find useful for hacking on FennecFirefox for Android. Feel free to add more if you find things are missing!* [[Mobile/Fennec/Android#Coding_Style|Coding style]]
* [https://dxr.mozilla.org/mozilla-central DXR for source browsing]
* [https://developer.mozilla.org/en-US/docs/Mercurial_FAQ Mercurial FAQ]or [http://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/index.html Mercurial for Mozillians] for a more detailed version* [https://developer.mozilla.org/en-US/docs/Developer_Guide/mach mach], a tool for building from commandline
* [http://blog.margaretleibovic.com/post/36893756730/bugzilla-101 Bugzilla 101]
* [http://www.mozilla.org/hacking/commit-access-policy/ Commit access policy]
* [http://mozillians.org Mozillians Directory]
* [https://wiki.mozilla.org/ReleaseEngineering/TryServer Try Server]
 
==== Videos ====
* [https://air.mozilla.org/mozilla-engineering-culture/ Mozilla Engineering Culture]
=== Mentor Bugs ===
If you are looking for a bug with guidance, we maintain a set of introductory bugs to help get you started! We have a tag called "good first bug" that are accessible for new contributors and will help you get familiar with the code review and landing process.
 
[https://github.com/mozilla-mobile/focus-ios/labels/good%20first%20bug Focus for iOS]
[https://github.com/mozilla-mobile/focus-android/labels/good%20first%20bug Focus for Android]
==== Firefox for Android ====
*[https://bugzilla.mozilla.org/buglist.cgi?list_id=11922249&o1=substring&v1=%5bgood%20next%20bug%5d&f1=status_whiteboard&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Android%20Background%20Services&product=Firefox%20for%20Android [good next bug]]
You can browse these bugs on [http://www.joshmatthews.net/bugsahoy/?mobileandroid=1 Bugs Ahoy!], but here's a list of unassigned mentor bugs to get you started: <bugzilla> { "product": "Firefox for Android", "f1": "bug_mentor", "o1": "isnotempty", "resolution": "---", "include_fields": "id, summary, whiteboard", "assigned_to": "nobody@mozilla.org" }</bugzilla>
== Testing ==
If you want to help us find issues on the latest Fennec releases, join the [https://wiki.mozilla.org/QA/Fennec Mobile QA team] and participate in the breadth of areas that are offered. We're always looking for assorted Android Device coverage and a breadth of website compatibility testing.
Start by filing [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox+for+Android Firefox for Android Issues] , Github issues for Focus and Firefox iOS, or converse directly with us on [[#Communication|IRC]] about the bugs you find. Or watch the [https://quality.mozilla.org/category/events/month Events calendar] for upcoming Mobile Testdays on focused topics! Testdays are an interactive opportunity to participate in real time with other community testers on testing and debugging.
Finally, subscribe to our [https://mail.mozilla.org/listinfo/android-mobile-nightly-testers bi-monthly newsletter] on the latest and greatest in Fennec features!
''Useful links:''
* [https://developer.mozilla.org/en/bug_writing_guidelines Bug Writing Guidelines]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox+for+Android Report a Firefox for Android Bug]
* [https://quality.mozilla.org/category/events/month QA Events Calendar]
== Support ==
=== IRC ===
To keep in touch with the Mobile team on a daily basis, you should hang out on the ''#mobile'' channel at irc://irc.mozilla.org/mobile, or ''#focus'' at irc://irc.mozilla.org/focus. We're always there, in different timezones. You can read the [http://wiki.mozilla.org/IRC general Mozilla IRC wiki page] for more details about joining IRC.
''#mobile'' tries and ''#focus'' try to be new -contributor friendly. We love it when new folks want to get involved. It's totally reasonable to just sign-on, introduce yourself, and listen to the chatter. And always ask your questions! But be patient: folks are busy and you might need repeat your question, or come online at different times of day, to get feedback.
If you want to talk to people from specific areas or have any questions, here are a few people you can ping:
* '''Android front-end:''' liuche, mcomella, sebastian, liuche, grisha, nalexander, rnewman* '''iOS:''' st3fan, jhugman, bkmunar, farhan, justindarc, rnewman
* '''Android platform:'''esawin, gcp, jchen, kats, rbarker, snorp, droeh
* '''QA:''' AaronMT, kbrosnan, njpark* '''Design:''' antlam, tecgirl, tif
* '''Marketing:''' mhan
* '''Support:''' rolandtanglao, rrayborn
You should also be able to find us in the [https://mozillians.org/en-US/group/mobile/ mobile Mozillians group].
== Glossary ==
*[good first bug] - a whiteboard comment that means this bug is a great one to start with. These bugs are ready for you to work on as soon as you have a development environment configured. Good first bugs should be small and include detailed instructions explaining what needs to be done.
 
*[good second bug] - a whiteboard comment that means this is a great bug to follow your first bug with. These bugs are ready for you to work once you've submitted a patch and gotten review on your first bug. They should be small and include some instructions about what needs to be done.
 
*[bad first bug] - a whiteboard comment that means this bug looks very simple but is harder than it looks! Consult the bugs mentor or ask in #mobile about tackling it if you think you're ready.
[[Category:New Contributor Landing Page]]
Confirm
400
edits

Navigation menu