linux-kernel - Re: [PATCH v2 1/2] README: restructure with role-based documentation and guidelines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdWaVvAfm6LMxSpPuz3yZ7FDAexbUTOXrg58TqoWbce5ag@mail.gmail.com>
Date: Mon, 11 Aug 2025 10:22:34 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Sasha Levin <sashal@...nel.org>
Cc: corbet@....net, josh@...htriplett.org, kees@...nel.org, 
	konstantin@...uxfoundation.org, linux-doc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, rostedt@...dmis.org, workflows@...r.kernel.org
Subject: Re: [PATCH v2 1/2] README: restructure with role-based documentation
 and guidelines

Hi Sasha,

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