[Bugsquad] Mailinglist and website

Martin Fitzpatrick martin.fitzpatrick at gmail.com
Wed Aug 20 21:19:55 CEST 2008


Hi folks

Just dropping out of lurk here.

>> > One thing I'm not quite sure about is making a list of people in
>> > bugsquad. First of all making such a list would make it seem harder to
>> > get into bugsquad (whereas we surely appreciate everyone joining IRC and
>> > helping a little). Second there are certainly some "core" members who're
>> > staying around quite some time but there's also quite some fluctuation
>> > and I would neither want to publish just the core members nor change the
>> > site frequently.
>> It could be created the "TOP 50 triagers" using some stats from bugzilla
>> (excluding users which are developers too).

I've helped out a few times in the past and mentioned in the IRC site
the idea of putting up a bugsquad logging system to track progress
etc. I did actually get this up and running using the KDE bugsquad
feed/mailinglist (I had it online on dyndns for a while but my config
is now messed up). Generally speaking it worked and it was possible to
track individuals contribution quite well (i.e. FiNeX is a machine :)
).

On Wed, Aug 20, 2008 at 1:19 PM, Michael Leupold <lemma at confuego.org> wrote:
> I'm not so sure about that. Many people have a tendency to "try to be the
> best". Some might close bugs prematurely to advance, others might be

I had originally planned to incorporate a combination of stats both by
desktop and by distribution but the folks at Gnome were concerned
about the issues of people being "compared" as you mention.

Saying that though it should be possible to track the "bugsquad team"
as a group fairly trivially using email addresses. This could be
implemented either using a form to submit an address to or using irc
bot to "register" - from that point on that users bugsquad
contribution is included in the team. Because the results are
aggregate it is really just a reflect of the team performance ( could
display it as a % of total bugsquad for example ).  Just a thought.
As mentioned the code to do this already exists and can be demoed once
I figure out the config issue here.

Oh and I also own the domain bugsquad.org which was either going to
host this or point to the bugsquad.kde page too :)  I could happily
leave a system running churning out these stats and them dumping them
to a wiki (or other bugsquad page) for example.  The bugzilla upgrade
makes this even simpler I imagine I would just need to take a look.

Another thought to throw out there - the regular commit digest on the
dot is quite popular in terms of people keeping up to date. I think an
equivalent for bugfixing would perhaps go down well also. I don't know
how regular it would be possible to produce this but there must be at
least one "notable" bug closed each month - either for longevity,
popularity, etc. that could be covered in a bit of detail together
with some general stats. Last time I helped out I closed a bug
relating to floppy disks ;)

This is not something I could contribute enough to keep running but
I'd be happy to help with scripting/automation side of things.

Martin


More information about the Bugsquad mailing list