Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!PT.CS.CMU.EDU!andrew.cmu.edu!lb1y+
From: lb1y+@andrew.cmu.edu (Linda Branagan)
Newsgroups: comp.lang.c
Subject: installation documentation
Message-ID: <oVS1q8y00Vs3YB809G@andrew.cmu.edu>
Date: Sat, 17-Oct-87 21:46:48 EDT
Article-I.D.: andrew.oVS1q8y00Vs3YB809G
Posted: Sat Oct 17 21:46:48 1987
Date-Received: Sun, 18-Oct-87 13:09:33 EDT
Organization: Carnegie Mellon University
Lines: 27
In-Reply-To: <190@sas.UUCP>



My manager has asked me to do some informal research on installation
documentation.  Specifically, we're interested in defining what should
be included in installation documentation and how it should be
structured.

I'd appreciate your input on this subject.  


	+  What do you think should be included in good
	installation documentation? 

	+  How should it be formatted?

	+  What factors specifically separate good documentation
	from bad? 

(This can involve any type of installation, from entire
operating systems to single applications, we're flexible.)  

I'd particularly appreciate pointers toward good or bad examples of
installation documentation.  If you've got a favorite installation
horror story, I'd like to hear that, too.


Linda Branagan
lb1y@andrew.cmu.edu