Hi All,
Julie and I are experimenting with using the minutes from our sprint
planning meetings as a kind of "preview" version of the "What's New in FxA"
emails. Instead of looking back on the things we shipped last train, can
we look forward to the things that are coming up in the next one?
In reviewing our Q2 OKRs this week, we highlighted the following:
-
Now that we have a first working prototype of OAuth reliers using
encryption keys via a webextension API, the next important steps for OKR #1
are:
-
Tighten up the proposed protocol documentation and get some formal
review from security-minded folks.
-
Two of our multi-device-related KRs are at risk: we cannot measure
second-device signin success rate until we land code in our mobile sync
clients, and the volume of second-device connections seems to be dropping
due to first-run page changes that are outside of our control. The next
important steps for OKR #2 are:
-
Prioritize landing the iOS deep-linking patch, since that client is
on a faster release schedule and will let us get some baseline metrics.
-
Ensure that we understand why the volume of second-device connections
is dropping, and decide what we can do about it.
-
Our three email-deliverabilty metrics have improved since the start of
the quarter, and we're starting to ship add-another-email in train-87, so
we've got higher confidence that we can hit OKR #3. The next important
steps there are are:
-
Obtain copies of the desktop Outlook versions used by email-on-acid,
to further debug spam filtering issues.
-
Finalize the change-email feature doc, and the security review
thereof.
-
Our DevOps metrics from OKR #4 are tracking well, with this quarter's
deploys running smoothly and the bug backlog already completed past 30%.
We'll continue pushing on dockerflow in both dev and prod deploys.
Based on the above and the items we flagged as P1, here's what will be in
the everything-went-according-to-plan version of train-88 in two weeks time:
-
Feature-flagged db support for chaning primary email address.
-
API support for sending and consuming signin codes in the SMS install
link.
-
Support for emojis in device names.
-
A completed feature doc for the SMS deep-link work.
-
Finalized protocol and prototype for OAuth key support.
-
The ability to deploy docker images from private repos.
-
Working loadtests for the auth-server.
-
Working verification reminders, after we disable replication on that
table.
-
The deeplinking patch landed (or ready to land) for Firefox on iOS.
Naturally some things will change over the next two weeks, but I think
it'll be interesting to sanity-check the above list and then to compare it
to what actually gets shipped in practice.
So, does this list seem like too much? Is it missing anything?
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
