Geoffrey McCaleb geoffrey@tabasco.net schreef:
From the trac documentation:
"Wiki itself does not enforce any structure, but rather resembles a stack of empty paper sheets, where you can organize information and documentation as you see fit, and later reorganize if necessary."
Ergo, the wiki world is flat. I suppose for a new project like this it can work, but am dubious how a flat structure will scale. All the example sites show wiki's with just a few pages. I have to be honest I like the way Wordpress has implemented their wiki, but it is early days I suppose.
The wiki will scale just fine. A great example of this is the Wiki at www.rubyonrails.org . It's good to see Trac accepted as source management tool for Roundcube. Maybe Thomas can make a roadmap now so we know where the priorities are. Plugins are nice, but i'd rather see the basic functionality like searching and sorting implemented now.
Trac doesn't want to impose any limitions which is great. I can volunteer for the Wiki too and I am looking forward to Bob's Trac setup.
Another feature request (like we don't have enough already) is the support of message flagging/labeling. It's somewhat prepared in the Ilohamail source but not in the interface of Roundcube.
Best regards,
Jasper
Geoffrey
On Mon, 10 Oct 2005 13:10:58 +0200, Thomas Bruederli roundcube@gmail.com wrote:
Geoffrey, Olivier:
We decided to install a Trac system (http://projects.edgewall.com/trac/) to manage the source code, tickets, changelogs and the documentation. This system enables to link all important parts together. Your suggestions look good but there might be some basic structure given by the Trac system itself.
Regards, Thomas