[yocto-ab] YP Advisory Board: VOTE Wind River Linux 8, YP Compatible

[Otavio Salvador]

Yes from O.S. Systems.

On Tue, Nov 22, 2016 at 10:48 PM, Osier-mixon, Jeffrey
<jeffrey.osier-mixon at intel.com> wrote:
> Sorry all, my fumble fingers. wrl 8 , yp 2.0.
>
>
>
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
> -------- Original message --------
> From: akuster <akuster at mvista.com>
> Date: 11/22/16 3:00 PM (GMT-08:00)
> To: "Volosincu, Andreea S (Wind River)" <andreea.volosincu at windriver.com>,
> Jeff Osier-Mixon <jefro at jefro.net>, yocto-ab at yoctoproject.org
> Subject: Re: [yocto-ab] YP Advisory Board: VOTE Wind River Linux 8, YP
> Compatible
>
> Andreea,
>
> On 11/22/2016 02:46 PM, Volosincu, Andreea S wrote:
>> Hi Armin,
>>
>> This is for Wind River Linux 8 - which is YP 2.0 compatible.
> Thanks for the clarification.
>
> Jefro ask for a "please vote yes/no for Wind River Linux 7 to be YP
> Compatible with YP 2.2.", which this is neither.
>
>
> So the request is to "vote Yes/No on Wind River Linux 8, YP Compatible
> with YP 2.0"
>
>> The submission for Wind River Linux 9 (which is indeed YP 2.2 compatible)
>> is coming next.
>
> BTW, the submission date is wrong in the form. not sure if that matters.
>
> Yes from MontaVista on "Wind River Linux 8, YP Compatible with YP 2.0"
>
> - armin
>
>>
>> Thanks!
>> Andreea
>>
>> -----Original Message-----
>> From: yocto-ab-bounces at yoctoproject.org
>> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of akuster
>> Sent: Tuesday, November 22, 2016 2:44 PM
>> To: Jeff Osier-Mixon; yocto-ab at yoctoproject.org
>> Subject: Re: [yocto-ab] YP Advisory Board: VOTE Wind River Linux 8, YP
>> Compatible
>>
>> Hmm,
>>
>>
>> On 11/22/2016 02:32 PM, Jeff Osier-Mixon wrote:
>>> Hi folks - this is an update from WR Linux 7, please vote yes/no for
>>> Wind River Linux 7 to be YP Compatible with YP 2.2.
>> You mean WR Linux 8?
>>
>>> thanks!
>>>
>>>    --Contact information--
>>>        Organization: Wind River
>>>        Project name: Wind River Linux 8
>>>        Contact name: Mark Hatle
>>>        Contact email address: mark.hatle at windriver.com
>>>        URL to organization or product link:
>>>        http://www.windriver.com/announces/wind-river-linux-8/
>>>        Registration date: 2015-12-22
>> 2015 really, is this back to the future?
>>>        Compliance Agreement revision: 1.0
>>>        Yocto Project Compatible Version: 2.0
>> Verison is 2.2, not 2.0 ? does the website need updating ?
>>
>> Please make corrections.
>>
>> - Armin
>>>
>>> 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)?: 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
>>> 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.: 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:
>>>
>> --
>> _______________________________________________
>> 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
>
> --
> _______________________________________________
> yocto-ab mailing list
> yocto-ab at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto-ab
>



-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750