psr.md

PHP Specification Requests (PSRs)

Having a settled specification allows those who choose to adopt these recommendations to have a solid foundation from which to build. The intention of this bylaw is to add guidelines around how to address changes to our recommendations.

This document is based (in spirit) on the work of the RSS Advisory Board and the patterns established by the IETF.

1. All voting in conjunction with PSRs is to be carried out in accordance with the voting protocol.
2. Anyone can propose a draft PSR for discussion, but only voting members can call for a vote to adopt a PSR in final form.
3. PSRs are not binding to any person, organisation or entity. They are recommendations only.
4. A PSR passed by vote adopts the next available subsequent integer for its identifier (for example, PSR-0, PSR-1, PSR-2, PSR-3, ..., PSR-n).
5. If a PSR is passed by vote, it cannot be changed except to make minor changes to the text the purpose of clarity. Any modifications what would result in a change to the meaning of the PSR requires that a new PSR be considered.
6. A new PSR may reference, require or expand on one or more previously accepted PSRs.
7. A new PSR may supercede an exsisting PSR. In this case, both PSR are still considered "accepted", but the superceded PSR is no longer considered "recommended". The superceded PSR will be modified to note which PSR superceded it.