Yocto Project and OpenEmbedded Contributor Guide
The Yocto Project and OpenEmbedded are open-source, community-based projects so contributions are very welcome, it is how the code evolves and everyone can effect change. Contributions take different forms, if you have a fix for an issue you’ve run into, a patch is the most appropriate way to contribute it. If you run into an issue but don’t have a solution, opening a defect in Bugzilla or asking questions on the mailing lists might be more appropriate. This guide intends to point you in the right direction to this.
- 1 Identify the component
- 2 Reporting a Defect Against the Yocto Project and OpenEmbedded
- 3 Recipe Style Guide
- 4 Contributing Changes to a Component
- 4.1 Contributing through mailing lists — Why not using web-based workflows?
- 4.2 Preparing Changes for Submission
- 4.3 Creating Patches
- 4.4 Validating Patches with Patchtest
- 4.5 Sending the Patches via Email
- 4.6 Using Scripts to Push a Change Upstream and Request a Pull
- 4.7 Submitting Changes to Stable Release Branches
- 4.8 Taking Patch Review into Account
- 4.9 Tracking the Status of Patches
Permission is granted to copy, distribute and/or modify this document under the terms of the Creative Commons Attribution-Share Alike 2.0 UK: England & Wales as published by Creative Commons.
To report any inaccuracies or problems with this (or any other Yocto Project)
manual, or to send additions or changes, please send email/patches to the Yocto
Project documentation mailing list at docs@lists.yoctoproject.org
or
log into the Libera Chat #yocto
channel.