From: Rich Freeman <rich0@gentoo.org>
To: Greg KH <gregkh@gentoo.org>
Cc: Ulrich Mueller <ulm@gentoo.org>,
gentoo-project <gentoo-project@lists.gentoo.org>
Subject: [gentoo-project] Re: [gentoo-core] Re: Poll: Would you sign a Contributer License Agreement?
Date: Mon, 25 Jun 2018 10:08:26 -0400 [thread overview]
Message-ID: <CAGfcS_nquun_0a5MHjJ9338F7AFzE0t4QHm2w-X-Poar0+KBTw@mail.gmail.com> (raw)
In-Reply-To: <20180625110540.GB3058@kroah.com>
On Mon, Jun 25, 2018 at 7:05 AM Greg KH <gregkh@gentoo.org> wrote:
>
> On Mon, Jun 25, 2018 at 09:54:19AM +0200, Ulrich Mueller wrote:
> >
> > The problems are listed in the rationale of GLEP 76.
> >
> > With the license currently listed at https://developercertificate.org/
> > ("changing is not allowed") nobody would even be allowed to commit the
> > DCO to a repository under it's own terms. Catch-22.
>
> And as the Debian developers said, "that's crazy-talk, don't worry about
> it." Seriously, don't.
Do you have some kind of link to this?
Distributing the licenses is completely legal, but I don't see how
anybody could make the certifications in the DCO when doing so.
>
> What company or legal entity has concern with the DCO as-written?
>
Well, I do, at least as far as license commits go. How could I make
the certifications in your DCO when committing a license file like the
GPL?
The text of the upstream DCO says that the file is "covered under an
appropriate open source license," and the GPL isn't covered under an
open source license.
Don't get me wrong, per the terms in the GPL it is completely legal to
redistribute. My problem isn't with redistributing the GPL. My
problem is with signing off on the DCO when committing the GPL to a
repository, because I'd be making a statement that isn't true.
An alternative to this would be to not require a DCO signoff when
committing license files.
> That's not the only thing that you have changed here, as you state. You
> changed the wording of the types of licenses (hint, "free software" is
> not the same as "open source" and has consequences by changing that
> wording.)
Sure, but our intent is to require the use of a free software license.
So, the consequences are intentional here. It isn't adequate to
merely certify that the work is covered by an open source license
(this would be one of those cases where the needs of the Linux
Foundation may not be the same as the needs of everybody).
The other wording change is in changing how the outline numbering
works, to separate the three OR clauses from the one AND clause.
--
Rich
next prev parent reply other threads:[~2018-06-25 14:08 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 14:36 [gentoo-project] Poll: Would you sign a Contributer License Agreement? Ulrich Mueller
2018-05-30 17:45 ` Robin H. Johnson
2018-05-30 18:56 ` Rich Freeman
2018-05-30 22:02 ` Ulrich Mueller
2018-05-31 5:48 ` kuzetsa
2018-05-31 18:53 ` Ulrich Mueller
[not found] ` <20180530182136.GB18004@kroah.com>
2018-05-30 21:44 ` [gentoo-project] Re: [gentoo-dev-announce] " Ulrich Mueller
2018-05-30 22:31 ` Rich Freeman
2018-05-30 22:44 ` Ulrich Mueller
[not found] ` <20180531070321.GC7744@kroah.com>
2018-05-31 9:34 ` Ulrich Mueller
2018-05-31 10:18 ` Ulrich Mueller
2018-05-31 10:23 ` Ulrich Mueller
2018-05-31 22:24 ` Jonas Stein
2018-05-31 22:27 ` Kristian Fiskerstrand
2018-05-31 23:52 ` Raymond Jennings
2018-06-01 1:55 ` R0b0t1
2018-06-01 2:32 ` Rich Freeman
2018-06-01 11:49 ` Ulrich Mueller
2018-06-01 1:52 ` Ulrich Mueller
2018-06-04 12:35 ` [gentoo-project] " Ulrich Mueller
2018-06-04 12:44 ` Kristian Fiskerstrand
[not found] ` <20180625013334.GA28404@kroah.com>
2018-06-25 6:50 ` [gentoo-project] Re: [gentoo-core] " Ulrich Mueller
2018-06-25 7:02 ` Paweł Hajdan, Jr.
[not found] ` <20180625070525.GA6151@kroah.com>
2018-06-25 7:54 ` Ulrich Mueller
[not found] ` <20180625110540.GB3058@kroah.com>
2018-06-25 14:08 ` Rich Freeman [this message]
2018-06-25 14:37 ` Ulrich Mueller
2018-06-25 14:46 ` M. J. Everitt
2018-06-25 14:56 ` Rich Freeman
2018-06-25 15:53 ` Denis Dupeyron
2018-06-25 16:50 ` Rich Freeman
2018-06-25 19:02 ` Denis Dupeyron
2018-06-25 20:13 ` Michał Górny
2018-06-25 20:28 ` Paweł Hajdan, Jr.
2018-06-25 20:33 ` Denis Dupeyron
2018-06-25 20:31 ` Alec Warner
2018-06-25 20:52 ` Denis Dupeyron
2018-06-25 21:06 ` Alec Warner
2018-06-25 21:06 ` Ulrich Mueller
2018-06-25 22:10 ` Rich Freeman
2018-06-25 23:55 ` Andreas K. Huettel
2018-06-25 16:54 ` Ulrich Mueller
2018-06-25 17:10 ` M. J. Everitt
2018-06-25 17:37 ` Rich Freeman
2018-06-09 9:02 ` [gentoo-project] " Ulrich Mueller
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=CAGfcS_nquun_0a5MHjJ9338F7AFzE0t4QHm2w-X-Poar0+KBTw@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=gregkh@gentoo.org \
--cc=ulm@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