Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BABF559.12AE17D8@paradise.net.nz>
Date: Sat, 22 Sep 2001 14:20:09 +1200
From: Edmund Horner <ejrh AT paradise DOT net DOT nz>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Periodic plea for someone to work on cygwin docs
References: <20010921143948 DOT A3617 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am looking for a way to make a positive contribution (as opposed to
asking stupid questions of the list, of which I have been occassionally
guilty...).  Part of my work responsibility is technical documentation,
so I have some idea of the kind of technical research that's necessary
to update these sorts of documents.

Unfortunately I don't know much about either CVS or SGML, though of
course I could learn.

If the major requirement is simply someone who can write and has the
time to do so, then I think I can help.  If you think this is a
possibility, I will re-familiarise myself with the docs and think
further on it.

Edmund.

> I periodically ask if anyone is interested in helping out with cygwin
> documentation.
> 
> We need people to pull things from the FAQ into the documentation and
> to generally improve what is currently available.
> 
> Unfortunately, I have very little understanding of what is required to
> build the current documentation.  It is written in sgml and uses
> some tools that need to be downloaded from the net.  That is about
> as much as I know.
> 
> So, the problem is that I can't offer much guidance about what is
> required to actually make the documentation.  It should be possible to
> figure out what is required from the archives, though.  I can help with
> content, of course.  The whole cygwin mailing list can help with this,
> in fact.
> 
> If anyone is interested in doing this, I'll provide them with CVS access
> to the cygwin repository which would allow them to update cygwin
> documentation.
> 
> I can also provide access to the cygwin web pages so that the
> documentation can be updated there.  This happens automatically from
> CVS.
> 
> Anyone interested?  I've asked this this question before and I think
> I've had some nibbles but I haven't seen any activity on this front.
> It is a shame that a project which is the size of cygwin doesn't have
> anyone actively working on documentation (besides the FAQ, of course).

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/