[yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

[Mills, William]

Jeffro/Tracy,

What is the goal of this list?  Is it just BSP layers?  (I don't know why we would limit it that way).

If it is just BSPs then meta-qt5 should not be listed and meta-osssystems-base should not be either.

If non-BSP layers should be included (and I think they should be) why isn't meta-browser listed?
Why would meta-arago not be listed? What about the OSV?  I voted for a lot of Wind River and Mentor etc products, where does that show up?

WRT to web presentation it would be great if it was a real table that could be sorted by name or release etc but the low tech version of that would be to break the release name out as a column and keep the table sorted by that with most recent releases listed first.

Bill

From: Mills, William
Sent: Wednesday, March 7, 2018 1:33 PM
To: 'Osier-mixon, Jeffrey'; Erway, Tracey M; Dmytriyenko, Denys
Cc: yocto-ab at yoctoproject.org
Subject: RE: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

This is simply not true.  Meta-ti was submitted everytime we submitted meta-arago.
I will have Denys send you the evidence.

From: Osier-mixon, Jeffrey [mailto:jeffrey.osier-mixon at intel.com]
Sent: Wednesday, March 7, 2018 11:54 AM
To: Erway, Tracey M; Mills, William
Cc: yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: RE: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

I fixed this (in the layer index). I had set the wrong layerbranch to have the status.

I really wish I could go back and update older releases of everyone's software to YP Compatible. However, the plain truth is that no one actually applied for Compatible status for BSP layers. Intel did so as part of the release cycle for their BSP. I went back through every form I have received since we launched the program in 2012. There have been a number of products and distros - including Arago - that have been listed over the years, but no one has kept up with submitting BSP layers.

I do agree that the site would look better if we pulled down the older meta-intel layers.

Jeffrey "Jefro" Osier-Mixon, Intel Corporation
Open Source Community Manager

From: yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Erway, Tracey M
Sent: Wednesday, March 07, 2018 8:12 AM
To: Mills, William <wmills at ti.com<mailto:wmills at ti.com>>
Cc: yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: Re: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

I'll take care of it.

On Mar 7, 2018, at 7:42 AM, Mills, William <wmills at ti.com<mailto:wmills at ti.com>> wrote:
Tracy,

I assume Jeffro did it, so I also assume he can fix it.

On this page: https://www.yoctoproject.org/software-overview/layers/
It says:
meta-ossystems-base
version: master<https://code.ossystems.com.br/gitweb?p=meta-ossystems-base.git>

It should say rocko not master.

And while we are talking about it:  which compatibility certifications are we listing?
Intel has a lot including old releases where everyone else's older certifications seem to be missing.
I know TI has more than just the one now listed and I know I have voted for Wind River and Mentor etc etc.
What is the policy?

Bill

From: Erway, Tracey M [mailto:tracey.m.erway at intel.com]
Sent: Tuesday, March 6, 2018 4:21 PM
To: Mills, William; Noal, Daniel F (Wind River); Jeff Osier-Mixon; yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: RE: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

Bill,
What specifically should not be listed on the website?  And where on the website?
/t

From: yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Mills, William
Sent: Tuesday, March 06, 2018 1:11 PM
To: Noal, Daniel F (Wind River) <dan.noal at windriver.com<mailto:dan.noal at windriver.com>>; Jeff Osier-Mixon <jefro at jefro.net<mailto:jefro at jefro.net>>; yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: Re: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

Jeffro,

Compatibility is against a specific release correct?
It good to test against master but it should not be listed on the website (as it is now).

What is meta-osssytems-base?  It says it is a BSP layer in the readme but I see no machines and I see things that modify busybox etc.  Is this really a distro layer?  Is it a mix of distro and some bsp?

Bill


From: yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Noal, Dan
Sent: Tuesday, March 6, 2018 9:44 AM
To: Jeff Osier-Mixon; yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: Re: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

Wind River votes yes.

Dan Noal | Sr. Director, Core Platforms Group
direct 510.749.2555  mobile 510.710.6691
<image001.png>

From: yocto-ab-bounces at yoctoproject.org<mailto:yocto-ab-bounces at yoctoproject.org> [mailto:yocto-ab-bounces at yoctoproject.org] On Behalf Of Jeff Osier-Mixon
Sent: Monday, March 05, 2018 10:53 AM
To: yocto-ab at yoctoproject.org<mailto:yocto-ab at yoctoproject.org>
Subject: [yocto-ab] YP Advisory Board: VOTE meta-ossystems-base, meta-browser YP Compatible

Hi folks - the layers are rolling in! Otavio has submitted
meta-ossystems-base
meta-browser
for YP Compatible. Both have Yes answers throughout the form for all appropriate answers and have been tested on rocko and master.

Please vote yes/no on these layers. I am granting provisional status while voting commences.
thanks

--
Jeff Osier-Mixon - Open Source Community Strategist, Intel Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto-ab/attachments/20180308/97a1d627/attachment-0001.html>