rfc:policy-repository
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| rfc:policy-repository [2023/12/04 17:41] – derick | rfc:policy-repository [2024/01/30 17:36] (current) – derick | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| * Date: 2023-12-04 | * Date: 2023-12-04 | ||
| * Author: Derick Rethans < | * Author: Derick Rethans < | ||
| - | * Status: | + | * Status: |
| * First Published at: http:// | * First Published at: http:// | ||
| 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:// | + | Similarly, the canonical security classification will move from https:// |
| + | |||
| + | 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. | Changes to the policy repository should only be made through a new RFC, unless it is for fixing spelling mistakes or grammar. | ||
| Line 21: | Line 23: | ||
| 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. | ||
| - | |||
| - | ===== Next Steps ===== | ||
| - | |||
| - | 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. | ||
| ===== Backwards Compatibility Breaks ===== | ===== Backwards Compatibility Breaks ===== | ||
| Line 30: | Line 28: | ||
| None in code, but [[rfc: | None in code, but [[rfc: | ||
| - | ===== Open Issues | + | ===== Future Scope ===== |
| - | * Should the historical information in " | + | 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. |
| + | |||
| + | Integrate https:// | ||
| + | |||
| + | Both of these will be implemented through a separate PR to the policy repository. After comment integration, | ||
| + | |||
| + | ===== Voting Choices ===== | ||
| - | ===== Proposed | + | 2/3rds majority required. |
| - | Do we want all the policies in one place in a Git repository? | + | <doodle title=" |
| - | 2/3rds majority required. | + | * yes |
| + | * no | ||
| + | </doodle> | ||
| ===== Patches and Tests ===== | ===== Patches and Tests ===== | ||
| Line 71: | Line 77: | ||
| ===== References ===== | ===== References ===== | ||
| + | |||
| Links to external references, discussions or RFCs | Links to external references, discussions or RFCs | ||
rfc/policy-repository.1701711663.txt.gz · Last modified: 2023/12/04 17:41 by derick