Yoshi contacted me requesting I inquire as to the plausibility of modifying the current license of LGPL to EPL. I personally do not care which licensed is used, but he would like to package the project with some other set up plugins, of wich at least one apparently interfaces with SQL Explorer, and he is not able to distribute the package because the other plugin was developed under the EPL license. The EPL and LGPL license are not compatible from a distribution stand point.
Does anyone have any opinions on this matter?
Austin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
AFAIUI the EPL is more restrictive that LGPL - the LGPL allows the code to be reused in other programs which are not released under the LGPL (including proprietary programs). The EPL is more slightly more restrictive than even the GPL in that it (apparently, I've not read it) requires granting of more patent rights.
Yoshi contacted me requesting I inquire as to the plausibility of modifying the current license of LGPL to EPL. I personally do not care which licensed is used, but he would like to package the project with some other set up plugins, of wich at least one apparently interfaces with SQL Explorer, and he is not able to distribute the package because the other plugin was developed under the EPL license. The EPL and LGPL license are not compatible from a distribution stand point.
Does anyone have any opinions on this matter?
Austin
AFAIUI the EPL is more restrictive that LGPL - the LGPL allows the code to be reused in other programs which are not released under the LGPL (including proprietary programs). The EPL is more slightly more restrictive than even the GPL in that it (apparently, I've not read it) requires granting of more patent rights.
There is more info here: http://www.fsf.org/licensing/licenses/
John