<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
</HEAD>
<BODY>
But I have separated the need for sleepycat out.<BR>
<BR>
So a user need not be anyway encumbered by sleepycat, using no code <BR>
from them whatsoever, if they choose not to install it.<BR>
<BR>
On Tue, 2006-01-24 at 19:16 -0600, Ben wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">it's fine with me and andrew, so i'm happy with LLGPL. on the other</FONT>
<FONT COLOR="#000000">hand, there are some licensing issues with using sleepycat itself, so</FONT>
<FONT COLOR="#000000">that should be taken into account.....</FONT>
<FONT COLOR="#000000">B</FONT>
<FONT COLOR="#000000">On 1/23/06, Robert L. Read <<A HREF="mailto:read@robertlread.net">read@robertlread.net</A>> wrote:</FONT>
<FONT COLOR="#000000">> For the code that I have written, I am completely in accordance with this</FONT>
<FONT COLOR="#000000">> suggestion to use the LLGPL.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> However, Ben and Andrew and others are really the primary authors; unless</FONT>
<FONT COLOR="#000000">> we reach consensus with them, and perhaps others, I don't see how we</FONT>
<FONT COLOR="#000000">> can make the switch.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> On Mon, 2006-01-23 at 23:45 -0500, Ian Eslick wrote:</FONT>
<FONT COLOR="#000000">> I am writing to see if I can restart the license discussion I saw a</FONT>
<FONT COLOR="#000000">> little of in the archives late last year. With the SQL backends it</FONT>
<FONT COLOR="#000000">> seems more appropriate to release the next version of elephant as an</FONT>
<FONT COLOR="#000000">> LLGPL code base to encourage wider adoption by folks who work for or</FONT>
<FONT COLOR="#000000">> consult for other companies and can't use the existing elephant code</FONT>
<FONT COLOR="#000000">> with a SQL backend in commercial software. It certainly makes it more</FONT>
<FONT COLOR="#000000">> motivating for me to contribute to the code base as my lab (sponsored by</FONT>
<FONT COLOR="#000000">> a bunch of companies) has expressed a preference for LLGPL in my own</FONT>
<FONT COLOR="#000000">> library projects. I've had to strip all the GPL'ed outside lisp</FONT>
<FONT COLOR="#000000">> libraries but am holding for the time being to see if elephant will</FONT>
<FONT COLOR="#000000">> indeed reconsider its license. :)</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Regardless it's a wonderful system already and the first shot in awhile</FONT>
<FONT COLOR="#000000">> for the lisp community to settle on a PODB. It's probably also helpful</FONT>
<FONT COLOR="#000000">> that the code is maturing at the same time as AllegroCache is generating</FONT>
<FONT COLOR="#000000">> some broad interest.</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Please consider this my request for the LLGPL.</FONT>
<FONT COLOR="#000000">> <A HREF="http://opensource.franz.com/preamble.html">http://opensource.franz.com/preamble.html</A></FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> Regards,</FONT>
<FONT COLOR="#000000">> Ian</FONT>
<FONT COLOR="#000000">> _</FONT>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>