canmove, Confirmed users
640
edits
(Created page with "The Android Background Services module is a collection of related functionality that supports Mozilla's work on Android. Its remit is services, adapters, uploaders, downloaders, ...") |
No edit summary |
||
Line 6: | Line 6: | ||
Other work (e.g., the updater) lives in mozilla-central, typically as part of the mobile/ tree. | Other work (e.g., the updater) lives in mozilla-central, typically as part of the mobile/ tree. | ||
== People == | |||
; Owner : Richard Newman | |||
; Peers : Chris Peterson, Nick Alexander, Chenxia Liu, James Willcox | |||
Look for us in #androidsync, #mobile on IRC. | |||
== Bugs == | |||
See the following: | |||
* [https://bugzilla.mozilla.org/describecomponents.cgi?product=Services%20for%20Android Services for Android] (pending) | |||
* [https://bugzilla.mozilla.org/describecomponents.cgi?product=Mozilla%20Services Mozilla Services] | |||
* [https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox%20for%20Android Firefox for Android] | |||
== Getting started == | |||
There are two tiers of working with the Android Services codebase: | |||
* Standalone, which involves working in Git, probably in Eclipse, using Maven for dependencies, and running JUnit tests. Tests that involve running against a Fennec instance can use a repackaged binary. | |||
* Integrated, which means you deploy services code into a <code>mozilla-central</code> tree. You need this if you're landing code in the shipping product, or need to run tests using [[Auto-tools/Projects/Robocop|Robocop]]. | |||
=== Getting the repo === |