[elephant-devel] License Discussion

[Ben]

well i think kudos should go to robert for managing this beast,
keeping it alive and keeping andrew and me honest about our code!

B

On 1/24/06, Ian Eslick <eslick at csail.mit.edu> wrote:
> That's great to hear!  As Robert indicated, I think the real benefit is
> to users of the SQL backend.  Also, if we write a lisp backend using the
> current front-end metaclass and serializer then we'll (hopefully) have a
> fully LLGPL library solution for persistent objects.  I think that makes
> it much easier to build user community momentum.  License issues
> ultimately kept much work from proceeding on PLOB and a couple of other
> potential lisp persistent databases.
>
> Ben & Andrew, thank you for your great work on the system to date!
>
> Cheers,
> Ian
>
> Ben wrote:
>
> >it's fine with me and andrew, so i'm happy with LLGPL.  on the other
> >hand, there are some licensing issues with using sleepycat itself, so
> >that should be taken into account.....
> >
> >B
> >
> >On 1/23/06, Robert L. Read <read at robertlread.net> wrote:
> >
> >
> >> For the code that I have written, I am completely in accordance with this
> >> suggestion to use the LLGPL.
> >>
> >> However, Ben and Andrew and others are really the primary authors; unless
> >> we reach consensus with them, and perhaps others, I don't see how we
> >> can make the switch.
> >>
> >>
> >> On Mon, 2006-01-23 at 23:45 -0500, Ian Eslick wrote:
> >> I am writing to see if I can restart the license discussion I saw a
> >>little of in the archives late last year. With the SQL backends it
> >>seems more appropriate to release the next version of elephant as an
> >>LLGPL code base to encourage wider adoption by folks who work for or
> >>consult for other companies and can't use the existing elephant code
> >>with a SQL backend in commercial software. It certainly makes it more
> >>motivating for me to contribute to the code base as my lab (sponsored by
> >>a bunch of companies) has expressed a preference for LLGPL in my own
> >>library projects. I've had to strip all the GPL'ed outside lisp
> >>libraries but am holding for the time being to see if elephant will
> >>indeed reconsider its license. :)
> >>
> >>Regardless it's a wonderful system already and the first shot in awhile
> >>for the lisp community to settle on a PODB. It's probably also helpful
> >>that the code is maturing at the same time as AllegroCache is generating
> >>some broad interest.
> >>
> >>Please consider this my request for the LLGPL.
> >>http://opensource.franz.com/preamble.html
> >>
> >>Regards,
> >>Ian
> >>_______________________________________________
> >>elephant-devel site list
> >>elephant-devel at common-lisp.net
> >>http://common-lisp.net/mailman/listinfo/elephant-devel
> >>
> >>
> >>_______________________________________________
> >>elephant-devel site list
> >>elephant-devel at common-lisp.net
> >>http://common-lisp.net/mailman/listinfo/elephant-devel
> >>
> >>
> >>
> >>
>