linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Sasha Levin <sashal@kernel.org>
Cc: corbet@lwn.net, josh@joshtriplett.org, kees@kernel.org,
	 konstantin@linuxfoundation.org, linux-doc@vger.kernel.org,
	 linux-kernel@vger.kernel.org, rostedt@goodmis.org,
	workflows@vger.kernel.org
Subject: Re: [PATCH v2 1/2] README: restructure with role-based documentation and guidelines
Date: Mon, 11 Aug 2025 10:22:34 +0200	[thread overview]
Message-ID: <CAMuHMdWaVvAfm6LMxSpPuz3yZ7FDAexbUTOXrg58TqoWbce5ag@mail.gmail.com> (raw)
In-Reply-To: <20250809234008.1540324-2-sashal@kernel.org>

Hi Sasha,

On Sun, 10 Aug 2025 at 10:09, Sasha Levin <sashal@kernel.org> wrote:
> 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>

Thanks for your patch!

> --- a/README
> +++ b/README

> +Who Are You?
> +============
> +
> +Find your role below:
> +
> +* New Kernel Developer - Getting started with kernel development
> +* Academic Researcher - Studying kernel internals and architecture
> +* Security Expert - Hardening and vulnerability analysis
> +* Backport/Maintenance Engineer - Maintaining stable kernels
> +* System Administrator - Configuring and troubleshooting
> +* Maintainer - Leading subsystems and reviewing patches

Kernel Maintainer?
Driver/Subsystem Maintainer?

> +* Hardware Vendor - Writing drivers for new hardware
> +* Distribution Maintainer - Packaging kernels for distros
> +* Agentic Coding - AI assistants working with kernel code

Given the extensive split, what about normal (existing) kernel
developers?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  parent reply	other threads:[~2025-08-11  8:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-09 23:40 [PATCH v2 0/2] Add unified configuration for coding agents Sasha Levin
2025-08-09 23:40 ` [PATCH v2 1/2] README: restructure with role-based documentation and guidelines Sasha Levin
2025-08-10 15:44   ` Joe Perches
2025-08-10 16:46     ` Sasha Levin
2025-08-11  0:10       ` Joe Perches
2025-08-11  0:06   ` Randy Dunlap
2025-08-11  8:22   ` Geert Uytterhoeven [this message]
2025-08-11 15:48     ` Sasha Levin
2025-08-15  6:19   ` Kees Cook
2025-08-09 23:40 ` [PATCH v2 2/2] agents: add unified agent coding assistant configuration Sasha Levin
2025-08-10  7:01   ` Greg KH
2025-08-10 14:22     ` Sasha Levin
2025-08-14  0:36       ` Steven Rostedt
2025-08-15  6:23   ` Kees Cook

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=CAMuHMdWaVvAfm6LMxSpPuz3yZ7FDAexbUTOXrg58TqoWbce5ag@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=corbet@lwn.net \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).