*Theme: mid-way through train-82*

This was a combined UX/PM & Ops/General dev meeting.

*UX/PM*

   - During last week's Product meeting, it was decided that Connect
   Another Device is performing well and should be enabled for 100% of users
   signing up. There was a question about how to enable this for 100% of
   users.


   1. Option 1 - place 100% of users in the `treatment` group of the
      experiment.
      2. Option 2 - remove the experiment.


   - Pros of Option 1 - The metrics reported to DataDog do not need to
      change. When we report experiment metrics to DD, we encode the experiment
      name & group as part of an event name. Cons of option 1 - we have
      experiment code lying around.
      - Pros of Option 2 - Less code to manage since all experiment related
      code is removed. Cons of option 2 - A bunch of DataDog graphs
will need to
      be updated.
      - We decided to go with Option 1 for a train to ensure no important
      stats have regressed as part of the rollout. After a train,
we'll shift to
      Option 2.

      - Ryan Feeley wants to find out the cause of the "mystery reconnect"
   when users click on "Manage account" from "about:preferences#sync". We
   found STRs today [1].

   - Alex Davis asked for status updates on backup/secondary emails & Send
   SMS
      - For backup/secondary emails, Vijay has started on the DB and
      auth-server endpoint updates. He'll show a "rough" demo later today.
      - Send SMS is discussed below.

*Ops/General Dev*

   - Action items from last time:
   - IN PROGRESS - stomlinson - move SMS feature doc to GitHub
   - DONE - stomlinson - ask legal whether we can release send SMS in Canada
   - DONE - vbudhram - tag auth-server 81.1, update deploy doc.
   - NOT DONE - vladikoff - deploy web sessions to a box

      - train-81 will release this week. Exact date TBA.

   - Web Sessions
      - the DB PR has merged!

      - The initial patch has landed on the content server to use joi
   validation instead of homegrown validation for POST endpoints.

   - Send SMS
      - The first iteration has landed in master and should be on prod this
      week for UX and QA to test.
      - Phil is working on the /sms/status endpoint which will allow us to
      gate the feature so that it only appears to users in the US, and
if our SMS
      provider account has sufficient funds. As part of this, Phil updated the
      fxa-geodb to return the user's ISO country code.
      - I have migrated the feature doc from Google Docs to GitHub
      (finally!) [2].
      - I have also updated the feature doc with a basic test plan.
      - We have asked legal if we can also release the feature in Canada,
      the per message charge is the same as the US.

      - For the secondary email work, Vijay asked whether he should
   overload the recovery_email/verify_code endpoint to verify secondary
   emails, or whether that should be reserved for primary emails.
      - About half the team thought "use the same endpoint", the other half
      thought "new endpoint."

      - Action items for next time:
   - rfeeley to convert sync fest problems to bugs
      - stomlinson to finish converting send SMS doc

Shane


[1] - https://github.com/mozilla/fxa-content-server/issues/4763
[2] - https://github.com/mozilla/fxa/pull/227
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to