[yocto-ab] Form submission from: Yocto Project Compatible Registration

[Chris Hallinan]

yes from Mentor


On Sat, Feb 16, 2013 at 10:08 AM, Stewart, David C <
david.c.stewart at intel.com> wrote:

> Yes
>
> On 2/16/13 6:15 AM, "Yocto Project" <webmaster at yoctoproject.org> wrote:
>
> >Submitted on Sat, 2013-02-16 06:15
> >Submitted by anonymous user: [93.97.175.187]
> >Submitted values are:
> >
> >    --Contact information--
> >      Organization: Yocto Project
> >      Project name: Poky (meta-yocto)
> >      Contact name: Richard Purdie
> >      Contact email address: richard.purdie at linuxfoundation.org
> >      URL to organization or product link:
> >      http://git.yoctoproject.org/cgit.cgi/poky/
> >      Registration date: 2013-02-16
> >      Compliance Agreement revision: 1.0
> >      Yocto Project Compatible Version: 1.3
> >
> >
> >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?: 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 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?: 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:
> >
> >
> >The results of this submission may be viewed at:
> >https://www.yoctoproject.org/node/351547/submission/25
> >
> >_______________________________________________
> >yocto-ab mailing list
> >yocto-ab at yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/yocto-ab
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab
>



-- 
Life is like Linux - it never stands still.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20130219/d3064f8f/attachment.html>