From: "Theodore Ts'o" <tytso@mit.edu>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: Pavel Machek <pavel@ucw.cz>,
"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 23:05:20 -0400 [thread overview]
Message-ID: <20250730030520.GD273706@mit.edu> (raw)
In-Reply-To: <f145b475-5b61-4565-8406-98894e706077@linuxfoundation.org>
Pavel, you might also want to consider that there is a range of ways
that autmation and/or AI can be used.
*) When coding a patch --- this might include Coccinelle, not just
Large Language Models
*) When writing text in the body of the e-mail. And again, it's not
just LLM, but also scripts that might automate Pull requests, or
replies that maintainers like Greg K-H use when people send
malformed patches.
Accusing someone who is using Coccinelle to generate a patch is
somehow lacking ethics is hopefully self-evidently nonsense. And I'd
argue that if someone uses some AI tool to generate patches, or to
help backport a patch to an LTS release, that is similarly a situation
where to claim that therefore the patch "lacks ethics" also just
does't make any sense.
And with both of these categories, there is a distinction regarding
*how* these tools might be used, and how much the human is in the
loop. If a human uses a tool like Coccinelle, but spends a lot of
time verifying the result, that's quite different from a situation
where Skynet sends a T-1000 robot back in time which with instrctions
to kill without any human in the loop.
Developers have been using tools to help their work for decades,
starting with Emacs macros, perl and sed scripts, and then on to
Coccinelle, and more recently Large Language Models. So in many ways,
this is nothing new.
It does seem that in your e-mail messages, that you seem to be
engaging in a bit of "all or nothing" thinking, where if someone is
using some kind of AI tool, that it is automatically the most extreme
end of the spectrum --- and so not only do you not know which e-mails
might have used LLM in some way, you don't know *how* LLM was used,
and how much a human being may have curated the output before sending
the e-mail or the patch.
There are discussions that perhaps people should disclose when LLM's
are used to generate patches, and that might make sense (although
people haven't made similar demands when Emacs macros were used to
help automate say, a global renaming of function or variable).
Regaerdless of how those discussions turn out, your making the
*assumption* that a fellow developer must be lacking in all ethics is
just not a great way to interact with each other. Whether the tool
involved is a bash script sending patches or a pull request, Emacs, or
Coccinelle, or some Large Language Model, using tools is not grounds
for assuming that all messages sent by a particular person is "lacking
in ethics".
Cheers,
- Ted
next prev parent reply other threads:[~2025-07-30 3:05 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 ` Code of Conduct violation complaint 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
2025-07-30 3:05 ` Theodore Ts'o [this message]
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=20250730030520.GD273706@mit.edu \
--to=tytso@mit.edu \
--cc=conduct@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.