some suggestions regarding bug triage and UNCONFIRMED reports.

[Christian Robottom Reis]

On Wed, Mar 29, 2006 at 06:44:09PM +1100, Lex Hider wrote:
> In dealing with the UNCONFIRMED bug issue, if you look at most OSS bugzillas, 
> it is scary how many bugs are just sitting there that have been either: not 
> looked (or at least as far as the reporter knows noone has looked at it), or 
> has been confirmed by a developers comment but not set to NEW.
> 
> check out this bug for an interesting example:
> http://bugs.kde.org/show_bug.cgi?id=84953#c4
> 
> Perhaps something like products with most UNCONFIRMED bugs:
> http://bugzilla.gnome.org/page.cgi?id=reports.html
> 
> I think a really useful one would be a link to all bug reports for packages in 
> "main" (i.e. not uni/multiverse), which are UNCONFIRMED. This would have 2 
> useful effects:
> 
> 1) easy place for newbie triages to get started.
> 2) the number from this search (showing 1-25 of 1255 for example) is a useful 
> metric and we could perhaps set some short term targets (OK let's this number 
> below XXX).

Do you mean something like:

    https://launchpad.net/distros/ubuntu/+bugs?advanced=1&field.searchtext=&search=Search+bugs+in+Ubuntu&orderby=datecreated&field.status%3Alist=Unconfirmed&assignee_option=any&field.assignee=&field.owner=&field.component=1&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=

I wonder? Have you tried using the _Advanced_ link on

    https://launchpad.net/distros/ubuntu/+bugs

-- ?

> Also, something like:
> http://bugs.kde.org/weekly-bug-summary.cgi
> would also be good.
> Some useful things you can see from this page:
> * what's the net change for number of bugs in package
> * number of bugs
> * Most importantly, is the top 20 bug resolves in last 7 days. At various 
> times where I have been involved in KDE bug triaging, I have got a real kick 
> out of being number one on that list. And I have done that only through 
> closing duplicates and obsolete bugs without writing code.
> So it could be a nice little competitive thing for triagers to get involved 
> with, and perhaps we could regularly publicise the top bug closers not on the 
> ubuntu payroll

This is a great idea. We don't currently have any reports which allow
you to view changes over time with Malone (and updating the data model
to better provide for these things was discussed the previous week at
our London sprint), but I definitely see the value in them. I registered
a spec stub at

    https://launchpad.net/products/malone/+spec/weekly-bug-reports

to track thoughts and work on an initial feature to give it pratical
direction.
-- 
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125