public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: linux-kernel@vger.kernel.org
Subject: Tracking and crediting bug reporters
Date: Mon, 12 May 2008 11:27:52 -0600	[thread overview]
Message-ID: <4388.1210613272@vena.lwn.net> (raw)

Several members of the Linux Foundation's Technical Advisory Board recently
got together with Andrew Morton to talk about kernel quality issues.  One
of the things which came out of that meeting was a desire to improve
incentives for people who report bugs.  Clearly, actually fixing those bugs
would qualify; nobody has lost sight of that.  But it was suggested that
the creation and publication of statistics on bug reporting would also
help.

One way to do this might be for Andrew (being the only one who actually
reads every message posted on the list) to keep a spreadsheet along with
everything else he does.  That idea did not go over very well.

So here's what we would like to try instead.  Whenever somebody sends up a
patch fixing a reported bug, the name of the person who reported the bug
would be immortalized with this tag:

	Reported-by: A. Bug Reporter <email@goes.here>

In particular, reporters who work with the developers toward the resolution
of the bug should be thanked in this way.  If we wanted to take things
further, perhaps we could add a Bisected-by: tag for really hard-core
helpers. 

If these tags go into the commit messages in any sort of consistent way, it
should be possible generate the usual sort of statistics from them.  I'll
then happily publicize them next to the traditional lists of people who are
adding new bugs.  The result will certainly be fame, fortune, and job
offers for the people at the top of the list.  Or something like that.

If the rest of the community is agreeable, it would be nice to make an
immediate start on this; it's not yet too late to get reasonable data for
the 2.6.26 kernel, and to have the habits well ingrained for 2.6.27.

Thoughts?

jon

             reply	other threads:[~2008-05-12 17:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12 17:27 Jonathan Corbet [this message]
2008-05-12 17:48 ` Tracking and crediting bug reporters Cyrill Gorcunov
2008-05-12 18:20 ` Alan Cox
2008-05-12 20:52   ` David Miller
2008-05-12 21:08     ` Alan Cox
2008-05-13 10:51       ` Andi Kleen
2008-05-13 10:50         ` Alan Cox
2008-05-13 16:36           ` Jeff Garzik
2008-05-12 20:54   ` Jiri Slaby
2008-05-12 21:11     ` Alan Cox
2008-05-12 21:59       ` Rafael J. Wysocki
2008-05-12 18:27 ` Rik van Riel
2008-05-12 19:11 ` Rafael J. Wysocki
2008-05-13 10:28 ` Adrian Bunk
2008-05-16 16:35   ` Jonathan Corbet
2008-05-17 22:53     ` Adrian Bunk
2008-05-17 23:18       ` Rene Herman
2008-05-18 19:51       ` Jonathan Corbet
2008-05-13 15:10 ` Rene Herman
2008-05-14 17:30   ` Stefan Richter
2008-05-21 10:41 ` Pavel Machek
2008-05-21 13:34   ` Johannes Weiner
2008-05-21 13:46     ` Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2008-05-15  8:02 Roland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4388.1210613272@vena.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox