Re: Licensing in PEAR

On Mon, 2 Dec 2002, Ian Eure wrote: > After trying to submit GPL'd PEAR modules[1], I've looked over the PHP > license, the GPL, and the LGPL. I'm feeling stuck, and I'd like advice. > > PHP License: > Unacceptable. I will not release my code under this license, unless major > changes are made. In particular, Clause 4 irks me, in that I'm not given a > choice to bind my code to a particular version of the license. With the > (L)GPL, I may specify a specific version of the license. This is an issue > because if a later version of the PHP license contains a clause that I don't > agree with, I have no way to prevent people from using it anyways. Do you have the latest version (3.0) of this document? Clause 4 is somethign different.. and Clause 5 says (besides other stuff) " Once covered code has been published under a particular version of the license, you may always continue to use it under the terms of that version. You may also choose to use such covered code under the terms of any subsequent version of the license published by the PHP Group. " so your argument is not an issue anymore (don't have licence < 3 here..) > > LGPL: > Unacceptable. This license makes it far too easy to modify the class without > contributing the code back. For example, writing a 'wrapper' class which > overloads the original, and changes the behavior, or adds a feature, or > whatever. since when forces (L)GPL code to contribute back, if I change something? AFAIK, you only have to give the sourcecode to people, which get your "binaries". That's it. There is no Clause, which forces you to give the code to the original author back. > > GPL: > Unacceptable. Prevents non-GPL'd projects from using the class. that's true :) chregu