From: Jorge Ramirez <jorge.ramirez-ortiz@linaro.org>
To: Joe Perches <joe@perches.com>,
Himanshu Jha <himanshujha199640@gmail.com>
Cc: 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 18:54:48 +0100 [thread overview]
Message-ID: <d77a378b-4a5b-daed-2fff-45c29aa12fa2@linaro.org> (raw)
In-Reply-To: <8242597611424ecd79d7863552b2281d89ccae76.camel@perches.com>
On 12/14/18 18:39, Joe Perches wrote:
> On Fri, 2018-12-14 at 22:58 +0530, Himanshu Jha wrote:
>> On Fri, Dec 14, 2018 at 08:27:33AM -0800, Joe Perches wrote:
>>> Is it really important to specify things like 75% / 25%
>>> authorship crediting?
>> IDK how that ratio came up into this discussion ?
> How does one tell when a co-developed-by: person
> should be notated or blamed for a defective commit?
>
> git blame shows only 1 author.
>
>
>
>
co-developed is simply about crediting a piece of work, something which
is intrinsically connected to the philosophy of open source.
I could name a number of papers but one that comes to my mind is a work
from Pekka Himanen, The Hacker Ethic...[1993].
anyway, so while sign-of is of a practical nature, co-developed is more
of a social one. at least that is my understanding.
next prev parent reply other threads:[~2018-12-14 17:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 13:01 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
2018-12-14 17:39 ` Joe Perches
2018-12-14 17:54 ` Jorge Ramirez [this message]
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=d77a378b-4a5b-daed-2fff-45c29aa12fa2@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=himanshujha199640@gmail.com \
--cc=joe@perches.com \
--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 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®