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

Daniel Stenberg Daniel.Stenberg at enea.com
Tue Feb 19 00:23:36 PST 2013


On Tue, 19 Feb 2013, Yocto Project wrote:

Hi,

Interesting submission. He answers 'no' to all questions and no additional 
comments were submitted. Is this a language problem ?

> Submitted on Mon, 2013-02-18 17:53
> Submitted by anonymous user: [61.194.11.241]
> Submitted values are:
>
>    --Contact information--
>      Organization: Japan
>      Project name: Wec7IntelNM10
>      Contact name: Wataru
>      Contact email address: kawamura at contec.jp
>      URL to organization or product link: http://www.contec.com/
>      Registration date: 2013-02-18
>      Compliance Agreement revision: 1.0
>      Yocto Project Compatible Version: 1.2
>
>
> 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.: No (explain
> below)
>   - Promoting the OpenEmbedded architecture, layer model, and BSP format.: No
> (explain below)
>   - Making visible contributions in the OpenEmbedded and component projects
> of
> the Yocto Project.: No (explain below)
>   - Be an open source project, non-profit, or member of the Yocto Project
> working group, regardless of organization size.: No (explain below)
>   - 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?: No (explain below)
>   - 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?: No (explain below)
>   - Do all layers build without errors against OpenEmbedded-Core with only
> the
> dependencies/requirements listed in their README file?: No (explain below)
>   - (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?: No
> (explain below)
>   - 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?: No (explain
> below)
> 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.:
> No (explain below)
> Explanation:
>
>
> The results of this submission may be viewed at:
> https://www.yoctoproject.org/node/351547/submission/26
>
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab
>

-- 
  / Daniel Stenberg



More information about the yocto-ab mailing list