public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] Re: Forming Gentoo Policy - Copyright Assignment and Attribution
Date: Mon, 11 Mar 2013 16:51:17 -0400	[thread overview]
Message-ID: <CAGfcS_k8-MOupF-9MT8L+ChuvhNX7wEpdoTTs=SwLdcX-JRqpA@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_njN_z=jOC5Tzn-tRH9qsfZoGcL44XU-NzrSdmGHeNqug@mail.gmail.com>

On Mon, Feb 25, 2013 at 5:29 PM, Rich Freeman <rich0@gentoo.org> wrote:
> I'm CCing this to gentoo-dev-announce since this has been a something
> high-profile topic, but all replies should stay on gentoo-nfp.
>
> In order to avoid completely undirected
> bikeshedding we're tossing out a strawman for how we might move
> forward.  This isn't policy - just a proposal for policy, and
> decisiveness shouldn't be confused for any unwillingness to discuss
> alternatives.

To date there have been no responses.  If none are received this week
the Trustees are likely to move forward with enacting a policy similar
to what was described.  This might entail enlisting legal counsel.
(The final policy will be circulated for comment first, with the
caveat below.)

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.  While we will of course
entertain comments on the final wording of the policy we do not want
to have any further debate on the overall direction once we start
bringing in lawyers.  This is not a good use of our volunteer's time,
and possibly even a modest amount of the Foundation's money (obviously
we will make every attempt to use the former before the latter).  Now
is the best time to make any big changes in our approach.

In short, speak now (on -nfp) or forever hold your peace...

Rich


      parent reply	other threads:[~2013-03-11 21:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-25 22:29 [gentoo-dev-announce] Forming Gentoo Policy - Copyright Assignment and Attribution Rich Freeman
2013-02-26  1:14 ` Robin H. Johnson
2013-03-11 20:51 ` Rich Freeman [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='CAGfcS_k8-MOupF-9MT8L+ChuvhNX7wEpdoTTs=SwLdcX-JRqpA@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev-announce@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