Return-Path: Delivered-To: apache-docs-archive@hyperreal.org Received: (qmail 15658 invoked by uid 6000); 2 Dec 1998 14:27:59 -0000 Received: (qmail 15651 invoked from network); 2 Dec 1998 14:27:58 -0000 Received: from mail12.voicenet.com (HELO voicenet.com) (207.103.0.6) by taz.hyperreal.org with SMTP; 2 Dec 1998 14:27:58 -0000 Received: (qmail 9198 invoked from network); 2 Dec 1998 14:27:53 -0000 Received: from dialup962-pri.voicenet.com (HELO petrovsk.voicenet.com) (207.103.117.190) by mail12.voicenet.com with SMTP; 2 Dec 1998 14:27:53 -0000 Message-Id: <3.0.6.32.19981202092601.007b3100@popmail.voicenet.com> X-Sender: petrovsk@popmail.voicenet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 02 Dec 1998 09:26:01 -0500 To: apache-docs@apache.org From: Michele Petrovsky Subject: RE: Case Studies In-Reply-To: References: <3.0.6.32.19981201114227.007ba9b0@popmail.voicenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: apache-docs-owner@apache.org Precedence: bulk Reply-To: apache-docs@apache.org At 11:07 AM 12/2/98 +0200, you wrote: >On Tue, 1 Dec 1998, Michele Petrovsky wrote: > >> This is where questions as to structure, presentation, >> audience etc. start to crop up. Once there's a good >> general in-English tutorial of the type you've described, >> a case could be made that the existing docs are sufficient >> for all other needs (e.g., sysadmins, programmers). >> So, should apache-docs concentrate solely on: >> >> * producing a tutorial >> * broadening/facilitating access to the >> existing docs (e.g., a document "portal" >> as has been suggested; creating numerous >> format versions such as PDF, SGML) >> >> or do we need other levels/types of documentation? >> And if the latter, what? > >I'd love to see how-to type documents answering to very practical problems >like user wants to use SSI how do I enable it or I don't want all people >to see my private pages how do I stop them. >Those are for buzy (and maybe lazy) part time admins, like me. But >tutorials would be great also covering things more in depth and paving >path to "conventional" apache documentation use. I find this example particularly interesting because it's pretty much a word-for-word description of what the sysadmin at the college where I teach is working on right now. Fine-tuning of various sorts might make for a very useful category of howto docs. So here's a question: what other specific types of howtos might we include in such a category? >This is my first appearance on list so I might introduce myself a bit. My >main job is to develop searh system with Java. I also admin departments >apache server on solaris. I need web-server in my work so my desktop is >Linux with apache and jserv (apache servlet module). >