X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_CG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20101009052830.GA12072@ednor.casa.cgf.cx>
References: <29894398 DOT post AT talk DOT nabble DOT com>	<376593050 DOT 20101006200403 AT mtu-net DOT ru>	<AANLkTikBi-G5wmNq=P8KG8HJ8hyxhwL_k5kv0M2Ykhsi AT mail DOT gmail DOT com>	<20101007220900 DOT GE24824 AT ednor DOT casa DOT cgf DOT cx>	<AANLkTikHQo2WNh4n71NCe81LsEsni5PW3gWU6C=uxkwv AT mail DOT gmail DOT com>	<AANLkTi=0AA4d8GPkGP=xHwyfp9ju4HLcjE8+59O2eHSH AT mail DOT gmail DOT com>	<AANLkTimBeqmwPLXLv0Z_acbzRRYMR42S_Gn3AR2rwt3K AT mail DOT gmail DOT com>	<20101009052830 DOT GA12072 AT ednor DOT casa DOT cgf DOT cx>
Date: Sat, 9 Oct 2010 07:26:11 -0500
Message-ID: <AANLkTimUc9Tbs7ifR4pRV2A_PpvBekQum-EGzBV4aMc4@mail.gmail.com>
Subject: Re: Looking for experienced CygWin Users
From: mike marchywka <marchywka AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> We've already mentioned that we need help improving our documentation.
> The documentation at the Cygwin site should, in a perfect world, contain
> what a user needs and there should be no need to go to google for
> information.  So, rather than invent some convention to make it easy
> to look up things in google, we really should be updating the words
> available on the cygwin site.

No matter what you do someone will have some other idea- this is the same
old argument that always comes up with the software itself, " you should have
written than it [awk,sed,perl,python] instead of
[awk,sed,perl,python]. Personally
I'm more concerned with having stuff that works well than help in some
pre-defined format. Even with what you are suggesting, I often have to
resort to something like using google for grep confined to a single
site. So you put up documents that looks like man pages for utility
swiss_army_knife, or take the man page for g++ as an example. You
end up having to grep through that anyway just as you end up
using google cached results to highlight what you want ( although
I have a highlight script too LOL).

The idea I had was more for collaborative document creation but
if you want to dsitrbute the work to motivated people whoreally use
the documentation, you would think you could get people who
receive email help to add their new found knowledge to a wiki page.
the point on talk list however is well taken, it seems to have
been tried and failed.

And of course in a perfect world no one would need computers
since there are no problems to solve.

( btw, I tried twice to respond on talk list and both times post was rejected
and I finally decided I have other things to do as does everyone else LOL)


>
> cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple