Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-developers-unsubscribe-archive-cygwin-developers=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <199911182222.QAA18587@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
cc: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: Maintainers wanted 
In-Reply-To: Your message of "Thu, 18 Nov 1999 16:04:33 EST."
             <19991118160433 DOT A13395 AT cygnus DOT com> 
Date: Thu, 18 Nov 1999 16:22:44 -0600
From: Mumit Khan <khan AT nanotech DOT wisc DOT edu>

Chris Faylor <cgf AT cygnus DOT com> writes:
> I sent a plea to the cygwin mailing list asking for volunteers to
> maintain packages but didn't get much response.  So, I'm trying
> the same thing here with high hopes that I'll get a better response.

Enumerating the list of packages is definitely a better approach, and
provides a concrete target when you're thinking about volunteering.

Put me down for gcc and binutils. If others don't come forward, I'll
probably pick up a few more (since I build most of these myself anyway,
it's not that much of a bother). 

I'd add mingw as a separate package as we had talked about, and you can
put me down for that of course.

New GNU packages that should probably be there -- groff.

How about adding a secondary level -- contrib packages such as Perl 
(Charles Wilson is essentailly maintaining Perl for Cygwin, so that's
a good start). I'll probably take on a few -- GNU Octave, GMP, CLN
and possibly even Pine. However, this should be separate from the
main distribution to avoid (1) delays, and (2) reduce download size.

> 
> Btw, the next version of Cygwin will be 1.1.0.  DJ and I have decided to
> adopt the linux method for numbering releases.

Yes, please. I'm tired of using beta software ;-)

Regards,
Mumit