Re: Guidelines for RFC post feature-freeze
| From: | Ben Ramsey | Date: | Wed, 25 Aug 2021 19:58:40 +0000 |
| Subject: | Re: Guidelines for RFC post feature-freeze | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115832@lists.php.net to get a copy of this message | ||
Deleu wrote on 8/25/21 14:35:
> On Wed, Aug 25, 2021 at 8:52 PM Ben Ramsey <ramsey@php.net> wrote:
>> I would be in favor of an "informational" RFC rather than a "policy"
>> RFC. An informational RFC can define terms, such as "refinement RFC" and
>> "feature freeze," without burdening the project with more policy overhead.
>
> Do we have the concept of an informal RFC? As far as I could see there are
> language changes targeting a specific version and policy and processes [1].
> I could not find another type of RFC to be proposed.
I meant "informational" not "informal." I don't know that we have that
concept in any of the PHP RFCs, but I know that IETF RFCs, Python PEPs,
and others have the concept of informational documents that do not
prescribe process, policy, or recommendations.
Cheers,
Ben
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc