Incomplete with no response >30 days

Jordan Mantha mantha at
Tue May 27 20:38:41 BST 2008

On Tue, May 27, 2008 at 12:01 PM, Henrik Nilsen Omma <henrik at>

> sense at wrote:
> > If you just say in
> > capitals at the beginning of each workflow report: "WORKFLOW BUG" I
> > think we won't touch it.
> Simple, but probably effective. It may prove to be the best option as we
> are having difficulty getting consensus on using privacy, states or
> assignment.
> If each wokflow bug started with a standard text blob pasted from a wiki
> page they could be self-explanatory. That should take a few seconds to
> copy and paste and could even be added later if it was left out. It
> could link to a wiki page with a longer explanation.
> These bugs would continue to appear in default searches and so it would
> continue to crop up on working lists of triage teams. OTOH many such
> lists are generated with bughelper (like the bugday lists), which can
> easily be taught to leave out these bugs.

While I do think this could be a good "solution", why not just educate
people on what kinds of bugs are out there? I have great confidence in the
learning abilities of Ubuntu contributors and I think it's often better to
educate rather than ignore/hide/obfuscate. From what I've seen almost all
cases where we've had problems is when people didn't know any better. That
sounds like an education and community integration problem to me. Triaging
is a part of the Ubuntu development process and as such triagers and
packagers should be working together in a common space and with common
goals. Triaging is a subset of development activities and so triagers should
be within that community and should feel like they are.

I believe it was only when triaging was split off into it's own entity
because of scaling issues and the two communities (triagers and packagers)
grew apart that we ran into problems. Can we perhaps work to bring them back
together more? If I were a budding triager (as I was once upon a time) I
would want to know about *all* kinds of bugs and how they're used and to
talk with packagers about how they do what they do. Would something like a
mentoring program be feasible? Perhaps triagers who have similar working
hours to a developer/packager/advanced triagers can work with them on the
education process. Perhaps also weekly Triager Education classes could be
done to go over issues like workflow bugs. I don't expect things like
workflow bugs to be obvious to new triagers, but I *do* expect them to have
a willingness to learn because that is at the heart of our community.

-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Ubuntu-bugsquad mailing list