All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Loic Dachary <loic@dachary.org>,
	Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Signed-off-by and aliases
Date: Sat, 01 Aug 2015 10:11:58 +0200	[thread overview]
Message-ID: <55BC7F4E.5070003@42on.com> (raw)
In-Reply-To: <55BBD384.7030703@dachary.org>

On 07/31/2015 09:59 PM, Loic Dachary wrote:
> Hi Ceph,
> 
> We require that each commit has a Signed-off-by line with the name and email of the author. The general idea is that the Ceph project trusts each developer to understand what it entails[1]. There is no formal verification : the person submitting the patch could use a fake name or publish code from someone else. In reality the odds of that happening and causing problem are so low that neither Ceph nor the Linux kernel felt the need to impose a more formal process. There is no bullet proof process anyway, it's all about balancing risks and costs.
> 
> If a contributor was using an alias that looks like a real name (for instance I could contribute under the name Louis Lavile), (s)he would go unnoticed and her/his contribution would be accepted as any other. If the same contributor was using an alias that is obviously an alias (such as A. Nonymous), it would raise the question of accepting contributions Signed-off with an alias.
> 
> I think Ceph should accept contributions that are signed with an alias because it does not make a difference.
> 
> From a lawyer perspective, there is a difference between an alias and a real name, of course. Should the author be in court, (s)he would have to prove (s)he is the person behind the alias. If (s)he was using her/his real name, an ID card would be enough. And probably other differences that I don't see because IANAL. However since we already accept Signed-off-by that are not formally verified, we're already in a situation where we implicitly accept aliases. Explicitly accepting aliases would not change that, therefore it is not actually something we need to run by lawyers because nothing changes from a legal standpoint.
> 
> What do you think ?
> 

Using an alias is just dumb since it would only make you loose the
copyright since it's not you doing the commit.

However, if we want to go for security, there is also a way to sign your
Git commits using GPG [2].

[2]: https://git-scm.com/book/tr/v2/Git-Tools-Signing-Your-Work

> Cheers
> 
> [1] SIGNING CONTRIBUTIONS https://github.com/ceph/ceph/blob/master/SubmittingPatches#L13
> 


-- 
Wido den Hollander
42on B.V.
Ceph trainer and consultant

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2015-08-01  8:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31 19:59 Signed-off-by and aliases Loic Dachary
2015-08-01  8:11 ` Wido den Hollander [this message]
2015-08-02 16:19   ` Joao Eduardo Luis
2015-08-03 19:02     ` Wido den Hollander
2015-08-03 19:18 ` John Spray
2015-08-03 20:10   ` Loic Dachary
2015-08-12 10:54     ` Gregory Farnum
2015-08-12 12:51       ` Loic Dachary
2015-08-14  8:49         ` Joao Eduardo Luis
2015-08-14 10:56           ` Loic Dachary
2015-08-17 20:19             ` Alex Elsayed
2015-08-17 20:44               ` Loic Dachary
2015-08-17 20:58                 ` Alex Elsayed
2015-08-17 21:18                   ` Loic Dachary
2015-08-17 21:23                     ` Alex Elsayed
2015-08-18 13:39                   ` Sage Weil
2015-08-18 15:11                     ` Alex Elsayed
  -- strict thread matches above, loose matches on Subject: below --
2014-05-19 15:13 Loic Dachary
     [not found] ` <1400513274.44658.YahooMailNeo@web165002.mail.bf1.yahoo.com>
2014-05-19 16:47   ` Loic Dachary
2014-05-20  4:19   ` Richard Fontana
2014-05-20  5:31     ` Loic Dachary
2014-05-20 13:56       ` Richard Fontana
2014-05-21 17:06 ` Loic Dachary
2014-05-21 17:31   ` Richard Fontana

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=55BC7F4E.5070003@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=loic@dachary.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.