Bug 16007

Summary: Yocto Compatible Submission for Yocto Project
Product: [Yocto Project Subprojects] Yocto Project Compatible Reporter: Michael Halstead <mhalstead>
Component: yocto-project-compatible-requestsAssignee: LF PMO <operations>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: richard.purdie
Version: 3   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard: Complete- sending to advocacy
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Michael Halstead 2025-10-14 22:27:16 UTC
Organization/Company Name
Yocto Project
Organization URL
www.yoctoproject.org
Contact Name
Richard Purdie
Email
richard.purdie@linuxfoundation.org
Layer / Product Name
Meta-poky
Layer URL
https://git.yoctoproject.org/meta-yocto/
Layer / Product Description (180 character limit)
Poky reference distribution for the Yocto Project
The submitter is a current Yocto Project member (Platinum, Gold, or Silver level), or the submission is being sponsored* by a Yocto Project member or OpenEmbedded (please state which member or indicate OpenEmbedded below).
Yes, the submitter is a current YP member.
List the branches to which you are applying for compatibility.
kirkstone, scarthgap, walnascar, master
All publicly accessible layers being submitted are listed in the OpenEmbedded Layers index (http://layers.openembedded.org).
Yes
All layers in the submission contain a README* file which details the origin of the layer, its maintainer, where to submit changes, and any dependencies or version requirements of any required layers or tools.
Yes
All layers in the submission contain a SECURITY* file which details how and where to report any security issue arising with the layer.
Yes
All layers build without errors against OpenEmbedded-Core, with only the required dependencies listed in their README file?
Yes
All layers in this submission do not disable or otherwise bypass error QA checks as defined as ‘core’ tests in the package_qa code and the yocto-check-layer script.
Yes
All submitted layers only access the network during do_fetch and only use bitbake fetcher APIs for source components during builds so that source mirroring code functions correctly and software manifests are fully complete.
Yes
All layers in this submission have a mandated dependency on have Yocto Project Compatible Status,
Yes
Inclusion of any layer in the submission does not change the behavior/configuration of the overall system without the user explicitly opting into those changes
Yes
All layers have successfully passed testing with yocto-check-layer
Yes
Any BSP layers contained follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide
Yes
Hardware support, configuration (distro) policy, and recipe metadata are separated into different layers which do not depend on each other.
Yes
If the submission includes build system functionality, BitBake and OpenEmbedded-Core are included as components to provide that and can be clearly identified and isolated.
Yes
Any patches applied to BitBake and OpenEmbedded-Core (if present) have been submitted to the open source community using the upstream review process for the component
Yes
The submitter attests they are supporting and promoting the OpenEmbedded architecture, layer model, and BSP format. The submitter attests to working towards and supporting the aims and objectives of the Yocto Project including: Decreasing the fragmentation of embedded ecosystem. Focusing around a common shared set of tools, formats and best practices. Avoiding multiple groups of people repeating the same work. Aiming for one set of great tools rather than multiple tools with drawbacks. The submitter attests to making visible contributions to OpenEmbedded and Yocto Project components.
Yes
The submitter acknowledges the following recommendations: Ideally Linux kernel versions should be based around Yocto Project kernel version. Submitted layers should build with the standard OE-Core toolchain without modification. Submitted layers should add testing and promote automated testing and CI to ensure the best end user experience. Test results for the submission should be published in a format compatible with resulttool to allow for test result interchange and comparison and to document the supported configurations.
Yes
Comment 1 LF PMO 2025-11-13 01:44:27 UTC
Complete- sending to advocacy