Task:Publishing API docs
qgil (Talk | contribs)
(New page: {{Template:2010 agenda}} {{task|proposed}} Currently the API docs are spread in different spaces and are processed through different tools. We need a unified process and a single place. T...)
Newer edit →
(New page: {{Template:2010 agenda}} {{task|proposed}} Currently the API docs are spread in different spaces and are processed through different tools. We need a unified process and a single place. T...)
Newer edit →
Revision as of 20:04, 20 July 2008
 |
This article is continued discussion from the maemo.org brainstorm Please see the 2010 Agenda for more. |
|
This task is in the list of maemo.org development proposals, please help planning and getting it ready for a sprint. Put a note on the talk page if you're interested in helping work on this task. Please see the talk page for discussion. |
 |
Currently the API docs are spread in different spaces and are processed through different tools. We need a unified process and a single place. This task needs to be done in collaboration with the Nokia teams. The ideal time rame would be the Fremantle release cycle.
Contents |
Tasks
We can split the work in three loads adaptable to sprints:
Plan
- Recover the useful information from the previous discussions - Ferenc knows.
- Have a look at the best practices around.
- Agree on what we want for maemo.org.
Tool & Process
- Define the process.
- Get the commitment from Nokia.
- Implement the tool.
Release
- Real content needs to land.
- Test, debug, fine tune.
- Final release.