license-update: update website with new license info #1762
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,14 @@ | ||
| ============= An example PHP License, version 2.01 file ============ | ||
|
|
||
| This is the original PHP License, version 2.01, which applies only to | ||
| old versions of PHP software (such as versions 4.0RC2 and earlier). | ||
|
|
||
| This license is provided for historical purposes only. | ||
|
|
||
| This license has been superseded by the PHP License, version 4, | ||
| available at <https://www.php.net/license/>. The PHP License, version 4 | ||
| is the Modified BSD License (BSD-3-Clause). All new works using the PHP | ||
| License should use the Modified BSD License. | ||
|
|
||
|
|
||
| -------------------------------------------------------------------- | ||
|
|
@@ -29,32 +30,32 @@ are met: | |
|
|
||
| 3. The name "PHP" must not be used to endorse or promote products | ||
| derived from this software without prior permission from the | ||
| PHP Group. This does not apply to add-on libraries or tools | ||
| that work in conjunction with PHP. In such a case the PHP | ||
| name may be used to indicate that the product supports PHP. | ||
|
|
||
| 4. The PHP Group may publish revised and/or new versions of the | ||
| license from time to time. Each version will be given a | ||
| distinguishing version number. | ||
| Once covered code has been published under a particular version | ||
| of the license, you may always continue to use it under the | ||
| terms of that version. You may also choose to use such covered | ||
| code under the terms of any subsequent version of the license | ||
| published by the PHP Group. No one other than the PHP Group has | ||
| the right to modify the terms applicable to covered code created | ||
| under this License. | ||
|
|
||
| 5. Redistributions of any form whatsoever must retain the following | ||
| acknowledgment: | ||
| "This product includes PHP, freely available from | ||
| http://www.php.net/". | ||
|
|
||
| 6. Permission to freely distribute and use Zend as an integrated | ||
| part of PHP is granted, under the conditions of version 0.91 | ||
| of the Zend License. | ||
| The license is bundled with the Zend engine, and is available | ||
| at http://www.zend.com/license/0_91.txt, or by contacting | ||
| [email protected]. | ||
|
|
||
|
|
||
|
|
||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| Copyright © The PHP Group and Contributors. | ||
| Copyright © Zend by Perforce. | ||
|
|
||
| Redistribution and use in source and binary forms, with or without | ||
| modification, are permitted provided that the following conditions are met: | ||
|
|
||
| 1. Redistributions of source code must retain the above copyright notice, this | ||
| list of conditions and the following disclaimer. | ||
|
|
||
| 2. Redistributions in binary form must reproduce the above copyright notice, | ||
| this list of conditions and the following disclaimer in the documentation | ||
| and/or other materials provided with the distribution. | ||
|
|
||
| 3. Neither the name of the copyright holder nor the names of its | ||
| contributors may be used to endorse or promote products derived from | ||
| this software without specific prior written permission. | ||
|
|
||
| THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" | ||
| AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | ||
| IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE | ||
| DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE | ||
| FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | ||
| DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR | ||
| SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER | ||
| CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, | ||
| OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE | ||
| OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,65 +1,59 @@ | ||
| <?php | ||
| $_SERVER['BASE_PAGE'] = 'license/distrib-guidelines-code.php'; | ||
| include_once __DIR__ . '/../include/prepend.inc'; | ||
| site_header("Code Distribution Guidelines", ["current" => "help"]); | ||
| ?> | ||
| <h2>PHP Code Distribution Guidelines</h2> | ||
|
|
||
| <p> | ||
| The PHP code can be redistributed in source or binary form provided that | ||
| you respect the terms of the <a href="/license/#bsd-3-clause">license</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 in source | ||
| or binary form. One way of doing this is to put a copy of the license in 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 instead of source code. A text file containing license and | ||
| copyright information is sometimes given the filename "Notice" or "NOTICE," | ||
| and may be referred to as a "notice file." | ||
|
Member
There was a problem hiding this comment. nit: The
Member
Author
There was a problem hiding this comment. Those silly American style guides! 😉 I generally follow the MLA style guide in writing, but the APA style guide and AP stylebook also agree that commas and periods should be placed inside closing quotation marks. However, I'm aware that British English generally places them outside closing quotation marks. Is it the style of php.net to follow the British style? |
||
| </p> | ||
| <p> | ||
| Some files in the PHP codebase have been contributed under other licenses. | ||
| If you want to distribute these files, you must also respect the terms of | ||
| their licenses. Look for the terms in the license/copyright comment block at | ||
| the top of the source file. Sometimes the license terms are included in a | ||
| separate license file in the same directory as the source file. The license | ||
| terms may require that its own license and copyright information be included | ||
| with every distributed copy (including binaries). This is a common requirement, | ||
| which may be satisfied by adding the appropriate license text to a text file | ||
| for distribution purposes, like the notice file suggested above. | ||
| </p> | ||
| <p> | ||
| A single notice file may list all the licenses and copyright information | ||
| applicable to the entire codebase you are distributing. 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 may distribute your own software product derived from PHP, in source or | ||
| binary form, provided that relevant copyright information and license(s) from | ||
| the PHP codebase are distributed in human-readable form with every copy, as | ||
| described above. | ||
| </p> | ||
| <p> | ||
| In accordance with the <a href="/license/#bsd-3-clause">license</a>, you may | ||
| not use the name of any copyright holders or contributors to endorse or | ||
| promote products derived from PHP without specific prior written permission. | ||
| </p> | ||
| <p> | ||
| Please do not use "PHP" in the names of products derived from PHP. This | ||
| creates confusion and implies a relationship between your product and the PHP | ||
| project that may not exist. However, you may indicate that your product works | ||
| with, is compatible with, or is intended for use with PHP. | ||
| </p> | ||
|
|
||
| <?php site_footer(); | ||
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PEAR server might possibly no longer exist by this Friday, and maybe we should just remove this section now? PECL also does no longer accept new packages either.