From: Sasha Levin <sashal@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, josh@joshtriplett.org,
kees@kernel.org, konstantin@linuxfoundation.org,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
workflows@vger.kernel.org, joe@perches.com,
rdunlap@infradead.org
Subject: Re: [PATCH v3] README: restructure with role-based documentation and guidelines
Date: Tue, 18 Nov 2025 11:52:12 -0500 [thread overview]
Message-ID: <aRykPFH0sIfmARvs@laps> (raw)
In-Reply-To: <87wm3n47u6.fsf@trenco.lwn.net>
On Tue, Nov 18, 2025 at 09:35:29AM -0700, Jonathan Corbet wrote:
>Sasha Levin <sashal@kernel.org> writes:
>
>> Reorganize README to provide targeted documentation paths for different user
>> roles including developers, researchers, security experts, maintainers, and AI
>> coding assistants. Add quick start section and essential docs links.
>>
>> Include proper attribution requirements for AI-assisted contributions using
>> Assisted-by tags with agent details and tools used.
>>
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>> Changes in v3:
>> - Replace "Agentic Coding" terminology with clearer "AI Coding Assistants"
>> - Add concrete examples of proper Assisted-by tag usage with multiple formats
>> - Add "Bad examples" section showing anti-patterns to avoid
>> - Add detailed tool categorization distinguishing specialized vs basic tools
>> - Add explicit format specification: $AGENT_NAME:$MODEL_VERSION [$TOOL1] ...
>> - Expand section description to clarify it applies to both AI tools and
>> developers using AI tools
>>
>> README | 212 +++++++++++++++++++++++++++++++++++++++---
>> scripts/checkpatch.pl | 1 +
>> 2 files changed, 202 insertions(+), 11 deletions(-)
>
>Overall I really like this change. We could quibble forever about the
>details, but that's probably not worthwhile.
Thanks Jon!
What would you say about taking this patch (assuming this falls under the
Documentation subsystem) if I completely drop the AI parts for now?
>That said, I have one quibble :)
>
>> +Examples of Proper Attribution:
>> +
>> +Good examples:
>> + Assisted-by: AI-Tool:model-version-1.0 coccinelle
>> + Assisted-by: AI-Assistant:v2.5.0
>> + Assisted-by: Code-Helper:model-2024-04-09 sparse smatch
>> + Assisted-by: ML-Agent:version-2024-11
>> +
>> +Bad examples (DO NOT USE):
>> + Assisted-by: AI # Too vague
>> + Assisted-by: AI-Tool coccinelle git # Don't list basic tools
>> + Signed-off-by: AI Assistant <ai@...> # NEVER - AI cannot sign off
>
>I don't think this belongs here - we don't have examples of good SOB
>lines - or of anything else. What this needs, instead, is a link to
>Dave's tools document once that goes in.
Makes sense.
>(We also, in truth, do not yet have a consensus on what the attribution
>tags should be, and here isn't the place to try to form one.)
Ack - I've posted this v3 in response to tglx's ask on Dave's doc about having
a standard tag for this to gather more input prior to LPC.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-11-18 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 21:38 Sasha Levin
2025-11-18 1:11 ` Bagas Sanjaya
2025-11-18 2:24 ` Sasha Levin
2025-11-18 8:08 ` Geert Uytterhoeven
2025-11-18 16:35 ` Jonathan Corbet
2025-11-18 16:49 ` Kees Cook
2025-11-18 16:52 ` Sasha Levin [this message]
2025-11-18 17:42 ` Jonathan Corbet
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=aRykPFH0sIfmARvs@laps \
--to=sashal@kernel.org \
--cc=corbet@lwn.net \
--cc=joe@perches.com \
--cc=josh@joshtriplett.org \
--cc=kees@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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