Task:Maemo public roadmapping process
 |
This article is continued discussion from the maemo.org brainstorm Please see the 100 Days agenda for more. |
|
This is an accepted task and it is currently in the maemo.org development backlog. Probably nothing is stopping you from starting on it, though. Please see the talk page for discussion. |
 |
This is a subtask of Task:maemo roadmap coordinated by qgil.
Feedback welcome!
- How Nokia should disclose roadmap plans.
- Good practices (URLs welcome).
- 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)
- 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.
- 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.
- How the community should provide input and influence the roadmap.
- Anything else missing.