public inbox for gentoo-nfp@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: [gentoo-nfp] Re: Please vote on this proposal related to http://bugs.gentoo.org/667602
Date: Thu, 4 Oct 2018 12:08:02 -0400	[thread overview]
Message-ID: <CAAr7Pr8yt8un-vUSug2usR0ZYF4ipbMMiZ548vVQc=MUtSLChg@mail.gmail.com> (raw)
In-Reply-To: <CAAr7Pr8azzBVeuaHOJ_K3mvTaBfsL+vhNew33ZdrX49VtkDteA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

On Thu, Oct 4, 2018 at 11:14 AM Alec Warner <antarus@gentoo.org> wrote:

> Summary:
> The short version of the bug is that a non-trivial number of developers
> cannot commit with an SoB line because their company has not yet reviewed
> the new Gentoo Copyright GLEP, and so they lack company approval to attach
> SoB lines or agree to the DCO.
>
> The bug requests that a reprieve be granted until the company reviews the
> new policy and (hopefully) grants approval. This would be in the form of an
> allowlist where specific identities (approved by some delegate of council
> && trustees) do not require an SoB line to commit for some period of time.
>
> Proposal:
> I propose the board grant this reprieve, for whitelisted accounts for 90
> days, with no extension. Williamh will supply the initial list of accounts,
> to be reviewed verbally by a board delegate and a council delegate.
>
> If the company cannot return a decision in 90 days, we can revisit the
> motion with any updated data.
>
> If the company returns a decision before 90 days, the whitelist program
> will be terminated (regardless of decision reached.) Note that if the
> company decides that approval will not be granted, we will in effect be
> unable to accept commits from these developers on work time.
>
> As president, I will not vote on this motion, because I'm proposing it, so
> a tie vote is possible.
>
> Please vote on -nfp; a GPG signed mail is sufficient.
>

If you could please vote within the next 7 days; I think the council would
appreciate some expedient action in this matter.

Thanks,

-A



>
> -A
>

[-- Attachment #2: Type: text/html, Size: 2281 bytes --]

  parent reply	other threads:[~2018-10-04 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 15:14 [gentoo-nfp] Please vote on this proposal related to http://bugs.gentoo.org/667602 Alec Warner
2018-10-04 15:24 ` Matthew Thode
2018-10-04 15:41 ` Ulrich Mueller
2018-10-04 15:50   ` Alec Warner
2018-10-04 16:08 ` Alec Warner [this message]
2018-10-04 16:17 ` Michał Górny
2018-10-09 21:06   ` Alec Warner
2018-10-06 13:00 ` Aaron Bauman

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='CAAr7Pr8yt8un-vUSug2usR0ZYF4ipbMMiZ548vVQc=MUtSLChg@mail.gmail.com' \
    --to=antarus@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