On 1/3/2014, 3:59 PM, Chris Karlof wrote:
Hi all,
I see today listed as the deadline for a decision on a transition plan.
I haven't seen significant discussion on this over the last day or two.
What I've seen is:
- https://wiki.mozilla.org/User_Services/Sync/Migration
- https://services.etherpad.mozilla.org/sync-migration
-
https://www.lucidchart.com/documents/edit/4678-1408-52b1b652-9823-7a810a00c462
(Sync
Migration tab)
- Brendan asking "why given how sync works now, we can't keep the option
for those users who want the same secrecy property they have now"
The most concrete transition proposal I've seen is by Richard and Ryan
F., largely captured in the Lucid chart linked to above. It's largely
sensible, but it includes elements that I don't consider minimal (e.g.,
auto transitioning users and upselling).
Here's my proposal for a bare minimum strategy for an *initial*
transition from Existing Sync to FxA Sync.
tl;dr *Just let Existing Sync users be. Support FxA Sync and Existing
Sync side by side in Fx29 with no attempt to upsell or transition from
Existing Sync -> FxA Sync.*
I support this.
*What this means:*
1) For users that are already connected to Existing Sync, Existing Sync
will continue to work when they upgrade to Fx29. There will be no upsell
to FxA Sync, and no attempt to transition them to FxA Sync in Fx29. Just
let 'em be. In Fx29, these users will see no evidence of FxA Sync
without disconnecting from Existing Sync first.
2) The default "Create Account" screen for Sync will change to use FxA.
We include warnings that this won't work with Sync on Fx29- or Sync with
pairing. For users looking for "Existing Sync", we also include a link
that will direct them to the Existing Sync "Setup Sync" and "Pair A
Device" screens.
3) The default "Login" screen for Sync will change to use FxA. We
include warnings that this won't work with Sync on Fx29- or Sync with
pairing. For users looking for "Existing Sync", we include a link that
will direct them to the Existing Sync "Setup Sync" and "Pair A Device"
screens.
I support this approach. Documentation and SUMO are the drivers to make
this palatable, and I assume that doesn't need to be done by Fx29 code
complete.
*What this means for the future:*
1) We don't necessarily have to commit to a sunset date or strategy for
Existing Sync *now*. New users will (most likely) get FxA Sync and old
users have the capability to continue to use Existing Sync, if they desire.
2) In Fx29, we lay what technical groundwork we can for a future sunset
date, e,g, deprecation messaging channels.
3) In Fx29, we lay what technical groundwork we can for future
transition strategies and upsells, e.g., starting to record the Firefox
version of connected sync clients.
I think we should be a little more opportunistic at Fx29 with one
upsell: user with a single device. This user is completely confused
about what Sync does. We can transition them. We should transition
them. Then we can at least message them via email about how we can do
better for them.
Nick
_______________________________________________
Sync-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/sync-dev
