Firefox/Accounts/Progress Report/2017Q3: Difference between revisions

Firefox/Accounts/Progress Report/2017Q3 (view source)

Revision as of 14:39, 18 September 2017

394 bytes removed , 18 September 2017

Updated with Sept. 5th confidence levels.

Juliemccracken

670

edits

@@ Line 49: / Line 49: @@
 *[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20 Quality related P1s that we’ve identified to fix in Q3.]
 |
-*Great progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR.
+*Good progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR.
 *In this sprint (as of Sept. 14th):
 **A couple are in review: [https://github.com/mozilla/fxa-content-server/issues/5197 Issue 5197: Sign-in flow: Never send users to about:preferences after Sign-in] and [https://github.com/mozilla/fxa-content-server/issues/5262 Issue 5262: Expand Connect Another Device to all sync Desktop sign-ins]
@@ Line 101: / Line 101: @@
 *[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
 |
-*Next step is to design test to measure results.
+*A little bit of code needs to land. Need to land the copy and set things up in LeanPlum.
 |-
 | align="left"|2.2 Complete 80% of Q3 mobile bugs.
@@ Line 119: / Line 120: @@
 *[https://github.com/mozilla/fxa-bugzilla-mirror/issues/332 Issue 332: Use Firefox Account server's /.well-known/fxa-client-configuration to configure servers in Firefox for iOS [bz1237407]]
 |
-*Did the easy ones first. Medium level ones are left to do. Should have 9/13 done by next week.
+*Did the easy ones first. Medium level ones are left to do.
 *[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
 |-
@@ Line 135: / Line 136: @@
 *Feature doc and Issues coming soon.
 |
-*Not confident that we’ll have QR codes ready to test
+*Saw movement on the bug with Android camera not auto-focusing, but bug has recently been re-prioritized from P1 to P2.
-*Too many unknowns to have any confidence
-*We can try a file input but that would be a crappy experience. Have never tried to import a photo into the encoder. What if there’s too much noise in the photo or the QR code?
-*We can play with the one built into iOS but still might not have time to figure it out by the end of the quarter.
-*Confidence level for use of a QR code is <25%; type a code maybe >50%
-*Need to regroup now that we know more about technical limitations and figure out what we want to do. Need a smaller discussion about what the next steps are.
-*Ryan will reach out to iOS team.
 |-
 | align="left"|3.2 Ship secondary email.
@@ Line 175: / Line 170: @@
 Relier encryption keys
 |
-*Waiting to engage crypto consultants.
+*Focusing on completing pieces for crypto review
+*We have an end-to-end demo with Notes
 *[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes]
 |-
@@ Line 189: / Line 185: @@
 Implementation of Amplitude
 |
-*Getting help from Amplitude to move forward
+*Played with the test data, and it looks good.
-*Still discovering new things
+*Working on minor changes to remove duplicate properties.
-*Should have environment with train-95 that we can send events to.
+*Made a dot release in 95 and should be able to add more with 96 so that we have data to play with for Amplitude training.
 |-
 |}