A well-built wiki can be a treasure box of valuable knowledge, indeed, but it is not capable of replacing email lists: ll the lists i know that have moved to forums have died. Forums work, just not like email lists.
I think email lists are for generally-interested people: they want to get all the chatter about their favorite object
Forums are for interested people - but perhaps with just a specific interest (in posting or answering a post)
Wikis are for storing knowledge, lists, plans…
Often where forums stop and wikis start, is in collecting a final view on a topic.
A wiki is like a forum where the current page is an intelligent summary of all contributions.
A blog… well. It's one person or small group pushing info out, and getting back comments. So it's like an email list, where people are interested, but feel like listeners, not contributors, and where their interest is somewhat fragile.
I think wikis are bad places for sand.
Better to think of it as a place for carving stone
- How do you allow chatter to happen in one space, and knowledge to be published in another.
- Have IRC, email lists, blogs, forums for chatter. And publish knowledge in a wiki :-)
- How do you do this on your wikis today?
- Do you use different categories?
- The closest I get is using a link to a "ToDo" page for collecting things that need doing.
- Do you use separate wikis?
- That would not be helpful, I think. The work in getting from Chat to knowledge is actual hard intellectual and integrative work…two wikis won't get the work done.
- And what is still missing from Wikidot to make this work neatly?
- I think that wikidot would most valuably be improved in this direction by adding GTD-type features. That would involve adding built in support, perhaps hanging off tags, for Projects, Contexts, Tasks, Delegated helpers, and time/iCal scheduling.
It's a massive market, so worth exploring.
In that vein, something that lots of organizations would like is a template-able event scheduling system.
If users could create pages easily, which became events (so each page would need start, finish, duration, location fields (like pages currently are allowed to have tags, they would have "times", and "places")), then these could be flexibly viewed filtering on date, and tags, contact, speaker, location, etc.