Great to see the interest on Maemo in the last weeks. As expected, traffic in the forum, in Bugzilla and in Brainstorm has increased impressively.
Discussions have been taking place (with regard to Bugzilla for example here or here) how to make infrastructure work out better for users, with some good proposals. I am also impressed by the patience and friendlyness towards new folks not searching for already existing threads or bug reports, partially pushing the limits of english grammar and punctuation, or towards folks having wrong expectations (Symbian is a completely different codebase than Maemo, hence talking about “regressions” is technically speaking wrong. If you want all of the Symbian functionality and lose some of the Maemo functionality, just get a Symbian device if it makes you happier). On a related note, I’m also trying to keep Bugzilla a technically focused place and make clear that it’s not a forum (“WTF???” comments are counterproductive noise if you want developers to read maemo.org Bugzilla mail, really).
Two issues that have been on my mind lately:
- I am afraid of Nokia doing the same mistake for Maemo5 that was done for Maemo4 – evolving and supporting a platform just for a few minor updates which is bad for the ecosystem around. “Maemo hasn’t had a chance yet to gain real long-term stability. The life-cycle of a Maemo version is too short for that, and there is no continuity between versions.” If 3rd party developers are unsure whether to write their new great application in GTK (abandoned for Maemo6) or Qt (not yet ready for Maemo5) they in doubt don’t write it at all and might support a different platform instead.
- Also, there must be improvements with regard to contributing (patches or even co-maintenance of modules). It’s too unclear where to find which codebase. Garage? Stage? Gitorious? Is it free or closed? Glad to know that Stskeeps is working on it as part of the maemo.org Sprints (ID: 9.11-04).
Open source community expectations are about taking (Give me the code!) but also about giving back (Let me provide patches in Bugzilla and have maintainers review them!).
Tarballs are available in the repositories, but hackers normally prefer the fresh code instead.