Peter Huene (Dec 01 2022 at 02:02): Peter Huene (Dec 01 2022 at 02:02):I'll be filing a stream of new issues soon on https://github.com/bytecodealliance/registry to add to a github project kanban so we can track progress towards the user stories that comprise the MVP (noted that what's considered "in" is still flexible, but some are _clearly_ table stakes).
My thoughts here are having a "story" issue that encapsulates part of one (or more since there's overlap) top-level user stories from the user story document; some stories may depend on other stories. An example story issue would be "authoring a component from Rust using the registry", which obviously depends on a lot of pieces in place to work. Story tasks will link their task dependencies.
Then I'll have task issues that are discrete, actionable implementation work, which may depend on other tasks to complete. Given GitHub doesn't really track issue dependencies (extensions like Zenhub offer it, but let's stick to vanilla GitHub projects for now), I probably won't track these intra-task dependencies explicitly in the issue like we will for stories.
I think this is a decent basis to start from, but I'm certainly not married to this approach. How does everyone else feel about it?
Peter Huene (Dec 02 2022 at 01:33):Okay, I've filed the initial set of issues, feel free to add issues for what's being worked on or will be soon; the GitHub project tracking the issues (https://github.com/orgs/bytecodealliance/projects/7) isn't yet public as I don't have access to make it public
Peter Huene (Dec 02 2022 at 01:36):Okay, the project is now public (thanks Alex!)
Peter Huene (Dec 02 2022 at 01:54):I'll be updating the story issues with links to dependent tasks when I get the chance (I'm out tomorrow and Monday)
Last updated: Nov 22 2024 at 16:03 UTC