[yocto-ab] YP Advisory Board: VOTE YP Compatible for Wind River Pulsar Linux

[Cobbley, David A]

Yes from Intel.

From: <yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org>> on behalf of "Ta, Lieu" <Lieu.Ta at windriver.com<mailto:Lieu.Ta at windriver.com>>
Date: Thursday, December 10, 2015 at 2:09 PM
To: Jeff Osier-Mixon <jefro at jefro.net<mailto:jefro at jefro.net>>, "yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>" <yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>>
Subject: Re: [yocto-ab] YP Advisory Board: VOTE YP Compatible for Wind River Pulsar Linux

Yes from Wind River


Regards,
Lieu

-----Original Message-----
From: yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Jeff Osier-Mixon
Sent: Friday, December 04, 2015 5:35 PM
To: yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: [yocto-ab] YP Advisory Board: VOTE YP Compatible for Wind River Pulsar Linux

Hi all - this is WR's latest effort, YP based, please give it a look and a vote ASAP

thanks


---------- Forwarded message ----------
From: Yocto Project <webmaster at yoctoproject.org<mailto:webmaster at yoctoproject.org>>
Date: Tue, Dec 1, 2015 at 5:38 PM
Subject: Advisory Board Ballot: Yocto Project Compatible Registration
To: jefro at jefro.net<mailto:jefro at jefro.net>


Submitted on Tuesday, December 1, 2015 - 17:38 Submitted by anonymous user: [147.11.252.42] Submitted values are:

   --Contact information--
     Organization: Wind River Systems
     Project name: Wind River Pulsar Linux
     Contact name: Jason Wessel
     Contact email address: jason.wessel at windriver.com<mailto:jason.wessel at windriver.com>
     URL to organization or product link: pulsar.windriver.com
     Registration date: 2015-12-01
     Compliance Agreement revision: 1.0
     Yocto Project Compatible Version: 1.7


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: We are developing Pulsar directly on GitHub. You can download the build system, cross toolchain, and all layers and packages needed to build Pulsar on Intel® and ARM® hardware targets by following the instructions on GitHub.: https://github.com/WindRiver-OpenSourceLabs/wr-core.




--
Jeff Osier-Mixon
Open Source Community Architect, Intel Corporation
--
_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto-ab
--
_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/yocto-ab