Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <034301c21f49$a989f6e0$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin-developers AT cygwin DOT com>
References: <001901c21eee$8aadf060$0200a8c0 AT lifelesswks>
Subject: Re: Improved (?) cygserver available
Date: Sat, 29 Jun 2002 09:47:55 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Robert Collins" <robert DOT collins AT syncretize DOT net> wrote:
> Would you like to take maintenance of the cygserver over? I'm
> not sure when I'll have enough time to do a responsive job of
reviewing
> patches. As you are interested and working on the main code plus the
> SysVIPC, it's seems a small step to being maintainer.

Umm . . . I seem to recall my mother warning me about "small steps"
:-)

But yes, I do seem to have overstepped my initial mandate of "having a
look at the sysv ipc stuff" and I do have enough time (there is little
immediate threat of my starting work again). So, okay, assuming there
are no objections (and Chris has already given his blessing), I'll
take over the maintainance of cygserver.

> Maintainer
> entails: bugfixing the cygserver and related code, gatewaying
cygserver
> patches into HEAD (whether from branches or just emails to
> cygwin-patches), and finding a replacement before you stop being
> maintainer :}.

I see the last as being the really tough job.

> I'm not stepping out of cygwin at all - just facing some serious
time
> constraints. IOW I'll still be able to help if you need extra input
into
> the cygserver, and will probably still comment on changes after the
fact
> :}.

Comments and other input are very welcome: I'm confident enough about
most of the work (client/server programming is my bread and butter
work) but I'm not a Windows (or Cygwin) guru by any measure, and
there's going to be some more intricate issues coming up: security
issues and installing cygserver as a service come to mind.

All I've got to do now is find a rather problematic little bit of
memory corruption . . .

Cheers,
// Conrad