Right, the Community Edition is made up from the same platform parts (mcompositor, meegotouch-home, control panel UI, etc) as the Swipe UI. I'll respectfully disagree that it's just a template as it's functionally working (but that's down to a different discussion) for basic use cases. All the stuff to 'productize' UI would have to be reimplemented (some is already)

Similarly, Cordia is built from the same platform parts Maemo5 desktop is (hildon-desktop, clutter, etc) and all parts you see around in Maemo5 (control panels, themes, status bar applets, etc etc) has to be reimplemented.

The reason I brought up those two is simple: both of them need to be 'productized'. Nokia took the platform parts and made Maemo5 UI, Swipe UI. Similarly the two UI's community has to do the same.

I think we're actually in a really good situation. We have a solid and sustainable MeeGo N900 hardware adaptation that can support many different UX'es. Examples:

MeeGo tablet UX: http://www.youtube.com/watch?v=xjQukhXYt-U

Community Edition UX: http://www.youtube.com/watch?v=mMfVKlC_uBw

XBMC: http://www.youtube.com/watch?v=BAH8GqYmeGs

Digia's custom UX: http://www.youtube.com/watch?v=XWawBt8cXVU

Home automation: http://www.youtube.com/watch?v=Ob7icZ4XsIQ

CyberCom UX: http://www.youtube.com/watch?v=9Fk9rSsJMbE

(I can't seem to find a video of Cordia on N900 - anyone can point me to one)?

My personal preference is to build upon the hard work (EDIT: previous 'being', is actually 'has been') done in Community Edition to actually productize the MeeGo Handset UX in a open, community way to a point where basic functionality works properly. Those who has followed it has noticed it has improved greatly.

But that's maybe because I'm lazy and I don't want to reimplement everything in UI when someone else has already done it in open source. Feels a bit like KDE/GNOME all over again..