From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Forming Gentoo Policy - Copyright Assignment and Attribution
Date: Tue, 12 Mar 2013 00:27:13 -0700 [thread overview]
Message-ID: <CAAr7Pr9Y+2JB9TxhQk0UwpA1JKeHQAO8jrW+hzV0K-PeoTPHhQ@mail.gmail.com> (raw)
In-Reply-To: <201303120812.12605.dilfridge@gentoo.org>
On Tue, Mar 12, 2013 at 12:12 AM, Andreas K. Huettel
<dilfridge@gentoo.org> wrote:
> Am Dienstag, 12. März 2013, 00:12:43 schrieb Rich Freeman:
>> 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.
If you read earlier in the thread, you will see an example of a DCO.
My naive understanding is that a DCO helps shore up the legal defense
the foundation may have when inevitable violations occur.
A DCO is mentioned in step 12:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/SubmittingPatches#l298
>>
>> 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.
>
> Which obviously means, now if everyone signs a KDE with GPL'ed key and sends
> it with SPF to TGF (The Gentoo Foundation), everything is IPO. (In Perfect
> Order.)
http://fsfe.org/activities/ftf/fla.en.html
http://en.wikipedia.org/wiki/Contributor_License_Agreement
>
> Seriously, could you repeat this for laymen and non-americans?
Hey it all makes sense for us Americas, its you Europeans that make
stuff all complex :)
>
> --
>
> Andreas K. Huettel
> Gentoo Linux developer
> dilfridge@gentoo.org
> http://www.akhuettel.de/
>
next prev parent reply other threads:[~2013-03-12 7:27 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
2013-03-12 7:12 ` Andreas K. Huettel
2013-03-12 7:27 ` Alec Warner [this message]
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=CAAr7Pr9Y+2JB9TxhQk0UwpA1JKeHQAO8jrW+hzV0K-PeoTPHhQ@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@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