From: kuzetsa <kuzetsa@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Fri, 15 Jun 2018 12:03:42 -0400 [thread overview]
Message-ID: <068c46f9-cc89-702b-8c77-94896e1bf321@gmail.com> (raw)
In-Reply-To: <CAGfcS_=7_YwtBzTv+8XSVh8xUG2rsPZwc_t9rEaswJ_9O9XuDQ@mail.gmail.com>
On 06/15/2018 11:31 AM, Rich Freeman wrote:
> On Fri, Jun 15, 2018 at 10:55 AM kuzetsa <kuzetsa@gmail.com> wrote:
>>
>> "Gentoo Developer's Certificate of Origin" - shouldn't
>> the author / contributor themselves be involved in this?
>>
>
> It already requires this. The committer would have to certify:
>
> " (4) The contribution was provided directly to me by some other person
> who certified (1), (2), (3), or (4), and I have not modified it."
>
> (or one of the other items in the list, if they did modify it)
>
> Ultimately the committer is the person Gentoo has a relationship with,
> so they need to make the certification when they make the commit, even
> if it is just certifying that somebody else certified it.
>
> This goes along with something Thomas said earlier - ultimately the
> committers are responsible for what they commit. There really isn't a
> sane alternative since the whole reason we try to control our
> committers is to ensure that things don't end up in the repository
> which shouldn't be there. This isn't diminishing the value of 3rd
> party contributors - but simply affirming the value-add of having
> somebody we know actually look at what is being contributed. That
> includes the copyright/license and not just the code. After all, all
> this stuff ends up on all our users's systems so we want to protect
> them as well as ourselves. Users already have the freedom to use any
> overlays they wish if they value these things differently.
>
> --
> Rich
>
OH!!! (thanks, I completely missed that detail)
from: "$ man git-commit" : [...] The meaning of a
signoff depends on the project, but it typically
certifies that committer has the rights to submit
this work [...]
this is frustratingly vague (to me), but I suppose
the extra metadata included in the same paragraph
has a link to: https://developercertificate.org/
---
(c) The contribution was provided directly to me
by some other person who certified (a), (b) or (c)
and I have not modified it.
---
^ took me a few minutes to figure out what you meant,
or where that particular quote came from:
I had never considered this, because historically,
gentoo developers who use their PGP key to commit
rarely use the --signoff feature when committing the
submissions of a contributor, and even if they had,
there's not a stable definition.
in particular, I'm considering the meaning of the phrase:
"some other person who certified" - does this mean the
contributor needs to use their PGP key to sign or...?
it would be good for gentoo to have clarity on this.
I think it could lessen feelings / perceptions that
contributors ought to maintain a copy of the work on a 3rd
party mirror until it is no longer useful (IMO, at least).
-- kuza
next prev parent reply other threads:[~2018-06-15 16:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 7:25 [gentoo-project] Repo mirror & CI: official statement wrt GitHub Michał Górny
2018-06-09 7:50 ` Ulrich Mueller
2018-06-09 7:52 ` Michał Górny
2018-06-09 9:11 ` Thomas Deutschmann
2018-06-11 12:15 ` Kristian Fiskerstrand
2018-06-11 13:28 ` Rich Freeman
2018-06-14 9:47 ` James Le Cuirot
2018-06-14 14:14 ` Alec Warner
2018-06-14 14:25 ` Mauricio Lima Pilla
2018-06-15 0:33 ` Thomas Deutschmann
2018-06-15 1:14 ` Aaron W. Swenson
2018-06-15 2:16 ` Alec Warner
2018-06-15 7:20 ` Kristian Fiskerstrand
2018-06-16 23:55 ` Virgil Dupras
2018-06-17 0:25 ` Rich Freeman
2018-06-16 21:58 ` Andreas K. Huettel
2018-06-16 23:14 ` Rich Freeman
2018-06-16 23:45 ` Alec Warner
2018-06-17 1:05 ` Brian Dolbec
2018-06-14 19:55 ` kuzetsa
2018-06-15 0:26 ` Thomas Deutschmann
2018-06-15 2:27 ` kuzetsa
2018-06-15 11:50 ` Thomas Deutschmann
2018-06-15 14:55 ` kuzetsa
2018-06-15 15:31 ` Rich Freeman
2018-06-15 16:03 ` kuzetsa [this message]
2018-06-15 16:11 ` Rich Freeman
2018-06-15 16:22 ` kuzetsa
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=068c46f9-cc89-702b-8c77-94896e1bf321@gmail.com \
--to=kuzetsa@gmail.com \
--cc=gentoo-project@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