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

[Ta, Lieu]

Yes from Wind River


Regards,
Lieu

-----Original Message-----
From: yocto-ab-bounces at yoctoproject.org [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Osier-mixon, Jeffrey
Sent: Thursday, April 24, 2014 12:41 PM
To: akuster at mvista
Cc: Yocto Project; yocto-ab at yoctoproject.org
Subject: Re: [yocto-ab] Form submission from: Yocto Project Compatible Registration

I love it that you guys are voting before I even call for a vote :)

All - please vote to upgrade the Arago YP Compatible status from 1.4 to 1.5

thanks

On Thu, Apr 24, 2014 at 12:35 PM, akuster at mvista <akuster at mvista.com> wrote:
> On 4/24/14, 12:17 PM, Yocto Project wrote:
>
> Yes on behalf of MontaVista.
>
> - Armin
>
>
>> Submitted on Thursday, April 24, 2014 - 12:17 Submitted by anonymous 
>> user: [71.191.205.189] Submitted values are:
>>
>>     --Contact information--
>>       Organization: Texas Instruments
>>       Project name: The 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: 2014-04-24
>>       Compliance Agreement revision: 1.0
>>       Yocto Project Compatible Version: 1.5
>>
>>
>> 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 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?: 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: Linux kernels used in meta-ti are either latest staging 
>> work-in-progress or aligned with Long-Term Stable from GregKH as much 
>> as possible.
>>
>>
>> The results of this submission may be viewed at:
>> https://www.yoctoproject.org/node/351547/submission/93
>>
>



--
Jeff Osier-Mixon @Intel
Yocto Project Community Manager http://yoctoproject.org
--
_______________________________________________
yocto-ab mailing list
yocto-ab at yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto-ab