1Poky 2==== 3 4Poky is an integration of various components to form a pre-packaged 5build system and development environment which is used as a development and 6validation tool by the [Yocto Project](https://www.yoctoproject.org/). It 7features support for building customised embedded style device images 8and custom containers. There are reference demo images ranging from X11/GTK+ 9 to Weston, commandline and more. The system supports cross-architecture 10application development using QEMU emulation and a standalone toolchain and 11SDK suitable for IDE integration. 12 13Additional information on the specifics of hardware that Poky supports 14is available in README.hardware. Further hardware support can easily be added 15in the form of BSP layers which extend the systems capabilities in a modular way. 16Many layers are available and can be found through the 17[layer index](https://layers.openembedded.org/). 18 19As an integration layer Poky consists of several upstream projects such as 20[BitBake](https://git.openembedded.org/bitbake/), 21[OpenEmbedded-Core](https://git.openembedded.org/openembedded-core/), 22[Yocto documentation](https://git.yoctoproject.org/cgit.cgi/yocto-docs/), 23the '[meta-yocto](https://git.yoctoproject.org/cgit.cgi/meta-yocto/)' layer 24which has configuration and hardware support components. These components 25are all part of the Yocto Project and OpenEmbedded ecosystems. 26 27The Yocto Project has extensive documentation about the system including a 28reference manual which can be found at <https://docs.yoctoproject.org/> 29 30OpenEmbedded is the build architecture used by Poky and the Yocto project. 31For information about OpenEmbedded, see the 32[OpenEmbedded website](https://www.openembedded.org/). 33 34Contribution Guidelines 35----------------------- 36 37The project works using a mailing list patch submission process. Patches 38should be sent to the mailing list for the repository the components 39originate from (see below). Throughout the Yocto Project, the README 40files in the component in question should detail where to send patches, 41who the maintainers are and where bugs should be reported. 42 43A guide to submitting patches to OpenEmbedded is available at: 44 45<https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded> 46 47There is good documentation on how to write/format patches at: 48 49<https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines> 50 51Where to Send Patches 52--------------------- 53 54As Poky is an integration repository (built using a tool called combo-layer), 55patches against the various components should be sent to their respective 56upstreams: 57 58OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/): 59 60- Git repository: <https://git.openembedded.org/openembedded-core/> 61- Mailing list: openembedded-core@lists.openembedded.org 62 63BitBake (files in bitbake/): 64 65- Git repository: <https://git.openembedded.org/bitbake/> 66- Mailing list: bitbake-devel@lists.openembedded.org 67 68Documentation (files in documentation/): 69 70- Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/> 71- Mailing list: docs@lists.yoctoproject.org 72 73meta-yocto (files in meta-poky/, meta-yocto-bsp/): 74 75- Git repository: <https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto> 76- Mailing list: poky@lists.yoctoproject.org 77 78If in doubt, check the openembedded-core git repository for the content you 79intend to modify as most files are from there unless clearly one of the above 80categories. Before sending, be sure the patches apply cleanly to the current 81git repository branch in question. 82 83[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/765/badge)](https://bestpractices.coreinfrastructure.org/projects/765) 84 85