EDIT 2: Damn, I’m so dump. I had the answers already but I totally forgot about them. I posted something similar to this blog post in the comments section of that article but being a bit ill (not surprising in November..) I completely forgot about it and never checked back.
Due weird circumstances my websearching brought me back to that article where I found a reply by Nokia’s Quim Gil. He wrote:
The apps included in the MeeGo Handset UX are the top of a complex iceberg. Nokia is contributing heavily to Core OS and Handset UX, from Kernel to MeeGo Touch Framework. The Handset application/services layer in MeeGo products from Nokia will be heavily tied to Ovi and Nokia proprietary apps. It would be quite schizophrenic to also develop the open alternatives. Still you can see Nokia’s involvement in Mozilla, KOffice and essential application back-ends like Kcal or Buteo.
Now we have it: Nokia won’t open source the actual front-ends. The code for the Handset UX front-ends is just meant to be a reference implementation and nothing to ever become a usable product on its own.
Apart from MeeGo Touch Framework (a component I wasn’t really aware of at that time, even though I had heard the name before but it never caught my attention) Nokia is involved with upstream projects for back-end services.
A misconception (likely due my unclear use of words because I’m not a native English speaker) in said comments section was that I accused Nokia to be not involved in FOSS except Qt. That is not what I meant. Both my comment and this blog post were solely about MeeGo-specific projects and not multi-purpose upstream projects like Mozilla where Nokia is developing a Qt port of Firefox Mobile.
With my regained memory about the VisionMobile article, let me say a few words about the comparison of MeeGo Handset and Android. If the MeeGo Handset front-ends stay a mere reference implementation, cheap smartphone manufacturers will more likely opt for Android because even stock Android is a polished product. The development may occur behind closed doors but a complete end to end stack is released with each development cycle.
This however may serve as opportunity for us KDE people. If Plasma Mobile + our apps turn out as polished product bundle, we “only” have to make potential MeeGo adopters aware of it as in “Just take it all for free. You only need to set a branded wallpaper and you’re set. If you do encounter bugs, our development is open – just submit a patch.”
Now that it’s all settled, I can go to bed again. For reference I keep my original blog post below:
A while ago I was wondering about MeeGo. In every article about MeeGo it’s being told how it’s a project of both Nokia and Intel.
But then I had a look at MeeGo source codes. Strangely, apart from Qt itself, I could not find any Nokia code at all. I thought that at least the Handset UX must obviously be a Nokia product. After all, Nokia plans to ship their first MeeGo phone in the coming months.
Well, MeeGo’s Handset developer group has not a single Nokia member. All but two have Intel mail addresses and the two don’t have a @nokia.com address either.
Wherever I look, I can only find Intel code.
The only area where I could find actual Nokia involvement was the semi-official N900 port. The table on that page contains some Nokia-related names and the page also talks about “closed components” only Nokia has access to.
Is it actually true that Nokia’s only involvement with open source MeeGo-specific code is to port Intel’s open source code to the N900 via “closed components”?
Then I thought that Nokia will probably develop a closed source user interface for their upcoming MeeGo devices, similar to the WeTab. However that would contradict page 4 of Nokia’s Software Strategy White Paper.
Anybody got a clue what’s going on? My elite web searching skillz left me as puzzled as before…
EDIT: Nokia develops MeeGo Touch Framework. That’s still no front-end application that I had hoped to find, though.