From dee8da2a5ab4eccd3a33da4313cc2e4d07e3df65 Mon Sep 17 00:00:00 2001 From: jim winstead Date: Fri, 15 Jun 2001 15:56:45 +0000 Subject: [PATCH] change bsd-style to apache-style, fix typo, add link to zend license email address --- license/index.php | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/license/index.php b/license/index.php index 5eeecaa8b..e130629d1 100644 --- a/license/index.php +++ b/license/index.php @@ -13,7 +13,7 @@ Public License (GPL) like PHP 3 was?

A. GPL enforces many restrictions on what can and cannot be done with the licensed code. The PHP developers decided to -release PHP under a much more loose license (BSD style), to help +release PHP under a much more loose license (Apache-style), to help PHP become as popular as possible.

Q. What does the PHP license mean then, in simple words?

@@ -45,11 +45,11 @@ I be concerned about it?

First, if you publish patches to the Zend scriping engine library. The Zend license allows Zend Technologies, Ltd. to use those patches royalty-free (see the license for exact details). Second, -the license prevents commercial use of the Zend scriping engine +the license prevents commercial use of the Zend scripting engine library to build commercial applications. If you want to use the Zend scriping engine library commercially (for example, as a macro language in a commercial word processor you're writing), you must -contact Zend Technologies, Ltd. for licensing information. +contact Zend Technologies, Ltd. for licensing information.

Q. Where can I get more information on the QPL?