mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: "conduct@kernel.org" <conduct@kernel.org>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Code of Conduct violation complaint
Date: Tue, 29 Jul 2025 11:15:36 -0600	[thread overview]
Message-ID: <f145b475-5b61-4565-8406-98894e706077@linuxfoundation.org> (raw)
In-Reply-To: <aIXsYh9afmTxiqXF@duo.ucw.cz>

On 7/27/25 03:07, Pavel Machek wrote:
> On Thu 2025-07-24 13:18:16, Shuah Khan wrote:
>> On 7/17/25 10:32, Shuah Khan wrote:
>>> Hi Pavel,
>>>
>>> The Code of Conduct Committee holds these conversation privately
>>> with the people involved. Looks like you cc'ed the mailing list.
>>> Respecting your choice, we can continue this conversation publicly.
>>>
>>> Chose one or all of these threads to apologize to the developer
>>> directly.
>>
>> If you haven't already done so, chose one or all of these
>> threads to apologize to the developer and cc code of conduct list.
>>
>>>
>>> https://lore.kernel.org/all/aG2B6UDvk2WB7RWx@duo.ucw.cz/
>>> https://lore.kernel.org/all/aG2ClcspT5ESNPGk@duo.ucw.cz/
>>> https://lore.kernel.org/all/aG2BjYoCUYUaLGsJ@duo.ucw.cz/
>>>
> 
> Please clearly state what committee believes I did wrong and what
> should I apologize about.
> 
> There are clearly multiple actors behind Sasha Levin email address,
> and one of them is clearly LLM, sending hallucinations to the list.
> 
> Unfortunately, LLM and the human identify them in the same way, as
> "Sasha Levin". I am willing to apologize for the confusion, clearly
> human is human and has ethics, but I'm not the one who caused the
> confusion.

The use of LLMs in the development process and rules about such use
including how to clearly state if LLMs are used in the process is a
timely and important topic. It can be confusing when a developer
doesn't clearly state the LLM use.

However, as you acknowledged here that you couldn't tell if these
patches originated from the developer or not. In which case, there
are several constructive ways to move forward to clear up the confusion.

1. Send response to the patch and hold a constructive discussion about
    the confusion.
      
2. Start a separate thread to talk to the developer privately or publicly
    in a respectful and constructive way.

3. Start a Tech board conversation with the TAB.

You didn't take any of the above constructive approaches. Instead your
responses included personal attacks which are visible to community and
others to see.

The Code of Conduct Committee has determined these are personal attacks.
These are a clear violation of the agreed upon code of conduct which can
be easily remedied with an apology.

- https://docs.kernel.org/process/code-of-conduct.html
- https://docs.kernel.org/process/code-of-conduct-interpretation.html#code-of-conduct-interpretation

> 
> Please explain how to refer to the human being between "Sasha Levin"
> email address.

Assume you are speaking to a fellow developer and ask them to give details
on the nature of LLM use in the patch. It will result in a constructive
conversation for these important topics at hand.

thanks,
-- Shuah (On behalf of the Code of Conduct Committee)

  reply	other threads:[~2025-07-29 17:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13a6b8e3-a35a-425d-bafc-006e0a52599f@linuxfoundation.org>
2025-07-15 19:08 ` Pavel Machek
2025-07-17 16:32   ` Shuah Khan
2025-07-24 19:18     ` Shuah Khan
2025-07-27  9:07       ` Pavel Machek
2025-07-29 17:15         ` Shuah Khan [this message]
2025-07-30  3:05           ` Theodore Ts'o
2025-07-30  4:42   ` Hillf Danton

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=f145b475-5b61-4565-8406-98894e706077@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=conduct@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®