I think, up until now we don't have a clear roadmap that includes every aspect on how to document everything (code, scripts, user manual, entry points for new coders/artists).
Code
We have a central and up to date Doxyfile in "documentation/" Most of the new code is already doxygen compatible documented (\brief, \param, \return, \file...). Old code is still lacking documentation, but this should be done on the fly while refactoring it.
We should regulary upload the doxygen generated documentation to our sf page and link it from the wiki.
Scripts
For the first script (console.as) I used doxygen documentation for a start, but I'm not sure if this works (Doxygen has no AS parser). We will still have to figure what's the best way here.
In the end, we should upload an autogenerated documentation here, too.
User manual
The gameplay should be documented. This includes console commands. The specifics need to be worked out.
Repositories
We already have a README file on git root, it explaines the different folders and provides some links to the wiki and a quick compile guide. I think this is enough.
Something like this should happen on svn, too (along with mabe some cleaning up, unused/ and mediaSource/ could need some cleaning).
Any further input and opinions are welcome. I'll update this roadmap accordingly.