All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vali Cobelea <valentin.cobelea@enea.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, Alexandru Vaduva <Alexandru.Vaduva@enea.com>
Subject: Re: CGL compliance layer initiative
Date: Wed, 9 Apr 2014 14:05:41 +0300	[thread overview]
Message-ID: <53452985.7020202@enea.com> (raw)
In-Reply-To: <33266524.grSQoK8z6t@peggleto-mobl5.ger.corp.intel.com>

OK Paul, that indeed makes sense, I really did not knew that preliminary 
versions of layers are accepted.
I will discuss around here and if everything goes OK we will start the 
move in the "public" layer index.
I also do agree with an all-together strategy, no matter for the layer 
state.


Much appreciated,
Vali


On 04/09/2014 02:01 PM, Paul Eggleton wrote:
> 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@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
>



  reply	other threads:[~2014-04-09 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 15:34 CGL compliance layer initiative Vali Cobelea
2014-04-08 15:38 ` Chris Larson
2014-04-08 15:41   ` Vali Cobelea
2014-04-08 15:46     ` Chris Larson
2014-04-08 15:49 ` Chris Larson
2014-04-09  6:45   ` Vali Cobelea
2014-04-09 10:51 ` Paul Eggleton
2014-04-09 10:55   ` Vali Cobelea
2014-04-09 11:01     ` Paul Eggleton
2014-04-09 11:05       ` Vali Cobelea [this message]
2014-04-10 21:35         ` Diego Sueiro
2014-04-11  7:02           ` Vali Cobelea
2014-04-11 12:45             ` Bruce Ashfield
2014-04-11 13:38               ` Alexandru Vaduva
2014-04-11  2:20 ` João Henrique Ferreira de Freitas
2014-04-11  7:10   ` Vali Cobelea

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53452985.7020202@enea.com \
    --to=valentin.cobelea@enea.com \
    --cc=Alexandru.Vaduva@enea.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.