From: Theo Chatzimichos <tampakrap@gentoo.org>
To: gentoo-dev@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 22:44:41 +0100 [thread overview]
Message-ID: <1707157.W6kZBlP3eR@virtuoso> (raw)
In-Reply-To: <20130311211955.GB32527@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On Monday 11 of March 2013 14:19:55 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.
>
> 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 was here when the copyright assignment form was dropped due to all of
> the problems it was causing new developers (myself included.) Have you
> somehow figured out how to handle all of the issues that were raised 8+
> years ago with the old assignment we had?
>
> Is there really no one around now (other than myself) that had to deal
> with that mess in the past?
>
> History, forgetting it, doomed.
>
> sadly,
>
> greg k-h
I'm not having any personal issue here, but I'm with Greg here, since this
action means loosing any single contributor. We're a project ran by
volunteers, we get more retirements than additions lately, and we can't even
afford loosing anybody. -1 from me as well.
Theo
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-03-11 21:41 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 [this message]
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
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=1707157.W6kZBlP3eR@virtuoso \
--to=tampakrap@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