Subject: Heading back towards the mailing list subject (was: mechanised documentation and my business model solution)
From: DV Henkel-Wallace <gumby@henkel-wallace.org>
Date: Mon, 27 Mar 2006 09:55:50 -0800

 Mon, 27 Mar 2006 09:55:50 -0800
On Mar 26, 2006, at 15:53 , Rich Morin wrote:

> At 3:18 PM -0500 3/26/06, Randy Kramer wrote:
>> ... for wiki documentation I'd try to use CVS / Subversion (or ...
>
> Alternatively, the data could be stored in a version control
> system (VCS) and indexed by the RDBMS.  Or it could be stored
> in both places (ATA disks currently list at $0.20/GB :-).  Etc.
>
> However, I don't know of any wikis that use these ideas.

This mailing list is typically about free software business rather  
than design, and when I think of that I typically think of business  
models in the abstract sense.  However in this case I'll go for a  
model of a specific business.  That is to say:

Businesses that need to follow ISO 9000 (or any of its  
specialisations like 9001 etc) need documentation tracking systems.   
Typically these systems are outrageously priced...which provides an  
opening for a FS-based alternative.  I don't really know why they  
might need a DB on the back end; subversion might be enough.  On the  
other hand they have specialised, vertical needs (e.g. not everyone  
can edit; review cycles are required; automation is needed to try to  
ensure that everyone is reading off the latest version and  knows   
that the version has changed, etc) which also provide various FS  
advantages  la the "Cygnus model."

My industry, in particular (pharmaceuticals) is wasting money on  
this.  Oh yeah, these customers are typically price-sensitive in