David, I've browsed your past discussions on this topic and didn't quite get this point from them. So, according to their interpretation of the GPL, I cannot develop an application using Lift+Db4o, as a consultant, for my customer's internal use?
I guess my existing app using wicket+db4o is also in violation. bummer :-( On Oct 6, 11:40 am, David Pollak <[EMAIL PROTECTED]> wrote: > Kris Nuttycombe wrote: > > On Mon, Oct 6, 2008 at 7:53 AM, David Pollak <[EMAIL PROTECTED]> wrote: > > >> Unfortunately, DB4O's choice of license and business model drives them away > >> from JVM-land and toward CLR-land. > > >> I've had pretty extensive chats with the DB4O people and would really like > >> to do something with them related to Lift, but it's a huge challenge. > > >> DB4O is dual-licensed under a GPL variant and commercial. In order to do > >> any commercial development at all (according to the DB4O sales people), one > >> must buy a commercial license. But buying a commercial license is hard. I > >> spent more than a week in round-and-round discussions with DB4O sales just > >> to get a price list. Basically, it was going to cost about $10K for my > >> development licenses. This was a development license just to explore and > >> see if DB4O was right for the project that I was working on. Yes, I > >> know... > >> I could have just downloaded the code and tested it out, but I believe in > >> abiding by license terms. > > >> What this means is that people can't just play with DB4O in a commercial > >> setting... they have to plunk down cash. This is normal in Microsoft/CLR > >> land, but most JVM-based projects, even in corporate settings, are > >> prototyped with open source code. When things get closer to production, > >> the > >> companies buy support and indemnification from the open source vendors. > > >> So, I'd like to do something with DB4O. They'd like to do something with > >> Lift. But nobody's found the right ground or the right business model to > >> make things work. Sigh. > > >> David > > > Forgive my ignorance, but if all you're talking about is prototyping, > > wouldn't using the GPL'ed code okay? As I understand it, the GPL > > doesn't kick in until you actually go to distribute the software. > > Also, since Lift is server-side, doesn't that let it off the hook for > > most uses? > > According to the DB4O sales person, they interpret "distribution" to > include putting in a source repository that is not hosted on the > company's servers or having non-employee consultants access the code. > It's an extremely aggressive interpretation. It makes exploration > difficult. Plus, many companies have an absolute bar against any GPL > code entering any project. > > > Kris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
