Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.38 as permitted sender) client-ip=23.128.96.38;
Date:   Sat, 9 Dec 2023 02:48:32 +0000
From:   Matthew Wilcox <willy@infradead.org>
To:     Jonathan Corbet <corbet@lwn.net>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] Rework the top-level process page
Message-ID: <ZXPVgB/432RCo/Ux@casper.infradead.org>
References: <87msuk2pu8.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87msuk2pu8.fsf@meer.lwn.net>
Precedence: bulk

On Fri, Dec 08, 2023 at 05:15:43PM -0700, Jonathan Corbet wrote:
> +An introduction to how kernel development works
> +-----------------------------------------------
> +
> +Read these documents first: an understanding of the material here will ease
> +your entry into the kernel community.
>  
>  .. toctree::
>     :maxdepth: 1
>  
> -   license-rules
>     howto
> -   code-of-conduct
> -   code-of-conduct-interpretation
>     development-process
>     submitting-patches
> -   handling-regressions
> +   submit-checklist

I feel the policy section should come first.  Yes, howto is important,
but putting the policy first means it's more important.

> +Policy guides and developer statements
> +--------------------------------------
> +
> +These are the rules that we try to live by in the kernel community (and
> +beyond).
> +
> +.. toctree::
> +   :maxdepth: 1
> +
> +   license-rules
> +   code-of-conduct
> +   code-of-conduct-interpretation
> +   contribution-maturity-model
>     kernel-enforcement-statement
>     kernel-driver-statement
> +   stable-api-nonsense
> +   stable-kernel-rules
> +   management-style
> +   researcher-guidelines