[coyotos-dev] Documentation: CMS or SCM?

[Jonathan S. Shapiro]

We have an open issue: should we manage documentation primarily in a
content management system (CMS) such as Drupal, or should we manage
documentation primarily in a source code management (SCM) system such as
Mercurial?

I'm torn. The CMS route has the advantage that it lets people work with
us to improve the documents actively and immediately. If something is
busted, you can just go in and edit it. At the very least you can
comment on it. Unfortunately it does not give us any sort of a document
version control mechanism.

The SCM route gives us versioning without interactivity. It's not really
possible for people to comment directly if we go that route.

A third option is to have the "reference" version under SCM control and
upload it whenever a version snapshot is done. We could probably also
have a "commentable" version on the site.

If the "comments" model is sufficient, I would kind of like to keep our
documents under version control. One issue is that the import/export
facilities of Drupal simply *suck*, so automating this is rather a pain
in the butt.

In any case, I would greatly appreciate feedback and opinions on this.

Which way should we go and *why*?


shap