Difference between revisions of "StoryBoard"
(→Agenda) |
(→Agenda) |
||
| Line 21: | Line 21: | ||
'''Urgent Items''' | '''Urgent Items''' | ||
| − | * | + | * StoryBoard WebClient no longer updating, requires: |
| − | ** https://review.openstack.org/#/c/ | + | ** https://review.openstack.org/#/c/114383/ |
| − | ** https://review.openstack.org/#/c/ | + | ** https://review.openstack.org/#/c/114597/ |
'''Discussion topics''' | '''Discussion topics''' | ||
| Line 39: | Line 39: | ||
* Aishwarya | * Aishwarya | ||
* Krotscheck | * Krotscheck | ||
| + | ** On Honeymoon | ||
* Maxime | * Maxime | ||
* Nikita | * Nikita | ||
Revision as of 20:02, 15 August 2014
Storyboard is a task tracker for OpenStack.
Vision & Roadmap
Meeting
Weekly on Mondays at 15:00 UTC in #openstack-meeting
Agenda
Urgent Items
- StoryBoard WebClient no longer updating, requires:
Discussion topics
- Subscription and notification frameworks, libraries, queues. Which are we going to use?
MVP 1.1
- Search (krotscheck, nkonovalov)
- Launchpad Data Import (mordred)
- Subscription (nkonovalov, ish__, krotscheck)
- Project Groups (krotscheck)
- Tags (nkonovalov)
- Emails (tbd)
Ongoing work (In alphabetical order):
- Aishwarya
- Krotscheck
- On Honeymoon
- Maxime
- Nikita
- Thierry
- Still TODO: Team/Group requirements gathering (ttx)
- Yolanda
Open Discussion
Last Meeting
""From last week""
- Team/Group requirements gathering (ttx).
- Comments as a primary resource for searching (NikitaKovalov)
- Transfer permissions from etherpad to specs (krotscheck)
- StoryBoard Puppet Module (krotscheck)
Specs
- https://review.openstack.org/#/c/97254/
- https://review.openstack.org/#/c/97211/
- https://review.openstack.org/#/c/95307/
- https://review.openstack.org/#/c/103106/
Ongoing work (In alphabetical order):
- Aishwarya
- Krotscheck
- Maxime
- Nikita
- Thierry
- Yolanda
Open Discussion
Other doc
- 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:
Misc
- IRC channel: #storyboard on freenode
- Technical documentation: http://ci.openstack.org/storyboard/
