Just because Nokia has made a (shitty) decision doesn't make it a right one.
Couldn't give two shits about MeeGo. Even if the N900 gets MeeGo (in whatever form), it'll still be an OS laden with closed source components, thanks to Nokia.

Please... that's a joke. All the discussions re. requests are stagnant.
Hell, the one request I made to change the licensing of a component with its source already available in an open source program (I know; I was surprised too) has produced nothing.

Do I even need to mention the amount of WONTFIXES here?

Have some personalised replies, then.

• Modest: Don't use it for its main ability. Tho I must admit that it does make a brilliant email notifier.
• RSS Reader: Don't use it. I think mant prefer FeedingIt over the stock reader.
• Games: Don't play 'em.
• PDF Reader: Its XPDF engine is outdated as ****, and I don't ever recall seeing the patches that were uploaded for Diablo's version ever making it in Fremantle. One incentive lost. (jott's rotation support is a brilliant example of this. Silence for God knows how many months and then a FIXEDINFREMANTLE message)
• X-Terminal: Yes, I have hacked on it in the past. The X Terminal team did listen to some requests, however, so I can't criticise there.
• Hildon Desktop: Ah yes, a package which depends on closed source components. But to answer the question: No, not me. But Matan has and I don't believe I've seen his patches in PR 1.2, despite asking on -developers how he could do so.

Right, how do we know it takes that long? I mean, Nokia aren't exactly masters of communication (yes, the irony is not beyond me) - the licensing queue shows that.
And Nokia always seem to go the closed source route first. Take fmtx-middleware. A new component, introduced in Fremantle. You'd have hoped that Mer - which Nokia was obviously aware of - would've enlighted them somewhat. Why was it produced being closed source in the first place? It's bloody ironic due to Nokia contributing an open source driver for the transmitter to the kernel.

The community have modified some open source components; I named a couple above. There's more, however, like mafw-gst-subtitles-renderer, based on mafw-gst-renderer.

Oh, mafw-gst-subtitles-renderer was born out of a Brainstorm. Half of those requests can't be fulfilled as they have to be done in one of Nokia's closed components. I'm sure someone would be happy to do it if Nokia didn't close source many of their stuff. I mean, Nokia don't give a **** about what's in Brainstorm - how many requests from Brainstorm have been fixed by a Nokia employee?

The Queue shows why that doesn't work.

Nope. I'm after Diablo's components. Things like BME I'll never have a ****'s chance of understanding - that's a given - but other things that Nokia keep closed (to add insult, the headers aren't even available in nokia-binaries), like libconnui, sure.

Easier said than done. Easier said than done.

Anyway, amongst all this arguing, Nokia aren't gonna be changing their ways. I doubt I'll be going down anytime soon.