All of lore.kernel.org
 help / color / mirror / Atom feed
From: Himanshu Jha <himanshujha199640@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
	apw@canonical.com, Andrew Morton <akpm@linux-foundation.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, niklas.cassel@linaro.org
Subject: Re: [PATCH] checkpatch: add Co-Developed-by to signature tags
Date: Fri, 14 Dec 2018 22:58:43 +0530	[thread overview]
Message-ID: <20181214172843.GA18703@himanshu-Vostro-3559> (raw)
In-Reply-To: <8ae5c67a5c4516a783579e449313d1d59fe3a47d.camel@perches.com>

On Fri, Dec 14, 2018 at 08:27:33AM -0800, Joe Perches wrote:
> On Fri, 2018-12-14 at 21:46 +0530, Himanshu Jha wrote:
> > On Fri, Dec 14, 2018 at 07:52:15AM -0800, Joe Perches wrote:
> > > On Fri, 2018-12-14 at 14:01 +0100, Jorge Ramirez-Ortiz wrote:
> > > > As per Documentation/process/submitting-patches, Co-developed-by is a
> > > > valid signature.
> > > > 
> > > > This commit removes the warning.
> > > 
> > > Your commit message doesn't match your subject.
> > > 
> > > A couple variants have been documented and only
> > > one should actually be used.
> > > 
> > > $ git grep -i co-developed-by Documentation/process/
> > > Documentation/process/5.Posting.rst: - Co-developed-by: states that the patch was also created by another developer
> > > Documentation/process/submitting-patches.rst:12) When to use Acked-by:, Cc:, and Co-Developed-by:
> > > Documentation/process/submitting-patches.rst:A Co-Developed-by: states that the patch was also created by another developer
> > > 
> > > $ git log --grep="co-developed-by:" -i | \
> > >   grep -ohiP "co-developed-by:" | sort | uniq -c | sort -rn
> > >      80 Co-developed-by:
> > >      40 Co-Developed-by:
> > > 
> > > So which should it be?
> > > 
> > > btw: I prefer neither as I think Signed-off-by: is sufficient.
> > 
> > OK, but does multiple Signed-off-by: in the commits imply that
> > the patch was created by all those developers ?
> > 
> > I don't think so, perhaps this was the reason to introduce
> > Co-developed-by: tag.
> 
> Perhaps, but a sign-off is also a recognition that the
> patch was passed-through by individuals

Yes, Agreed!

> Effectively, there's no real difference.
> 
> "Co-developed-by:" is just another word for "Authored-by:"
> where multiple "Authorship" is the thing being notated.
> 
> Is it really important to specify things like 75% / 25%
> authorship crediting?

IDK how that ratio came up into this discussion ?

Anyway, I saw on IIO list that a bunch of students were involved
in driver cleaning with the help of developers from Analog Devices
Inc who intially wrote some code snippets.

And that authorship crediting for Analog Devices folks would be
helpful distinguishing that it was not just passed-through and rather
they spent their time on it.

> I don't really care about attribution so the concept is
> not particularly valuable to me.

Well, it might not be valuable to you but it is for others and I saw
one such example in the past during my project.

At least I do care about those developers who spent a considerable
time on IIO list guiding students aside from their mainline work.


FYI, IIO has already +1'd for "Co-developed-by:"

-- 
Himanshu Jha
Undergraduate Student
Department of Electronics & Communication
Guru Tegh Bahadur Institute of Technology

  reply	other threads:[~2018-12-14 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 13:01 [PATCH] checkpatch: add Co-Developed-by to signature tags Jorge Ramirez-Ortiz
2018-12-14 15:52 ` Joe Perches
2018-12-14 16:03   ` Jorge Ramirez
2018-12-14 16:13   ` Greg KH
2018-12-14 17:18     ` Jorge Ramirez
2018-12-14 16:16   ` Himanshu Jha
2018-12-14 16:27     ` Joe Perches
2018-12-14 17:28       ` Himanshu Jha [this message]
2018-12-14 17:39         ` Joe Perches
2018-12-14 17:54           ` Jorge Ramirez
2018-12-14 18:35           ` Himanshu Jha

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=20181214172843.GA18703@himanshu-Vostro-3559 \
    --to=himanshujha199640@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niklas.cassel@linaro.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 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.