I saw someone post the statement taht Maemo6 is a instance of Meego.

That would make more sense. Given that any Moblin/Maemo merger is going to have to expand the hardware computability of both. It seems logical to develop a top level product called MeeGO that defines the API etc. then to have sub products built on that core.

MeeGo with a kernal and binaries built for OMAP is Maebo
MeeGo with a kernal and binaries built for Intel is Moblin

Whenever MeeGo updates the core libs etc Meabo and Moblin would autobuild downstream. As much as possible would be moved into the upstream source and developed there. With and Nokia or Intel propitiatory code needed to support dedicated hardware being added on the downstream builds.

A guess of course. But such a structure would allow for many more MeeGo instances to be created by LG Samsung HTC etc etc. And given that the only benefit of such a move is to open up the ability to develop cross platform it would make sense.

This way foss app developer would compile for their own platform. The source when wanted would be moved upstream and communities like this would optimise etc downstream if needed/wanted.

And for profit companies could create single source for the product and build their own autobuild and repository tree for distribution.

Fairly similar to how many closed source houses have had to work for PDAs etc in the past but more of a common structure.

This is what I would want to see anyway.