Task:Publishing API docs: Difference between revisions
From Maemo Wiki
Jump to navigationJump to search
imported>qgil 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... |
imported>qgil mNo edit summary |
||
| Line 9: | Line 9: | ||
===Plan=== | ===Plan=== | ||
* Recover the useful information from the previous discussions - Ferenc knows. | * Recover the useful information from the previous discussions - Ferenc knows. | ||
* Have a look at the best practices around. | * Have a look at the best practices around. e.g. http://library.gnome.org - what else. | ||
* Agree on what we want for maemo.org. | * Agree on what we want for maemo.org. | ||
Revision as of 20:05, 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.
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. e.g. http://library.gnome.org - what else.
- 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.
