Re: Licensing of things within PEAR

I would like to avoid having a mishmash of 10 different licenses. So yes, my vote is that we use the PHP license and that if you wish to contribute something to PEAR you use the PHP license for the code you contribute. That doesn't prevent you from using the GPL on the same code elsewhere, but when the code is shipped with PEAR it is under the PHP license. And I have no problem with you saying in the contributed code that people can use it under the GPL instead if they so choose. By the PHP license I mean the license PHP 4 is under minus clause 6. Clause 6 is the Zend license hook which obviously does not apply to PEAR as there is no Zend code in PEAR. -Rasmus On Fri, 5 Jan 2001, Derek A. Neighbors wrote: > Seeing this little debate made me wonder the following? > > What license are the classes in PEAR? (I assume they are under the PHP > license) but did not see a LICENSE or COPYING file in the PEAR directory. > > If in fact it is under the PHP License are all contributions forced to > use this license? Example: I have the my kickbutt class. I licensed it > under the GPL and distributed to several other repositories and now want > it to be in the PEAR repository. Must I either dual license it or > change the license? or will every class have the license it author > desires. If the latter how will you manage this and whom has copyright > to what as people continue to improve on the works of others in a > significant way? > > Derek Neighbors > GNU Enterprise > http://www.gnue.org > derek@gnue.org > > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >