Planning process
We track our work with a hierarchy of GitHub issues, connected via Githubs sub-issue feature: Epics, Features, and Tasks. Understanding this structure makes it easier to find something to work on and to see how a given change fits into the bigger picture.
Each issue type has its corresponding kind/plan-* label, so you can browse the current work
directly on GitHub using the filter links below.
Project Board
You can see what we are working on, which features are planned to be included in the next release and what tasks are up for grabs, on our GitHub project board.
Task
A Task is a concrete unit of work that moves a Feature forward. A good Task provides enough context for someone to pick it up and deliver it and has its own acceptance criteria. Each Task is assigned to a single contributor who is responsible for delivering it, though they may collaborate with others. Please only assign yourself after coordinating with the project maintainers on the issue or in the Slack channel.
Feature
A Feature is a functional, often times user-facing unit of work that lives under a single Epic. Unlike an Epic, a Feature is never perpetual: it defines acceptance criteria and is closed once those criteria are met (not just when the tasks that happen to be defined at the time are complete). Where applicable, a Feature may include mockups or design notes. Each Feature has an owner who shepherds its delivery and decides who takes on its sub-tasks.
Epic
An Epic represents a large, ongoing area of work, for example, a complex user story or a core functional area of the project. Epics may be long-lived and are intentionally high-level: they capture what we want to achieve and why, without prescribing implementation details.
See Also
Feedback
Was this page helpful?
Thank you for your feedback!
We're sorry this page wasn't helpful. If you have a moment, please share your feedback so we can improve.