Reference Docs

• MVP Tasks: https://bugzilla.mozilla.org/showdependencytree.cgi?id=971986&hide_resolved=1
• Wiki: https://wiki.mozilla.org/CloudServices/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
• TEF Mobile roadmap: https://fxosroadmap.aha.io/published/e0d1cbf8cd519bea36a3053355b6d1f7?page=1
• Loop Dev Schedule: https://drive.google.com/a/mozilla.com/file/d/0B1KBl68pRmhsMmhqQXM3SVE2ZkE/edit?usp=sharing
• wiki https://wiki.mozilla.org/Media/Webrtc
  • extended team list: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AlKBl68pRmhsdENBZDRKclBSZlhiRC1tb1BGQS1JU2c&usp=drive_web#gid=0
• demo of tokfox - http://vimeo.com/89703829 (NOT PUBLIC - do not share)
  • this is awesome. :)

Agenda

Shell Escalante is joining us today to discuss & confirm server side bug list [see below]

• Bug 998332 - ( loop_mvp_server ) [meta] MVP Loop Server - what is the status on the server.
  • We don't have any real tickets for MVP yet on the server side we are waiting for adamroach green light on that.
    • Fernando has proposed the flows for the User Registration in the Server but he was not going to create the USs. Here are the flows https://wiki.mozilla.org/Loop/Architecture#Data_Flows... here are the inprogress UI work from Darrin https://people.mozilla.org/~dhenein/labs/loop-mvp-spec/#invitationlist. here are the user stories...https://fxosroadmap.aha.io/published/e0d1cbf8cd519bea36a3053355b6d1f7?page=3 - keep clicking right arrow at bottom to read more details.
• Bug 994115 - Set up a Nightly ready Server over https - looks like Remy and several other Services team engaged, blocked by SDK sign-off. How quickly after sign-off can it stand up against Tokbox.
  • We are working on it with OPS to get a pupettized server for dev and prod/nightly we already have a stage environment deploy by OPS for load testing.
    • puppetized/cfn/etc for loop is ready. Stage is deployed. Can be promoted to prod
    • some outstanding bits: sentry / statsd should be done May 13th,2014
• Bug 994360 - Deploy Loop server on AWS → Alexis believes this is already done, he says he's catching up with ops today / tomorrow
  • We have one for development but we need to reinstall it. Benson on operational side. deploy in stage load testing. dev server on Amazon...Ask Adam for info or Mark/Niko.
• Bug 994961 - Start load testing the staging environment → Alexis says this is blocked by 994360, but he/Services is ready to load test as soon as everything is deployed.
  • It is deployed but we need to make sure the stage environment is ready to run load test on it.
• Bug 987086 - Loop web client should use configuration for determining server url
  • Standard8 was working on it this week and it should be ready. No work on that from a server point of view. not block for dev flow - but deploy.
• Bug 988469 - ( loop_msisdn_verific ) MSISDN verification API for privileged apps - check status with Tauni. Remy working with Fernando, Remy Mozilla testing out POC of Tef Fernando implementation for feedback.
  • We have a dev environment here: http://msisdn.dev.mozaws.net/ with the MT authentication protocol PoC and we also have a web client PoC for it: http://msisdn.dev.mozaws.net/app/
• Bug 998748 - [meta] FxA Service
  • Still waiting for further information about it but we know that it will be needed for MVP
  • More than FxA there is also MSISDN Authentication hopefully the two services FxA and MSISDN are using a similar protocol for auth.
    • The sign-in cases are here https://fxosroadmap.aha.io/published/e0d1cbf8cd519bea36a3053355b6d1f7?page=4. only issue we should discuss is if LOOPMOB-7 requires Sync - which i've heard is not in 2.0.
    • what bare bones testing for Loop Mobile
• Bug 1009488 - Mobile Loop Client needs ability to authenticate via FxA to the server. does this depend on 984949?
  • Yes it is related to 984949 and 998748
• 984949 will need to support dif authentication schemes at same time....fits in next couple...turning back on FxA
• Contacts
  • Need SIM card and google ID's displayed - both already accessible.

Notes

• • Ask Ian Bicking for synching - John G. about FxA
    • Shell set up 1/2 intro with Rafa, John, Ryan, Darrin - are there mock-ups from Tef somewhere?
    • Ian sending email on what Fruux? can do....follow up
    • Shell: clarification Contacts for platforms... local on desktop - how is that handled or is just google contacts on desktop. Order and priority for each platform.
    • Shell and Ian talk on single-sign on with FxA account giving access to Loop Mobile with phone number association (Shell verify that if V1 or V2 for Loop mobile and then set expectations internal and external)
• We need to discuss sync beyond contacts sync
• Shell to confirm dev test schedule and get back to us - before June 9th to test compatibility of Loop Mobile platform and Loop Mobile client components - so need dev environment for Loop server to go against. It would be ideal if that went to TokBox servers... but that may be a reach.
• contacts integration into Loop?
  • gaia team is working to make the API accessible
  • TEF wants Facebook contacts (legal in discussions now)
  • google and SIM contacts are part of the v1 list and already handleable via API;