Contributors Manual

Plans for a hypothetical Maintainers Manual (which doubles as a Contributor manual).

• Patch guidelines (style guide (code and patch description), patch tags)
  • What to look for before sending? (No warning added, tests to do)
  • A checklist
• Patch submission process (git-send-email, lore, master-then-branches)
  • What does it mean to review a patch? (kernel doc "Submitting patches" has an example of this)
• CVE Triage process
• Autobuilder

Some related sparse info elsewhere :

• Contributions and Additional Information
• Newcomers
• Community_Guidelines
• Poky_Contributions
• Submitting patches: the essential guide to getting your code into the kernel