Tom, I think that you've raised a good point. I can see how a Wiki can potentially help with collaborative documentation, and I think it's a pretty good way of doing it.
However, I think it's more important to establish a certain standard framework for what the documentation should include, how it should be written, where it should be saved, etc. This would help the community collaborate simply by having a pretty straightforward starting point.
The problem with the documentation is not that there isn't a good tool, but there aren't any good docs! We do have the file manager, but that's not really the answer until something is written. There's the aD approach to documentation, but it's always hard for me to get a quick understanding of what a certain module is and how it works.
If something like this already exists, than I would be more than happy to be corrected. If not, then I think it's important that we think about setting one up before the OpenACS 4 release. I think there's some potential for a Wiki then, but I don't think a Wiki is paramount right now.
talli
