Received: with ECARTIS (v1.0.0; list gopher); Wed, 15 Jan 2003 15:44:11 -0600 (CST) Return-Path: Delivered-To: gopher@complete.org Received: from wile.excelhustler.com (unknown [68.99.114.102]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by gesundheit.complete.org (Postfix) with ESMTP id 12D3E6480A; Wed, 15 Jan 2003 15:44:09 -0600 (CST) Received: by wile.excelhustler.com (Postfix, from userid 1000) id 6ED65770E; Wed, 15 Jan 2003 15:44:07 -0600 (CST) Date: Wed, 15 Jan 2003 15:44:07 -0600 From: John Goerzen To: "J.A. Neitzel" Cc: gopher@complete.org Subject: [gopher] Re: Gopher Project is still alive..? Message-ID: <20030115214407.GA30338@wile.excelhustler.com> References: <200301152001.h0FK17W29363@sdf.lonestar.org> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200301152001.h0FK17W29363@sdf.lonestar.org> User-Agent: Mutt/1.4i Content-Transfer-Encoding: 8bit X-archive-position: 717 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-ID: Gopher X-List-ID: Gopher List-subscribe: List-owner: List-post: List-archive: X-list: gopher On Wed, Jan 15, 2003 at 08:01:07PM +0000, J.A. Neitzel wrote: > I am just curious about the current status of the Gopher Project. > Last release was gopher-3.0.5. Are there plans to continue > development? I sent a little patch a few weeks ago and did not > hear anything. Yes, there are such plans. Right now, I have been spending a lot of time on my OfflineIMAP project -- gopher://quux.org/1/devel/offlineimap -- and haven't had a lot of time to devote to Gopher. The patch did indeed go onto the queue though :-) Grand plan-wise, I want to discontinue support for UMN gopherd and encourage people with UMN repositories to switch to PyGopherd, which supports them. I would then continue to support UMN gopher as a client only. I find that for these projects, I tend to be bursty -- you'll see a couple weeks of furious activity, and then a month of silence. Dunno why, it's just how I seem to work. > You, John Goerzen, are listed as the NetBSD package maintainer for > gopher. The package is apparently still at 3.0.2..? The last > release made enough improvements that I thought an update of the > NetBSD package would have been appropriate, but ICBW. Of course, > your interpretation of what warrants an update may differ from > mine. I no longer have any NetBSD machines available to me, so feel free to take over that port (and any other assigned to me in NetBSD). Didn't know that submitting a port would set me up as a maintainer there :-) > I thought I might submit an OpenBSD port of gopher, but if the Please feel free to do that. > Anyway, I hope all is well. It is, I've just reached my brain bandwidth limit for the week :-) -- John