[yocto-ab] Yocto Project AB VOTE: Yocto GENIVI Baseline

[Osier-mixon, Jeffrey]

Hi all

This is an important vote for YP Compatible status for the Yocto
Project GENIVI Baseline. This software enables YP to be used as the
baseline in GENIVI automotive infotainment builds.

More info about the project: https://projects.genivi.org/meta-ivi/

Their application is appended below. Please vote YES or NO by end of
day Thursday.

thanks
_______________________________________________
Submitted on Tuesday, July 2, 2013 - 04:40
Submitted by anonymous user: [128.224.251.2]
Submitted values are:

   --Contact information--
     Organization: Wind River Systems
     Project name: Yocto GENIVI Baseline
     Contact name: Holger Behrens
     Contact email address: holger.behrens at windriver.com
     URL to organization or product link:
     https://projects.genivi.org/meta-ivi/
     Registration date: 2013-07-02
     Compliance Agreement revision: 1.0
     Yocto Project Compatible Version: 1.4


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 projects of
the Yocto Project.: Yes
  - Be an open source project, non-profit, or member of the Yocto Project
working group, regardless of organization size.: Yes
  - If the project includes build system functionality, are BitBake and
OpenEmbedded-Core included as components?: No (explain below)
  - If present, can the directories containing BitBake and OpenEmbedded-Core
be clearly identified within the system and only contain those components?:
No (explain below)
  - 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 the layer,
its maintainer, where to submit changes, and any dependencies or version
requirements?: Yes
  - Do all layers build without errors against OpenEmbedded-Core with only the
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?: No (explain below)
  - 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?: No (explain below)
  - 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:
The project is a layer which depends on Poky, and therefore depend on build
system functionality provided by Poky.  It's not a BSP.

We do smoke test the three builds that we currently support
* QEMU (ARMv7) — emulated machine: vexpressa9
* QEMU (IA-32) — emulated machine: qemux86
* QEMU (x86-64) — emulated machine: qemux86-64
But otherwise depend on Poky/oe-core to work and been tested.
--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org