bughelper idea: buglog

[Daniel Holbach]

Hello everybody,

I'm CCing the BugSquad on this topic as this might change and improve
our triage workflow soon.

Please give us input on the idea below. We had a session about it here
at UDS and I did some initial hacking on it at
https://code.launchpad.net/~bughelper-dev/buglog/main

At the moment we envision this as a Firefox plugin, which would open a
pop-up after you changed a bug and asked you to 
      * add a comment about what you did
      * put your reply into the categories "everything's ok with the bug
        now", "it'd be nice if somebody checked what I did" or "I had no
        clue what to do with the bug".


Am Dienstag, den 24.04.2007, 00:29 +0200 schrieb Henrik Nilsen Omma:
> I've been mulling over for a while a new feature of bughelper that would 
> help each person structure their bug triaging better and learn from others.
> 
> Developers and experienced triagers generally know how to deal with any 
> given bug. They either know  package well enough to be able to move the 
> bug on to its next stage They may know how it should be fixed and assign 
> it to themselves or someone else, they recognise that it needs more 
> info, that it belongs to a different package, that it should be moved 
> upstream, etc. Failing all that they will know who else on the team 
> would know better and ask. A developer will very rarely look at a bug 
> and just say 'I dunno, I give up' and walk away.
> 
> Novice bug triagers, myself included, do this often. And frequently it 
> is the right thing to do. There are certain bugs that I simply don't 
> know where to start working on. It may have all the right log files 
> attached and thus not need any more information. I can recognise some 
> characteristic traits in ubiquity log files, but other times I simply 
> don't know what to make of it. The best use of my time in that case is 
> probably to skip it (or spend half a day reading code and programming 
> text books for that one bug). By putting it aside I can move on to other 
> bugs where I can be more useful and leave this one to someone more 
> experienced. But, I would like to note that fact down somewhere, and 
> adding an 'I don't know' (followed by several 'me too don't know', just 
> creates noise).
> 
> When I was doing bulk triage of ubiquity I would make a list of the 
> mysterious bugs, group them to the best of my ability and send them off 
> in a batch by email to Colin. I would make special note of bugs that 
> looked like a new issue that he should know about or that were 
> noteworthy in some other way. It would be good to have a standard way of 
> doing this without everyone emailing or pinging the core developers 
> every day.
> 
> I suggest an approach to this in this spec: 
> https://wiki.ubuntu.com/BugHelper/BugLog


At the moment we're trying to gather use cases and ideas for this. So
please don't be shy and add your thoughts on this thread. Sky's the
limit.

Have a nice day,
 Daniel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20070508/2bce7981/attachment.sig>