Contributors Manual
From Yocto Project
Jump to navigationJump to search
Note: The Yocto Project and OpenEmbedded Contributor Guide should be the place to store this information.
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 :