CloudServices/Loop/WeeklyStandup/2014-04-14

FxA - Loop Project Kick-off: The purpose of this meeting is to review the user stories with focus on the FxOS use case and how it relates to desktop and the challenge of MSISDN identifiers in FxA.

• Meetings: Tuesday's 9am PDT, Services vidyo
• Facechannel: Services
• Backchannel: #loop
• Mailing List: loop-dev
• MVP Tasks: https://bugzilla.mozilla.org/showdependencytree.cgi?id=971986&hide_resolved=1
• Reference Docs:
  • Wiki: https://wiki.mozilla.org/Services/Loop
  • Loop MVP User Stories: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlJmiyFngeSwdGJEVnItQ2NVbGx6NXdjbVBUYmIxSGc#gid=0
  • Backlog User Stories: https://docs.google.com/a/mozilla.com/spreadsheets/d/1r_zkWTbold5dlA5vh8P4xugTmRlfYQo5mUAuYc2qAxQ/edit#gid=1480050446
  • Loop Server: https://docs.services.mozilla.com/loop/index.html
  • Design Docs: https://people.mozilla.org/~dhenein/labs/loop-docs/
  • Fernando's proposal: https://wiki.mozilla.org/Loop/Architecture/ID
  • Chris's phone number verification strawman: https://github.com/mozilla/fxa-auth-server/wiki/API-extensions-for-supporting-MSISDN-verification-in-FxA-auth-server
• Targets:
  • 2014-04-25: Definition of user flows, architecture & API confirmed for how authentication will work
  • TBD from this kick-off meeting
    • FxOS targets
    • Desktop targets
• Meeting notes: https://etherpad.mozilla.org/fxa-loop

NOTES:

• Phones will use phone number as authentication, desktop will use FxA, for MVP it will be either/or, never phone number and FxA simultaneously
• For MVP (and maybe beyond!) there is no direct connection between FxA and phone number auth
• Verification requirements for Loop don't seem very high, though we may want to do good verification for our own long-term phone number auth purposes. No reverification required. (For MVP do we need to detect changing SIM cards?)
• Loop's server handles matching people
• No Presence for MVP
• Loop incoming call requests contain auth information? (I.e., "incoming call from ian@ianbicking.org" – with signature? – no identity associated with a response to a callback URL)
• First time experience? Especially on desktop? This seems to be the active concern of John Gruen
• Some open questions about spam and blocking. In the future it would probably make sense for Loop to provide spam-related feedback to FxA.
• Ultimately phone number and FxA could be used together on a phone, but the Loop server also handles all the functional aspects of that.
• In the future, we will associate multiple identities with your Loop account, so you can search for users based on these identities (e.g., search for @ianbicking). Since FxA doesn't include querying functionality, this feature probably doesn't relate to FxA.
• Is Loop a Firefox feature? Should it be? Who decides if it is? (This seems very pertinent to desktop FxA integration)
• What is our email communication channel?
• UX to be confirmed for contact import flow - scheduled to be completed this week
  • assumption is you wouldn't load *all* your contacts
• Privacy/Security: will we be able to make a differentiation of our service vs other services out there
  • that would satisfy our cyrpto gang
• Cross-functional folks:
  • Darrin: Desktop UX
  • Mobile: TEF Raffa UX
  • Kerry Wong (?) Contacts Integration
  • John/Ryan to figure out FxA - FxA not part of MVP (?)
• TEF assumptions re: FxA are matched to Romain's assumptions
  • [action] we need to get aligned with Product TEF - orgainize discussion