grow your wiki
Since Wikis can support communication in many ways, the actual communication procedures need to be defined clearly to avoid misunderstanding. Furthermore, email is the main personal knowledge management tool so it's important to use it effectively to let people know when wiki pages need review. Social tags allow easy labeling of pages to be changed and thus, self-determined work on critical and most interesting content.
Briefly go over current work on the wiki and open questions at each meeting. Solve document interdependencies. During this discussion, try to avoid discussing the actual content so you can focus on logistical issues.
Have communication procedures that clarify at least when pages should be sent around via email (e.g., for review). In particular, clarify whether customers provide feedback directly to the Wiki. Discuss and change communication procedures if problems occur.
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
I have considered this for my current project.
I'm not sure if it is offered by any wiki's but heres how I think a great system would work to spread out the load on a public wiki
Already most wikis send out an email daily/weekly/monthly or just RSS feed when content is updated which is fine
But if we had several longstanding members who had selected that they were experts in certain fields then maybe the wiki could send all of them an email when a page (with tags corrisponding to their expertise) was revised asking if one of the experts could just check if the information changed was still correct
Just a thought but I hope someone picks it up and implements it