Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <054901c16d5e$7b566ee0$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <007f01c16cde$5016de20$0200a8c0 AT lifelesswks> <20011114124323 DOT C24614 AT cygbert DOT vinschen DOT de> <049601c16d58$d8565250$0200a8c0 AT lifelesswks> <20011114224335 DOT GA10472 AT redhat DOT com> Subject: Re: no more package moratorium? Date: Thu, 15 Nov 2001 09:48:29 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 14 Nov 2001 22:54:09.0030 (UTC) FILETIME=[45041260:01C16D5F] ----- Original Message ----- From: "Christopher Faylor" > > >I think we should either get a consensus from all the package > >maintainers, or perhaps, wait 3 days for objections. If no objections, > >then the package is allowed in. If there are objections, discuss until > >resolved. To prevent deadlock, a single individual objecting will not > >cause a package to be rejected, the objections must be agreed with by > >other package maintainers. > > As long as I get veto power or whatever the opposite of veto power, > that's fine with me. I'm not exactly Linus in this situation, I guess. Well in this situation you are a package maintainer - the cygwin package. Just object :]. > I'm not sure that we really need to be this formal, though. Who's going > to be doing the tracking? How many new packages are we going to get? I can easily keep a notepad list of packages that have had someone put their hand up for, and every 3 days delete 1 day off the list. Rob -- 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/