[oe] [RFC] meta-openembedded layer for yocto hosted on oe.org

[Frans Meulenbroeks]

2010/12/21 Koen Kooi <k.kooi at student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 20-12-10 18:16, Frans Meulenbroeks wrote:
>> Nice piece of work & a good plan but...
>>
>> Who will be the owners/maintainers of the layers?
>
> My intention was that the meta-openembedded layer will be maintained by
> the people interested in it. There will be a new MAINTAINERS file inside
> listing who feels responsible for various recipes.

Ah ok.
Seems a good plan.
>
>> An alternate approach would be to let the stuff live in poky-extras.
>> See this proposal from RP:
>> http://www.mail-archive.com/yocto@yoctoproject.org/msg00286.html
>
> The poky-extras thing is not what I want, and more importantly, I don't
> want to start diluting the OE brand.

Why wouldn't you want poky-extras?
My concern is that we get lots of duplicated effort because both
poky-extras and meta-openembedded might get the same recipes.
Maybe this should be one of the items to be discussed with the yocto
board (and maybe come to one user contributed layer).

BTW it seems good to come up with some guidelines on the
meta-openembedded layer (or maybe usage rules or so).
E.g. personally I would expect that if I put meta-openembedded on top
of e.g. poky/laverne that a recipe in it builds).
So no dependencies on non poky recipes. Is that an agreed assumption?

Wrt diluting the OE brand. This is a completely different topic.
IMHO the mere fact that yocto exists impacts OE.
Yocto also has much more resources (both people-hour wise as well as
HW wise), so I strongly doubt we can compete on it wrt the quality of
the base recipes.

That leaves the question:
Given the existence of Yocto in which parts do we see added value of
OE and on which things should we as OE focus.
But I guess this is more something for a different thread.

Frans