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
