TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: Anyone using Wiki for collaboration? From:"Richard Smith" <richard -dot- smith -at- windriver -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 16 Apr 2002 09:02:02 -0700
> To those experienced with Wikis, how do you use them at your company?
> I'm looking for ideas. Here are my plans:
We use twiki. We use it for a variety of things.
> * Documentation repository for project docs
> If you're writing project-related docs,
> then their home will be in the Wiki. For
> example, we'll store the release plans
> on the Wiki.
project life cycle info, schedules, project related
docs, info about where to find source, release view
names, etc. Product plans, doc plans, support plans,
testing plans, etc.
> * Technical support knowledge forum. Because
> publishing to a Wiki is open to anyone and
> because there's almost no overhead in
> writing something up, I want to encourage
> our tech support folks to use the Wiki.
Publishing to a wiki is ONLY open to everyone if
you set it it up that way. They can be access
restricted. I'm not sure twiki would be a good support
mechanism.
> * Competitive information forum. Lots of
> people in different positions in the company
> have different viewpoints on the competition.
> The Wiki can be a way to share that information.
> * Links repository. Industry-interest, news,
> and other links of interest to the folks
> at work can be encouraged in the Wiki.
We do use twiki for a variety of non-work or peripheral
stuff. Everything from discussions about local public
transit to a collection of experiences on laser eye surgery.
Many people put links of interest, their work schedules, and
a variety of other stuff on thier twiki main page.
I think the main benefit of a twiki web is also its
main problem. It takes effort to maintain. Collaboration
often means that no one person is responsible for content.
So content can become outdated quickly.
Overall, I have mixed feelings about twiki. I'm sure there
must be better a better way. But it sure beats no order at
all on an internal web server.
--
Richard
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you using Doc-to-Help or ForeHelp? Switch to RoboHelp for Word for $249
or to RoboHelp Office for only $499. Get the PC Magazine five-star rated
Help authoring tool for less! Go to http://www.ehelp.com/techwr
Free copy of ARTS PDF Tools when you register for the PDF
Conference by April 30. Leading-Edge Practices for Enterprise
& Government, June 3-5, Bethesda,MD. www.PDFConference.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
