mirror of
https://github.com/docker/compose.git
synced 2025-07-31 01:24:15 +02:00
Created Sprint Meetings (markdown)
parent
fb46574908
commit
61b0c69bde
32
Sprint-Meetings.md
Normal file
32
Sprint-Meetings.md
Normal file
@ -0,0 +1,32 @@
|
||||
Major decisions affecting the [Compose Roadmap](https://github.com/docker/compose/blob/master/ROADMAP.md) are discussed during these fortnightly meetings.
|
||||
|
||||
The expected outcome of a Sprint Meeting is to review (or define) the next [Milestone](https://github.com/docker/compose/milestones) and organize work for the 2-week Sprint.
|
||||
|
||||
### Who participates?
|
||||
|
||||
| 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 Compose Sprint Meetings.
|
||||
|
||||
### How does the content of a Milestone get defined?
|
||||
|
||||
1. Maintainers review the [Compose Roadmap](https://github.com/compose/machine/blob/master/ROADMAP.md) and decide which items to target for the milestone. These are recorded as "Release Goals" on the Project Page.
|
||||
2. 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.
|
||||
3. 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.
|
||||
|
||||
### What's the agenda of the meeting?
|
||||
|
||||
Meetings center around [Project Pages](https://github.com/docker/compose/wiki), and follow this agenda:
|
||||
|
||||
1. Review Release Goals
|
||||
* Update as needed
|
||||
* Ensure that there is a GitHub Issue to represent each major goal
|
||||
2. Review Progress
|
||||
* Progress is tracked using the [Compose Waffle Board](https://waffle.io/docker/compose), filtered by Milestone.
|
Loading…
x
Reference in New Issue
Block a user