AMD joins MeeGo

while maemo was debian based (as was moblin 1.x), meego uses RPM and will transition away from gtk and onto qt as the main ui lib (the netbook and ivi builds from intel are still gtk based however). I think gtk will stay as part of the core for the time being tho, as anything else will create a very nasty transition.

and the opening talk of this meego conference was a repeated message of contributing to upstream. Unlike android, where we see google going back into the "shed" after a release to work on the next in private, meego will be worked on in the open. ever so often there will be a "freeze" and a set of builds, but between those there will be open development with continual interaction with the various upstream projects it makes use of.

However, it is unlikely that the builds will be what we see on the devices that gets to market. Linpro for instance have taken the netbook build and put their own interface and a virtual keyboard on top to make a tablet release. Said release still holds the netbook interface however, and a way to transition between the two (useful for say convertible netbooks).

And likewise, the phone ui (ux?) developed will probably not be what nokia will use on whatever meego product they releases. It will however be compatible with the meego ui so that developing for one can be used on the other (same libs and such).