670
edits
Firefox/Accounts/Progress Report/2017Q3: Difference between revisions
Jump to navigation
Jump to search
Firefox/Accounts/Progress Report/2017Q3 (view source)
Revision as of 00:11, 24 August 2017
, 24 August 2017entered the rest of the OKR updates
(entered 2.1, 2.2) |
(entered the rest of the OKR updates) |
||
| Line 142: | Line 142: | ||
|align="center"|75% | |align="center"|75% | ||
|align="center"|50% | |align="center"|50% | ||
|align="center"| | |align="center"|25% | ||
|align="center"| | |align="center"| | ||
|align="center"| | |align="center"| | ||
| Line 150: | Line 150: | ||
*Feature doc and Issues coming soon. | *Feature doc and Issues coming soon. | ||
| | | | ||
* | *Not confident that we’ll have QR codes ready to test | ||
* | *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. | | align="left"|3.2 Ship secondary email. | ||
| Line 158: | Line 162: | ||
|align="center"|80% | |align="center"|80% | ||
|align="center"|90% | |align="center"|90% | ||
|align="center"| | |align="center"|90% | ||
|align="center"| | |align="center"| | ||
|align="center"| | |align="center"| | ||
| Line 170: | Line 174: | ||
**[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 | ||
* | *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. | ||
* | *Grisha is working on Android piece. | ||
*Still confident we an get it out the door. | |||
|- | |- | ||
| align="left"|3.3 Land support for relier encryption keys. | | align="left"|3.3 Land support for relier encryption keys. | ||
| Line 178: | Line 183: | ||
|align="center"|70% | |align="center"|70% | ||
|align="center"|75% | |align="center"|75% | ||
|align="center"| | |align="center"|75% | ||
|align="center"| | |align="center"| | ||
|align="center"| | |align="center"| | ||
| Line 185: | Line 190: | ||
Relier encryption keys | Relier encryption keys | ||
| | | | ||
* | *Waiting to engage crypto consultants. | ||
*[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 192: | Line 197: | ||
|align="center"|75% | |align="center"|75% | ||
|align="center"|75% | |align="center"|75% | ||
|align="center"| | |align="center"|75% | ||
|align="center"| | |align="center"| | ||
|align="center"| | |align="center"| | ||
| Line 199: | Line 204: | ||
Implementation of Amplitude | Implementation of Amplitude | ||
| | | | ||
*Amplitude | *Getting help from Amplitude to move forward | ||
* | *Still discovering new things | ||
* | *Should have environment with train-95 that we can send events to. | ||
|- | |- | ||
|} | |} | ||