Hot answers tagged project
I've found the MediaWiki wiki to be very flexible and useful. As a bonus, it's very familiar to anyone who's used Wikipedia.
You really can't beat Confluence, especially for $10 (for 10 or fewer users). We use it at my job and it is really fantastic. The organization takes a little getting used to, though.
Disclaimer: I work for Fog Creek The FogBugz wiki is great because it's integrated with the rest of the app, but the editor is buggy. The good news is we're doing a major revamp.
I suggest ScrewTurn for wiki. You can also take a look at AxoSoft OnTime which is very good software for bug tracking, scrum/agile project managment, dev wiki, help desk and more.
I have one non-recommended Wiki : the one available for Sharepoint intranet sites. Utterly a pain to use.
There is GANTTzilla.com. Upload & View: Open your Microsoft Project and Planner files right in the web browser! Edit: Edit projects using Gantt or PERT views. And yes, we do version control for your documents ;) Export: Use converters to quickly export documents into other project formats as well as PDF or PNG. Share: Share ...
We're using Assembla in the company I run. They provide unlimited code hosting (Git/SVN), ticketing, wiki, scrum and other useful tools, and doesn't cost much.
We tried most wiki packages over the years with little success. It was just tough getting enough traction to get the development and project teams to actually use one. We struck gold after we had converted to Google Apps enterprise for email and calendar as it also comes with "Sites". It turns out Google Sites can work as a very flexible and easy to use ...
We use DokuWiki Here is a comparison chart between DokuWiki, MediaWiki, TWiki and TracWiki
I setup an intranet site for disseminating research from and to technically savvy, but certainly not technically proficient crowd. I tried several solutions, and PMWiki is the best. Easy to administer, LOTS of "plugins," skins and extensions from the people using it, easy for less-technical folks to use and with a large base, it won't be abandoned anytime ...
I have been using redmine with my team. It is free and has a wiki that is more than adequate.
I like 37signals's Basecamp software. You get a great, inexpensive hosted solution with a lot of useful features.
PBWorks provides a bunch of features for collaborating on a project.
I had the same dilemma of which wiki to use for a dev project a few months ago. We went with Mindtouch due to the fact that it's free (Mindtouch Core), it has lots of great extensions, the design is modern and flexible, the file attachment and linking capabilities are comprehensive, and it can search through file content. The community and forums are also ...
Both Github and Gitorious include wikis.
I would choose Trac, which is perfect for software development since it combines Wiki with Issue Management and Version Control. From their site, Trac is an enhanced wiki and issue tracking system for software development projects. Trac uses a minimalistic approach to web-based software project management. Our mission is to help developers write great ...
You might check out Evernote. It's usually not thought of as a "project blog" but it meets all the requirements you list. You can link notes in Wiki style You can permission access to notes You can share notes publicly or privately Evernote also just launched their business version which might provide some additional features to help manage your work ...
You might take a look at Workflowy. It's a bit of a different editting approach but they have some pretty robust sharing and privacy mechanisms.
Only top voted, non community-wiki answers of a minimum length are eligible