From owner-freebsd-chat Thu Jan 22 20:43:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26307 for chat-outgoing; Thu, 22 Jan 1998 20:43:12 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26285; Thu, 22 Jan 1998 20:43:03 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.7/8.8.7) with UUCP id VAA05665; Thu, 22 Jan 1998 21:42:38 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id VAA03190; Thu, 22 Jan 1998 21:41:21 -0700 (MST) Date: Thu, 22 Jan 1998 21:41:21 -0700 (MST) From: Marc Slemko To: Warner Losh cc: chat@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Mike Shaver: Netscape gives away source code for Communicator In-Reply-To: <199801230340.UAA22987@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 22 Jan 1998, Warner Losh wrote: > In message <199801230204.SAA17663@kithrup.com> Sean Eric Fagan writes: > : Please bear in mind there is a good chance that it will be released under a > : "for non-commercial use only" license, in which case it won't be able to be on > : the freebsd cdrom. Still. > > The press release said GPL. It also said that binaries were free for > OEMs to redistribute. It does _not_ say GPL. Read it very carefully. It says: >The company will handle free source distribution with a license >that allows source code modification and redistribution and provides >for free availability of source code versions, building on the >heritage of the GNU Public License (GPL), familiar to developers >on the Net. I would be suprised if they used the GPL as is. It is also true that the freely available source part of this announcement is nothing more than hype until it is done. "building on the heritage" could mean allowing somewhat similar things yet "building" a _new_ licence. There are also going to be some components that will almost certainly end up being stripped out due to licencing issues. That is, of course, hard to tell right now because who knows what 5.0 will be. It will probably have substantial changes.