53
edits
CloudServices/Sync/OKRs 2016Q3: Difference between revisions
Added scores
No edit summary |
(Added scores) |
||
| Line 8: | Line 8: | ||
| 1.1 | | 1.1 | ||
| Measure structural integrity defects in users' bookmark trees. | | Measure structural integrity defects in users' bookmark trees. | ||
| | | 1 | ||
|- | |- | ||
| 1.2 | | 1.2 | ||
| Land fixes to the underlying defects related to the disabled, failing bookmark validation tests in TPS and enable these tests in TPS. | | Land fixes to the underlying defects related to the disabled, failing bookmark validation tests in TPS and enable these tests in TPS. | ||
| | | 0.7 | ||
|- | |- | ||
| 1.3 | | 1.3 | ||
| Deploy sync server API for batch atomic writes to production and land client integrations on Desktop. (iOS and Android need coordination) | | Deploy sync server API for batch atomic writes to production and land client integrations on Desktop. (iOS and Android need coordination) | ||
| | | 0.5 | ||
|- | |- | ||
| 1.4** | | 1.4** | ||
| Land improvements to the sync change tracker to ensure that users' bookmark changes are tracked before Sync has initialized or during a sync. | | Land improvements to the sync change tracker to ensure that users' bookmark changes are tracked before Sync has initialized or during a sync. | ||
| | | 0.5 | ||
|- | |- | ||
| 1.5* | | 1.5* | ||
| Land repair code that uploads missing bookmarks. | | Land repair code that uploads missing bookmarks. | ||
| | | 0 | ||
|- | |- | ||
| 1.6 | | 1.6 | ||
| Land validators to measure the integrity of 3 other sync data types. Integrate the validators into TPS and report defect rates via telemetry. | | Land validators to measure the integrity of 3 other sync data types. Integrate the validators into TPS and report defect rates via telemetry. | ||
| | | 0.9 / avg 0.6 | ||
|} | |} | ||
<nowiki>*Won't achieve | <nowiki>*Won't achieve | ||
| Line 41: | Line 41: | ||
| 2.1 | | 2.1 | ||
| Add affordance to Desktop context menu to send tab to connected sync devices. | | Add affordance to Desktop context menu to send tab to connected sync devices. | ||
| | | 1 | ||
|- | |- | ||
| 2.4 | | 2.4 | ||
| Add measurement to the sync ping for send tab usage. | | Add measurement to the sync ping for send tab usage. | ||
| | | 0.1 | ||
|- | |- | ||
| 2.2** | | 2.2** | ||
| Improve timeliness of sending tabs to devices using push events on Nightly Desktop, Android, and iOS. | | Improve timeliness of sending tabs to devices using push events on Nightly Desktop, Android, and iOS. | ||
| | | 0.8 | ||
|- | |- | ||
| 2.3 | | 2.3 | ||
| Land messaging to inform users of incoming tabs in Desktop (bug 1244597). | | Land messaging to inform users of incoming tabs in Desktop (bug 1244597). | ||
| | | 1 | ||
|} | |} | ||
3. Use data to help prioritize new features and fix defects in Sync | 3. Use data to help prioritize new features and fix defects in Sync | ||
| Line 64: | Line 64: | ||
| 3.1** | | 3.1** | ||
| Create a bookmark structural integrity dashboard on https://sql.telemetry.mozilla.org/. Dependent on 1.1 | | Create a bookmark structural integrity dashboard on https://sql.telemetry.mozilla.org/. Dependent on 1.1 | ||
| | | 0 | ||
|- | |- | ||
| 3.2** | | 3.2** | ||
| Create a integrity of 3 sync data types (1.6) dashboard on https://sql.telemetry.mozilla.org/ . Dependent on 1.6 | | Create a integrity of 3 sync data types (1.6) dashboard on https://sql.telemetry.mozilla.org/ . Dependent on 1.6 | ||
| | | 0 | ||
|- | |- | ||
| 3.3** | | 3.3** | ||
| Visualize send tab usage from 2.4 on https://sql.telemetry.mozilla.org/. | | Visualize send tab usage from 2.4 on https://sql.telemetry.mozilla.org/. | ||
| | | 0 | ||
|- | |- | ||
| 3.4** | | 3.4** | ||
| Measure lost data occurrences due to single device password resets, visualize on https://sql.telemetry.mozilla.org/ | | Measure lost data occurrences due to single device password resets, visualize on https://sql.telemetry.mozilla.org/ | ||
| | | 0.5 | ||
|} | |} | ||
<nowiki>**At risk but we believe we can get data in Presto or Redshift in order to make Re:Dash dashboards</nowiki> | <nowiki>**At risk but we believe we can get data in Presto or Redshift in order to make Re:Dash dashboards</nowiki> | ||