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: Tue, 1 Oct 2002 10:37:35 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Moving cygwin discussions to Usenet? (e.g., alt.os.cygwin) Message-ID: <20021001143735.GB15398@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200209301154 DOT g8UBssX27530 AT mailgate5 DOT cinetic DOT de> <20020930131716 DOT GD23881 AT redhat DOT com> <5 DOT 1 DOT 1 DOT 5 DOT 2 DOT 20020930172951 DOT 00a6b8a8 AT mail DOT earthlink DOT net> <20020930232235 DOT GC6181 AT redhat DOT com> <20021001083052 DOT GA1136 AT raphael DOT oninet DOT pt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021001083052.GA1136@raphael.oninet.pt> User-Agent: Mutt/1.4i On Tue, Oct 01, 2002 at 09:30:53AM +0100, raphael wrote: >On Mon, Sep 30, 2002 at 07:22:35PM -0400, Christopher Faylor wrote: >>However, this really side steps the issue. Five hundred "How do I get >>to the previous command in bash?" questions are not going to lead to >>new insight about cygwin. > >Yes they will. These questions are asked by starting users who are new >to posix but might very well be window guru's. Currently they are >being putt off in a very rude way by a few people, thus cutting into >Cygwins future potential. Please provide the URL of such a reply. Stating that a thing is so without proof is not useful. I see many people patiently answering "newbie" questions here. Surely everyone has seen answers from (to name a few) Randle Schulz, Larry Hall, Igor Pechtchanski, and Robert Collins. I won't deny that occasionally people (like me, maybe) come across as being brusque but I really don't think that people aren't being helped here. Even if it was the case, I don't see how a newsgroup would magically get people helped. All that it would take would be one brusque person and there you go. >I refuse to believe that it is hystorical that so many developers come >from a *.nix background and so few if any from the windows side. It doesn't matter where people come from. Theoretically everyone can be taught where and how to find answers. >Eventually IMHO the current behaviour will slow down intergration of >cygwin into windows. I don't see how. The project seems to grow more popular every day. Letting people ask any old question without attempting to rein in the questions to something manageable doesn't seem like a good way to ensure project growth. It seems more like an invitation to chaos to me. >>That's what we're talking about. A question like (to use a recent >>example) "Why doesn't vim notice when I resize a console window under >>cygwin?" will lead to cygwin insights. I'd rather see those kind of >>questions asked in the official forum and point the bash people to the >>appropriate documentation. > >Isn't that what the development list is actually for? No. It isn't. Why would anyone be arguing with me about this? I don't get it. I wrote most of the words on project page. Do you think I'm going to slap my forehead and say "Aha! The developers list! I forgot all about that!" >What is the development list for, I see most development done here. Check out http://cygwin.com/list.html for a description of what the mailing lists are for. It sounds like all of the proponents of this newsgroup should be checking this out. cgf -- 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/