From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <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 12:50:46 -0400 [thread overview]
Message-ID: <CAGfcS_kjRQ28=of12uJKJAeq00NSfaABZw4Y=a2PoTLZvt7Y0g@mail.gmail.com> (raw)
In-Reply-To: <CA+CSuALyQqEC7h_-3+f3LKuK_G5n1KTCi1g70nmC=fC+y8eiHQ@mail.gmail.com>
On Mon, Jun 25, 2018 at 11:53 AM Denis Dupeyron <calchan@gentoo.org> wrote:
>
> I want to note here that if this comes into effect, and becomes
> mandatory, some critical pieces of Gentoo would go unmaintained for
> months, if not longer and possibly indefinitely, until the employer of
> the maintainers allows them to sign whatever it is you would require.
Just to get you to elaborate a bit more: is this a concern with the
Gentoo DCO in particular, or any requirement to sign off on anything?
It is probably worth nothing that the DCO (either upstream's or
Gentoo's) is just an affirmation of compliance. It doesn't actually
have any binding statements on the signer. You aren't signing away
any rights or accepting any restrictions, and it doesn't constitute a
contract as far as I can tell. It is merely a statement of fact about
a commit.
That said, part of me does wonder as such whether we're just as
covered by a policy that requires all commits be redistributable,
training all developers in it, and leaving it at that. That would
basically be the status quo, and I don't think anybody is going to
object to a policy that says only stuff we can legally distribute goes
in the repos. That really isn't any more restrictive than our general
social contract.
Ultimately this is all just reasonable care. Somebody can add a
signed-off-by without reading the DCO just as they can do a commit
without reading our policy on what is allowed to be committed. Is the
one standard truly any more defensible than the other?
--
Rich
next prev parent reply other threads:[~2018-06-25 16:51 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
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 [this message]
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_kjRQ28=of12uJKJAeq00NSfaABZw4Y=a2PoTLZvt7Y0g@mail.gmail.com' \
--to=rich0@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