[Compcomm] Bug tracker

[Kristian Lyngstøl]

On 6/22/07, Mike Dransfield <mike at blueroot.co.uk> wrote:
> The problem I have is that bug trackers require an awful
> lot of work to make them useful.  Please do not take this
> wrong, but the beryl bug tracker was not much use to
> anyone.

Nope, it wasn't as useful as it should've been..

> We need to have at least one person who is in charge of
> new bugs.  They will need to get all the information
> required and then assign the bug to the correct developer.

As this is already part of Bugzilla, it makes more sense to have
people be in charge of different components. A few people on the top
in charge of "everything" also makes sense.

Since you actually get proper mail notification of bugzilla bugs, it's
easy to have several components, maybe even one for each plugin
(re-assigning bugs filed under the wrong plugin is a minor issue
anyway).

> Is anyone up for that responsibility?  We would obviously
> need someone with technical knowledge.  I think its very
> good for someone wanting to learn because you get the easy
> bugs first and you will be able to start by fixing those.

Speaking from experience from the beryl bug tracker, which I tried
maintaining myself, it is not an easy job for a newcomer to assign
bugs.

Then he/she at least needs a lot of guidelines. It's true that it's a
good job to FIX new bugs for newcomers, but for the more obscure bugs,
it's better to have someone who knows the project well enough to know
who to assign it to.

> We should outline some basic ground rules for the bug
> maintainers as well as the developers who are assigned
> bugs.  That way we can all be clear from the start.

Seconded.

-- 
Regards,
Kristian