Re: Appropriate license for packages
| From: | Lukas Smith | Date: | Wed, 18 Feb 2004 22:20:49 +0000 |
| Subject: | Re: Appropriate license for packages | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-25701@lists.php.net to get a copy of this message | ||
Stig S. Bakken wrote:
On Sun, 2004-02-15 at 22:29, Klaus Guenther wrote:Appearently FSF thinks otherwise :-/ http://yro.slashdot.org/yro/04/02/18/215242.shtml?tid=117&tid=148&tid=185&tid=99 regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07"Stefan Neufeind" <stefan@neufeind.net> wrote:I expect that the PHP 4.0 license will be upgraded to match the Apache 2.0 license (http://www.apache.org/licenses/). AFAICS, the two main advantages of the new Apache license is that it is GPL compatible, and it addresses potential patent/copyright/trademark issues so we never end up in any form of "SCO situation". Anyway, I suggest that we keep our cool for a while longer and tag along when PHP switches to the Apache 2.0 license. Check it out. I think this is just what PEAR needs.although this is a little OT, maybe somebody can help me out. Does somebody know of any talks held or articles written about choosing the right license? This would be of particular interest to me with reference to packages (like the ones shipped by PEAR).I think it would be of use. Iirc, there was an article on licensing in the PHP Magazine International Edition, but it would be nice to have a page in the manual that describes the various licenses that are acceptable to PEAR and the benefits of each.When reading the PHP license again I recently thought there might be paragraphs in it which completely don't go together with PEAR packages (not only but e.g. even the closing sentence "This product includes the Zend Engine" - which is not included when we distribute packages).That is right. Perhaps it is time to create a PEAR license that is based on the PHP license, but without certain clauses -- such as the one you mentioned. Ianal, but it may be possible to create a derivative license that automatically updates itself based on the latest PHP license (or we can use the same version numbers as the PHP license). Something like "This license is based on the PHP License 3.0, excluding paragraphs ... and substituting the following wording for paragraph ...".