Open development/Maemo roadmap

[edit] Roadmap examples

Some links. Please add yours. Still haven't distilled whether they are good practices or not.--qgil 06:11, 30 July 2008 (UTC)

Yeah, I know about that and in fact is in my ToDo list. Will attack that once the new Maemo is well defined after the 100 Days. However, afaik there are no roadmaps there. Or where? --qgil 19:32, 30 July 2008 (UTC)
Sorry. Saw the one for Sofia-SIP and thought each product would have a roadmap. Nope. --timsamoff 20:10, 6 August 2008 (UTC)

[edit] Dave's feedback

  • I wrote a paper on this for Wengo, a former employer - I could translate it & post it publicly somewhere if there were interest --Dave Neary 16:21, 6 August 2008 (UTC)
What about starting publishing the original in French. For me is enough now.--qgil 19:58, 6 August 2008 (UTC)
  • My favourite free software roadmap is Inkscape's - they have this concept of laying out big plans which will be the guiding principles of a release early, and as they get closer to the release, those guiding principles get broken down and enumerated, people take on features, and they end up with very fine-grained lists of things accomplished in past releases.
Inkscape is indeed a very good example. I like the way they connect roadmaps (future) with release notes (past). However, Inkscape is just one application and Maemo is a whole platform. Single products/components in this platform could work on roadmaps having references like Inkscape. However, how to apply the good lessons to a Maemo platform roadmap?--qgil 19:58, 6 August 2008 (UTC)
  • Other than that, I have looked - the canonical reference Producing Open Source Software doesn't say anything about guiding the technical direction of a project.
Retrieved from "http://wiki.maemo.org/Open_development/Maemo_roadmap"