Compliancy Discussion: Difference between revisions
From Yocto Project
Jump to navigationJump to search
(Created page with "What would it mean to be "Yocto Project Powered"? [Some initial ideas to seed the discussion] You would need to: * Support in the aims and objectives of YP (decrease fragmenta...") |
No edit summary |
||
| Line 1: | Line 1: | ||
== Yocto Project Aligned == | |||
To use this term in connection with any product or project or in | |||
marketing materials you need to: | |||
* Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks. | |||
* Be promoting the OpenEmbedded Architecture, layer model and BSP format over other systems | |||
* Be making visible contributions in the OpenEmbedded and component projects of the Yocto Project | |||
* Aim for compatibility and interoperability between different metadata layers. | |||
* Be an open source project, charity organisation or small business or consultancy. Larger companies (80+ employees) should really be members of the project. | |||
* | == Yocto Project Powered == | ||
* | |||
To use this term in connection with any product or project or in | |||
* | marketing materials you need to: | ||
* | |||
* | * Be able to satisfy all the criteria for "Yocto Project Aligned" (except company size/type) | ||
* | * Be a member of the Yocto Project | ||
* | * Be able to answer 'Yes' to all the required criteria in the compliancy checklist. | ||
* | |||
== Yocto Project Powered Compliancy Checklist == | |||
* Does the project have clearly identifiable components that correspond to BitBake and OpenEmbedded-Core if these are present? (Y/N) | |||
* Have all patches applied to BitBake and OpenEmbedded-Core components been discussed with the open source community? (Y/N) | |||
* Do all layers build against OE-Core? (Y/N) | |||
* Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N) | |||
* Are hardware support, configuration (distro) policy and recipe meatdata clearly separated into different layers which can be used separately? (Y/N) | |||
Optional Check Items (likely to become required at a later date) | |||
* (O) Are Linux kernels either based around LTSI kernel versions or more recent that the last LTSI release? (Y/N) | |||
* (O) Does all code basically work with the standard toolchain from OE-Core (it may be unoptimised) where the architecture is one supported by OE-Core as standard? (Y/N) | |||
Revision as of 15:00, 20 April 2012
Yocto Project Aligned
To use this term in connection with any product or project or in marketing materials you need to:
- Be working towards and supporting the aims and objectives of the Yocto Project. These include decreasing the fragmentation of embedded ecosystem and focus around a common shared set of tools, formats and best practices. We want to avoid multiple groups of people repeating the same work and have one set of great tools rather than multiple tools with drawbacks.
- Be promoting the OpenEmbedded Architecture, layer model and BSP format over other systems
- Be making visible contributions in the OpenEmbedded and component projects of the Yocto Project
- Aim for compatibility and interoperability between different metadata layers.
- Be an open source project, charity organisation or small business or consultancy. Larger companies (80+ employees) should really be members of the project.
Yocto Project Powered
To use this term in connection with any product or project or in marketing materials you need to:
- Be able to satisfy all the criteria for "Yocto Project Aligned" (except company size/type)
- Be a member of the Yocto Project
- Be able to answer 'Yes' to all the required criteria in the compliancy checklist.
Yocto Project Powered Compliancy Checklist
- Does the project have clearly identifiable components that correspond to BitBake and OpenEmbedded-Core if these are present? (Y/N)
- Have all patches applied to BitBake and OpenEmbedded-Core components been discussed with the open source community? (Y/N)
- Do all layers build against OE-Core? (Y/N)
- Does any hardware support follow the format defined in the Yocto Project Board Support Package (BSP) Developers Guide? (Y/N)
- Are hardware support, configuration (distro) policy and recipe meatdata clearly separated into different layers which can be used separately? (Y/N)
Optional Check Items (likely to become required at a later date)
- (O) Are Linux kernels either based around LTSI kernel versions or more recent that the last LTSI release? (Y/N)
- (O) Does all code basically work with the standard toolchain from OE-Core (it may be unoptimised) where the architecture is one supported by OE-Core as standard? (Y/N)
