Re: ZEO vs NEO

Yes, the LGPL would still be a problem.  Our lawyers don't want us to 
depend on any libraries or modules using licenses that have GPL in them, 
anywhere.  It's not really an issue of fact, rather it's an issue of what 
our clients might think, whether correctly or incorrectly.  Government 
contract managers often but not always have similar concerns.

Bill

On Tuesday, February 2, 2016 at 3:28:23 AM UTC-8, Jim Fulton wrote:
>
> I really like the NEO architecture, at least at a high level.  I 
> haven't studied it in detail.  I've been planning to work toward a 
> similar architecture with ZEO.  A big stumbling block for me has been 
> NEO's GPL license. 
>
> I was speaking with Jean-Paul Smets the other day and we discussed 
> adjusting NEO's license to make it more broadly usable.  He suggested 
> making the client LGPL.  Hypothetically, If NEO eventually replaced 
> ZEO and had an LGPL license, would the LGPL license present a problem 
> for anyone? 
>
> If the LGPL isn't a problem, I'd put a lot more effort into looking at 
> NEO as a client-server architecture for ZODB, likely as a replacement 
> for ZEO. 
>
> So does the LGPL present a problem to anyone? 
>
> Jim 
>
> -- 
> Jim Fulton 
> http://jimfulton.info 
>

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.