Hi devs, I like the idea that Romain exposed, but to be complete I think I should expose other options. The point of starting this discussion is to really think about what is best, before commiting for long. Arguing is important, but most important is the preference of the one who's going to do the work. Balbinus has prepared a new design for the site, so maybe he'll be that guy.
The other options are: * Stay with wakka, which did a good job until now. One problem is our ugly perl scripts for conversions. Another question is how much we can tweak it to get nice designs. Finally, I think it's a bit stupid to have a dynamic tool for a static content, and it requires some work to freeze the right version of the doc for releases, which could be seamless with a system inside our SVN. * Move everything to the trac. Romain loves his track, and we all thank him for it, so he proposed that at first. He likes the idea of having only one tool. I like the idea of having several simple tools, for more independence. Matter of taste. The same problems and questions as for the wiki hold here too. By the way, who'd like to join me at the Trophée [EMAIL PROTECTED] Innovation next saturday in Cachan ? See ya, -- David
