public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: "gentoo-nfp@lists.gentoo.org" <gentoo-nfp@lists.gentoo.org>
Cc: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: Forming Gentoo Policy - Copyright Assignment and Attribution
Date: Mon, 11 Mar 2013 18:40:44 -0400	[thread overview]
Message-ID: <CAGfcS_mDbefEb5zpR2wU_XJ6adrUf1pQPbBrqyGot4r7Tg72CQ@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20130311T221849-138730663Z@orbis-terrarum.net>

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

On Mar 11, 2013 6:22 PM, "Robin H. Johnson" <robbat2@gentoo.org> wrote:
>
> On Mon, Mar 11, 2013 at 02:19:55PM -0700, Greg KH wrote:
> > On Mon, Mar 11, 2013 at 04:51:17PM -0400, Rich Freeman wrote:
> > > If you have any concerns/objections to the policy which was outlined,
> > > which includes a mandatory requirement to sign a contributor license
> > > agreement and an option to also sign an assignment-like document based
> > > on the FSFe FLA, please speak up this week.
> > I've already said this before, but I guess I need to say it again:
> >       If a contributor license is required to be signed, I'll have to
> >       stop contributing to Gentoo.
> Did you read the entire email? We explicitly listed one of the options
> as (voluntary FLA/CLA AND mandatory DCO).
>
> Could you clarify that you're objecting to that as well? In your case,
> you could elect NOT to sign the FLA/CLA. Regardless, all of your commits
> would have the DCO SoB signature.
>
> The kernel is where we got the mandatory DCO concept.

This one is my bad. I wrote CLA when I meant DCO.

No change intended. This is what happens when you send a thirty second
follow-up to a policy formed over two weeks, and then step away to eat...

But, at least we know people read it!

Rich

[-- Attachment #2: Type: text/html, Size: 1511 bytes --]

  reply	other threads:[~2013-03-11 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGfcS_njN_z=jOC5Tzn-tRH9qsfZoGcL44XU-NzrSdmGHeNqug@mail.gmail.com>
     [not found] ` <CAGfcS_k8-MOupF-9MT8L+ChuvhNX7wEpdoTTs=SwLdcX-JRqpA@mail.gmail.com>
2013-03-11 21:19   ` [gentoo-dev] Re: Forming Gentoo Policy - Copyright Assignment and Attribution Greg KH
2013-03-11 21:44     ` Theo Chatzimichos
2013-03-11 22:22     ` Robin H. Johnson
2013-03-11 22:40       ` Rich Freeman [this message]
2013-03-11 23:12         ` Rich Freeman
2013-03-11 23:21           ` Greg KH
2013-03-12  7:12           ` Andreas K. Huettel
2013-03-12  7:27             ` Alec Warner
2013-03-12 10:16             ` Rich Freeman
2013-03-19 21:26     ` Stanislav Ochotnicky

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_mDbefEb5zpR2wU_XJ6adrUf1pQPbBrqyGot4r7Tg72CQ@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-nfp@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