From: Hector Martin <marcan@marcan.st>
To: Richard Acayan <mailingradian@gmail.com>, linux-kernel@vger.kernel.org
Cc: Asahi Lina <lina@asahilina.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg KH <gregkh@linuxfoundation.org>,
Michael Dolan <mdolan@linuxfoundation.org>
Subject: Re: Linux kernel DCO
Date: Thu, 2 Mar 2023 12:35:15 +0900 [thread overview]
Message-ID: <c1bf62a2-e381-c796-2219-17a578987a76@marcan.st> (raw)
In-Reply-To: <ZAAVuo81E3XA6/LS@radian>
On 02/03/2023 12.19, Richard Acayan wrote:
>> I agree that this should be changed (for many reasons, I could write
>> about this at length), and as I'm sure you can imagine, such change
>> would probably have to be a coordinated push with buy-in from several
>> kernel stakeholders. So I would appreciate it if you don't turn this
>> into a public discussion at this time, and let us figure out how to deal
>> with it when the time comes.
>
> Sorry to bother you, but what happened?
An offline discussion happened ;)
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=d4563201f33a022fc0353033d9dfeb1606a88330
>
> Two Acked-by's are a bit underwhelming for a coordinated push with
> buy-in from several kernel stakeholders.
The patch is by Linus, it's acked by Greg (who originally introduced the
"real name" wording) and by Mike (SVP of Projects & Legal at the Linux
Foundation, i.e. a lawyer). What more do you want?
Things don't always happen as one envisioned, but now the problem is
fixed either way. Linus ultimately gets to write the rules on this,
there's no need for more acks.
> Of course, it's easy to call this naive and ignorant. I accepted this
> explanation and respected this request to not turn this into a public
> discussion until the time comes. Now, I wonder if this patch was written
> and applied later than it should have been because we misunderstood the
> kernel contribution process as an aristocracy for this specific case.
Ultimately the reality is that enforcement of the "real name" rule has
been wildly inconsistent and some subsystems (like DRM) have always
accepted pseudonyms. The original wording was misguided and conflated
names with identity, leading to the eventual divergence of opinion on
how it should be enforced. The subject came up offline, and now the
official wording has been changed to match reality (i.e. that what the
kernel actually wants is knowing who people are in an abstract sense of
trust/continuity/reachability, not their "real" name whatever that might
mean).
- Hector
prev parent reply other threads:[~2023-03-02 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y820a/niMYtHfe8k@radian>
[not found] ` <58a5ad01-dbfc-04a7-2234-c57bb627ee84@marcan.st>
[not found] ` <Y84K1N3fzz/J4Pxa@radian>
[not found] ` <6d96fb3c-9027-c612-fca4-e22c7c19186f@marcan.st>
2023-03-02 3:19 ` Linux kernel DCO Richard Acayan
2023-03-02 3:35 ` Hector Martin [this message]
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=c1bf62a2-e381-c796-2219-17a578987a76@marcan.st \
--to=marcan@marcan.st \
--cc=gregkh@linuxfoundation.org \
--cc=lina@asahilina.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=mdolan@linuxfoundation.org \
--cc=torvalds@linux-foundation.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