Contributors Manual: Difference between revisions
From Yocto Project
Jump to navigationJump to search
RossBurton (talk | contribs) (Created page with "Plans for a hypothetical Maintainers Manual. - Patch guidelines (style guide, patch tags) - Patch submission process (git-send-email, lore, master-then-branches) - [[CVE Tria...") |
Yoann Congal (talk | contribs) (Point to "Yocto Project and OpenEmbedded Contributor Guide") |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
'''Note: The [https://docs.yoctoproject.org/dev/contributor-guide/index.html 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 : | |||
* [https://docs.yoctoproject.org/dev/ref-manual/resources.html Yocto docs: Contributions and Additional Information] | |||
* [https://docs.yoctoproject.org/dev/dev-manual/changes.html Yocto docs: Making Changes to the Yocto Project] | |||
* [[Newcomers]] | |||
* [[Community_Guidelines]] | |||
* [[Poky_Contributions]] | |||
* [https://kernel.org/doc/html/latest/process/submitting-patches.html Submitting patches: the essential guide to getting your code into the kernel] |
Latest revision as of 12:28, 31 August 2023
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 :