[yocto] CGL compliance layer initiative

[Paul Eggleton]

On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
> On 04/09/2014 01:51 PM, Paul Eggleton wrote:
> > On Tuesday 08 April 2014 18:34:08 Vali Cobelea wrote:
> >> Here at ENEA we decided to take the initiative regarding the CGL
> >> compliance when it comes to the Yocto Project.
> >> For this we started the work on a dedicated layer called 'meta-cgl'
> >> 
> >> which can be accessed / cloned from here:
> >>    http://git.enea.com/git/?p=linux/meta-cgl.git
> >>    git clone git at git.enea.com:linux/meta-cgl
> >> 
> >> Have a look of the things we got there so far, please remember that
> >> there is still plenty of work to be done (layer architecture, CGL
> >> requirements coverage mode and so on).
> >> It is a little bit more than a stub layer, consider it a starting point
> >> for the direction we would like to have with this layer.
> >> 
> >> Any input is much appreciated, lets keep the discussion by this email
> >> thread and see where it goes.
> > 
> > I don't have anything to offer on the layer contents, but I would say in
> > order to make it easy for people to find this layer I would strongly
> > encourage you to> 
> > submit it to the OpenEmbedded layer index:
> >    http://layers.openembedded.org/layerindex/submit/
>
> Thank you for the input.
> We will keep the layer for a short period of time at the current
> location while getting other ideas regarding the content / architecture.
> The layer initiative will also be raised up in the board advisory
> meeting, in order to get even more input.
> After which we will make it easier to find, access and use for anyone,
> exactly as you suggested.

OK, as the maintainer it's totally up to you.

I would say though generally that I'd like to see more people adding their 
work-in-progress layers to the layer index, even if at some time later they 
will be moved elsewhere or absorbed into another layer - it just makes it 
easier to point people to the layer index so they can find recipes that have 
already been written, rather than having to re-write them from scratch.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre