[yocto-ab] YP Advisory Board: VOTE Wind River Linux 8, YP Compatible

akuster akuster at mvista.com
Tue Nov 22 14:44:14 PST 2016


Hmm,


On 11/22/2016 02:32 PM, Jeff Osier-Mixon wrote:
> Hi folks - this is an update from WR Linux 7, please vote yes/no for
> Wind River Linux 7 to be YP Compatible with YP 2.2.
You mean WR Linux 8?

>
> thanks!
>
>   --Contact information--
>       Organization: Wind River
>       Project name: Wind River Linux 8
>       Contact name: Mark Hatle
>       Contact email address: mark.hatle at windriver.com
>       URL to organization or product link:
>       http://www.windriver.com/announces/wind-river-linux-8/
>       Registration date: 2015-12-22
2015 really, is this back to the future?
>       Compliance Agreement revision: 1.0
>       Yocto Project Compatible Version: 2.0

Verison is 2.2, not 2.0 ? does the website need updating ?

Please make corrections.

- Armin
>
>
> Acceptance Criteria:
>    - 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.: Yes
>    - Promoting the OpenEmbedded architecture, layer model, and BSP format.:Yes
>    - Making visible contributions in the OpenEmbedded and component projectsof
> the Yocto Project. Please describe your participation in the comments section
> below.: Yes
>    - Are all your publicly accessible layers listed in the OpenEmbedded Layers
> index (http://layers.openembedded.org)?: Yes
>    - Be a non-profit, or member of the Yocto Project working group, regardless
> of organization size, or if the project's parent organization is an
> open-source project.: Yes
>    - If the project includes build system functionality, are BitBake and
> OpenEmbedded-Core included as components?: Yes
>    - If present, can the directories containing BitBake and OpenEmbedded-Core
> be clearly identified within the system and only contain those components?:
> Yes
>    - Have all patches applied to BitBake and OpenEmbedded-Core (if present)
> been submitted to the open source community?: Yes
>    - Do all layers contain a README file which details the origin of thelayer,
> its maintainer, where to submit changes, and any dependencies or version
> requirements?: Yes
>    - Do all layers build without errors against OpenEmbedded-Core with onlythe
> dependencies/requirements listed in their README file?: Yes
>    - (For BSPs) Does the layer follow the format defined in the Yocto Project
> Board Support Package (BSP) Developers Guide?: Yes
>    - Are hardware support, configuration (distro) policy, and recipe metadata
> separated into different layers which do not depend on each other?: Yes
>    - Is a test report document included showing which combinations of layers,
> recipes, and machines have been tested?: Yes
>    - If any item in the "Yocto Project Compatible Compliance Recommendations"
> list is not true, is this documented in the testing report?: Yes
> Recommendations:
>    - Linux kernels are either based around LTSI kernel versions or a Yocto
> Project kernel version.: Yes
>    - Everything builds successfully with the standard toolchain from OE-Core,
> where the architecture is one supported by OE-Core as standard. This is to
> ensure that your layers are compatible with OE-Core. It is not required that
> the OE-Core toolchain be provided to customers or any downstream projects.:
> Yes
> Explanation:
>




More information about the yocto-ab mailing list