rfc:policy-repository

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:policy-repository [2023/12/04 17:23] – fix title derickrfc:policy-repository [2024/01/30 17:36] (current) – derick
Line 3: Line 3:
   * Date: 2023-12-04   * Date: 2023-12-04
   * Author: Derick Rethans <derick@php.net>   * Author: Derick Rethans <derick@php.net>
-  * Status: Under Discussion+  * Status: Implemented
   * First Published at: http://wiki.php.net/rfc/policy-repository   * First Published at: http://wiki.php.net/rfc/policy-repository
  
Line 12: Line 12:
 ===== Proposal ===== ===== Proposal =====
  
-This proposal suggests to set up a new Git repository to collect all the policies that we have. RFCs to add or amend to policy would then target additions or modification of the documents in this repository, instead of having them just as RFC text.+This proposal suggests to set up a new Git repository to collect all the policies that we have.
  
-Similarly, the canonical security classification will move from https://github.com/php/php-src/blob/master/SECURITY.md to https://github.com/php/policies/blob/main/security-classification.rst, with the former explaining how to file security issues only instead.+Similarly, the canonical security classification will move from https://github.com/php/php-src/blob/master/SECURITY.md to the new repository, with the former only explaining how to file security issues instead. 
 + 
 +To amend a policy a Pull Request must be raised against this repository. An RFC with considerations and arguments, as we have for all changes, are then created to approve the Pull Request. The text of the policy change rests solely in the Pull Request, with the RFC providing explanatory notes. 
 + 
 +Changes to the policy repository should only be made through a new RFC, unless it is for fixing spelling mistakes or grammar.
  
 ===== Proposed PHP Version(s) ===== ===== Proposed PHP Version(s) =====
Line 20: Line 24:
 As this is not for a specific PHP version, it is not targeting one either. As this is not for a specific PHP version, it is not targeting one either.
  
 +===== Backwards Compatibility Breaks =====
  
-===== Open Issues =====+None in code, but [[rfc:release_cycle_update|PHP RFC: Release cycle update]] needs to be partially redone to work with this new policy repository.
  
-- Should the historical information be moved out of release-process to a dedicated file?+===== Future Scope =====
  
-===== Proposed Voting Choices =====+Once (and if) this RFC is accepted, a first new step would be to rephrase the text so that it reads like a policy document, instead of an RFC. The wording is currently exactly as in the used RFCs, without modification.
  
-Do we want all the policies in one place in a Git repository? +Integrate https://github.com/php/php-src/blob/master/CODING_STANDARDS.md into the coding-standards policy file. 
-2/3rds majority required.+ 
 +Both of these will be implemented through a separate PR to the policy repository. After comment integration, an RFC will be created to confirm these changes. 
 + 
 +===== Voting Choices ===== 
 + 
 +2/3rds majority required. Voting runs until January 22nd, 2024, 08:00 UTC. 
 + 
 +<doodle title="Do we want all the policies in one place in a Git repository?" auth="derick" voteType="single" closed="true" closeon="2024-01-22T08:00:00Z"> 
 +   * yes 
 +   * no 
 +</doodle>
  
 ===== Patches and Tests ===== ===== Patches and Tests =====
Line 38: Line 53:
 Releases and Security Releases and Security
  
-- Release Process: https://wiki.php.net/rfc/releaseprocess +  * Release Process: https://wiki.php.net/rfc/releaseprocess 
-- Security Issue Classification: https://wiki.php.net/rfc/security-classification+  * Security Issue Classification: https://wiki.php.net/rfc/security-classification
          
 RFC Votes RFC Votes
  
-- Voting on PHP features: https://wiki.php.net/rfc/voting +  * Voting on PHP features: https://wiki.php.net/rfc/voting 
-- Abolish Short Votes: https://wiki.php.net/rfc/abolish-short-votes +  * Abolish Short Votes: https://wiki.php.net/rfc/abolish-short-votes 
-- Abolish Narrow Margins: https://wiki.php.net/rfc/abolish-narrow-margins+  * Abolish Narrow Margins: https://wiki.php.net/rfc/abolish-narrow-margins
          
 Support Timelines Support Timelines
  
-- PHP 5 Support Timeline: https://wiki.php.net/rfc/php56timeline +  * PHP 5 Support Timeline: https://wiki.php.net/rfc/php56timeline 
-- Define PHP 5.3 End of Life: https://wiki.php.net/rfc/php53eol +  * Define PHP 5.3 End of Life: https://wiki.php.net/rfc/php53eol 
-- Name of Next Release of PHP: https://wiki.php.net/rfc/php6 +  * Name of Next Release of PHP: https://wiki.php.net/rfc/php6 
-- PHP 7.0 timeline: https://wiki.php.net/rfc/php7timeline +  * PHP 7.0 timeline: https://wiki.php.net/rfc/php7timeline 
-- Cleaning Up Unmaintained Extensions: https://wiki.php.net/rfc/umaintained_extensions+  * Cleaning Up Unmaintained Extensions: https://wiki.php.net/rfc/umaintained_extensions
          
 Naming Things Naming Things
  
-- Namespaces in bundled PHP extensions: https://wiki.php.net/rfc/namespaces_in_bundled_extensions +  * Namespaces in bundled PHP extensions: https://wiki.php.net/rfc/namespaces_in_bundled_extensions 
-- Class Naming: https://wiki.php.net/rfc/class-naming+  * Class Naming: https://wiki.php.net/rfc/class-naming
  
  
 ===== References ===== ===== References =====
 +
 Links to external references, discussions or RFCs Links to external references, discussions or RFCs
  
rfc/policy-repository.1701710637.txt.gz · Last modified: 2023/12/04 17:23 by derick

Page Tools