> After talking about the workboards in phabricator during the meeting > earlier today, I mentioned trying to figure out a way to have > workboards for more than just a single project. > > I've been futzing around with qadevel-stg today and have a proposal to > make. > > * Keep the existing projects > * Remove workboards from at least the Taskotron related projects > (libtaskotron, resultsdb, taskotron-trigger etc.) > * Create a new project named "QA Devel" which has the same workboard > columns as the libtaskotron workboard currently does.
Would "Planning" project/tag name be more self-explanatory than "QA Devel"? IIUIC, this will be a meta-project just for planning purposes. > > The "process" for getting tasks proposed and worked on would then be: > > 1. add the "QA Devel" tag to the task, putting it on the "backlog" for > that project So, which tasks should go to the backlog column, those which are likely candidates for next work? Those which I personally like to work on? Something else? > 2. If the task has enough detail to move forward, it can move to > "groomed" Is there a better word for "groomed"? I'm always imagining horses. "Triaged" is not much better, but at least it's something we're used to from bug reports. But I'd like to have something more obvious. Any ideas? "Ready"? > 3. Immediate priorities are in the "On Deck" column, in priority order > from top to bottom Could be "up for grabs", "available", "unclaimed". But "on deck" is also fine. Is there a good reason to distinguish between "groomed" and "on deck", or would it be simpler to just join them? > 4. In progress and "ready for completion" are pretty self explanatory > > > I'd also like to start a 2 week cadence again. It may go away again as > we get closer to F24 final but I think it will help organize things a > bit better. > > Thoughts? > > Tim _______________________________________________ qa-devel mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
