All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-doc@vger.kernel.org, josh@joshtriplett.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 08:49:13 -0800	[thread overview]
Message-ID: <202511180848.8A660DDB@keescook> (raw)
In-Reply-To: <87wm3n47u6.fsf@trenco.lwn.net>

On Tue, Nov 18, 2025 at 09:35:29AM -0700, Jonathan Corbet wrote:
> 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.
> 
> (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.)

Agreed -- I love the new sections, but we need to drop the Assisted-by
portion until we've had the in-person discussions at Maintainers/LPC.

-Kees

-- 
Kees Cook

  reply	other threads:[~2025-11-18 16:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 21:38 [PATCH v3] README: restructure with role-based documentation and guidelines 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 [this message]
2025-11-18 16:52   ` Sasha Levin
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=202511180848.8A660DDB@keescook \
    --to=kees@kernel.org \
    --cc=corbet@lwn.net \
    --cc=joe@perches.com \
    --cc=josh@joshtriplett.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=sashal@kernel.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 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.