Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

My team is debating whether to put the specifications on a private wiki or in a google document.

Can someone provide me with a summarized list of pros/cons for using a private wiki vs google docs for team specifications?

My gut feeling is the google-docs is heavier and slower to use, but easier, while private wikis, like mediawiki, seem to be harder to set-up and run.

share|improve this question

closed as primarily opinion-based by MichaelT, GlenH7, Wayne M, Bart van Ingen Schenau, jwenting Jun 10 at 10:36

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

Better in what way? And what makes specifications any different than any other document? –  Yannis Rizos Jun 13 '12 at 14:27
Start up process for wikis –  TZHX Jun 13 '12 at 14:30
As for wiki vs google doc, google doc is easier to format as you'll probably need to for distribution to stakeholders, pm's, etc. –  TZHX Jun 13 '12 at 14:31
Why the -1? I find it rather interesting. –  ONOZ Jun 13 '12 at 14:34
@ONOZ I suspect it is because the question is unclear about what "better" means, and is specified in such a way that the question is hard to provide an answer for. I edited the question to try and make it clearer what is being asked, although Adel, if I misunderstood your question please feel free to rollback the edit :) –  Rachel Jun 13 '12 at 15:05

3 Answers 3

up vote 2 down vote accepted

Depends what you mean by "better", and with whom you plan on sharing it.

I would usually go for the wiki, for ease of use and archiving and fast editing. However, you need to find one and host it somewhere, so if we don't really know what you want to do with more details, we can't really recommend one more than another.

However, I've resorted to using Google Docs for interview sessions, shared interactive meeting notes, or when my clients were not technically savvy enough and not willing to deal with a wiki. Plus the associated features (download to PDF, in-editor chat, and versioning make it great to use with non-technical uses)

To everyone their own.

share|improve this answer
Thanks! great points! –  Adel Jun 13 '12 at 14:54
@Adel: you're welcome. –  haylem Jun 13 '12 at 14:54

Personally, I would use Google Sites (which is a wiki) over Google Docs.

And I would use the free Google Sites over a paid service until you require a feature which is not available in Google Sites (like tagging).

share|improve this answer

I'd suggest Trac (http://trac.edgewall.org/). It integrates tightly with version control systems, is easy to set up, and in addition to wiki functionality, it also provides a VCS browser, project management tools, and issue tracking - all things that can be turned on or off easily.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.