Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
Message-ID: <421E434F.77EA4D41@dessent.net>
Date: Thu, 24 Feb 2005 13:12:47 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: packg mngmnt model & other cygwin package releases...(where did they come from?)
References: <4208270D DOT 4080801 AT tlinx DOT org> <20050208063149 DOT GB3096 AT efn DOT org> <42091B63 DOT 1080908 AT tlinx DOT org> <20050208234325 DOT GA2944 AT efn DOT org> <420AAF5E DOT 1030506 AT tlinx DOT org> <420AB5EC DOT 1070904 AT familiehaase DOT de> <420BB627 DOT 7040905 AT tlinx DOT org> <20050210200410 DOT GA3728 AT efn DOT org> <420BEEB6 DOT 3070303 AT x-ray DOT at> <421CCF9A DOT 5010202 AT tlinx DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0502231348470 DOT 25676 AT slinky DOT cs DOT nyu DOT edu> <421CEAE3 DOT 3080401 AT tlinx DOT org> <421CEF9B DOT EDF56FBD AT dessent DOT net> <421E3DE6 DOT 7030300 AT tlinx DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Linda W wrote:

>     I'm not saying that there is some "approval" -- just
> that the module author can't check it in themselves.  I
> think this was the case with theh kernel -- it wasn't
> that linus went through and approved each line sent in
> by the senior kernel maintainers, but I had the impression
> that there was a bottle-neck on the check-process to the main
> tree.  That's why, I believe, they chose to go to a more public version
> control model - so "owners" of specific parts could
> check in changes in their section directly.  I don't see,
> from what you said, that the cygwin model is any different
> than having only a few people with check-in access to the
> tree, rather than each packager maintainer having check-in
> ability for their individual packages.

We're not talking about "checking in" anything, we're talking about
uploading files to the sourceware.org site which is mirrored to the
download locations.  And anyone with an account and sufficient
permissions can do this, it has nothing to do with CVS checkin ability. 
Many package maintainers have sourceware accounts and can upload their
packages themselves.  Those that don't just post a "please upload"
message and it's usually done within hours, by any of the people with
such an account.  You seem to be saying that there is some kind of
inherent flaw in that maintainers can't push out versions whenever they
wish, but that's just not the case.

If there is a package that is "stuck in the process" it's because the
maintainer does not have time to finish it or has not tested it yet, or
hasn't coordinated with other package maintainers of related packages. 
None of that has anything to do with the logistics of sourceware.org and
giving everyone an account with upload permissions would do nothing to
change that.

>     Perhaps a list of "related projects" or links to
> 3rd party cygwin-app projects on the cygwin website
> would benefit the cygwin community.  Something along the
> lines of "Other projects using cygwin (note we have no
> connection or responsibility for 3rd party projects)"...

http://cygwin.com/ported.html or scroll down to the bottom of the
cygwin.com home page.

Brian

--
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/