rfc:third-party-code

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:third-party-code [2024/10/06 02:25] – Spelling crellrfc:third-party-code [2024/11/23 19:23] (current) – Close the vote crell
Line 3: Line 3:
   * Date: 2024-10-02   * Date: 2024-10-02
   * Author: Larry Garfield (larry@garfieldtech.com)   * Author: Larry Garfield (larry@garfieldtech.com)
-  * Status: Discussion+  * Status: Approved
   * First Published at: http://wiki.php.net/rfc/third-party-code   * First Published at: http://wiki.php.net/rfc/third-party-code
  
Line 15: Line 15:
 ===== Proposal ===== ===== Proposal =====
  
-==== Definitions ==== 
  
 +The specific policy to adopt is documented precisely in this Pull Request: https://github.com/php/policies/pull/10
  
-**PHP tooling** refers to the code behind the PHP.net website, the documentation generator project PhD, the PHP wiki, and other similar systems.  In general, "PHP code run by PHP.net." +In the interest of avoiding confusion by having multiple versions of it, this RFC will not repeat what is listed there.
- +
-**Documentation** refers to objective information about PHP, the PHP language, the PHP standard library, and PHP ecosystem hosted on PHP.net.  This may include reference material, tutorials, FAQs, and similar. +
- +
-**Marketing material** refers to content on PHP.net or similar sites intended to promote or evangelize PHP the language or ecosystem. +
- +
-**Libraries** refers to existing third party code packages or tools, either C extensions or PHP code, maintained by someone other than the PHP Internals team.  It may also refer to non-profit PHP ecosystem organizations, such as the PHP Foundation or PHP-FIG. +
- +
-**Approved license** refers to a license [[https://www.gnu.org/licenses/license-list.en.html|approved by the Free Software Foundation]] as Free Software, and that is inbound compatible with GPLv3. +
- +
-==== PHP tooling ==== +
- +
-PHP tooling MAY make use third party libraries, provided that the library meets all of the "Inclusion" criteria, and does not meet any of the "Exclusion" criteria. +
- +
-Inclusion criteria: +
- +
-  - The library must have a stable >= 1.0 release, and have had one for at least a year.  (This is to ensure it has longevity.) +
-  - The library provides targeted, necessary functionality. +
-  - The library is a recognized de facto standard, or one of a small number of de facto standards, in its problem space. +
-  - The library is available under an Approved License. +
- +
-Exclusion criteria: +
- +
-  - The library is a "full" framework or application +
-  - The library is not available under an Approved License. +
-  - The library has shown no meaningful activity for one year prior to its first inclusion. +
- +
-PHP tooling maintainers MAY use their judgement to determine if a library meets the above criteria, but SHOULD be conservative in their interpretation of whether or not a library satisfies the necessary criteria. +
- +
-==== PHP documentation ==== +
- +
-Documentation MAY reference and link to third party libraries, provided that the library meets all of the "Inclusion" criteria, and does not meet any of the "Exclusion" criteria.  Additionally, the language used to refer to the library must also follow the criteria below. +
- +
-Inclusion criteria: +
- +
-  - The library must have a stable >= 1.0 release, and have had one for at least a year. +
-  - The library provides a use that is commonly needed by many types of projects, making it of **broad interest** to the PHP ecosystem. +
-  - The library is a recognized de facto standard, or one of a small number of de facto standards, in its problem space.  If there are a small number of de facto standard libraries, then all should be listed and given equal weight. +
-  - The library is available under an Approved License. +
-  - The language used to describe the library does not imply that the PHP Project is involved in or specifically recommends the library over some other. +
- +
-Exclusion criteria: +
- +
-  - The library is one of many (more than ~4) viable options in its problem space, even if it is the most common of those many options. +
-  - The library is a "full" application or framework. +
-  - The library is not available under an Approved License. +
-  - The library has shown no meaningful activity for one year prior to its first mention. +
-  - The library is not of broad interest to the PHP ecosystem. +
- +
-PHP documentation maintainers MAY use their judgement to determine if a library meets the above criteria, but SHOULD be conservative in their interpretation of whether or not a library satisfies the necessary criteria. +
- +
-==== Marketing material ==== +
- +
-Marketing material MAY reference and link to third party libraries, provided that the library meets all of the "Inclusion" criteria, and does not meet any of the "Exclusion" criteria.  Additionally, the language used to refer to the library must also follow the criteria below. +
- +
-Inclusion criteria: +
- +
-  - The library must have a stable >= 1.0 release, and have had one for at least a year. +
-  - The library provides a use that is commonly needed by many types of projects, making it of **significant interest** to the PHP ecosystem. +
-  - The library is a recognized de facto standard, or one of a small number of de facto standards, in its problem space.  If there are a small number of de facto standard libraries, then all should be listed and given equal weight. +
-  - The library MAY be a full application or framework, provided its mention clearly does not specifically endorse the library.  If many options exist in a space that bears mention, the most common should be given equal exposure. +
-  - The library is available under an Approved License. +
-  - The language used to describe the library does not imply that the PHP Project is involved in or specifically recommends the library over some other. +
- +
-Exclusion criteria: +
- +
-  - The library is not available under an Approved License. +
-  - The library has shown no meaningful activity for one year prior to its first mention. +
-  - The library is not of broad interest to the PHP ecosystem. +
- +
-PHP marketing material maintainers MAY use their judgement to determine if a library meets the above criteria, but SHOULD be conservative in their interpretation of whether or not a library satisfies the necessary criteria. +
- +
-==== Conflict resolution ==== +
- +
-Should there be a reasonable dispute as to whether a given library satisfies the criteria above, an RFC may be posted to explicitly approve the library for one or more of the above cases.  The RFC MUST have a 2/3 vote threshold to approve the library.  If the library is rejected, it may be revisited after six months, like any other RFC. +
- +
-==== Initially approved libraries ==== +
- +
-The following packages are explicitly approved for use by this RFC, as they meet all of the criteria above. +
- +
-  * Composer +
-  * PHPUnit +
-  * Xdebug +
-  * PHPStan +
-  * Psalm +
-  * Any library or PSR published by the PHP-FIG +
- +
-Additionally, for historical reasons, Dokuwiki is explicitly approved for use despite it being a "full" application. +
  
 ===== Discussion ===== ===== Discussion =====
Line 122: Line 34:
  
   - It likely would not come up, but are we OK with using AGPL code in PHP tooling?  It's not like any of our code is inaccessible.   - It likely would not come up, but are we OK with using AGPL code in PHP tooling?  It's not like any of our code is inaccessible.
-  -  
  
 ===== Proposed Voting Choices ===== ===== Proposed Voting Choices =====
Line 128: Line 39:
 Simple 2/3 majority vote. Simple 2/3 majority vote.
  
 +<doodle title="Accept this policy proposal?" auth="crell" voteType="single" closed="true">
 +   * Yes
 +   * No
 +</doodle>
  
 ===== References ===== ===== References =====
rfc/third-party-code.1728181548.txt.gz · Last modified: 2024/10/06 02:25 by crell

Page Tools