From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: Marek Szuba <marecki@gentoo.org>
Subject: Re: [gentoo-project] [RFC] glep-0076: add clarification about the sign-off requirements
Date: Wed, 28 Jul 2021 11:03:38 -0400 [thread overview]
Message-ID: <CAGfcS_krGQABLjmJq=L95pVR-5ncYGEYdXPt1zm5Q82x0uOP4A@mail.gmail.com> (raw)
In-Reply-To: <utuke7ax0@gentoo.org>
On Wed, Jul 28, 2021 at 10:47 AM Ulrich Mueller <ulm@gentoo.org> wrote:
>
> We have taken the blueprint for the certificate-of-origin model from
> Linux, and it does have a real name requirement. I'd rather not change
> any element of it without getting legal advice first.
>
While I completely get the sentiment, and tend to be a proponent of
real-name at least from Gentoo contributors, we have to keep in mind
that we're not Linux.
The Linux Foundation can afford to push people away, because half of
their contributions are probably corporate at this point, and most
contributors have a lot of motivation to get their patches included.
Their customers (who also are their board members and financial
backers) probably also value a more conservative approach.
I'm sure a lawyer will tell you that you're taking less risk if you
require legal names. I'll go ahead and add my own advice that
everybody reading this will also be taking less risk if they never get
in a car or better still don't get out of bed. Getting legal advice
isn't a bad idea, but ultimately the organization has to decide
whether the risks/benefits are worth it. A lawyer might be able to
help the organization better understand these tradeoffs, but if you're
going to wait for somebody else to call the lawyer for you it isn't
likely to happen. I suspect that most anonymous contributors don't
care THAT much - they're just going to stop contributing.
I think the key is to find the balance. You can make an argument
either way, and I'm not sure how essential these anonymous
contributions are. If we're better off without them then just be
aware that is the choice we're making...
--
Rich
next prev parent reply other threads:[~2021-07-28 15:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 4:07 [gentoo-project] [RFC] glep-0076: add clarification about the sign-off requirements Joonas Niilola
2021-07-28 4:29 ` Sam James
2021-07-28 9:49 ` Emily Rowlands
2021-07-28 7:14 ` Michał Górny
2021-07-28 10:39 ` Ulrich Mueller
2021-07-28 11:50 ` Thomas Deutschmann
2021-07-28 15:42 ` Sam James
2021-07-28 17:26 ` Michael Jones
2021-07-28 10:49 ` Andrew Ammerlaan
2021-07-28 11:22 ` Ulrich Mueller
2021-07-28 14:08 ` Marek Szuba
2021-07-28 14:47 ` Ulrich Mueller
2021-07-28 15:03 ` Rich Freeman [this message]
2021-07-28 15:08 ` Ulrich Mueller
2021-07-28 15:15 ` Rich Freeman
2021-07-28 15:49 ` Ulrich Mueller
2021-07-29 6:36 ` Joonas Niilola
2021-07-28 15:12 ` Andrew Ammerlaan
2021-07-28 15:14 ` Marek Szuba
2021-07-28 14:33 ` Rich Freeman
2021-07-29 6:39 ` Joonas Niilola
2021-07-29 8:05 ` Ulrich Mueller
2021-07-29 8:31 ` Joonas Niilola
2021-07-29 9:53 ` Ulrich Mueller
2021-07-29 10:30 ` Joonas Niilola
2021-07-29 11:46 ` Ulrich Mueller
2021-07-28 17:30 ` Alec Warner
2021-07-29 6:28 ` Joonas Niilola
2021-08-05 6:01 ` Anna Vyalkova
2021-08-05 9:43 ` Ulrich Mueller
2021-08-05 11:02 ` Anna Vyalkova
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_krGQABLjmJq=L95pVR-5ncYGEYdXPt1zm5Q82x0uOP4A@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=marecki@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