The project I am involved with regarding a complete rewrite of the transfership of student identity data between the Registrar and the Identity Management system. It involves people from ITS and the Registrar. A wiki setup that only people on the Student Identity Managment Mailing List could read and write would be wonderful.
I'm on another project concerning the continual evolution of the Case Daily emails. Again, I am working with people in different departments (ITS and Marketing & Communications). I would love a wiki site that only we could access.
There's another beginning of a project regarding iTunes@Case. It would be great if we could setup a separate wiki that was world-readable but only writeable by people on the iTunes@Case mailing list.
Project and group specific wikis created on demand would be nice.
Now I know there are ways to tailor something like MediaWiki to do it. But I don't know, it just doesn't feel like the right wiki software to do it. For some reason (and this is probably because my exposure to the engine is WikiPedia and the Case Wiki), MediaWiki powered sites feel lofty, official, grandiose — places to store official stuff... like an encyclopedia... like the Case Wiki. It just doesn't feel like software I use to do one-off project documentation. Internally, we use DokuWiki, and that does feel like a place to store project documentation.
I like TiddlyWiki and its variants but navigating a TiddlyWiki is difficult for normal users. (Seriously, go find a normal user and watch them try to use TiddlyWiki... they get completely lost and confused.)
Regardless, some way to automate installs (and upgrades) of DokuWiki on a per-project or per-group basis would be wonderful. It wouldn't have to be DokuWiki, but thus far, it feels like the best to me (if only it could have database support for backups).
Automating the creation of a wiki site is one aspect. The other aspect is controlling you can read it and who can edit it. But that's the subject of my #1 most wanted ITS Service.