public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Greg KH <gregkh@gentoo.org>
Subject: [gentoo-project] Re: [gentoo-core] Re: Poll: Would you sign a Contributer License Agreement?
Date: Mon, 25 Jun 2018 09:54:19 +0200	[thread overview]
Message-ID: <23344.40875.105369.227774@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20180625070525.GA6151@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

>>>>> On Mon, 25 Jun 2018, Greg KH wrote:

> On Mon, Jun 25, 2018 at 08:50:26AM +0200, Ulrich Mueller wrote:
>> [Replying to gentoo-project only.]

> Why?  You put this on -core for a reason, why take conversations
> somewhere that not everyone can see them?  That's just rude :)

>> Please read the whole thread. We have dropped the FLA/CLA in the
>> latest iteration. Also even in the previous versions it was meant to
>> be voluntary, i.e. devs were "welcome and encouraged (but *not*
>> required)" to sign it.

> Where is "the whole thread" at these days?  It's hard to keep track of
> it all.

gentoo-project mailing list, thread "[RFC] GLEP 76: Copyright Policy".
Latest draft is at: https://www.gentoo.org/glep/glep-0076.html

>> > And again, as I previously stated, "forking" the DCO is a horrible
>> > idea,
>> 
>> Has there ever been a wider review of the Linux DCO? If not, then it
>> is not surprising if it fits the needs of kernel development only
>> (which is very homogeneous, license wise), but not necessarily other
>> projects.

> Yes, there has been, it is used by lots of differently licensed
> projectes these days.  One example would be a large number of the CNCF
> projects (kuberneties and friends).

> It has also been vetted and approved by the legal departments of all
> companies that allow their developers to contribute to open source
> projects.  Again, a very wide range of legal and developer vetting has
> happened.  If you know of any current problems, please let us know.

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.

We can only commit it under the CC-BY-SA under which it (fortunately)
has been released earlier, and then we _are_ permitted to fix any bugs
in it.

>> Are you saying that the DCO is so complicated that all devs will need
>> a lawyer, in order to understand what they are certifying? Then we are
>> doing something fundamentally wrong.

> I'm saying that if you change the DCO then it will have to be vetted by
> all corporate legal departments.  If you do not change it, it is an easy
> "we know all about that one, it's fine" 1 minute conversation.

It hopefully takes less than 1 minute to read and understand the item
that we have added:

   (3) The contribution is a license text (or a file of similar nature),
       and verbatim distribution is allowed; or

Do you think that anybody would have difficulties understanding this?
Then please propose a better wording.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2018-06-25  7:54 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 [this message]
     [not found]           ` <20180625110540.GB3058@kroah.com>
2018-06-25 14:08             ` Rich Freeman
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=23344.40875.105369.227774@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=gregkh@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