Received: with LISTAR (v1.0.0; list gopher); Mon, 08 Jan 2001 11:03:31 -0600 (CST) Return-Path: Delivered-To: gopher@complete.org Received: from alexanderwohl.complete.org (localhost [127.0.0.1]) by pi.glockenspiel.complete.org (Postfix) with ESMTP id 3350E3B908; Mon, 8 Jan 2001 11:03:30 -0600 (CST) Received: by alexanderwohl.complete.org (Postfix, from userid 1000) id 34FCBEFC3; Mon, 8 Jan 2001 12:00:38 -0500 (EST) To: gopher@complete.org Subject: [gopher] Re: Forking UMN gopher? References: <87ofxivdk3.fsf@complete.org> <20010108021129.A25512@mothra> From: John Goerzen Date: 08 Jan 2001 12:00:38 -0500 In-Reply-To: <20010108021129.A25512@mothra> Message-ID: <87puhyj7wp.fsf@complete.org> Lines: 31 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-archive-position: 54 X-listar-version: Listar 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 X-list: gopher David Allen writes: > I'm not clear on who else is working on it. Who is the 'official' > maintainer of it? I know that you're the debian package maintainer, > but if you're also the maintainer, we're not forking. :) The official maintainer is University of Minnesota. Except for a small security fix, they have been inactive on it since 1995. > Where is the other work available? Is it reconcilable? What code has > been written for UMN gopherd that isn't in our tree, and why isn't it > there? There is no other work going on for UMN gopher(d) that is not in our tree. AFAIK, the two of us are the only people working on it. > Sorry for the barrage of questions...I just didn't know that forking > was going to be an issue. Well, the question is this -- if we are going to be putting serious work into it, and it looks like we are, then it makes sense to start versioning it, making releases, etc. like a real project. IE, 2.3.2, 2.4.0, whatever. When a project is active, distributing a diff that gets revved periodically is rather confusing to the users (well, anyone that doesn't run Debian.) So, essentially it's a fork but the other prong doesn't exist :-) -- John Goerzen www.complete.org Sr. Software Developer, Progeny Linux Systems, Inc. www.progenylinux.com #include