a926dd6cdd
We have a long history with maintainers files and good and bad experiences. There are people who'd like to see a kernel style machine readable file which defines exactly which people should be reviewing which areas. In practise, the files we do have struggle to stay up to date (e.g. the recipe maintainers file) and such a file would also cause conflicts of expectations where person X would want to be cc'd on patches touching file Y and want a revert if they hadn't acked it. We also don't have clearly defined boundaries in some areas, e.g. toolchain. We have a wide peer review system and nobody gets to make changes without that review, even myself as the lead for OE-Core/Bitbake. I do want to recognise that some people are key experts on particular areas and hightlight that their views on those areas do carry weight. With that also comes repsonsibility to help try and figure out bugs, help with review and so on. I've tried to strike a balance with this file to detail who some of the experts for particular areas are and to also highlight where we don't have coverage and that there are opportunities. I've tried to put the file in the wider context of the project, not just OE-Core. It is in a repo rather than a wiki so we have visibility to changes through the change control process. I'm sure I will miss people, sorry, it is inevitable when you try and make a list. There may be people who want to step down and don't want to be in this role, I'm also hoping there are going to be some new volunteers to help in some areas. Please do send follow up updates, this patch is really meant to help get us started. Volunteers to maintainer specific areas of the project are very welcome and feel free to reach out to ask about areas or getting started and working towards an official maintainer role (e.g. help with bug fixing). (From OE-Core rev: b629978efae35d5ea3821f4375bc0d8228b6cc26) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
The project works using a mailing list patch submission process. Patches should be sent to the mailing list for the repository the components originate from (see below). Throughout the Yocto Project, the README files in the component in question should detail where to send patches, who the maintainers are and where bugs should be reported.
A guide to submitting patches to OpenEmbedded is available at:
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
There is good documentation on how to write/format patches at:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.