This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2k
Sprint Meetings
Amy Lindburg edited this page Mar 20, 2015
·
1 revision
Major decisions affecting the Machine Roadmap are discussed during these fortnightly meetings.
The expected outcome of a Sprint Meeting is to review (or define) the next Milestone and organize work for the 2-week Sprint.
Title | Role |
---|---|
Maintainers | Maintainers drive the Sprint meetings. |
Contributors | Contributors provide feedback, offer advice, and make proposals. |
Contributors are defined as those who have demonstrated significant interest in the project (via substantial code contributions or major usage), and Partners.
Maintainers of other Docker subsystems (i.e., Engine, Distribution, …) are welcome to attend Machine Sprint Meetings.
- Maintainers review the Machine Roadmap and decide which items to target for the milestone. These are recorded as "Release Goals" on the Project Page.
- Maintainers triage the Community backlog to identify issues that correspond to the Release Goals. Placeholder issues are created so that all Release Goals are represented in the GitHub Milestone.
- Milestones get reviewed during Sprint Meetings, where Contributors and other Maintainers have the opportunity to provide their feedback.
Items might be moved to different Milestones or discarded altogether based on the outcome of the meeting.
Meetings center around Project Pages, and follow this agenda:
- Review Release Goals
- Update as needed
- Ensure that there is a GitHub Issue to represent each major goal
- Review Progress
- Progress is tracked using the Machine Waffle Board, filtered by Milestone.