From: Alec Warner <antarus@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Subject: Re: [gentoo-nfp] Please vote on this proposal related to http://bugs.gentoo.org/667602
Date: Thu, 4 Oct 2018 11:50:07 -0400 [thread overview]
Message-ID: <CAAr7Pr8kCQEPsJLKN=JZw5KZ4w7zjZQM+d9N5464VM904+veaw@mail.gmail.com> (raw)
In-Reply-To: <w6gtvm11zyd.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Thu, Oct 4, 2018 at 11:41 AM Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Thu, 04 Oct 2018, Alec Warner wrote:
>
> > 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.
>
> Does this imply that whitelisted developers are exempt from the
> copyright policy altogether? Or are they expected to follow all other
> aspects of the copyright policy, with the Signed-off-by line being the
> only exception?
>
The bug wording was:
"We are requesting a 30 day reprieve on the hard enforcement of
sign-off-by lines in commits to give our legal dept time to approve the
new copyright policy."
Is that clear? This proposal is 90 days, and the reprieve only applies to
approved whitelisted identities.
-A
>
> Please clarify.
>
> Ulrich
>
[-- Attachment #2: Type: text/html, Size: 1631 bytes --]
next prev parent reply other threads:[~2018-10-04 15:50 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 [this message]
2018-10-04 16:08 ` [gentoo-nfp] " Alec Warner
2018-10-04 16:17 ` [gentoo-nfp] " 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='CAAr7Pr8kCQEPsJLKN=JZw5KZ4w7zjZQM+d9N5464VM904+veaw@mail.gmail.com' \
--to=antarus@gentoo.org \
--cc=gentoo-nfp@lists.gentoo.org \
--cc=ulm@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