The problematic items (at least from a Debian packaging prospective are)
3. The name “PHP” must not be used to endorse or promote products
derived from this software without prior written permission. For
written permission, please contact email@example.com.”
4. Products derived from this software may not be called “PHP”, nor
may “PHP” appear in their name, without prior written permission from
firstname.lastname@example.org. You may indicate that your software works in
conjunction with PHP by saying “Foo for PHP” instead of calling it
“PHP Foo” or “phpfoo”
6. Redistributions of any form whatsoever must retain the following
acknowledgment: “This product includes PHP, freely available from
Generally these terms don’t apply well to stuff that isn’t PHP.
Anyhow how have other people approached this problem. For phpDocumentor im looking towards just doing a dual license with PHP and BSD, just because its been PHP licensed for so long. If I can get Harry to relicense the code I used I might just release HTML_AJAX on the BSD license for the next release, otherwise I guess im stuck unless I finish up all the JS refactoring I have planned.
Charles Fry wrote up Debian’s concerns and sent them to pear-dev if you want more details on why the license is a problem.