From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org,Ulrich Mueller <ulm@gentoo.org>
Subject: Re: [gentoo-dev] New copyright policy approved, please weigh your Signed-off-bys
Date: Sun, 16 Sep 2018 13:40:49 +0000 [thread overview]
Message-ID: <A361A2A4-BDFB-472D-9E99-ED764AB29B88@gentoo.org> (raw)
In-Reply-To: <w6gefdtbywp.fsf@kph.uni-mainz.de>
Dnia September 16, 2018 8:59:50 AM UTC, Ulrich Mueller <ulm@gentoo.org> napisał(a):
>>>>>> On Sun, 16 Sep 2018, Michał Górny wrote:
>
>> Just FYI: the Trustees have approved GLEP 76 aka our new copyright
>> policy [1]. While the exact implementation details are to be
>determined
>> yet, please note that *Signed-off-by* line will mean you are
>certifying
>> our GCO [2].
>
>> Since some developers were giving the sign-off 'in blanco' so far,
>> I would like to emphasize that now it will actually mean agreeing to
>> the document. Unless you have read the new policy and agreed with
>it,
>> please don't do that.
>
>I wonder how we should treat those existing Signed-off-by lines in the
>tree.
>
>We could either say that we ignore any such lines on commits before
>2018-09-16 00:00:00 UTC, because there was no policy in place.
>
>Or we could say that they certify the commit under the Linux DCO 1.1
>(https://developercertificate.org/), because in absence of an explicit
>policy that's the only meaningful interpretation of a Signed-off-by
>line.
>
>Presumably, the first alternative is cleaner. Especially, since there
>are commits with a Signed-off-by line that don't comply with the
>conditions of the Linux DCO.
I don't think we really need to be concerned about them right now.
AFAIU the whole signoff business boils down to two things: verifying that contributors understand the terms of contributing, and protecting Gentoo from liability for commits violating those terms.
I think that in this context only the latter point really matters, and I don't think making statement either way right now would change anything if we ever had to exercise it.
>
>Ulrich
>
>> [1]:https://www.gentoo.org/glep/glep-0076.html
>> [2]:https://www.gentoo.org/glep/glep-0076.html#certificate-of-origin
--
Best regards,
Michał Górny
next prev parent reply other threads:[~2018-09-16 13:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 6:59 [gentoo-dev] New copyright policy approved, please weigh your Signed-off-bys Michał Górny
2018-09-16 8:59 ` Ulrich Mueller
2018-09-16 10:29 ` Thomas Deutschmann
2018-09-16 13:40 ` Michał Górny [this message]
2018-09-18 2:52 ` Michael Orlitzky
2018-09-18 6:09 ` Michał Górny
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=A361A2A4-BDFB-472D-9E99-ED764AB29B88@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@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