[oe] Bitbake Architecture, Roadmap, Maintainers and the future

[Richard Purdie]

On Fri, 2010-12-31 at 11:26 +0100, Andrea Adami wrote:
> On Fri, Dec 31, 2010 at 3:42 AM, Richard Purdie <rpurdie at rpsys.net> wrote:
> > There is a little friction around bitbake at the moment. I think after a
> > discussion I had with Chris earlier on some things are clearer and its
> > probably good to summarise how things stand.
> ...
> 
> If I'm not wrong, Chris just finished the Poky-Sync on a personal branch:
> 
> https://github.com/kergoth/bitbake/tree/poky-sync
> 
> AFAIK he's trying to stabilize master before merging Poky's changes.
> Just ask him :)

I have talked to Chris both in person and over IRC. Recently this
consisted of personal insults thrown at me when I tried to talk about
technical details. I'm doing my best to ignore this and do something
about the technical stuff which is actually what matters.

Regarding the poky-sync branch, its a good move and I do really
appreciate it. I've also been working on the opposite part of the
problem of bringing Poky back into sync incrementally using atomic
commits rather than one big "sync" commit. Its been worthwhile as I've
found a few small areas I think functionality is still missing in
upstream despite the poky-sync branch and I'm going to be addressing
these to bring everything back 100% into sync again (as they were a few
months ago).

This work has been made particularly hard by the tendency of recent
bitbake commits to change several different things in one commit and for
small fixes to sneak into other unrelated commits too.

Cheers,

Richard