Re: co-mentor for a GSoC proposal wanted: debbugs web submission
On Fri, Mar 16, 2007 at 02:21:02PM -0700, Don Armstrong <firstname.lastname@example.org> wrote:
> So to summarize you want tags which have the ability to be mutually
That could be a part of the solution. What I believe is necessary is a
workflow for the bug, pretty much like the one with bugzilla, but this
workflow has to be defined.
Considering team work and stuff like this, an assigned status would be
good too, with possibility, like forwarded, to specify an email address
of the person dealing with the bug. That would make it clear, in teams,
if bugs are dealt with, and by whom.
Another waste of time is having to add the bug number to control
messages, which is very error prone, while most of the time, there
is only one bug treated at a time, which is in the To: or Cc: header.
I also often forget to add control@ to Cc which makes me waste some more
time to bounce the message or resend the control commands, so it would
be even greater if one could just pass control commands to the bug
directly. Simple checks could tell control commands and message apart.
The moreinfo tag is pretty much useless, because unless someone unsets
it, you don't know if a "moreinfo" bug has been answered or not. A
message from the bug submitter should untag the bug.
Something automatically tagging the bug if it has been answered by a
maintainer would also help telling which bugs are unanswered. Or
something to force the maintainer to tag confirmed or unreproducible.
Tags are not only for maintainers, but also for the submitter, and
also for people wanting to help triaging bugs. I think we should mandate
that bugs must be tagged confirmed or unreproducible or some
acknowledgement tag (ack ?).
Also, the email@example.com address should reach the bug submitter.
These are random ideas, which would improve *my* handling of bugs. I
don't know if it would suit anyone. Comments anyone ?
PS: And (stupid idea), once triaged/untriaged bugs can easily be told
appart, create an applet that would go in the notification area, and
would give a (voluntary) user a random bug from the list of untriaged
bugs that are related to the packages she uses the most for her to