From owner-freebsd-chat Tue Apr 21 08:19:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23664 for freebsd-chat-outgoing; Tue, 21 Apr 1998 08:19:35 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@lariat.lariat.org [129.72.251.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23619 for ; Tue, 21 Apr 1998 15:19:29 GMT (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id JAA07257; Tue, 21 Apr 1998 09:19:28 -0600 (MDT) Message-Id: <199804211519.JAA07257@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1.327 (Beta) Date: Tue, 21 Apr 1998 09:19:24 -0600 To: chat@FreeBSD.ORG From: Brett Glass Subject: The "Anti-GPL" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had an interesting discussion with some friends who are Linux "fanatics" last night. They said that the *BSDs will naturally never do as well as Linux, because the GPL "locks" code into the GNU model. That is to day, the Linux folks can take code from FreeBSD, add their own, and "copyleft" the result -- at which point it can't be published again under the less restrictive Berkeley license. (And to think that the Linux folks claim that *others* "take code hostage.") If I publish code that's free for anyone to use, I want to make sure that it *stays* that way and is not encumbered by the GPL. So, I'm working on the text of an "anti-GPL" license -- in effect, a variation of the Berkeley license that explicitly prevents derivative works from being released under a more restrictive license like the GPL. Of course, I don't want to *call* it the "Anti-GPL," though that's my working name.... I'd like it to call it something like the "truly free software" license. Or something even more catchy. Any ideas for names? For provisions that should be included in the license? Would it be desirable to place existing parts of FreeBSD under such a license? --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message