| Re: [location-iwg] uDig proposal - license |
Well, actually I excluded ALv2 on purpose. The patent license provisions in the ALv2 may complicate the cut-and-paste into LGPLv2 - which is what I assumed you meant by "LGPL". If it's LGPLv3, then we could look more carefully. BTW, there is no lawyerly consensus on whether cutting-and-pasting code from different licenses ever works. Reasonable people can and do disagree on that point. To further complicate the answer, dual-licensing the Eclipse project under the EPL+EDL(BSD) could be an interesting option. Don't forget that people within the Eclipse community may also want to pull your code into their projects. And for some consumers, the patent license provisions of the EPL (which are virtually identical to the ALv2) are important to them. Furthermore, this particular dual-licensing pattern has quite a few precedents within the Eclipse community. Hope that helps. From: Jody Garnett [mailto:jody.garnett@xxxxxxxxx] So going to take that back to udig-devel as follows: Q: Is this story possible with EPL, or should we focus on one of the other license options? A: EPL to LGPL is not possible at the patch level (can be handled at the component jar level) A: The "universal donor licenses" are MIT and BSD and ALv2 |