php/archived-web-php
1
0
Fork 0
mirror of https://github.com/php/web-php.git synced 2026-03-23 23:02:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

- Update with more humain explainations on license issues

Browse Source 
- Add "I know which licenses PHP projects use, and will develop my code using
  them" checkbox to the cvs-request form
# Patch by Judy Taylor <@uk.ibm.com> and Zoe
This commit is contained in:
Hannes Magnusson
2008-12-31 10:24:58 +00:00
parent 2b9cd53dcf
commit ec6181e1ec
5 changed files with 220 additions and 95 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
cvs-php.php
View File

@@ -37,7 +37,6 @@ $groups = array(
// We have a form submitted, and the user have read all the comments
if (count($_POST) && (!is_array($_POST['purpose']) || !count($_POST['purpose']))) {
// Clean up incoming POST vars
if (get_magic_quotes_gpc()) {
foreach ($_POST as $k => $v) {
@@ -76,6 +75,9 @@ if (count($_POST) && (!is_array($_POST['purpose']) || !count($_POST['purpose']))
if (empty($_POST['group']) || !isset($groups[$_POST['group']])) {
$error .= "You did not fill out where to send the request. ";
}
if (!isset($_POST['guidelines']) || !$_POST['guidelines']) {
$error .= "You did not agree to follow the contribution guidelines. ";
}
// Post the request if there is no error
if (!$error) {
@@ -305,16 +307,6 @@ EOT;
here, make sure to mention them here!
</p>
<p>
One last thing, before you fill in the form you should also understand the principles under which PHP itself is developed. These are summarised in the next paragraph.</p>
<p>Any code contributed to PHP will be received under the PHP (or a compatible) license. PHP will be redistributed under the PHP license (currently version 3.01, http://www.php.net/license/). This includes implementation code, test cases, utility scripts and tools - that is, all code associated with the PHP project. If you contribute code that isn't entirely your own (for example it may be partially derived from other Open Source software) you are asked to add a comment into the source code to indicate the origin and the license of the original code. If you are unsure of the license you are asked to confirm with the owner of the code that they are happy for it to be contributed to PHP under the PHP license. Specifically regarding GPL and LGPL source code:
<ul>
<li>GPL or LGPL licensed code cannot be used as a basis for any derived work contributed to PHP.</li>
<li>Extensions which link GPL'd libraries will not be accepted.</li>
<li>Extensions which link to LGPL libraries will be strongly discouraged.</li>
</ul>
</p>
<p>
The CVS account, once granted and activated (which could take a while, so be
patient!), gives you access to a number of things. First, and most
@@ -376,6 +368,10 @@ foreach ($purposes as $i => $p) { ?>
<th class="subr">If your intended purpose is not in the list, <br />please state it here:</th>
<td><textarea cols="50" rows="5" name="realpurpose" class="max"><?php if (isset($_POST['realpurpose'])) echo clean($_POST['realpurpose']);?></textarea></td>
</tr>
<tr>
<th class="subr">Do you agree to follow the <a href="license/contrib-guidelines-code.php">contribution guidelines</a>?</th>
<td><input type="checkbox" name="guidelines" value="1" />Check the box if you agree.</td>
</tr>
<tr>
<th class="subr">User ID:<br /> <small>(single word, lower case)</small></th>
<td><input type="text" size="10" name="id"

1
include/layout.inc
View File

@@ -195,6 +195,7 @@ function site_header($title = '', $config = array())
<a href="/FAQ.php">faq</a> |
<a href="/support.php">getting help</a> |
<a href="/mailing-lists.php">mailing lists</a> |
<a href="/license">licenses</a> |
<a href="http://wiki.php.net/">wiki</a> |
<a href="http://bugs.php.net/">reporting bugs</a> |
<a href="/sites.php">php.net sites</a> |

46
license/contrib-guidelines-code.php Normal file
View File

@@ -0,0 +1,46 @@
<?php
// $Id$
$_SERVER['BASE_PAGE'] = 'license/contrib-guidelines-code.php';
include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
site_header("License Information");
?>
<h2>PHP Contributor Guidelines for Code Developers</h2>
<p>
Before you complete the form to request a CVS id, you must understand and accept the principles under which PHP
itself is developed. These are summarised in the next paragraph.
</p>
<p>
Any code contributed to PHP must be contributed under the PHP license (or a compatible BSD-style license).
PHP will be redistributed under the PHP license (currently
<a href="http://www.php.net/license/3_01.txt">version 3.01</a>).
This includes implementation code, test cases, utility scripts and tools - that is, all code associated
with the PHP project. If you contribute code that isn't entirely your own
(for example it may be partially derived from other Open Source software) you are asked to add a comment
into the source code to indicate the origin and the license of the original code.
If you are unsure of the license you are asked to confirm with the owner of the code that they are
happy for it to be contributed to PHP under the PHP license.
</p>
<p>
Specifically regarding GPL and LGPL source code:
</p>
<ul>
<li>GPL or LGPL licensed code cannot be used as a basis for any derived work contributed to PHP.</li>
<li>Extensions which link GPL'd libraries will not be accepted.</li>
<li>Extensions which link to LGPL libraries will be strongly discouraged.</li>
</ul>
<h2>Guidelines for Related Projects</h2>
<p>
For related projects, please refer to the Project websites:
</p>
<ul>
<li><a href="http://pecl.php.net/copyright.php">PECL</a></li>
<li><a href="http://pear.php.net/copyright.php">PEAR</a></li>
<li><a href="http://gtk.php.net/copyright.php">GTK</a></li>
</ul>
<?php site_footer();

68
license/distrib-guidelines-code.php Normal file
View File

@@ -0,0 +1,68 @@
<?php
// $Id$
$_SERVER['BASE_PAGE'] = 'license/distrib-guidelines-code.php';
include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
site_header("License Information");
?>
<h2>PHP Distribution Guidelines</h2>
<p>
The PHP code can be redistributed in source or binary form provided that
the terms of the PHP license are respected (see
<a href="http://www.php.net/license/3_01.txt">version 3.01</a>).
</p>
<p>
In plain English, this means that you have to include the full license text
in human-readable form with every distributed copy of PHP, whether source
or binary. One way of doing this is to put a copy of the PHP license into a
text file that you include with the source or binary package before
distribution. This ensures that the license information can be read
properly even when a binary is shipped.
A text file containing license and copyright information is sometimes
given the filename "Notices", and may be referred to as a "Notices file".
</p>
<p>
Some files in the PHP codebase have been contributed under other licenses.
If you want to distribute these files, you also need to respect the terms
of those licenses.
To check, look for the terms indicated in the license + copyright comment
block at the top of the source file.
</p>
<p>
The license terms for such a file may require that its own license and copyright
information must be included with every distributed copy (including binaries).
This is quite a common requirement, which can be satisfied by adding the
appropriate license text into a text file for distribution purposes, like the
"Notices"-type of file suggested above.
</p>
<p>
A single "Notices" file could be used to hold the collection of license
and copyright information that applies to PHP in general (the PHP license) and
any files with additional licenses that you want to distribute (for example
Zend, TSRM etc.)
It is good practice to indicate which source file(s) a particular license
applies to.
</p>
<h3>Modified products derived from PHP</h3>
<p>
You can distribute your own software product which has been derived
from PHP, in source or binary form, provided that:
</p>
<ul>
<li>
relevant copyright information and license(s) from
the PHP codebase are distributed in human-readable form with
every copy, as described above.
</li>
<li>
you don't use the name "PHP" without permission, either
to promote your own product or within your product's name
(see clauses #3 and #4 in the PHP license
<a href="http://www.php.net/license/3_01.txt">version 3.01</a>).
</li>
</ul>
<?php site_footer();

182
license/index.php
View File

@@ -5,15 +5,84 @@ include_once $_SERVER['DOCUMENT_ROOT'] . '/include/prepend.inc';
site_header("License Information");
?>
<h1>License Information</h1>
<h1>PHP Licensing</h1>
<p>
You can <a href="3_01.txt">download the text of the latest version (3.01)</a>
of the PHP license.
</p>
For licensing and copyright information on the PHP project materials, please see the following links:
</p>
<a name="#FAQ"><h1>Frequently Asked Questions</h1></a>
<ol>
<li><a href="#code-lic">PHP Codebase</a></li>
<li><a href="#doc-lic">PHP Documentation</a></li>
<li><a href="#web-lic">PHP Website</a></li>
<li><a href="#faq-lic">FAQ's</a></li>
<li><a href="#other-lic">Licensing information for related projects</a></li>
</ol>
<ol>
<li><!-- {{{ code-lic -->
<a name="code-lic"></a>
<h2>PHP Codebase</h2>
<ul>
<li>
PHP 4 and PHP 5 are distributed under the
<a href="http://www.php.net/license/3_01.txt">PHP License v3.01</a>, copyright (c) the PHP Group.
<ul>
<li>
This is an <a href="http://www.opensource.org/docs/osd">Open Source license</a>,
certified by the Open Source Initiative.
</li>
<li>
The PHP license is a BSD-style license which does not have the "copyleft"
restrictions associated with GPL.
</li>
</ul>
</li>
<li>
Some files have been contributed under other (compatible) licenses and carry
additional requirements and copyright information.<br/>
This is indicated in the license + copyright comment block at the top of the source file.
</li>
<li>
Practical Guidelines:
<ul>
<li><a href="/license/distrib-guidelines-code.php">Distributing PHP</a></li>
<li><a href="/license/contrib-guidelines-code.php">Contributing to PHP</a></li>
</ul>
</li>
</ul>
</li><!-- }}} -->
<li><!-- {{{ doc-lic -->
<a name="doc-lic"></a>
<h2>PHP Documentation</h2>
<ul>
<li>
The PHP manual text is covered by the
<a href="http://creativecommons.org/licenses/by/3.0/legalcode">Creative Commons Attribution 3.0 License</a>,
copyright (c) the PHP Documentation Group
</li>
<li><a href="http://creativecommons.org/licenses/by/3.0/">Summary</a> in human-readable form</li>
<li>Practical Information: <a href="http://doc.php.net/php/dochowto/">Documentation HOWTO</a></li>
</ul>
</li><!-- }}} -->
<li><!-- {{{ web-lic -->
<a name="web-lic"></a>
<h2>PHP Website</h2>
<ul>
<li>The Website copyright can be viewed here: <a href="/copyright.php">Website Copyright</a></li>
</ul>
</li><!-- }}} -->
<li><!-- {{{ faq-lic -->
<a name="faq-lic"></a>
<h2>Frequently Asked Questions</h2>
<!-- Selecetd FAQ points from former page on License Information [v 1.13] -->
<!-- Comments ref.old versions of PHP license prior to v3.0 have been removed -->
<h3>Use of the "PHP" name</h3>
<p>
<strong>Q.</strong> I've written a project in PHP that I'm going to release
as open source, and I'd like to call it PHPTransmogrifier. Is that
@@ -21,15 +90,18 @@ site_header("License Information");
</p>
<p>
<strong>A.</strong> We cannot really stop you from using PHP in the name of
<strong>A.</strong>
We cannot really stop you from using PHP in the name of
your project unless you include any code from the PHP distribution, in
which case you would be violating the license. But we would really
prefer if people would come up with their own names independent of the
PHP name.
which case you would be violating the license.
See Clause 4 in the <a href="http://www.php.net/license/3_01.txt">
PHP License v3.01</a>.
<br/>But we would really prefer if people would come up with their own names
independent of the PHP name.
</p>
<p>
Why you ask? You are only trying to contribute to the PHP
"Why?" you ask. You are only trying to contribute to the PHP
community. That may be true, but by using the PHP name you are
explicitly linking your efforts to those of the entire PHP development
community and the years of work that has gone into the PHP project.
@@ -51,6 +123,7 @@ site_header("License Information");
in the name and does quite well.
</p>
<h3>Change in licensing from PHP 4 onwards</h3>
<p>
<strong>Q.</strong> Why is PHP 4 not dual-licensed under the GNU General
Public License (GPL) like PHP 3 was?
@@ -63,80 +136,21 @@ site_header("License Information");
PHP become as popular as possible.
</p>
<p>
<em>
Note: the following questions and answers only apply to version
2.01 and 2.02 of the PHP license. Ignore for 3.x versions.
</em>
</p>
</li><!-- }}} -->
<li>
<a name="other-lic"></a>
<h2>Licensing information for related projects</h2>
<p>
<strong>Q.</strong> What does the PHP license mean then, in simple words?
</p>
<p>
For related projects, please refer to licensing information on the Project websites:
</p>
<ul>
<li><a href="http://pecl.php.net/copyright.php">PECL</a></li>
<li><a href="http://pear.php.net/copyright.php">PEAR</a></li>
<li><a href="http://gtk.php.net/copyright.php">GTK</a></li>
</ul>
</li>
</ol>
<p>
<strong>A.</strong> (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>
<?php site_footer();
<p>
<strong>Q.</strong> 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>
<strong>A.</strong> <strong>No.</strong> Not at all. This clause only
concerns software built around the Zend scripting 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 scripting engine library directly.
</p>
<p>
<strong>Q.</strong> So, what's the point of the Zend license?
When should I be concerned about it?
</p>
<p>
<strong>A.</strong> You should be aware of the Zend license in two cases.
First, if you publish patches to the Zend scripting 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 scripting 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>
<strong>Q.</strong> Where can I get more information on the QPL?
</p>
<p>
<strong>A.</strong> 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.trolltech.com/licenses/qpl-annotated.html">here</a>.
</p>
<p>
<strong>Q.</strong> 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>
<strong>A.</strong> With fries.
</p>
<?php site_footer(); ?>