nanogui: keeping the project alive
Subject:
Re: [nanogui] keeping the project alive
From:
Jason Kingan ####@####.####
Date:
20 Apr 2005 16:58:58 +0100
Message-Id: <4a5edd968aafb7adc36e86fbabd4b0bb@toast442.org>
Yow!
I've been unsubscribed as well - from talking with Greg it happened on
the exact same day. I'm not sure I've been properly re-subscribed yet -
I've not been able to get a response from the list server. Apologies to
anyone who requested information on ViewML and didn't get a response.
I'm still going through the archives as well.
Jason Kingan
On Apr 20, 2005, at 9:51 AM, Greg Haerr wrote:
> Hi Everyone,
> I've just found out that I've not been receiving emails on
> the nanogui list for two months!!! Thanks Alex and Steven
> for sending me an email. I get about 2-3 personal emails
> a day about nano-X, and answer them, and I had thought
> that was the nano-X traffic.. Very sorry.
>
> I'm frantically reading the archive emails, and definitely see
> where nano-X developers think there's been no response
> from me, since there hasn't been any. But that hasn't been
> intentional.
>
> I'd like to make a quick read-through of the last month's emails,
> and some consideration of the technical discussion. At a very
> quick glance, I don't think splitting the project is a good idea,
> but think I should appoint CVS write access to some key
> developers, and remain involved with architecture issues.
> I've always been very concerned with introducing bugs,
> since I hate buggy software, but realize that I haven't had
> time to apply patches nearly quickly enough.
>
> As I stated some time before I got unsubscribed, I would
> like to release the current CVS as 0.91, and then apply some
> older patches as 0.92. I would be happy to discuss all of these
> before 0.92, so as to best "sequence" patches all of you may
> have, to allow nano-X to move forward as a community project.
>
> Thanks!
>
> Regards,
>
> Greg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>
