From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy
Date: Sun, 17 Jun 2018 10:45:56 +0200 [thread overview]
Message-ID: <23334.8132.376755.778057@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20180617193618.1a02a539@katipo2.lan>
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
>>>>> On Sun, 17 Jun 2018, Kent Fredric wrote:
>> I don't see how any of this would prevent a committer from adding a
>> Signed-off-by line.
> Here, it just seems like unnecessary fluff, given the committer and the
> signed-off-by line should be identical.
The Signed-off-by line certifies agreement to the Gentoo DCO, whereas
the Commit line doesn't have any such meaning. Also the committer info
is somewhat transient and can change, e.g. when a branch gets rebased.
S-o-b lines won't get lost on a rebase.
> It makes more sense in the kernel, where patches get formatted with
> only author data, and the chain of custody from the border to its final
> commit in kernel@ is not necessarily completely obvious.
There are many commits in Linux that have only a single S-o-b line.
> Whereas in Gentoo, we don't really have any of those intermediate steps.
> Its more a question what it seeks to achieve that can't be done with
> existing data.
> Especially considering anyone can trivially forge such a statement
> and pretend they committed on somebody elses behalf after receiving a
> patch.
That's why we also require commits to be PGP signed.
> And I somewhat find the "real names" policy somewhat obnoxious, for as
> far as I'm aware, pseudonyms are just as legally binding as real names.
> Requiring a legal name just excludes people, and well known pseudonymous
> authors like "why_" would never participate in such a scheme.
The real name requirement is nothing new, but a policy that is in
effect since 2004 [1,2]:
| Real names must be provided for all developers, including
| infrastructure and documentation. Any exceptions to this for
| extenuating circumstances will be considered on a case-by-case
| basis. No exceptions will be made for people doing copyrightable
| work (ebuilds, software, scripts, documentation, etc.).
Ulrich
[1] https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/recruiters/index.xml?revision=1.15&view=markup
[2] https://wiki.gentoo.org/wiki/Project:Recruiters/Recruiting#What_does_the_recruitment_process_involve.3F
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-06-17 8:46 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-10 20:34 [gentoo-project] [RFC] GLEP 76: Copyright Policy Ulrich Mueller
2018-06-10 20:49 ` Michał Górny
2018-06-11 16:20 ` Brian Evans
2018-06-11 16:25 ` NP-Hardass
2018-06-11 17:07 ` Rich Freeman
2018-06-11 18:08 ` NP-Hardass
2018-06-11 17:27 ` Ulrich Mueller
2018-06-11 17:57 ` NP-Hardass
2018-06-13 20:35 ` Ulrich Mueller
2018-06-13 20:44 ` William Hubbs
2018-06-17 2:18 ` Kent Fredric
2018-06-11 17:45 ` Michał Górny
2018-06-12 6:01 ` Matt Turner
2018-06-17 1:03 ` Kent Fredric
2018-06-17 1:39 ` Rich Freeman
2018-06-17 2:14 ` Kent Fredric
2018-06-17 2:34 ` Rich Freeman
2018-06-17 2:17 ` Aaron Bauman
2018-06-17 2:39 ` Rich Freeman
2018-06-17 2:52 ` Aaron Bauman
2018-06-17 3:30 ` Kent Fredric
2018-06-17 7:09 ` Ulrich Mueller
2018-06-17 7:00 ` Ulrich Mueller
2018-06-17 7:15 ` Kent Fredric
2018-06-17 7:38 ` Kent Fredric
2018-06-17 8:45 ` Ulrich Mueller [this message]
2018-06-17 20:12 ` Kristian Fiskerstrand
2018-06-17 20:37 ` Ulrich Mueller
2018-06-17 20:41 ` Kristian Fiskerstrand
2018-06-17 23:19 ` Kent Fredric
2018-06-19 17:30 ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v2] Ulrich Mueller
2018-06-23 19:39 ` Andreas K. Huettel
2018-06-23 21:57 ` Ulrich Mueller
2018-08-31 15:18 ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v3] Ulrich Mueller
2018-09-03 17:40 ` Ulrich Mueller
2018-09-08 11:43 ` Andrew Savchenko
2018-09-08 13:35 ` Ulrich Mueller
2018-09-08 18:17 ` Andrew Savchenko
2018-09-08 18:55 ` Ulrich Mueller
2018-09-08 19:20 ` Justin Lecher
2018-09-08 23:38 ` Andrew Savchenko
2018-09-09 6:15 ` Ulrich Mueller
2018-09-08 14:25 ` Michael Orlitzky
2018-09-08 17:09 ` Michał Górny
2018-09-08 17:36 ` Ulrich Mueller
2018-09-26 19:25 ` [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4] Ulrich Mueller
2018-09-27 5:00 ` kuzetsa
2018-09-27 12:00 ` NP-Hardass
2018-09-27 12:42 ` Rich Freeman
2018-09-27 13:08 ` kuzetsa
2018-09-27 13:43 ` Rich Freeman
2018-09-27 14:14 ` kuzetsa
2018-09-27 13:52 ` NP-Hardass
2018-09-27 14:13 ` Rich Freeman
2018-09-27 14:24 ` NP-Hardass
2018-09-27 14:32 ` kuzetsa
2018-09-29 3:15 ` desultory
2018-09-29 7:08 ` Kent Fredric
2018-09-29 9:13 ` Ulrich Mueller
2018-09-27 14:32 ` Michał Górny
2018-09-27 14:40 ` kuzetsa
2018-09-28 9:39 ` kuzetsa
2018-09-29 7:46 ` Ulrich Mueller
2018-10-02 20:29 ` NP-Hardass
2018-10-02 21:23 ` Michał Górny
2018-10-03 15:48 ` Ulrich Mueller
2018-10-03 19:16 ` Andrew Savchenko
2018-10-03 19:28 ` Rich Freeman
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=23334.8132.376755.778057@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-project@lists.gentoo.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