background info & discussions
goldmoon: Are you sure? The web page states only that PHP license version 3 is incompatible with the GPL, NOT the LGPL. There might be a great deal of uncessary rewriting, if the licenses actually are compatible. In fact, the PHP license does not contain ANY clause that extends the license to code added by the Tiki team. The "covered code created under this License" does not extend to new code written by the Tiki team, as the PHP license lacks the "virul" clause found in the GPL. I believe the LGPL and PHP 3 licenses are compatible. I think we can apply our own license to our own code, even though we produce application combining PHP code and our code. We should check for verification from the ultimate authority .. Zend. Zend uses the same license as PHP, but has lawyers and experts and experience enforcing its license.
Terence: The problem is if we modify libs under the PHP License, Tiki becomes, arguably, a derivative work of these libs. In such a case, the LGPL requires that the work as a whole be licensed under the LGPL. The PHP License does not allow anyone but the authors to relicense code protected by it. That's my take on the problem.
Sulimma: "So, just also release the modified libraries seperately under the PHP license. Then you have contributed to a modified library. Tiki then is using this new PHP licensed library. That's exactly the same situation as when using unmodified PHP licensed libraries.
Damian says, the PHP libraries that we have used can in most cases be rewritten from scratch, this is something that Im currently looking at with POP3 as a example
GMuslera: Maybe for still using pear packages, and maybe some more things, Zzoss Installer could be used. Seems to be an installer for PHP applications, run in windows/linux, is LGPL, and between more features, can install PEAR packages, so for this particular problem it maybe could download on installation the needed pear packages so they could not be bundled with Tiki.
This is a tree of our current lib/ with licenses. They need removing and replacing:
(as lib/pear is in path, some pear call are without path, you can get whole list with
Some possible alternatives:
Note : It seems the CVS status of that file is actually the opposite : it's absent from BRANCH-1-8, was never removed from HEAD and was put back in 1.9 by mose in a merge. I think we should examine if it reappeared in 1.9 by human error or if the merge script has a problem (considering the similarity with CVS issues we had). Chealer9
Today i tried to figure out why PHP license is incompatible to GPL (not LGPL) License. If you compare the PHP License V3 with the newer BSD License, then you can see that the PHP License is almost the same with two sections more.