[Compcomm] Bug tracker

[Mike Dransfield]

I am still sifting through emails so sorry if this is
covered already.

I personally have no problem with the bug tracker
being hosted wherever and on whichever domain you
choose.

I don't personally have a problem with putting core
bugs in there because a lot of us are capable of fixing
those bugs, and if we cannot then we can make sure
that David has an account there (or bugs are copied to
fdo - even just with a link to our bug report).

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.

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.

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.

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.

I doubt David would be interested in closing the fdo bug
tracker in favour of ours, but he may well be interested
in using ours too if we make it easy for him (although
you would have to ask him).