Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 29 Jun 2003 18:30:24 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: newbie shell-users howto, guide, cheatsheet, or reference? Message-ID: <20030629223024.GC2167@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030626192146 DOT GE5870 AT ganymede> <20030627193140 DOT GS22695 AT ganymede> <20030629091232 DOT GU22695 AT ganymede> <20030629152614 DOT GA28799 AT redhat DOT com> <20030629215825 DOT GV22695 AT ganymede> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030629215825.GV22695@ganymede> User-Agent: Mutt/1.4.1i On Sun, Jun 29, 2003 at 10:58:25PM +0100, Karsten M. Self wrote: >on Sun, Jun 29, 2003 at 11:26:14AM -0400, Christopher Faylor (cgf-rcm AT cygwin DOT com) wrote: >> On Sun, Jun 29, 2003 at 10:12:32AM +0100, Karsten M. Self wrote: >> >on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self (kmself AT ix DOT netcom DOT com) wrote: > >> >> Given my research and responses (both on and off list), I'll be >> >> putting together something shortly at http://twiki.iwethey.org/, >> >> which the Cygwin project will be free to use. >> > >> >For better or worse, started as: >> > >> > http://twiki.iwethey.org/Main/CygwinEndUserQuickReference >> > >> > >> >Peace. >> >> Rather than throwing your efforts out there and expecting "the cygwin >> project" to use them, why don't you investigate what is required to >> change the actual documentation? A getting started section could be >> added to the actual documentation. >> >> As a general rule, your efforts will have a much wider audience and >> will benefit more people if you direct them towards the actual >> distribution rather than putting them on a personal web page. > >I've been through the existing Cygwin docs. I don't see anything >specifically answering this need. Huh? Addressing what need? Did I say that there wasn't a need to address? Is this really hard to understand? If you want people to benefit from your work, you try to get said work into the main cygwin web site and cygwin distribution. >The page isn't a personal web page. IWeThey is a group of tech >professionals who've been loosely associated for over five years, and >have run a number of web and other Internet-based services for much of >this time. I've got a big hand in the TWiki. It's not by any means >limited to me alone, only my product. As far as the cygwin project is concerned, it is a "personal web page". It is not located on the cygwin site. It is not incorporated with the rest of the documentation. The fact that there is a group of people associated with your effort is irrelevant. >The document I'm developing presently is just that -- a document in >development. When it's at a stage I feel it's suitable for inclusion in >the core Cygwin docs, I'll contact whomever is appropriate and y'all can >cleave off a snapshot. I'll likely continue to use the TWiki as a >development tool however, for extending this and related docs. Ok. This is not what you said at first. If you are willing to do some work to get this into the cygwin documentation, it will be appreciated. If you are expecting that you can just say "It's over there take it or leave it" then I suspect that this will always exist on a non-cygwin-project web site and we'll be seeing a lot of "I followed the directions over at..." followed by "The ... site is not affiliated with the cygwin project. We take no responsibility for the information there. If you have questions please contact the people at ... directly." cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/