User:Anaaktgeboren/theSyncK9OMilestone
Contents
The Mountain
Moving Parts
Sync in K9o
Item | Time estimate | Deadline | Tracking/Meta bug | Additional Info | Team | Point person | Status |
client split notification in preflag day release: desktop | Sync Client | green light decision needed | |||||
client split notification in preflag day releases: fennec | Sync Client | green light decision needed | |||||
BrowserId API: desktop | Identity | :ddahl | started | ||||
BrowserId API: native fennec | Identity | not started. spec needed? | |||||
BrowserId API: B2G | Identity | not started? spec needed? | |||||
2.0/Bid integration in Sync Client: desktop | Sync Client | :gps | started | ||||
2.0/Bid integration in Sync Client: fennec | Sync Client | not started. waiting on desktop to finish | |||||
Sync Client for B2G | see chart below | Sync Client | not started. Not speced | ||||
UI Design: desktop | Product/UX | needs work | |||||
UI Design for Sync Options | is this on persona.org? on desktop client? engine selection, quotas, change of server? | UX/Product | needs work | ||||
UI Design: fennec | Product/UX | needs work? | |||||
Migration Path: Desktop | Product | asa/thunder/ally? | needs work? | ||||
Migration Path: Fennec | Product | madhava/jay/thunder/ally? | needs work? | ||||
Migration Plan: Firefox Home | Do we have a decision yet? | Product | Jay | kill/keep decision needed | |||
HTML client | can we do this/should we do this/do we have enough time to do this? | Product, Eng | green light decision/scoping decision needed | ||||
Sync 2.0 Spec | https://github.com/mozilla-services/docs/blob/master/source/storage/apis-2.0.rst | Sync Client, Sync Server | finished | ||||
discovery/token server | Sync Server | finished | |||||
token processing lib | Sync Server | tarek/telliot | in progress/ blocked on mconnor | ||||
deployment to staging | Services Ops | ||||||
deployment to production | 2 weeks+ | Services Ops | |||||
metlog | nice to have or blocker? | decision needed | |||||
packaging | 2 weeks | ||||||
decision: handling of flag day | marketing? pr? eng? pmm? | not started | |||||
New Privacy Policy, Terms of Service | crypto changes, pp/tos is out of date | discussions have begun. | |||||
dev docs | how to set up your own server in the brave new world | Sync Server, Sync Client | |||||
new sumo articles | not started | ||||||
fate of accounts portal | decision/plan needed | ||||||
notification of other clients | asap | BerrySync, Adblock Plus, DolphinHD | Sync Management | Ally | Done, may require followup | ||
durable storage | 6 months from POs signed | Services Ops | Todd/JV? | Work on getting POs |
B2G Sync
Item | Time estimate | Deadline | Tracking/Meta bug | Additional Info | Team | Point person | Status |
porting over sync guts* assumes Bid API is done | |||||||
contacts db API | cjones, rnewman | ||||||
contacts sync engine | |||||||
DOM API for Sync | |||||||
Sync Options UI |
User Stories/Use cases
- See questions below (1)
Outstanding Questions, BID+2.0 Sync
0) Missing timelines
a) keywrapping/master storage c) iOS, firefox home, web client instead?
1) Missing cohesive UX story
a) I have ffx14 with sync set up, I upgrade to ffx15 (and thus the old acct no longer work). - What do I see? - What tells me I have reset up sync? - options: 'setup sync', 'turn off sync' - migrate user's credentials over? - users whose username was not an email are screwed - How do we make them understand it's not interoperable b) I have upgraded to ffx15 and I dont have sync. I click 'Setup Sync' - What walks me through getting browserid and getting back into sync setup? - Does setup at persona.org stay in XUL? - Does it need to open a new tab? c) I have a mobile (fennec, b2g) and no desktop nearby and want to set up sync. - Can I create a browserid account on the phone? d) I have a phone and sync(and browserid) and its all cool. I lost my phone. - Can I reset my account? - How do I reset my account? e) My email (my previous sync credentials for example) doesn't support browserid (its in unicode for example). - Can I still use sync? - If not, what error will the user experience and it will it actually communicate the underlying problem? f) I wear a tinfoil hat and I dont trust this new keywrapping. I'm a 1337 user and want to j-pake. - Are we going to stand by the 'take both pills' & keep jpake in an advanced setup? g) I run my own sync server. Where do I input the custom server URL? - can I change it after setup on this browser? - do i change it in the client? on persona.org? h) I want to use a browserid from somewhere other than persona but still use moz sync servers - can I do this?
2) What is the fate of the Account Portal in a Persona world?
- probably used for right to be forgotten - start thinking about unifying deletion of user data for all Mozilla-hosted services. For us, that means solving it for Sagrada/token server. - How long do we have/plan to take? - we also have to guarantee that the data doesn't live on backup tapes forever. - does that include logs? - Sounds like we'll need an explicit policy about backup retention/deletion for our services, along with ensuring we call out the current log retention policy
3) How do we(sync, identity) plan to handle that browserid login/persona.org are going to look even more like iCloud/google cloud?
a) We probably can't get around this one, but I want us to be prepared and proactive instead of reactive b) This probably concerns whoever is doing the messaging on persona.org itself
4) Where is the sync client code getting the browserid assertion?
a) gps-ben, is everything cool here?
5) Do we have a self-destruct-all-my-data/erase-me-from-the-system ability? do we need it for ship?
a) Will BID support this? - Or will users have to b) How would we expose this to the users? - web based? device based? c) Does this impact the Sync Account Portal? - yes d) probably needs legal follow up e) does this change the token server spec?
6) While Metlog is not a dealbreaker/ship blocker, do we want it sending data to metrics?
a) We have not decided. we need a decision, it can log to the system logs b) If we send to metrics, there are netops dependencies, which impact schedule
7) Do we plan to support 2.0 on fennec XUL?
a) It may continue to ship for the rest of this year, but is supposed to be doomed b) Toby & I are fairly certain we don't want to, but this should be a decision we make
8) Flag day: Kilomonjero
a) If we target 17, ESR for 10 ends jan 1 b) meaning EOL of sync 1.1 is jan 1 2012 c) so the ESR ffx doesnt sync with any updated clients is less of an
issue?
c.i) theyre still screwed, but we have to care less
9) Do we need an explicit opt-in for legal (and germany) for bid+sync
a) probably need answers from legal
10) Is rollback an option?
a) my conversation with toby in dec suggests it is not
11) Will a user have to enter credentials and redo things on every device?
- Are there enough of these we consider a problem? - Is there any way to ease that pain?
Reference
- k9o
- s2b
- https://wiki.mozilla.org/User:Mconnor/BIDSync%28s%29
- https://wiki.mozilla.org/BrowserID_Key_Wrapping
- f.cl.ly/items/1P1O0C143T0a261b3F38/Sign%20into%20Browser_UI%20Indicator.jpg
- https://wiki.mozilla.org/Identity/Features/Sign_into_the_browser
- http://people.mozilla.com/~zfang/SignInMobile/Mobile.html
- http://people.mozilla.com/~zfang/SignIn/Home.html
- http://people.mozilla.com/~zfang/UserTesting_SignIn3:29/assets/fallback/index.html
- b2g