From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] [RFC] GLEP 76: Copyright Policy [v4]
Date: Wed, 3 Oct 2018 22:16:15 +0300 [thread overview]
Message-ID: <20181003221615.88d543bde07109aae55e38c8@gentoo.org> (raw)
In-Reply-To: <w6gh8i32fr1.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
On Wed, 03 Oct 2018 17:48:18 +0200 Ulrich Mueller wrote:
> >>>>> On Tue, 02 Oct 2018, NP-Hardass wrote:
> > UNLESS you think this falls under #2:
> > "The contribution is based upon previous work that, to the best of my
> > knowledge, is covered under an appropriate free software license, and I
> > have the right under that license to submit that work with
> > modifications, whether created in whole or in part by me, under the same
> > free software license (unless I am permitted to submit under a different
> > license), as indicated in the file; or"
> > Which, as written, means that the committer must make a modifications to
> > the pseudonymous work to qualify as "[FOSS licensed and] created in
> > whole or in part by me."
>
> That wording has be copied from the Linux DCO. Presumably it would be
> clearer if it said "submit that work with or without modifications".
> If unmodified distribution/submission was not allowed, the license
> wouldn't qualify as a free software license, in the first place.
>
> > The premise of which is that pseudonymous contributions aren't allowed
> > unless the author submits it as a patch, not using a VCS (as
> > contributions via VCS must use the Certificate of Origin), and the
> > committer makes some trivial modification to them, and then, by magic,
> > we avoid requirements for real names.
>
> See above, the right to distribute the work with modifications doesn't
> preclude its distribution without modifications.
>
> The only problem I see is that usually it would not be very polite to
> sign off someone else's work. However, I don't think there is a real
> problem with that, as long as the committer can confirm that the
> contribution is under a free software license.
Sign-off usually means "I have reviewed this commit and approve it".
This is how it works in the Linux kernel where one have to collect
sufficient number of sign-offs to pass commit in the main tree. An
attempt to give it another meaning like "I'm the author of this
commit" looks questionable. Of course DCO certification is fine as
well.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-03 19:16 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
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 [this message]
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=20181003221615.88d543bde07109aae55e38c8@gentoo.org \
--to=bircoph@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