All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jason Cooper <jason@lakedaemon.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 13:41:35 -0400	[thread overview]
Message-ID: <20141028134135.59dbc512@lwn.net> (raw)
In-Reply-To: <20141028165827.GG15252@titan.lakedaemon.net>

On Tue, 28 Oct 2014 12:58:27 -0400
Jason Cooper <jason@lakedaemon.net> wrote:

> 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.

As I understand it, having been in the room when these tags were
developed and encouraged, was that credit was a big part of the initial
motivation.  We need more testers and bug reporters; this was a way to
give them credit for the valuable work that they do.  I still think
that's important, for whatever that's worth.

> 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.
> """

That addresses my concern, but loses the point of the initial patch:
publicly reporting a bug can be seen as implicit permission to credit the
reporter.

Thanks,

jon

  reply	other threads:[~2014-10-28 17:41 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
2014-10-28 17:41               ` Jonathan Corbet [this message]
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=20141028134135.59dbc512@lwn.net \
    --to=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jason@lakedaemon.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.