From: Stanislav Ochotnicky <sochotnicky@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Greg KH <gregkh@gentoo.org>,
gentoo-nfp@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Forming Gentoo Policy - Copyright Assignment and Attribution
Date: Tue, 19 Mar 2013 22:26:25 +0100 [thread overview]
Message-ID: <20130319212625.7794.31355@nimbus.binaryparadise.com> (raw)
In-Reply-To: <20130311211955.GB32527@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
Quoting Greg KH (2013-03-11 22:19:55)
> 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.
>
> Other developers will be also affected, and you will find it hard to
> attract new developers who happen to work for companies that forbid
> their employees to sign these types of things (a _very_ common thing in
> the US, I have yet to work for a company in the past 20+ years that
> would have allowed this without going through the company's legal
> council for approval, a usually very difficult thing to achieve for a
> single developer.)
I am wondering if even things like Fedora Project Contributor Agreement[1] would
cause trouble for you and people in similar situation. I.e. FPCA is not a
copyright agreement as such, it's just setting default license for project for
contributions without license and provides a set of licenses that are OK for
project. In Fedora's case MIT was chosen as default for code and CC-BY-SA-3.0
for content. I am also assuming FPCA-style agreement wouldn't really solve
whatever issues are to be solved with optional assignment policy but who
knows...
I myself do not care much for copyright assignment policies even though I have
no legal problem with it per se.
[1] https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement
--
Stanislav Ochotnicky
PGP: 7B087241
jabber: stanislav@ochotnicky.com
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQIcBAABCgAGBQJRSNgBAAoJELy9dS57CHJBzxkQAIRbP+J86fyYD8nj3rbxrVBD
UizpS+UCK7EWepXg/OVzeVrMxjY1JAVrgfdZAxeTMqiMRKdpNXEFsXtkpMg/SObF
P4115pbUNYM9WkMueYrGSKrSaLsm38M89cBbQP0elrn16XNsZ4/PLxtpm500e26L
sjXT4BPc+HkR1fGGFaxdXnHVIKSTgnCUeHeV84CYcNx4PD8ClGuhQ17ijhtNzf26
siwvbYJt57yuJaHo9xwZHkjroDjA4nYSKjqWyb46I+Z13aCFHLjmiU+W4orHHLXq
r80A8TqINyy8nVDUY9d8SjqydwIhSjSLLNwoLXUG4yR+pP5ZmHl6Gt4N/gsINnTd
RgZf3EClLCzuOnxdxl77d1YhTWHlHQljD7ulpfMqhay5hr28E4mM4Yrv7YknQGZ4
X6PwopBHFEkW2J0Jpfpq9iBqloKcNJmNqf58IGKeQ1ZmIZC1HPG2/UKztRseilxF
jPdw4JAH0w5YViwffVpmNwCfAoYSLufdy56Eik2wb/YeQeQ16yAZCYhoInBuTb+r
CfSEhEfsZqvKvFT7c6X1u2PJNjva+xZSiO+nmlHiO2+bUhkPCwNWkZjPMeZNqhIW
BS1H8DN7zvvnOr6rdKISbLIG+Ts5S3Go+9mpuB3CJ+SgpPH5xLd7gdctfrRXYSYE
x68+imaoKRaChtJlqUe8
=slc4
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-03-19 21:26 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
2013-03-12 10:16 ` Rich Freeman
2013-03-19 21:26 ` Stanislav Ochotnicky [this message]
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=20130319212625.7794.31355@nimbus.binaryparadise.com \
--to=sochotnicky@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-nfp@lists.gentoo.org \
--cc=gregkh@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