From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Sasha Levin <sashal@kernel.org>,
skhan@linuxfoundation.org, rdunlap@infradead.org,
federico.vaga@vaga.pv.it, apw@canonical.com, joe@perches.com,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: remove Assisted-by references
Date: Sat, 10 Oct 2026 21:04:59 -0400 [thread overview]
Message-ID: <20261010210459.754754db@226.227.38.69.naturalwireless.com> (raw)
In-Reply-To: <87h5iuc34d.fsf@trenco.lwn.net>
On Fri, 09 Oct 2026 09:20:18 -0600
Jonathan Corbet <corbet@lwn.net> wrote:
> Krzysztof Kozlowski <krzk@kernel.org> writes:
>
> > On 09/10/2026 10:31, Sasha Levin wrote:
> >> The Maintainers Summit reached consensus to deprecate the Assisted-by
> >> tag. Remove the documentation requiring it.
> >
> > Please provide here some sort of arguments used in that summit
> > consensus/discussion. This basically reverts/changes previous consensus
> > [1], which is fine itself, but it lacks reasoning.
> >
> > [1] https://lore.kernel.org/workflows/2026070224-unholy-commode-cf45@gregkh/
>
> I'm working on a report on the discussion, don't worry...Monday or
> Tuesday probably.
But changes like this should not rely on LWN articles. They need to be
presented in mailing list.
Honestly, I would like to have a "Vibe-coded-with:" tag. Why?, when I
do a git blame and want to ask the author why they did the change the
way they did, I would likely not expect much if they vibe coded it.
When we first started talking about what constitutes an Assisted-by tag
(using AI to debug, or review, or simply add templates), there wasn't
really any agreement to where it should stop. I have always been of the
idea that I want to know if someone actually wrote the code. If all you
did was use prompts, then you didn't write it. You simply instructed
a computer what to do. Much like helping a junior engineer. But with a
junior engineer, they would have the authorship and signed-off-by and
the kernel developer would likely just get "suggested-by". But we don't
do that for computers. But still it should be tagged that the author
didn't write the code somehow.
I wasn't at the maintainer summit to express my opinion so I'm doing it
here.
-- Steve
prev parent reply other threads:[~2026-10-11 1:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 8:31 Sasha Levin
2026-10-09 9:38 ` Laurent Pinchart
2026-10-09 10:09 ` Sasha Levin
2026-10-09 10:05 ` Krzysztof Kozlowski
2026-10-09 10:24 ` Greg KH
2026-10-09 15:20 ` Jonathan Corbet
2026-10-11 1:04 ` Steven Rostedt [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=20261010210459.754754db@226.227.38.69.naturalwireless.com \
--to=rostedt@goodmis.org \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=joe@perches.com \
--cc=krzk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=workflows@vger.kernel.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
all inboxes | Powered by JetHome®