mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Cooper <jason@lakedaemon.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Rob Landley <rob@landley.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paul Bolle <pebolle@tiscali.nl>,
	devel@driverdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [patch] Documentation/SubmittingPatches: Reported-by tags and permission
Date: Tue, 28 Oct 2014 12:58:27 -0400	[thread overview]
Message-ID: <20141028165827.GG15252@titan.lakedaemon.net> (raw)
In-Reply-To: <20141028090451.41ed6aad@lwn.net>

On Tue, Oct 28, 2014 at 09:04:51AM -0400, Jonathan Corbet wrote:
> On Fri, 14 Feb 2014 12:30:01 +0300
> Dan Carpenter <dan.carpenter@oracle.com> wrote:
> 
> > -If this patch fixes a problem reported by somebody else, consider adding a
> > -Reported-by: tag to credit the reporter for their contribution.  Please
> > -note that this tag should not be added without the reporter's permission,
> > -especially if the problem was not reported in a public forum.  That said,
> > -if we diligently credit our bug reporters, they will, hopefully, be
> > -inspired to help us again in the future.
> > +The Reported-by tag is to give credit to people who find bugs and report them.
> > +Please note that if the bug was reported in private, then ask for permission
> > +first before using the Reported-by tag.
> 
> As the guy who wrote the original text, I think this is an
> improvement...but can we get a version that retains the motivation for
> crediting bug reporters in the first place?

At the risk of upsetting the apple cart, I'd prefer we downplay anything
that walks down the path of gamification (by focusing on credit).

As best anyone has ever explained it to me, the Acked-by, Reviewed-by,
etc are there to impart information regarding a specific commit.  In the
event that a commit is fingered in a bisect, you have a much better list
of names to Cc, instead of just the maintainer from MAINTAINERS and the
author from the top of the offending file.  The author has often moved
on, and the maintainer may not have been around for the bugfix.

I know Greg has spoken out against gamification before, and I also
understand the desire to encourage bug reporters.  Perhaps I should just
suggest the following:

"""
The Reported-by tag helps us maintain contact info for people with
intimate knowledge of a commit or a bug fix.  Please seek the reporter's
permission before adding the tag to the commit.  That said, if we
diligently credit our bug reporters, they will, hopefully, be inspired
to help us again in the future.
"""

It's most likely ok here since it's rather hard to manufacture a list of
bugs in order to inflate ones count of Reported-by's.  Unlike S-o-b,
Ack's, etc.

thx,

Jason.

  reply	other threads:[~2014-10-28 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 12:31 [PATCH] staging: r8188eu: default to "y" in Kconfig Paul Bolle
2014-02-11 12:53 ` Dan Carpenter
2014-02-11 13:01   ` Paul Bolle
2014-02-11 13:17     ` Dan Carpenter
2014-02-13 23:22       ` Paul Bolle
2014-02-14  9:30         ` [patch] Documentation/SubmittingPatches: Reported-by tags and permission Dan Carpenter
2014-02-14 23:34           ` Randy Dunlap
2014-10-28 13:04           ` Jonathan Corbet
2014-10-28 16:58             ` Jason Cooper [this message]
2014-10-28 17:41               ` Jonathan Corbet
2014-10-29 10:01             ` [patch v2] " Dan Carpenter
2014-10-29 12:57               ` Jonathan Corbet
2014-10-29 15:50               ` Rob Landley
2014-02-12  0:09 ` [PATCH] staging: r8188eu: default to "y" in Kconfig Martin Walch
2014-02-12  0:25   ` Paul Bolle
2014-02-12  0:37     ` Paul Bolle

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=20141028165827.GG15252@titan.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=rob@landley.net \
    /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

all inboxes | Powered by JetHome®