Differences

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

--- rfc:policy-repository [2023/12/04 17:54] – derick
+++ rfc:policy-repository [2024/01/30 17:36] (current) – derick
@@ Line 3: / Line 3: @@
   * Date: 2023-12-04
   * Author: Derick Rethans <derick@php.net>
-  * Status: Under Discussion
+  * Status: Implemented
   * First Published at: http://wiki.php.net/rfc/policy-repository
@@ Line 12: / Line 12: @@
 ===== 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 the new repository, 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.
@@ Line 34: / Line 36: @@
 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.
-===== Open Issues =====
+===== Voting Choices =====
-  * Should the historical information in "release process" be moved out of release-process to a dedicated file?
-  * Are there any policy RFCs or related documents that I missed and also should be moved?
-===== Proposed Voting Choices =====
-Do we want all the policies in one place in a Git repository?
+/3rds majority required. Voting runs until January 22nd, 2024, 08:00 UTC.
-/3rds majority required.
+<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 =====

Differences

Page Tools