Changes

Firefox Sync is a set of software components and specifications that synchronize data between multiple Mozilla product instances. The software is open source and the specifications are all public. This means that others are free to implement components or run the software on their own.

We have some pages we use to help our "advanced" users get us diagnostic information

We also have some [[CloudServices/Sync/Canned_bug_responses|canned responses]] for bugzilla bugs.

The Sync family consists of the following products and services:

; Client integrated in the Firefox and Firefox Mobile browsers

; [[Services/Sync/Server|Server]] : Server component used for cross-client communication

; Server Instance : A Sync server operated by Mozilla available for use by anybody in the world, free of charge. This is where Firefox sends data by default, unless you specify a different server.

The [[Services/Sync/Specs|Specifications]] of Sync cover:

; Client APIs : These include the JavaScript API available in Firefox

Shout out in the [https://matrix.to/#/#sync:mozilla.org #sync:mozilla.org] room on [[Matrix|Mozilla's Matrix]] server.

Most team members are geographically located in North America and Australia. If you don't hear a response, try asking again in a few hours.

See [[Services/services-dev|services-dev]] for email contact info.

Sync bugs should be reported in the [https://bugzilla.mozilla.org/describecomponents.cgi?product=Cloud%20Services Cloud Services Component] of Bugzilla.

Source code for all products and services is available and open source. Public contributions and feedback for product direction is encouraged and very welcome.

* [https://wiki.mozilla.org/CloudServices/Sync/FAQ Low level sync FAQ]

* [https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=t0hTbNyvO5uhObi Sync internals video] | [https://docs.google.com/presentation/d/1zDjuboT81BgKmixFqQkxyKIEy2DWUt6YTe_Gpara1Bg/edit#slide=id.p slides]

* [[CloudServices/Sync/ReDash#Table_Described|Definitions of data available in Re:Dash under main Sync ping]]

* [[Firefox Sync extended logging]] for fetching successful sync event logfiles

* [https://wiki.mozilla.org/CloudServices/Sync/OKRs_2016Q3 Themes and Initiative OKRs]

* [https://wiki.mozilla.org/CloudServices/Sync/Sprint_1 Current Work - Sprint 1]

* [https://wiki.mozilla.org/Bugmasters/Process/Triage Bug process for sprints]

* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Sync%20Backlog&sharer_id=458547&list_id=13152406 Backlog (all priorities)]

* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Sync%20Triage&sharer_id=458547&list_id=13152407 Triage (unprioritized)]

* [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Sync%20Team%20P1&sharer_id=465825&list_id=13152451 P1s Desktop]

* [https://wiki.mozilla.org/CloudServices/Sync/Status View Bugs by Feature]

* [https://docs.google.com/document/d/10Ytw1kZjBHhlTkQGTW8usJ5CJLhko74dgFND9egjkI0/edit iOS issues doc]

* [https://docs.google.com/document/d/189f1pCcc8nKZGl-y1KhD0JoXgct8BdjQEiYvyTunejs/edit Bi-Directional bookmarks reference doc]

* Problem

** Currently sync uses the 'clients' sync data collection as a list of active devices. This list has no state and difficult to 'delete' an device off list. Most client display a device if it's been active within the last two weeks. This design creates a number of bugs visible to the user.

** Pending management UI of devices.

* [https://docs.google.com/document/d/17OkChAAlavNnYKzX-z-ihKdg3CWk26R0mgxhNhDz7o8/edit PRD]

* Design

** iOS must have device registration

* [https://wiki.mozilla.org/CloudServices/Sync/Atomic_IO Atomic IO]