From owner-freebsd-chat Mon Mar 20 0:14:32 2000 Delivered-To: freebsd-chat@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 927E537B974 for ; Mon, 20 Mar 2000 00:14:26 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA95973; Mon, 20 Mar 2000 09:14:21 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Terry Lambert Cc: noslenj@swbell.net (Jay Nelson), freebsd-chat@FreeBSD.ORG Subject: Re: The Merger, and what will its effects be on committers? References: <200003171545.IAA16366@usr06.primenet.com> From: Dag-Erling Smorgrav Date: 20 Mar 2000 09:14:19 +0100 In-Reply-To: Terry Lambert's message of "Fri, 17 Mar 2000 15:45:48 +0000 (GMT)" Message-ID: Lines: 22 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert writes: > The point is that, if a driver already exists in BSDI, and FreeBSD > becomes the public shadow of the BSDI source tree, there is very > little incentive to write a new driver among volunteers, because > the job has already been done, and there are interesting things to > write that haven't yet been done. Why would FreeBSD become the public shadow of the BSDI source tree? From what I've read about the merger, the reverse (BSDI becoming the commercial shadow of FreeBSD) is more likely. Let me spell it out for you: BSDI WILL NOT CONTROL FREEBSD. Nobody can take arbitrary control of FreeBSD. It's open source. Even if Jordan, David & co. were to "sell out" to BSDI today, they couldn't stop committers from finding another place to host the project and carry on with its development. The worst they can do is stop us from using the name. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message