Re: PHP License

Why is this a problem? Just change the license of PEAR ... It's NOT a big deal to change a license. What's the problem of going from PHP to a more liberal license (LGPL or BSD)? None. There aren't any BC's because we're becoming MORE liberal, not less. If our licenses and standards for licenses are prohibiting other projects from adopting PEAR then we need to become more liberal with our licenses. It's not like PEAR is some corporation that needs to monitor this kind of stuff. The only possible "problem" is that PEAR < 1.4.0 will be the PHP license and PEAR > 1.4.0 will have a more liberal license (BSD, LGPL, whatever). That's not a problem - it just means that the earlier versions will have more restrictions, but upgrading will mean you have less restrictions. --Joe On Aug 24, 2005, at 12:40 AM, Lukas Smith wrote:

Jon Parise wrote:

I understand the basis of this thread is regarding some potentially inappropriate clauses (with regard to PHP script code) in the PHP license, but package developers have always been free to license their code under an alternate approved license.

The problem though is that at the core we have the PEAR package. This package is licensed under the PHP license and every package depends on it for error handling and other aspects. regards, Lukas PS: I cut the cross posting to pear-dev and pear-group.

-- Joseph C. Stump joe@joestump.net http://www.joestump.net