*Meeting Theme: Getting back into the swing of things.*

   - Train-78 is going to be cut early next week.
   - jbuck and jrgm are in the beginning states of Business Continuity
   Planning (BCP)
      - Try to answer, how can we ensure FxA continues to operate in the
      event of disaster?
      - First question is "What are the critical user flows?"
      - Once those are answered, it's possible to look at which services
      are used and how.
      - Planning continues from there.
      - I suggested they contact rfeeley who (I think) has a big pdf with
      the primary flows.
   - Connect another device, phase 2.
      - adavis has started a feature doc at [1].
      - stomlinson to do more review, waiting on Q1 OKRs/priorities before
      starting development effort.
      - pb has volunteered to be my project buddy.
   - There is some confusion around the UX led firstrun experiment.
      - Where can we find out more information?
   - The circle-ci tests are stable again!
      - A huge thanks to vlad for tracking down the last flaky tests.
   - We still have a flaky test on teamcity [2].
      - The test makes use of a mailinator.com address and is being rate
      limited. The functionality being tested needs an email domain
that does not
      trigger the "Open email provider" button functionality on the "go confirm
      your email" screen.
   - Starting with Firefox 50, both Desktop and Fennec expect WebChannel
   payloads to be strings. Sending strings instead of objects is more secure
   from the browser's point of view. FxA is on a temporary list of sites still
   allowed to send objects. We want to Do The Right Thing, send strings, and
   get off of the list.
      - [3], which merged today, makes it so.
   - pb has a cross-repo testing proposal to reduce the chance of changes
   to the auth-server or js-client breaking the content server.
      - The basic idea is similar to how circle tests are run. For the
      auth-server at least, have a remote content server that is already setup
      that points to the auth-server to be tested. Run a subset of the
      content-server's functional tests against the updated auth-server code.
   - Greg Guthe (g-k in IRC) stopped by our meeting to tell us about
   SecOps' goal to have FxA's baseline scan all green by the end of Jan.
      - jrgm and jbuck are likely to field a bunch of questions/requests.

Shane

[1] -
https://docs.google.com/document/d/133_Cu0TlWQZIw-ihMH1s-U_80I12MXZcvHQEuFhWbPg
[2] - https://github.com/mozilla/fxa-content-server/issues/4537
[3] - https://github.com/mozilla/fxa-content-server/pull/4579
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to