[yocto-ab] YP Advisory Board: VOTE YP Compatible, Angstrom/YP 1.7

[William Mills]

Yes, from TI
(I thought I had already)

On 08/03/2015 07:42 PM, Jeff Osier-Mixon wrote:
> Hi folks - I need a few more votes to finish this one up. If you
> haven't voted yet, please let me know.
>
> thanks
>
> On Fri, Jul 24, 2015 at 12:08 PM, Jeff Osier-Mixon <jefro at jefro.net
> <mailto:jefro at jefro.net>> wrote:
>
>     Hi all - this is a simple update for the Angstrom release to be YP
>     Compatible vs. YP 1.7. Angstrom has been a YP Compatible project
>     for several years. Please vote yes/no
>
>     thanks
>
>        --Contact information--
>          Organization: The Angstrom Distribution
>          Project name: The Angstrom Distribution
>          Contact name: Koen Kooi
>          Contact email address: koen at dominion.thruhere.net
>     <mailto:koen at dominion.thruhere.net>
>          URL to organization or product link:
>          http://www.angstrom-distribution.org/
>          Registration date: 2015-07-18
>          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
>     <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?: 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 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.: No (explain below)
>       - 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: As mentioned in the previous registrations, this is a
>     distro
>     layer, so no embedded bitbake or OE-core, no kernels, etc.
>
>     -- 
>     Jeff Osier-Mixon
>     Open Source Community Architect, Intel Corporation
>
>
>
>
> -- 
> Jeff Osier-Mixon
> Open Source Community Architect, Intel Corporation
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20150804/c97f1243/attachment.html>