mirror of
https://github.com/php/web-php.git
synced 2026-03-31 19:52:29 +02:00
74 lines
3.0 KiB
PHP
74 lines
3.0 KiB
PHP
<?php
|
|
require_once "prepend.inc";
|
|
commonHeader("License Information");
|
|
?>
|
|
|
|
<h1>License Information</h1>
|
|
|
|
<p>You can download the text of the latest version (3.0) of the
|
|
PHP license <a href="3_0.txt">here</a>.</p>
|
|
|
|
<a name="#FAQ"><h1>Frequently Asked Questions</h1></a>
|
|
|
|
<p><b>Q.</b> Why is PHP 4 not dual-licensed under the GNU General
|
|
Public License (GPL) like PHP 3 was?</p>
|
|
|
|
<p><b>A.</b> 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 (Apache-style), to help
|
|
PHP become as popular as possible.</p>
|
|
|
|
<p><b><i>Note: the following questions and answers only apply to version
|
|
2.01 and 2.02 of the PHP license. Ignore for version 3.0.</i></b></p>
|
|
|
|
<p><b>Q.</b> What does the PHP license mean then, in simple words?</p>
|
|
|
|
<p><b>A.</b> (Note: This answer should in no way be taken to replace
|
|
the PHP license, it is intended to give you a general impression
|
|
of what the license means.) Essentially, the PHP license gives you
|
|
the right to use, distribute and modify PHP as much as you want,
|
|
for both commercial and non-commercial use. You just have to make
|
|
it clear to the user that what you have distributed contains PHP.</p>
|
|
|
|
<p><b>Q.</b> The Zend license says I may not charge money for stuff
|
|
I sell along with Zend. Does that mean I cannot sell PHP scripts
|
|
or web sites that I build?</p>
|
|
|
|
<p><b>A.</b> <strong>No.</strong> Not at all. This clause only
|
|
concerns software built around the Zend scriping engine library,
|
|
not scripts that PHP executes, using that library. You are free
|
|
to distribute PHP source code you write freely or commercially,
|
|
without any concern about the PHP or Zend licenses. You may also
|
|
package PHP as a whole with your commercial applications as much
|
|
as you want. You just can't build commercial applications that use
|
|
the Zend scriping engine library directly.</p>
|
|
|
|
<p><b>Q.</b> So, what's the point of the Zend license? When should
|
|
I be concerned about it?</p>
|
|
|
|
<p><b>A.</b> You should be aware of the Zend license in two cases.
|
|
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 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 <a href="mailto:license@zend.com">Zend Technologies,
|
|
Ltd.</a> for licensing information.</p>
|
|
|
|
<p><b>Q.</b> Where can I get more information on the QPL?</p>
|
|
|
|
<p><b>A.</b> The authors of the QPL, Troll Tech AS,
|
|
have published an annotated version of the license which
|
|
makes it easier to understand. You can view it online <a
|
|
href="http://www.troll.no/qpl/annotated.html">here</a>.</p>
|
|
|
|
<p><b>Q.</b> You suck! I'm going to take the last version of PHP 3
|
|
that was distributed under the GPL and fork! How would you like
|
|
that?</p>
|
|
|
|
<p><b>A.</b> With fries.</p>
|
|
|
|
<?php commonFooter(); ?>
|