Re: openembedded-core git repository

[Frans Meulenbroeks <fransmeulenbroeks@gmail.com>]

2011/1/19 Graeme Gregory <dp@xora.org.uk>:
> Hi, this email is sent as an ordinary member of OE.
>
> It seems to be on a technical level we are agreed that we should split
> parts of OE out into the so called openembedded-core which will have a
> stricter commit access and higher QA requirements on changes.
>
> I therefore think it is time to actually create the repository and let
> the people who are interested in merging the good stuff from poky with
> the good stuff from openembedded to create our "core". I don't think
> there is any need to wait on the political part of the Yocto/OE
> collaboration as its something we have agreed in principal to do anyway.
>
> I would request then that the TSC drive this forward with the server
> admins and create this repo so work can happen.
>
> Graeme

Graeme,

Seems  a fine plan to me.
Do we already have an idea what would be the starting base?
And do we already have an idea on the QA requirements we want to impose on this?
Lastly we might try to define some common understanding what is core
and what not.

I did some experiments with poky and found that some of the recipes I
needed were missing; some of them might perhaps become part of core
(e.g. i2ctools, squashfstools, libftdi, fastcgi), whereas others are
quite unlikely to end up in core (e.g. urjtag). For the latter we must
find another home (e.g. meta-openembedded), where hopefully we can
also raise the QA bar somewhat.

I'll happily contribute to raise the quality bar. However, if the goal
is shuffling recipes without significant QA improvement or if QA
improvement is optional, I'll probably pass.

Frans.