I think this is a great idea! This would really help with getting more eyes on StoryBoard. I think a lot of people haven't touched it much in the last year or two and aren't aware of all of its capabilities at this point and this would be a great way to get people up to speed.
This use case (cross project efforts) is also what StoryBoard was built for after all :) If anyone has questions about StoryBoard or feedback, please join our channel #storyboard! Thanks Doug! -Kendall (diablo_rojo) On Fri, Jan 12, 2018 at 12:38 PM Doug Hellmann <d...@doughellmann.com> wrote: > Since we are discussing goals for the Rocky cycle, I would like to > propose a change to the way we track progress on the goals. > > We've started to see lots and lots of changes to the goal documents, > more than anticipated when we designed the system originally. That > leads to code review churn within the governance repo, and it means > the goal champions have to wait for the TC to review changes before > they have complete tracking information published somewhere. We've > talked about moving the tracking out of git and using an etherpad > or a wiki page, but I propose that we use storyboard. > > Specifically, I think we should create 1 story for each goal, and > one task for each project within the goal. We can then use a board > to track progress, with lanes like "New", "Acknowledged", "In > Progress", "Completed", and "Not Applicable". It would be the > responsibility of the goal champion to create the board, story, and > tasks and provide links to the board and story in the goal document > (so we only need 1 edit after the goal is approved). From that point > on, teams and goal champions could collaborate on keeping the board > up to date. > > Not all projects are registered in storyboard, yet. Since that > migration is itself a goal under discussion, I think for now we can > just associate all tasks with the governance repository. > > It doesn't look like changes to a board trigger any sort of > notifications for the tasks or stories involved, but that's probably > OK. If we really want notifications we can look at adding them as > a feature of Storyboard at the board level. > > How does this sound as an approach? Does anyone have any reservations > about using storyboard this way? > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev