Description

This repo already has a lot of nice stuff to help other developers contribute. But it could be better. We will want to leverage GitHub features to help facilitate project management in an open-source, self-organizing project.

Questions

• What milestones should we create to group together issues?
• How do we want to size issues?
• What are the priorities of issues?
• How can we better standardize issues?
• How can we organize issues to give developers a better overview?

DoD (Definition of Done)

• General issue template
• Bug report template
• Issue backlog kanban board
• Issues are organized into the backlog into their categories: new, in progress, done, etc.
• Issues are sized: What is tiny, small, etc.?
• Documented issue sizing: How much work is tiny? 1h, 1d? What about the other sizes? At what size should an issue be broken into 2 or more issues?
• Issues are prioritized
• New milestone(s) are created to group together the majority of issues that don't currently have a milestone