From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "gentoo-nfp@lists.gentoo.org" <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Forming Gentoo Policy - Copyright Assignment and Attribution
Date: Mon, 11 Mar 2013 16:21:19 -0700 [thread overview]
Message-ID: <20130311232119.GA25639@kroah.com> (raw)
In-Reply-To: <CAGfcS_mY932pOF3-0vNCeaoHd-217FKCPna9qb5OmAN5-F5rxA@mail.gmail.com>
On Mon, Mar 11, 2013 at 07:12:43PM -0400, Rich Freeman wrote:
> On Mon, Mar 11, 2013 at 6:40 PM, Rich Freeman <rich0@gentoo.org> wrote:
> > 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...
>
> So, clarification now that I'm back at a keyboard...
>
> DCO is mandatory, and is simply a declaration that the committer has
> checked and the new code is distributed under the license chosen for
> the project (see original email for details, but generally
> GPL/BSD/etc). The Linux kernel is the main model for this. Since
> Gentoo is not always being assigned copyright we need to have a clear
> declaration that the code is available under a suitable free license
> so that we can further distribute it.
>
> FLA is optional, and is essentially a copyright assignment (or
> reasonable facsimile in certain jurisdictions designed by the FSFe).
> KDE is the main model for this.
>
> But, to whatever extent that anything I just wrote disagrees with the
> original email, just read the original email. The original email was
> carefully proofread by the Trustees, the rest is just
> discussion/reminders/etc. The final policy will be even more
> carefully reviewed. The whole bit about mandatory copyright
> assignment was dropped after the last round of discussion for all the
> reasons that have just been rehashed...
Ok, good, that's why I didn't object to the first email, only to this
one which seemed to say something else, so I assumed it was I who
misread the first version.
Nevermind then, sorry for the noise :)
greg k-h
next prev parent reply other threads:[~2013-03-11 23:21 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
2013-03-11 23:12 ` Rich Freeman
2013-03-11 23:21 ` Greg KH [this message]
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=20130311232119.GA25639@kroah.com \
--to=gregkh@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