CloudServices/Roadmaps/Sync/Client/Sequence: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Undo revision 399022 by Anaaktgeboren (talk))
Line 1: Line 1:
<h2> Summary </h2>
== Summary ==
<p>This wiki is meant to capture the expanded sequence of work for the <a href="https://wiki.mozilla.org/Services/Roadmaps/Sync/Client">2011 Sync Client Roadmap</a>. It will also serve as a way to see what is in progress or available.  
This wiki is meant to capture the expanded sequence of work for the [https://wiki.mozilla.org/Services/Roadmaps/Sync/Client 2011 Sync Client Roadmap]. It will also serve as a way to see what is in progress or available.  
</p>
<h2> Definitions </h2>
<ul><li> <b>Road map:</b> A product theme or set of themes, broken down into units of work that are shippable. Product progress is tracked against the road map.
</li><li> <b>Road map item:</b> a single item that be delivered independently. It can have dependencies. The work is significant enough to warrant several days (3+ days) or weeks. <i>Due to rapid release train model, may want to keep roadmap items to a max of a few weeks of work (&lt; 6weeks).</i>
</li><li> <b>Feature</b>: one or more road map items that have a user experience impact, most commonly they are user visible. For more information on what a feature is go <a href="https://wiki.mozilla.org/Features/Planning_and_Tracking#What_is_a_.22feature.22.3F">here</a>.
</li><li> <b>Project:</b> like a feature, but not user-facing. (Jen says, "perhaps call this type of work "Enhancement")
</li><li> <b>Work item:</b> a task within a road map item
</li><li> <b>Feature page:</b> is where a feature is defined, spec'ed, staffed, and tracked. Each feature or project should have a feature page associated with it.
</li></ul>
<h2>Sequence</h2>
<h3> 2012 Draft Roadmap Sequence </h3>
<table class="fullwidth-table" style="width: 950px">


<tr>
== Definitions ==
<td style="font-weight: bold; background: #DDD;"> Roadmap Item
* '''Road map:''' A product theme or set of themes, broken down into units of work that are shippable. Product progress is tracked against the road map.
</td>
* '''Road map item:''' a single item that be delivered independently. It can have dependencies. The work is significant enough to warrant several days (3+ days) or weeks. ''Due to rapid release train model, may want to keep roadmap items to a max of a few weeks of work (< 6weeks).''
<td style="font-weight: bold; background: #DDD; width: 100px"> Type
* '''Feature''': one or more road map items that have a user experience impact, most commonly they are user visible. For more information on what a feature is go [https://wiki.mozilla.org/Features/Planning_and_Tracking#What_is_a_.22feature.22.3F here].
</td>
* '''Project:''' like a feature, but not user-facing. (Jen says, "perhaps call this type of work "Enhancement")
<td style="font-weight: bold; background: #DDD; width: 80px"> Owner
* '''Work item:''' a task within a road map item
</td>
* '''Feature page:''' is where a feature is defined, spec'ed, staffed, and tracked. Each feature or project should have a feature page associated with it.
<td style="font-weight: bold; background: #DDD; width: 100px"> (Nonbinding) Estimated Year/Quarter
</td>
<td style="font-weight: bold; background: #DDD; width: 150px"> Status
</td></tr>
<tr>
<td> First release of Android Sync
</td>
<td> Project, Entirely New Product
</td>
<td> Richard Newman
</td>
<td> 2012 Q1
</td>
<td> In Progress
</td></tr>
<tr>
<td> BrowserID Integration into Desktop Client
</td>
<td> Project, Backend, Frontend
</td>
<td> Greg Szorc
</td>
<td> 2012 Q1
</td>
<td> In Progress
</td></tr>
<tr>
<td> Syncing Do Not Track Preferences across platforms
</td>
<td> Project, Significant Backend work
</td>
<td>&#160;?
</td>
<td> 2012 Q2
</td>
<td>&#160;?
</td></tr>
<tr>
<td> Device Management Dashboard <span class="fck_mw_template">{{bug|694272}}</span> and <span class="fck_mw_template">{{bug|694276}}</span>
</td>
<td> Project
</td>
<td> Marina?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> sync search engine prefs
</td>
<td> Feature, New engine
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/FxSync/FaviconSync">Favicon Sync</a>
</td>
<td> Feature, New engine
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> Rewrite (async &amp; improve) service.js
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/Async engine API">Provide an async engine API</a> (repository, synchronizer)
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/port tabs engine">Port the tabs engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/port clients engine">Port the clients engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/port prefs engine">Port the prefs engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/Port Bookmarks Engines">Port the bookmarks engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/Port Passwords Engines">Port the passwords engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/Port Forms Engines">Port the forms engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/Port History Engines">Port the history engine to async APIs</a>
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> Port the addons engine to async APIs
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> Port the favicons engine to async APIs
</td>
<td> Project, Backend
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/FxSync/Syncorro">Automatic sync error reporting</a>
</td>
<td> Feature
</td>
<td> Chenxia/Mime?
</td>
<td>&#160;?
</td>
<td> On hold
</td></tr>
<tr>
<td> <a href="Services/Sync/FxSync/Crossweave2">TPS: Failure handling &amp; recovery</a>
</td>
<td> Project, tools
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/FxSync/Crossweave2">TPS: Rudimentary performance instrumentation</a>
</td>
<td> Project, tools
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/site-specific prefs sync">Site-specific prefs Sync (now async)</a>
</td>
<td> Feature, new engine
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/client cert sync">Client Certificate Sync (now async)</a>
</td>
<td>  Feature, new engine
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/localstorage sync">Local Storage Sync (now async)</a>
</td>
<td> Feature, new engine
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
<tr>
<td> <a href="Services/Sync/FxSync/Crossweave2">TPS: Automatic Profiling of Sync</a>
</td>
<td> Feature, tooling
</td>
<td>&#160;?
</td>
<td>&#160;?
</td>
<td>&#160;?
</td></tr>
</table>
<p><br />
</p>
<h4> Under Consideration (Should we even put these on our roadmap?) </h4>
<table class="fullwidth-table" style="width: 950px">


<tr>
==Sequence==
<td style="font-weight: bold; background: #DDD; width: 50px"> Type
=== 2012 Draft Roadmap Sequence ===
</td>
{| class="fullwidth-table" style="width: 950px"
<td style="font-weight: bold; background: #DDD; width: 200px"> Item
|-
</td>
| style="font-weight: bold; background: #DDD;" | Roadmap Item
<td style="font-weight: bold; background: #DDD;width: 100px"> Requestor
| style="font-weight: bold; background: #DDD; width: 100px" | Type
</td>
| style="font-weight: bold; background: #DDD; width: 80px" | Owner
<td style="font-weight: bold; background: #DDD;width: 200px"> Comments
| style="font-weight: bold; background: #DDD; width: 100px" | (Nonbinding) Estimated Year/Quarter
</td></tr>
| style="font-weight: bold; background: #DDD; width: 150px" | Status
<tr>
|-
<td> Feature
| First release of Android Sync
</td>
| Project, Entirely New Product
<td> Firefox Home Revamp/Nofications addition?
| Richard Newman
</td>
| 2012 Q1
<td> Several folks
| In Progress
</td>
|-
<td> SUMO reports there are more inquiries on this every week. BrowserID will not work with the existing system. We could also use this to get a notifications foothold on ios
| BrowserID Integration into Desktop Client
</td></tr>
| Project, Backend, Frontend
<tr>
| Greg Szorc
<td> <a href="Services/Sync/Push to device">Push to device</a> revive? kill?
| 2012 Q1
</td>
| In Progress
<td>
|-
</td>
| Syncing Do Not Track Preferences across platforms
<td> greg did a lot of work on this, but it was put on hold due to native fennec.
| Project, Significant Backend work
</td></tr>
| ?
<tr>
| 2012 Q2
<td> Feature
| ?
</td>
|-
<td> Add last Sync'ed message to the error messages
| Device Management Dashboard {{bug|694272}} and {{bug|694276}}
</td>
| Project
<td> SUMO
| Marina?
</td>
| ?
<td> Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.
| ?
</td></tr>
|-
<tr>
| sync search engine prefs
<td> Feature
| Feature, New engine
</td>
| ?
<td> Get rid of Sync Now in tool bar, and put "Last Synced" time in there.
| ?
</td>
| ?
<td> SUMO
|-
</td>
| [[Services/Sync/FxSync/FaviconSync|Favicon Sync]]
<td> Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See <span class="fck_mw_template">{{bug|675817}}</span>.
| Feature, New engine
</td></tr>
| ?
<tr>
| ?
<td> Feature
| ?
</td>
|-
<td> Error message that points to FAQ on error on SUMO
| Rewrite (async & improve) service.js
</td>
| Project, Backend
<td> SUMO
| ?
</td>
| ?
<td> If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
| ?
</td></tr>
|-
<tr>
| [[Services/Sync/Async_engine_API|Provide an async engine API]] (repository, synchronizer)
<td> Feature
| Project, Backend
</td>
| ?
<td> Sync Sub-Set of Bookmarks
| ?
</td>
| ?
<td> SUMO
|-
</td>
| [[Services/Sync/port_tabs_engine|Port the tabs engine to async APIs]]
<td> Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
| Project, Backend
</td></tr>
| ?
<tr>
| ?
<td> Feature
| ?
</td>
|-
<td> Automatic reset-prompted backup
| [[Services/Sync/port_clients_engine|Port the clients engine to async APIs]]
</td>
| Project, Backend
<td> atoll, rnewman
| ?
</td>
| ?
<td> Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options.  "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data.  Users sure aren't willing to do the hard work.  Maybe we are.
| ?
</td></tr>
|-
<tr>
| [[Services/Sync/port_prefs_engine|Port the prefs engine to async APIs]]
<td> Feature
| Project, Backend
</td>
| ?
<td> App Tabs Syncing <span class="fck_mw_template">{{bug|651817}}</span>
| ?
</td>
| ?
<td> Security: From Bugzilla
|-
</td>
| [[Services/Sync/Port_Bookmarks_Engines|Port the bookmarks engine to async APIs]]
<td> 10/18: Jennifer with circle back with FF PM team
| Project, Backend
</td></tr>
| ?
</table>
| ?
<h2> Inbox (Old &lt; 2011 Q3) </h2>
| ?
<dl><dt> This is a place to put any Sync ideas. We'll review these periodically.
|-
</dt></dl>
| [[Services/Sync/Port_Passwords_Engines|Port the passwords engine to async APIs]]
<table class="fullwidth-table" style="width: 950px">
| Project, Backend
| ?
| ?
| ?
|-
| [[Services/Sync/Port_Forms_Engines|Port the forms engine to async APIs]]
| Project, Backend
| ?
| ?
| ?
|-
| [[Services/Sync/Port_History_Engines|Port the history engine to async APIs]]
| Project, Backend
| ?
| ?
| ?
|-
| Port the addons engine to async APIs
| Project, Backend
| ?
| ?
| ?
|-
| Port the favicons engine to async APIs
| Project, Backend
| ?
| ?
| ?
|-
| [[Services/Sync/FxSync/Syncorro|Automatic sync error reporting]]
| Feature
| Chenxia/Mime?
| ?
| On hold
|-
| [[Services/Sync/FxSync/Crossweave2|TPS: Failure handling & recovery]]
| Project, tools
| ?
| ?
| ?
|-
| [[Services/Sync/FxSync/Crossweave2|TPS: Rudimentary performance instrumentation]]
| Project, tools
| ?
| ?
| ?
|-
| [[Services/Sync/site-specific_prefs_sync|Site-specific prefs Sync (now async)]]
| Feature, new engine
| ?
| ?
| ?
|-
| [[Services/Sync/client_cert_sync|Client Certificate Sync (now async)]]
|  Feature, new engine
| ?
| ?
| ?
|-
| [[Services/Sync/localstorage_sync|Local Storage Sync (now async)]]
| Feature, new engine
| ?
| ?
| ?
|-
| [[Services/Sync/FxSync/Crossweave2|TPS: Automatic Profiling of Sync]]
| Feature, tooling
| ?
| ?
| ?
|-
|}


<tr>
 
<td style="font-weight: bold; background: #DDD; width: 50px"> Type
==== Under Consideration (Should we even put these on our roadmap?) ====
</td>
{| class="fullwidth-table" style="width: 950px"
<td style="font-weight: bold; background: #DDD; width: 200px"> Item
|-
</td>
| style="font-weight: bold; background: #DDD; width: 50px" | Type
<td style="font-weight: bold; background: #DDD;width: 100px"> Requestor
| style="font-weight: bold; background: #DDD; width: 200px" | Item
</td>
| style="font-weight: bold; background: #DDD;width: 100px" | Requestor
<td style="font-weight: bold; background: #DDD;width: 200px"> Comments
| style="font-weight: bold; background: #DDD;width: 200px" | Comments
</td></tr>
|-
<tr>
| Feature
<td> Feature
| Firefox Home Revamp/Nofications addition?
</td>
| Several folks
<td> Key Escrow
| SUMO reports there are more inquiries on this every week. BrowserID will not work with the existing system. We could also use this to get a notifications foothold on ios
</td>
|-
<td> Various groups
| [[Services/Sync/Push_to_device|Push to device]] revive? kill?
</td>
|
<td>
| greg did a lot of work on this, but it was put on hold due to native fennec.
<p>11/29: We need the requirements to move forward. 10/18: Jen will go speak to the other product managers interested (Identity, Pancake, etc) to understand their drivers and time lines. Ibai will also help identify user issues with this and what possible flow might look.  
|-
</p>
| Feature
</td></tr>
| Add last Sync'ed message to the error messages
<tr>
| SUMO
<td> Feature
| Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.
</td>
|-
<td> Syncing Prefs across apps. <span class="fck_mw_template">{{bug|652631}}</span>
| Feature
</td>
| Get rid of Sync Now in tool bar, and put "Last Synced" time in there.
<td> Security: Sid
| SUMO
</td>
| Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See {{bug|675817}}.
<td> 10/18: Pre-requisite is to understand how prefs are going to be handled in Fennec
|-
</td></tr>
| Feature
<tr>
| Error message that points to FAQ on error on SUMO
<td> Feature
| SUMO
</td>
| If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
<td> App Tabs Syncing <span class="fck_mw_template">{{bug|651817}}</span>
|-
</td>
| Feature
<td> Security: From Bugzilla
| Sync Sub-Set of Bookmarks
</td>
| SUMO
<td> 10/18: Jennifer with circle back with FF PM team
| Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
</td></tr>
|-
<tr>
| Feature
<td> Project
| Automatic reset-prompted backup
</td>
| atoll, rnewman
<td> New Sync Protocol version
| Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options.  "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data.  Users sure aren't willing to do the hard work.  Maybe we are.
</td>
|-
<td> Everyone
| Feature
</td>
| App Tabs Syncing {{bug|651817}}
<td> Long backlog of changes requested for the HTTP protocol. <a _fcknotitle="true" href="Services/Sync/Protocol 2.0">Services/Sync/Protocol 2.0</a>.
| Security: From Bugzilla
</td></tr>
| 10/18: Jennifer with circle back with FF PM team
<tr>
|-
<td> Feature
|}
</td>
 
<td> Device Management Dashboard <span class="fck_mw_template">{{bug|694272}}</span> and <span class="fck_mw_template">{{bug|694276}}</span>
== Inbox (Old < 2011 Q3) ==
</td>
; This is a place to put any Sync ideas. We'll review these periodically.
<td> SUMO
 
</td>
{| class="fullwidth-table" style="width: 950px"
<td>
|-
</td></tr>
| style="font-weight: bold; background: #DDD; width: 50px" | Type
<tr>
| style="font-weight: bold; background: #DDD; width: 200px" | Item
<td> Feature
| style="font-weight: bold; background: #DDD;width: 100px" | Requestor
</td>
| style="font-weight: bold; background: #DDD;width: 200px" | Comments
<td> Add last Sync'ed message to the error messages
|-
</td>
| Feature
<td> SUMO
| Key Escrow
</td>
| Various groups
<td> Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.
|
</td></tr>
11/29: We need the requirements to move forward. 10/18: Jen will go speak to the other product managers interested (Identity, Pancake, etc) to understand their drivers and time lines. Ibai will also help identify user issues with this and what possible flow might look.  
<tr>
|-
<td> Feature
| Feature
</td>
| Syncing Prefs across apps. {{bug|652631}}
<td> Get rid of Sync Now in tool bar, and put "Last Synced" time in there.
| Security: Sid  
</td>
| 10/18: Pre-requisite is to understand how prefs are going to be handled in Fennec  
<td> SUMO
|-
</td>
| Feature
<td> Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See <span class="fck_mw_template">{{bug|675817}}</span>.
| App Tabs Syncing {{bug|651817}}
</td></tr>
| Security: From Bugzilla  
<tr>
| 10/18: Jennifer with circle back with FF PM team  
<td> Feature
|-
</td>
| Project
<td> Error message that points to FAQ on error on SUMO
| New Sync Protocol version
</td>
| Everyone
<td> SUMO
| Long backlog of changes requested for the HTTP protocol. [[Services/Sync/Protocol_2.0]].
</td>
|-
<td> If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
| Feature
</td></tr>
| Device Management Dashboard {{bug|694272}} and {{bug|694276}}
<tr>
| SUMO
<td> Feature
|
</td>
|-
<td> Firefox Home maintenance
| Feature
</td>
| Add last Sync'ed message to the error messages
<td> Several folks
| SUMO
</td>
| Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.  
<td> SUMO reports there are more inquiries on this every week.
|-
</td></tr>
| Feature
<tr>
| Get rid of Sync Now in tool bar, and put "Last Synced" time in there.
<td> Feature
| SUMO
</td>
| Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See {{bug|675817}}.
<td> Sync Sub-Set of Bookmarks
|-
</td>
| Feature
<td> SUMO
| Error message that points to FAQ on error on SUMO
</td>
| SUMO
<td> Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
| If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
</td></tr>
|-
<tr>
| Feature
<td> Feature
| Firefox Home maintenance
</td>
| Several folks
<td> Automatic reset-prompted backup
| SUMO reports there are more inquiries on this every week.  
</td>
|-
<td> atoll, rnewman
| Feature
</td>
| Sync Sub-Set of Bookmarks
<td> Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options.  "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data.  Users sure aren't willing to do the hard work.  Maybe we are.
| SUMO
</td></tr>
| Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
<tr>
|-
<td> Project
| Feature
</td>
| Automatic reset-prompted backup
<td> EOL Sync Add-on
| atoll, rnewman
</td>
| Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options.  "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data.  Users sure aren't willing to do the hard work.  Maybe we are.
<td> SUMO
|-
</td>
| Project
<td>
| EOL Sync Add-on
</td></tr>
| SUMO
<tr>
|
<td> Project
|-
</td>
| Project
<td> Sync to use BroweserID
| Sync to use BroweserID
</td>
| mconnor
<td> mconnor
| A use case this would support is Log into the Browser
</td>
|}
<td> A use case this would support is Log into the Browser
</td></tr></table>

Revision as of 22:48, 17 February 2012

Summary

This wiki is meant to capture the expanded sequence of work for the 2011 Sync Client Roadmap. It will also serve as a way to see what is in progress or available.

Definitions

  • Road map: A product theme or set of themes, broken down into units of work that are shippable. Product progress is tracked against the road map.
  • Road map item: a single item that be delivered independently. It can have dependencies. The work is significant enough to warrant several days (3+ days) or weeks. Due to rapid release train model, may want to keep roadmap items to a max of a few weeks of work (< 6weeks).
  • Feature: one or more road map items that have a user experience impact, most commonly they are user visible. For more information on what a feature is go here.
  • Project: like a feature, but not user-facing. (Jen says, "perhaps call this type of work "Enhancement")
  • Work item: a task within a road map item
  • Feature page: is where a feature is defined, spec'ed, staffed, and tracked. Each feature or project should have a feature page associated with it.

Sequence

2012 Draft Roadmap Sequence

Roadmap Item Type Owner (Nonbinding) Estimated Year/Quarter Status
First release of Android Sync Project, Entirely New Product Richard Newman 2012 Q1 In Progress
BrowserID Integration into Desktop Client Project, Backend, Frontend Greg Szorc 2012 Q1 In Progress
Syncing Do Not Track Preferences across platforms Project, Significant Backend work ? 2012 Q2 ?
Device Management Dashboard bug 694272 and bug 694276 Project Marina? ? ?
sync search engine prefs Feature, New engine ? ? ?
Favicon Sync Feature, New engine ? ? ?
Rewrite (async & improve) service.js Project, Backend ? ? ?
Provide an async engine API (repository, synchronizer) Project, Backend ? ? ?
Port the tabs engine to async APIs Project, Backend ? ? ?
Port the clients engine to async APIs Project, Backend ? ? ?
Port the prefs engine to async APIs Project, Backend ? ? ?
Port the bookmarks engine to async APIs Project, Backend ? ? ?
Port the passwords engine to async APIs Project, Backend ? ? ?
Port the forms engine to async APIs Project, Backend ? ? ?
Port the history engine to async APIs Project, Backend ? ? ?
Port the addons engine to async APIs Project, Backend ? ? ?
Port the favicons engine to async APIs Project, Backend ? ? ?
Automatic sync error reporting Feature Chenxia/Mime? ? On hold
TPS: Failure handling & recovery Project, tools ? ? ?
TPS: Rudimentary performance instrumentation Project, tools ? ? ?
Site-specific prefs Sync (now async) Feature, new engine ? ? ?
Client Certificate Sync (now async) Feature, new engine ? ? ?
Local Storage Sync (now async) Feature, new engine ? ? ?
TPS: Automatic Profiling of Sync Feature, tooling ? ? ?


Under Consideration (Should we even put these on our roadmap?)

Type Item Requestor Comments
Feature Firefox Home Revamp/Nofications addition? Several folks SUMO reports there are more inquiries on this every week. BrowserID will not work with the existing system. We could also use this to get a notifications foothold on ios
Push to device revive? kill? greg did a lot of work on this, but it was put on hold due to native fennec.
Feature Add last Sync'ed message to the error messages SUMO Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.
Feature Get rid of Sync Now in tool bar, and put "Last Synced" time in there. SUMO Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See bug 675817.
Feature Error message that points to FAQ on error on SUMO SUMO If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
Feature Sync Sub-Set of Bookmarks SUMO Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
Feature Automatic reset-prompted backup atoll, rnewman Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options. "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data. Users sure aren't willing to do the hard work. Maybe we are.
Feature App Tabs Syncing bug 651817 Security: From Bugzilla 10/18: Jennifer with circle back with FF PM team

Inbox (Old < 2011 Q3)

This is a place to put any Sync ideas. We'll review these periodically.
Type Item Requestor Comments
Feature Key Escrow Various groups

11/29: We need the requirements to move forward. 10/18: Jen will go speak to the other product managers interested (Identity, Pancake, etc) to understand their drivers and time lines. Ibai will also help identify user issues with this and what possible flow might look.

Feature Syncing Prefs across apps. bug 652631 Security: Sid 10/18: Pre-requisite is to understand how prefs are going to be handled in Fennec
Feature App Tabs Syncing bug 651817 Security: From Bugzilla 10/18: Jennifer with circle back with FF PM team
Project New Sync Protocol version Everyone Long backlog of changes requested for the HTTP protocol. Services/Sync/Protocol_2.0.
Feature Device Management Dashboard bug 694272 and bug 694276 SUMO
Feature Add last Sync'ed message to the error messages SUMO Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. Let's look at this after "Death to Unknown Error" code is in GA. Then we can measure if the complaints of error bar have gone done enough that we don't have to do any more.
Feature Get rid of Sync Now in tool bar, and put "Last Synced" time in there. SUMO Users really dislike the errors. It would be good to at least put last time sync'ed so the user knows how old their current data is. See bug 675817.
Feature Error message that points to FAQ on error on SUMO SUMO If we can identify all the errors some how then we could point the users to the information that can help them better understand what is going on. And if they can solve their own problem even better!
Feature Firefox Home maintenance Several folks SUMO reports there are more inquiries on this every week.
Feature Sync Sub-Set of Bookmarks SUMO Provide the option to Sync just a group of bookmarks. This can be done in different ways (only sync bookmarks with certain label or in certain folder or with a certain parameter changed to positive) but the goal is to simply allow users not to sync all their bookmarks but just a set of their collection.
Feature Automatic reset-prompted backup atoll, rnewman Firefox should be capable of writing a profile backup to the Downloads directory, and ask the user to approve such a backup a couple times a year, and as part of doing various deadly Sync Reset options. "Why is this important?" clickable to SUMO. I know everybody will whinge to infinity about how backups are hard, but until we can make it trivially simple to do this, it's never going to happen, and users are going to continue to lose their data. Users sure aren't willing to do the hard work. Maybe we are.
Project EOL Sync Add-on SUMO
Project Sync to use BroweserID mconnor A use case this would support is Log into the Browser
Retrieved from "https://wiki.mozilla.org/index.php?title=CloudServices/Roadmaps/Sync/Client/Sequence&oldid=399024"