View Single Post
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#78
Originally Posted by qgil View Post
There is also the argument that Nokia prefers to encourage contributions around the frameworks currently in development rather than encourage contributions (by opening the source code) around the frameworks that the Nokia software strategy is not interested in pushing anymore.

The developer community can contribute to community projects under development with a good chance to become a top notch media player, a top notch calendar, etc. The frameworks and APIs are all there - I would argue that the candidates as well.

You have the KDE mobile developers, the Qt Quick app developers, the Python+Qt developers, the traditional Qt developers, the new MeeGo... all of them with interesting projects in the hands and looking for contributions. Is there any reason in the N900 hardware and the Maemo 5 software to stop that coolness? Honestly, I don't see it.
Well yes I agree that there are projects that will be part of the vanilla Meego release that we could (and thinking about it, really should) contribute to, but it's unclear how long it will be before there's a day-to-day usable N900 image (no disrespect to Stskeeps and the rest of the meego-arm gang, I know how hard it is to get these things working and am sorry I don't have the time to get involved)

It's hard working (in terms of motivation) on something that you can't actually test and use.
 

The Following 5 Users Say Thank You to lardman For This Useful Post: