From: "Paweł Hajdan, Jr." <phajdan.jr@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-core] Re: Poll: Would you sign a Contributer License Agreement?
Date: Mon, 25 Jun 2018 09:02:15 +0200 [thread overview]
Message-ID: <68a7b83a-f3b6-3615-7c97-dfd665c8e4f7@gentoo.org> (raw)
In-Reply-To: <23344.37042.753481.563752@a1i15.kph.uni-mainz.de>
[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]
On 25/06/2018 08:50, Ulrich Mueller wrote:
> 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.
+1
It's been very convincing for me as a software engineer to use DCO
everywhere. However, I can also see the opposing argument, that the
situation of many companies and project is very different from Linux
Foundation's, especially from legal point of view. Even though I might
not personally be fully convinced, I certainly accept that specialists
(lawyers) have a deeper understanding of that perspective.
>> and doing it by not getting legal review of such changes is an even
>> worse idea.
>
>> Would you want a medical doctor to write a legal document? If not,
>> why would you want a programmer to do so?
>
> 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.
Greg has a good point here. It may help to state clearly what are we
trying to accomplish here, and evaluate different solutions against that
goal. If our fork of DCO would still be optional, what does it
accomplish? Might it create some additional issues?
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2018-06-25 7:02 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. [this message]
[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
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=68a7b83a-f3b6-3615-7c97-dfd665c8e4f7@gentoo.org \
--to=phajdan.jr@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