Hey Ryan, On Mar 5, 2012, at 2:27 PM, Ryan McKinley wrote:
>> >> Unfortunately I do see it as a roadblock. The goal of SIS was to write >> a pure ALv2 licensed (or compatible) spatial library and toolkit, which >> in my mind does *not* include any dependencies (even optional) on >> LGPL components. >> > > Got it, this was my understanding. The goal of SIS is to build an ASL > version of JTS -- that's a great goal, just not one I have any > energy/time to contribute towards. No worries. I appreciate you reaching out. Is there a way to have everything in spatial4j that doesn't rely on the LGPL code here? > > >> Is there any way that the works of spatial4j could be replaced by ALv2 code? > > The code in spatial4j is all ASL. If there were a viable ASL polygon > library, we could use that too. How can you have an ALv2 licensed library that has dependencies on LGPL upstream components? Doesn't the LGPL and its viral nature [1] spill into your code? > > It looks like github is an appropriate place for the spatial4j development. Would be great to reach some sort of compromise, and like I said, I'm totally supportive of what you guys are trying to do. If we can't, I wish you the best and hopefully we can build an ALv2 licensed polygon support capability that you guys could leverage, and perhaps help merge the communities then. Thanks! Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
