Difference between revisions of "StoryBoard"
(→Design) |
(→Meeting) |
||
| Line 15: | Line 15: | ||
Agenda: | Agenda: | ||
| − | * | + | * MVP status (ttx) |
| + | * What to use to plan the next step (ttx) | ||
| + | * Sane design (ttx) | ||
| + | ** Add branch / landed milestone to tasks: [[StoryBoard/Task_Branch]] | ||
| + | * Crazy design (ttx) | ||
| + | ** Priorities are for the weak, let's use parallel tasklists for that: [[StoryBoard/Task_Lists]] | ||
| + | ** Statuses are for the weak, let's use tags for that: [[StoryBoard/Story_Tags]] | ||
== Design == | == Design == | ||
Revision as of 13:35, 27 February 2014
Storyboard is a task tracker for OpenStack.
Work areas
- Main Concepts (REST API)
- Technical Architecture (REST/UI decoupling)
- UI (switch to Semantic UI)
- CI/CD/onboard-guinea-pigs
The latter is driving the development milestones.
Meeting
Weekly on Thursdays at 16:00 UTC in #openstack-meeting
Agenda:
- MVP status (ttx)
- What to use to plan the next step (ttx)
- Sane design (ttx)
- Add branch / landed milestone to tasks: StoryBoard/Task_Branch
- Crazy design (ttx)
- Priorities are for the weak, let's use parallel tasklists for that: StoryBoard/Task_Lists
- Statuses are for the weak, let's use tags for that: StoryBoard/Story_Tags
Design
- StoryBoard/Task_Branch -- how we'll track backporting work and show what landed in a given milestone
- StoryBoard/Task_Lists -- how we'll let developers track what matters to them and prioritize work on a flexible way
- StoryBoard/Story_Tags -- how we could use tags to implement flexible workflows. Or not.
Alternate solutions:
