eld120
commented
1 year ago I'd like to introduce the idea of writing issues as user stories as a way to define what we want to accomplish. I think a lot of the user stories will be about us (people writing/running programs) and some desired state that we're seeking. It's pretty typical to break larger ideas down into smaller/very small tickets that can be assigned or picked up by individuals on the team.
The purpose of the small scope of work is to make it easy to figure out what needs to be done and easy to figure out when the program/code is behaving as expected and it's therefore time to push to Github. I'm wondering if we were to start with building out issues, folks could then pick up issues and work on them. I guess I'm wondering if we could increase participation by building out an epic.
idk I'm open to ideas
edit: I also want to mention that I'm unsure if ideas like this fall into the "hey we should do this" category or if it's one small detail too far.
As a developer/admin I want a small manageable and quantifiable amount of work to be contained within an issue/ticket/task so that I can understand who the user is and what they are trying to accomplish.