[oe] openembedded-core git repository

[Khem Raj]

On Tue, Jan 25, 2011 at 3:05 AM, Koen Kooi <k.kooi at student.utwente.nl> wrote:
> Ignoring the timeline a bit, since ideally we would do this around a
> yocto milestone to get them to use this straight after their freeze.
>
> The technical roadmap/todo:
>
> * setup openembedded-core repo on oe.org
> * setup oe-core ml on oe.org
> * add oe-core ml to patchwork
> * import yocto-core in oe-core
> * start an integration branch
>  o remove bitbake
>  o cleanup namespace (s/yocto/OE/, s/poky/OE/)
>  o split out superfluous layers (e.g. ememlow)
> * start merging in OE things
>  o e.g. OE gcc 4.5, toolchains for avr32, bfin, etc
> * switch meta-oe to build on top of oe-core, fix issues
>
> When that is done meta-oe can start to expand.
>
> The non-technical roadmap/todo:
>
> * Assign 2 gatekeepers to oe-core, one from yocto, one from OE
> * sketch out decision tree (RP -> gatekeepers -> maintainers)
> * work out model for meta-oe
> * appoint OE member to yocto SC
> * work out how to marry yocto goals (4 archs, one toolchain) to OE goals
> (zillion archs, as much toolchains as we can manage)
> * Work out OE roadmap and align with yocto
>
> The above tries to restrict itself to dealing with the new oe-core, not
> with how OE is going to split into layers (meta-oe, meta-graveyard, etc).
> It also ignores the maintainer aspects since we will be dealing with
> yocto metadata at the start. After oe-core reaches a ready enough state
> we can start looking at assigning maintainers, but for the time being
> let's get things done first.
>
> So, let's start fleshing out the above roadmaps and implement them!

very well said. I think lets get started by setting up the repo.

>
> regards,
>
> Koen