Well, that is the power of trac, linking from other non-wiki pages to wiki pages. This model also encourage us to integrate the project documentation in the wiki. This way, commit log and tickets could refer to specifications or technical guides when needed. However, project documentation is an integral part of the project, and should not be limited to be browsed using trac. Using a wiki processor like rst may help. So if we produce wiki pages in rst that should be integral part of the project, that would be nice to have it in the project repository. Currently, we are thinking about a regular dump of these wiki pages to the repository, which will create redundancy of course. Having the wiki integrated with the versioning system would be really nice, and have a lot of sense. What else in wiki pages than related project information ? Why not having all these information in the project repository itself ? To answer your question, it will not be only a wiki, if you just want a wiki, take a standalone one not trac. This is only my honest opinion, no flame here, and congratulation, trac is a great product. We have started using it for our open-source projects and we are planning to use for our internal projects too. Denis Gervalle SOFTEC sa http://www.softec.st Emmanuel Blot wrote: > >> Another nice benefit for having an external version-control system >> used for >> wiki backend would be the ability to add/remove/manage wiki pages >> outside of >> Trac. > > > Could be dangerous: how do you manage cases where a Wiki page is > removed from outside Trac, but non-Wiki page in Trac (like the issue > tracker) points onto this page ? > Editing Wiki pages with an external editor... yes, but will it still > be a *Wiki* in this case ? > > _______________________________________________ > Trac mailing list > Trac at lists.edgewall.com > http://lists.edgewall.com/mailman/listinfo/trac