Okay, here’s the latest…
Unfortunately, we’re down a team member. Dmitry N., who was the primary owner for keycard issues in status-react, will no longer be working with us.
We’re looking to backfill his position, but in the meantime, we need to plan on moving ahead with the team we have.
So we held a call to get alignment on the remaining v1 must-haves. Trail of Bits provided us with their final report this week, which means we now have a complete picture of work remaining.
Luckily, getting alignment on the remaining scope was easy. This spreadsheet (internal only - sensitive) now offers the best view of our v1 backlog.
- 28 items are must-haves ()
- 10 keycard; 7 security issues; 11 core (ENS, onboarding, misc. bugs, etc.)
- 9 in progress
- 2 owned by bounty contributors; 7 by core contributors
- 10 addtl nice-to-haves; 5 being worked on by contributors
We’ve been dutifully filling out planning poker spreadsheets over the past few weeks, though I’d say the data has been too inconsistent to come up with an accurate translation for points : time. I’m still going to make sure we have estimates for all the feature work in this list + will offer a fuzzy timeline once I do.
At this moment, I don’t think it would be smart for us to aim for a pre-Christmas release date—though it might in fact be feasible, it wouldn’t be comfortable, and I want to protect all of our sanity.
Edit: I want to add - if we target mid-December to have this scope completed, we could spend the second half of December dogfooding. I really like the idea of having buffer for testing, and it’s only a couple of weeks difference.
Please let me know if there are any questions!