Firefox/Push/Progress Report/2017Q2

From MozillaWiki
Jump to: navigation, search

June 30, 2017

Q2 OKR Progress

Objective Key Result Confidence Features Notes
Apr 5 Apr 19 May 3 May 17 May 31 June 15 June 30 Score
1. Create a process for working with partners that enables them to implement push with confidence. 1.1 Partner endpoint ready for production deployment 50% 50% 50% 50% 55% 65% 55% .5

Load test stage autopush partner endpoint

  • Major part of this that remains is the load testing.
  • Need to get certs set up for partners and write up a short document explaining this to partners.
  • Should already have this done, as we just released 54.
1.2 Preliminary partner run book available for external partners that defines quality of service, points of contact, requirements for what partners need to have in place 50% 50% 50% 67.7% 67.7% 75% 67.7% .75

Preliminary Partner Run Book

  • Pretty much done. Not worried about this. Only requires a few small edits. Needs to go to Bryan for review.
2. Reduce costs to maintain Push. 2.1 Report generated twice a month for status email that includes AWS resource cost per-user, and cost of service mis-use/abuse 50% 50% 50% 30% 20% 20% 20% .3 KPI Metrics Logging Statement
  • Still discussing where our data is. Talking about getting a dump of all the data (entire set) so that the queries can be run. We’ll try to do all the work we can get done on our side.
  • Some of the queries need longer term analysis.
  • Skipping spark data pipeline stuff and going straight to redshift.
  • We’re farther along than we’ve been.
2.2 Four code refactor issues completed and obsolete legacy code removed to improve quality of code and pay down technical debt 50% 50% 60% 60% 75% 85% 100% .75
  • 3 of 4 are finished. Working on the last one.
  • 75% of the refactor for object reinitializers has been completed.
3. Thrill our developers! 3.1 Additional bridge API methods provided to help the client team understand errors they are receiving on the server side. 50% 100% 100% 100% 100% 100% 100% 1.0
3.2 Release improvements to Assist libraries for subscription providers. (pywebpush & vapid to support latest Draft / update test pages to use latest Drafts) 50% 50% 65% 90% 90% 100% 100% .75
  • Holding steady.
3.3 Q2 Blog Post about "Expiring Endpoints" Debugging WebPush published 50% 50% 90% 90% 90% 100% 100% .75 Debugging Web Push in Mozilla Firefox Blog Post
  • Still hoping to increase the number of people who have seen and read it.
4. Understand how developers / clients use Push. 4.1 Dashboard created that shows the metrics described on Issue 56 50% 75% 70% 75% 75% 40% 100% .75 Uptime Dashboard
  • Data pipeline is undergoing improvements and is unavailable for dashboards in the short term.
4.2 Push Docs and Specs reviewed (update for latest changes & pull in new library updates) 50% 50% 50% 50% 60% 90% 100% .75
  • Pending a final pass to make sure everything is covered and waiting for Phil’s final refactor to be completed.
4.3 Push usage of third-party libraries on GitHub is logged and verified. 50% 50% 52% 50% 80% 100% 100% .75