MozillaWiki

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

Page Discussion

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

Revision as of 01:15, 19 September 2017

1,263 bytes removed ,  19 September 2017
Entered final updates for Sept 18
(Updated with Sept. 5th confidence levels.)
(Entered final updates for Sept 18)
Line 1: Line 1:
__NOTOC__
__NOTOC__
<big><big>'''Sept 5, 2017'''</big></big>
<big><big>'''September 18, 2017'''</big></big>


== Q3 OKR Progress ==
== Q3 OKR Progress ==
Line 28: Line 28:
|align="center"|75%
|align="center"|75%
|align="center"|90%
|align="center"|90%
|align="center"|
|align="center"|100%
|align="left"|
|align="left"|
|
|
Line 34: Line 34:
*[https://waffle.io/mozilla/fxa?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Issues for 57 release.]
*[https://waffle.io/mozilla/fxa?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Issues for 57 release.]
|
|
*As of Sept. 5th, there were only a handful of "crouton" bugs remaining. Confidence % reflects where we were at on Sept. 5th. By week of Sept 11th, they were all finished! Confidence will be updated to 100% at next team review on Sept. 18th.
*Done!
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-130:%20Crouton%20Flow Crouton Flow Burndown Chart]
|-
|-
Line 43: Line 43:
|align="center"|75%
|align="center"|75%
|align="center"|90%
|align="center"|90%
|align="center"|
|align="center"|100%
|align="left"|
|align="left"|
|
|
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.]
*[https://waffle.io/mozilla/fxa?milestone=FxA-131:%20Q3%20 Quality related P1s that we’ve identified to fix in Q3.]
|
|
*Good progress has been made on the Quality P1s. Nearly at 50% closure, the goal for this OKR.
*Done!
*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]
**One is active: [https://github.com/mozilla/fxa-content-server/issues/4863 Issue 4863: Add descriptions to Choose What to Sync]
**A couple were moved to the backlog: [https://github.com/mozilla/fxa-content-server/issues/5009 Issue 5009: Only show "email verified" on /connect_another_device if the user actually verfied their email.] and [https://github.com/mozilla/fxa-content-server/issues/5196 Issue 5196: Sign-up/in flow: Don't ask to connect a mobile device when you started flow on mobile]
 
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-131:%20Q3%20Quality Quality P1s Burndown]
|-
|-
Line 63: Line 58:
|align="center"|40%
|align="center"|40%
|align="center"|0%
|align="center"|0%
|align="center"|
|align="center"|0%
|align="center"|
|align="center"|
|
|
Line 79: Line 74:
|align="center"|95%
|align="center"|95%
|align="center"|90%
|align="center"|90%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|
|
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
Fixes a problem with getting marketing newsletter opt-in data over to Salesforce.
|
|
*Not sure if the fix is working. Maybe the situation it fixed was small numbers and just not noticeable. We should be able to go through the flow ourselves and have Ben verify.  
*Not sure if the fix is working. Ryan is going to put together a test plan to confirm it.  
|-
|-
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
|rowspan=2| 2. To have improved the quality of the Firefox Account experience on mobile.
Line 95: Line 90:
|align="center"|55%
|align="center"|55%
|align="center"|50%
|align="center"|50%
|align="center"|
|align="center"|50%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Line 101: Line 96:
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
*[https://mozilla.invisionapp.com/share/76CPM7AC2#/screens/240561291_Desktop-_Connect_Another_Device Proposed mock up]
|
|
*A little bit of code needs to land. Need to land the copy and set things up in LeanPlum.
*Bug to set up a feature flag for it.
 
*Should be able to get into 9.1 and do an A/B test with the beta users.
*Probably won’t be able to declare this a success within this quarter.
|-
|-
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
| align="left"|2.2 Complete 80% of Q3 mobile bugs.
Line 110: Line 106:
|align="center"|60%
|align="center"|60%
|align="center"|65%
|align="center"|65%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="left"|  
|align="left"|  
Line 120: Line 116:
*[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]]  
*[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.
*70% of the 80% are done. Probably won’t reach 80%, but confident that we’ll be close.
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
*[https://waffle.io/mozilla/fxa/metrics/burndown?milestone=FxA-132:%20Q3%20Mobile Mobile Quality Burndown Chart]
|-
|-
Line 130: Line 126:
|align="center"|25%
|align="center"|25%
|align="center"|0%
|align="center"|0%
|align="center"|
|align="center"|0%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Allow users to test out device pairing. This does not necessarily mean that QR codes are used.
*Allow users to test out device pairing. This does not necessarily mean that QR codes are used.
*Feature doc and Issues coming soon.
*Feature doc and issues coming soon.
|
|
*Saw movement on the bug with Android camera not auto-focusing, but bug has recently been re-prioritized from P1 to P2.
*Not going to happen this quarter.
*This KR is about device pairing. What we tried with QR code hasn't worked out.
|-
|-
| align="left"|3.2 Ship secondary email.
| align="left"|3.2 Ship secondary email.
Line 144: Line 141:
|align="center"|90%
|align="center"|90%
|align="center"|90%
|align="center"|90%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|
|
Line 154: Line 151:
**[https://github.com/mozilla/fxa-bugzilla-mirror/issues/341 Issues 341: Detect when account email has changed, and update local state to match]
**[https://github.com/mozilla/fxa-bugzilla-mirror/issues/341 Issues 341: Detect when account email has changed, and update local state to match]
|
|
*Shipped
*Android side is close to being done.
*Shaking out the downstream bugs in terms of getting the devices to update themsleves. That’s browser work that we don’t have a lot of control over.  
*Pretty confident this one is going to happen.
*Grisha is working on Android piece.
*We should be able to wrap up the server 2 side bugs (500 errors).
*Still confident we an get it out the door.
*Getting ready to test again.
|-
|-
| align="left"|3.3 Land support for relier encryption keys.  
| align="left"|3.3 Land support for relier encryption keys.  
Line 165: Line 162:
|align="center"|75%
|align="center"|75%
|align="center"|75%
|align="center"|75%
|align="center"|
|align="center"|80%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Relier encryption keys  
Relier encryption keys  
|
|
*Focusing on completing pieces for crypto review
*Crypto consultant started today.
*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]
*[https://github.com/mozilla/fxa/issues/245 Issue 245: Prototype key support api for Firefox Notes]
|-
|-
Line 180: Line 176:
|align="center"|75%
|align="center"|75%
|align="center"|75%
|align="center"|75%
|align="center"|
|align="center"|90%
|align="center"|
|align="center"|
|align="left"|
|align="left"|
Implementation of Amplitude
Implementation of Amplitude
|
|
*Played with the test data, and it looks good.  
*Feel good about having data in place in time for the training.
*Working on minor changes to remove duplicate properties.
*Logging 2.0 is sending the data over.
*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.
*Should be able to start doing the backfill using the same process.
 
|-
|-
|}
|}
Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1180693"