Open Stack

Hey everyone, during the meeting today we observed folk who are active
contributors were filing bugs without triaging them.

Triage is a team responsibility : we need to triage bugs that folk who
aren't familiar with TripleO file, but for bugs *we* file, it just
makes work for someone else on the team if they are filed without
doing triage. It's ok if you don't want to triage other peoples bugs -
thats fine, the team as a whole can handle it, but please don't /add/
work for other people when only a few seconds thought as you file the
bug will avoid that.

Triage specifically is:
 - assigning an importance
 - putting any obvious tags (e.g. 'baremetal') on it
 - setting status to 'triaged'.

As contributors, you can skip 'confirm' and go straight to triaged -
unless you believe the bug isn't real, in which case why are you
filing it? :)

The bug triage team for tripleo is https://launchpad.net/~tripleo -
and as all our code review etc is managed in Gerrit, there is no
reason why we can't accept pretty much anyone that is contributing to
TripleO into the team. I think the bar to being a bug supervisor
should be pretty low - e.g. show some familiarity with TripleO,
current program goals etc.

For reference: https://wiki.openstack.org/wiki/BugTriage - this isn't
100% what we're doing but it's not far off, with two key differences:
 - we don't use wishlist: things we'd like to do and things that we do
wrong are both defects; except for regressions the priority of the
work is not affect by whether we've delivered the the thing or not,
and using wishlist just serves to flatten all the priority of all
unimplemented things into one bucket: not helpful.
 - we use triaged, not just 'confirmed'.

Thanks!

-Rob



-- 
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud