I'm looking for some open source wiki software to do internal documentation for software, hardware, procedures, etc.<p>A google search for "open source enterprise wiki" returns Twiki and Socialtext. I also stumbled upon TeamPage. I poked around with Socialtext and I like that is a hosted solution (less admin and maintenance for us). Has anyone used any of these offerings or does anyone have any other suggestions?
We've implemented plain old MediaWiki in our division. It serves as a document and guidance distribution point to the wider corporate public, as well as an scratch pad for internal procedures and process. Due to the general lack of fine-grained access control and segmentation, we stood up two instances: one for the "public" site without authentication for read-only access (and mediawiki accounts for division members only to edit content) and another one for the "private" site with HTTP authentication for the wiki root.
Yeah, avoid TWiki like the plague. Horrible tool.<p>What's most important in an enterprise wiki is the search feature, so be prepared to use a 3rd party tool for search.
My small team (two network people, one sysadmin, two devs, one manager) gets a lot of mileage out of DokuWiki for project and systems documentation. It's fast, has good plug-ins, and stores pages in the filesystem, which we consider a plus because it makes backups and versioning a snap.<p>When we're collaborating with larger groups, though, we tend to pick Redmine by default. It offers a nice combination of ticketing, project management, and documentation features, without the learning curve of a traditional wiki or the deployment headaches of something like Confluence.
I see a lot of people bashing Confluence here.. may I ask why? Having used Twiki, DocuWiki, MediaWiki, and now Confluence; it has become my enterprise wiki of choice. If you can get over its J2EE requirements which make for a <i>huge</i> PITA when the time to upgrade to the next version or make it work with other J2EE applications on the same Tomcat instance, it's a pretty <i>productive</i> tool. It gets the job done, its straight-forward to use, and performs quite good. Can I ask why there are a lot of disenchanted Confluence users out there?
Twiki has the worst wiki markup of any wiki I've ever used. Avoid.<p>The company I'm working with at the moment is using Confluence, which is reasonable. I'd much rather be using MediaWiki or Trac though.
I've used moinmoin in the past and it worked very well.<p><a href="http://moinmo.in/" rel="nofollow">http://moinmo.in/</a><p>EDIT: just wanted to add I've also used Trac <a href="http://trac.edgewall.org/" rel="nofollow">http://trac.edgewall.org/</a>
Have you checked out PBWiki? I've heard good things, but haven't done anything with it personally.<p><a href="http://pbwiki.com/business.wiki" rel="nofollow">http://pbwiki.com/business.wiki</a>
One to check out that has been used internally here is DekiWiki ("enterprise-friendly"). We've also began to use it on external collaborative projects. For dev you can't beat Trac right now but Redmine may just superceed Trac. Ones I tend to avoid are TWiki (hugely extensible, but therein lies its weakness) and horrors of all horrors - sharepoint. MediaWiki of "old" is great if you need something up quicky.
For an enterprise environment, Confluence is the best of the bunch.<p>1. It has commercial support (you did say: enterprise)
2. It's easy for non-techies to use
3. If you buy the optional "Crowd" product, you can do identity management using AD
4. Use the tomcat bundled version, but upgrade the VM allocated memory to a gig to prevent slowness.
5. Upgrade frequently
We use Plone CMS (<a href="http://www.plone.org" rel="nofollow">http://www.plone.org</a>) and it's fantastic. Loads of options beyond standard wiki, easy to set up.<p>Edit: Quote from their site - "An eWeek Labs Analyst's Choice award winner, this open-source product is one of the best solutions period - for company portals and intranets"
- eWeek, April 2006 issue
My company has utilized MediaWiki, Twiki and Confluence (current) over my year with the company. By far, Confluence is the worst in my opinion. Despite Twiki's setup pains, I still prefer it over MediaWiki (and other wiki's I've personally tried for that matter).
I've been using git-wiki recently, with great success:<p><a href="http://github.com/jnewland/git-wiki/tree/master" rel="nofollow">http://github.com/jnewland/git-wiki/tree/master</a>
yeah, but what do you do if, despite cajoling and management emphasis, none of the damn programmers want to use the damn things? they seem to feel the code is self-sufficient.