Licensing in PEAR

From: Date: Mon, 02 Dec 2002 18:23:01 +0000
Subject: Licensing in PEAR
Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-11299@lists.php.net to get a copy of this message
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. 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. GPL: Unacceptable. Prevents non-GPL'd projects from using the class. So, what are my options? Maybe a dual-license? This is approximately what I want: * GPL-style code contribution back to the original class. * non-GPL projects must contribute any changes, direct (e.g. modifying the class) or indirect (creating a 'wrapper' class) back to the original class. Any suggestions? [1] http://lists.php.net/article.php?group=php.pear.dev&article=11186 -- "das ist liebe, das ist hass / mit eifersucht vermahlen"

« previous php.pear.dev (#11299) next »