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

[Osier-mixon, Jeffrey]

I'm definitely putting this one on the agenda for tomorrow as well


On Tue, Mar 19, 2013 at 1:51 PM, Yocto Project
<webmaster at yoctoproject.org> wrote:
> Submitted on Tue, 2013-03-19 13:51
> Submitted by anonymous user: [108.45.150.102]
> Submitted values are:
>
>    --Contact information--
>      Organization: Texas Instruments
>      Project name: Arago Project
>      Contact name: Denys Dmytriyenko
>      Contact email address: denys at ti.com
>      URL to organization or product link: http://arago-project.org
>      Registration date: 2013-03-19
>      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.: 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: Texas Instruments tries to base own kernel releases around LTK
> kernel versions, which is a goal, but not always possible. For new and
> current platforms TI uses the very latest kernel version (i.e. 3.8.x or
> 3.9rc) with focus on upstreaming and mainlining the changes. For legacy
> platforms, it may be required to use older kernel versions from a vendor
> tree
> (i.e. 2.6.37), if some of the features were not accepted upstream and/or
> were
> not forward-ported.
>
>
> The results of this submission may be viewed at:
> https://www.yoctoproject.org/node/351547/submission/29
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab



--
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org