On Jan 13, 2014, at 1:39 PM, Chris Karlof <[email protected]> wrote:
> > On Jan 13, 2014, at 1:37 PM, Chris Karlof <[email protected]> wrote: > >> >> On Jan 10, 2014, at 7:34 PM, Richard Newman <[email protected]> wrote: >> >>>> This is tricky. >>>> >>>> I'm going to ask Richard to weigh in here. We touched on this briefly in: >>>> >>>> https://bugzilla.mozilla.org/show_bug.cgi?id=949260 >>>> >>>> I need to review the sync again to remind myself how it all works. >>> >>> Got a bug number (or earlier email) to point me to? >>> >> >> Mark's work in progress, but he also retracted them. I haven't seen the >> updates yet. >> >> https://github.com/mhammond/gecko-dev/commit/de07620926025bf1e542315e3e4c1405e8ddc518 >> >> https://github.com/mhammond/gecko-dev/commit/3291a6f7f3a21a584d807685cb01ae24f0650069 >> Sorry for the noise, Richard. It looks like Mark created bugs for these and you are already clued in: https://bugzilla.mozilla.org/show_bug.cgi?id=959222 https://bugzilla.mozilla.org/show_bug.cgi?id=959088 -chris > > These commits seem to be updates on this effort, but I haven't heard from > Mark on these yet: > > https://github.com/mhammond/gecko-dev/commit/5136b6099309bf06a07b1d4729daf0abbede10ff > > https://github.com/mhammond/gecko-dev/commit/1bb17e590d36740bceece1409a1bac9b095e6382 > > -chris > > >> >>>>> and have sync re-configure itself based on the user "unlinking" the >>>>> device from a legacy account, which should them enable them to create a >>>>> new Fxa based account) >>> >>> I encourage you to have an existing user go through setup before you >>> replace their legacy account with a new account. For three reasons: >>> >>> • If they abort the process (or can't complete it due to maintenance or >>> something — or because we screwed up and need to push out a point >>> release!), you didn't just leave them in a bad state. "Reformat and >>> reinstall" is less friendly than "repair Windows". >>> >>> • You can offer a better user experience if you can directly look at their >>> existing settings (e.g., check their enabled engines, pre-fill their >>> existing email address), and you can't do that if you tell them to unlink >>> their device first. >>> >>> • If you still have their old credentials around when you finish FxA setup, >>> you can write a migration sentinel into the old account, rather than >>> flipping them a giant bird and making them do all of this work again on >>> their other devices. We definitely want to take this step when we're >>> encouraging migration of existing users, so engineering things such that >>> it's hard to do in the short term is probably the wrong call. Even if you >>> don't write a migration sentinel, you should delete the remote client and >>> tabs records. (There's already a method for this.) >>> >>> We'll be writing a migration sentinel on Android, so symmetry on desktop >>> would be pleasant — doesn't make sense that it's way more usable to set up >>> Sync on your phone rather than your desktop. >> >> To echo Mark, we decided to not tackle any of the migration issues in Fx29: >> >> https://wiki.mozilla.org/User_Services/Sync/Transition_To_FxA_Sync >> >> If current Sync users want to transition to FxA Sync, their option will be >> to disconnect all their current devices and login on each device to FxA >> Sync. We can get fancier in Fx30+ when we start to upsell existing Sync >> users to FxA Sync. We will not be doing this upsell in Fx29. >> >> -chris >> >> >> >> >> _______________________________________________ >> Sync-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/sync-dev > > _______________________________________________ > Sync-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/sync-dev
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
