Wiki as a documentation delivery system? (take II)

[Char James-Tanny]

> This may be adequate if the worst consequence of someone
> following incorrect information is a desktop or even a server
> crash, but if you're selling products that can kill people if
> improperly used, anything less than a "full review and approval
> prior to release" system is walking a tightrope without a net.

Then set stronger permissions; make it so only folks in a specific
group can edit those pages. (If all pages require those kinds of
permissions, then I'd think that something other than a wiki should be
used.)

Because this thread keeps breaking into bits that start new threads, I
can't check...but wasn't in this thread that someone posted about
barriers to collaboration? If the topic isn't a good one for
collaboration across multiple groups, then it shouldn't be in a wiki.

All sorts of safeguards exist...it just depends on which ones you want
to implement.

Char James-Tanny ~ JTF Associates, Inc. ~ http://www.helpstuff.com
----------------------------------------------------------
Please send follow-up questions to the list.
Contact me directly (CharJT at helpstuff dot com) with business inquiries.
----------------------------------------------------------
2005-2006 Microsoft Help MVP ~ MSHelpWiki http://www.mshelpwiki.com
AuthorIT Certified Consultant, Development, and Training
Moderator, HATT and MSHelp2
STC Secretary, 2006-2008
STC Online Information SIG: Online Help Lead
Web site Hosting and Design ~ http://www.jtfhosting.com