Using a wiki as a central development project repository

Answer 1

I think this would be extremly useful. Depending on the size of a project team members come and go. And a wiki is a good tool to keep the history and the "spirit" of a project available to new team members. I did that in many projects, and though the projects were already finished, all the informations are available.

One more idea: also try to integrate meeting schedules, minutes etc. If your team communicates via IM, try to integrate a log of the conversations.

Answer 2

The other classic integration would be your source code repository, e.g. svn, or cvs. trac is an existing product that does exactly this - it combines a wiki, custom bug tracker, and integrates nicely with svn.

Answer 3

Of course it's useful, there are already ready-made packages for this kind of project-overviews (like http://trac.edgewall.org/).

If possible, I'd integrate any existing CI-engine into the wiki, so that you have a complete overview over the current progress and your project's health.

Answer 4

You might be interested in the mediawiki extension I've created @ http://www.mediawiki.org/wiki/Extension:BugzillaReports. I'm getting a lot of great feedback that this is hitting a sweet spot - it allows you to bring bugzilla reports in line into mediawiki documents and create standard aggregated reports.