- the single biggest pain and gripe for me is having to clear out the
spam every few days. Otherwise I think the bugtracker is pretty smooth.
- One incentive for action might be to compile monthly statistics on
how many bugs were opened, closed, etc, and rank number of bugs
resolved vs. who closed them; the abiWord project used to do this,
maybe they still do. As with ranking CVS commits, this is a crude and
often misleading measure of who is doing the hard work, but maybe it is
a way of motivating the competitive types among us.
- I like the comment button for adding a note to a bug which doesn't
interest the general mailing list. I have enough email to sort through
as it is. What needs to be done I think is to better document how the
bug tracker should be used. Perhaps for the comment/reply buttons a
note directly under them.
At 04:22, giovedì 28 luglio 2005, Hamish has probably written:
Some comments regarding the bug tracker.
- One incentive for action might be to compile monthly statistics on
how many bugs were opened, closed, etc, and rank number of bugs
resolved vs. who closed them; the abiWord project used to do this,
maybe they still do. As with ranking CVS commits, this is a crude and
often misleading measure of who is doing the hard work, but maybe it is
a way of motivating the competitive types among us.
Agreed!
pc
--
Paolo Cavallini
cavallini@faunalia.it www.faunalia.it www.faunalia.com
Piazza Garibaldi 5 - 56025 Pontedera (PI), Italy Tel: (+39)348-3801953
On Wed, Jul 27, 2005 at 07:22:29PM -0700, Hamish wrote:
Some comments regarding the bug tracker.
- the single biggest pain and gripe for me is having to clear out the
spam every few days. Otherwise I think the bugtracker is pretty smooth.
Interestingly the spam (with very few exceptions) doesn't arrive at
'grass5'. right? This is due to the 'bogofilter' which takes care
at grass.itc.it. Apparently bogofilter performs better that the filter
implemented for RT.
- One incentive for action might be to compile monthly statistics on
how many bugs were opened, closed, etc, and rank number of bugs
resolved vs. who closed them; the abiWord project used to do this,
maybe they still do. As with ranking CVS commits, this is a crude and
often misleading measure of who is doing the hard work, but maybe it is
a way of motivating the competitive types among us.