From owner-freebsd-chat Tue Aug 28 23:56:48 2001 Delivered-To: freebsd-chat@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id EE59D37B418 for ; Tue, 28 Aug 2001 23:56:41 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id AAA25488; Wed, 29 Aug 2001 00:56:30 -0600 (MDT) Message-Id: <4.3.2.7.2.20010829005302.0500e730@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 29 Aug 2001 00:56:24 -0600 To: cfuhrman@iwaynet.net, freebsd-chat@FreeBSD.ORG From: Brett Glass Subject: Re: Switching from LGPL to ??? License In-Reply-To: <999001492.3b8b8d94b71c3@webmail.iwaynet.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 06:24 AM 8/28/2001, cfuhrman@iwaynet.net wrote: >So, this brings me to two questions: > >1) Which license to distributed the module under: the Perl Artistic License or >the BSD one. Actually, the MIT X license is even simpler than the BSD license. It might be the best if your goal is to allow people to do anything with the code except sue you for bugs. The Artistic License gives you a bit more control (especially over the name of the product) but also has some vague and probably unenforceable provisions. The advantage of it would be that the module would be licensed in the same way as Perl (a popular thing to do in the Perl community). >2) What is the best means of changing the license? Basically strip out the LGPL >and replace it? If the code is all yours, yes. Otherwise, get permission from all authors first to avoid legal problems.... --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message