Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122012
MIME-Version: 1.0
References: <21ed7837-3cd4-98e5-8ec7-c97b0e2a2146@php.net> <e95544b3-e799-9eb4-510a-1252300d7bb0@php.net>
In-Reply-To: <e95544b3-e799-9eb4-510a-1252300d7bb0@php.net>
Date: Mon, 18 Dec 2023 22:39:43 +0100
Message-ID: <CAPTD5yH44d-Y1B6HFxVGi70GeARGPRT9VNgJSF_Tg44ArNYJFA@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002da4a8060ccf97fc"
Subject: Re: [PHP-DEV] [RFC] Collecting All Policies Into One Repository
From: jorg.sowa@gmail.com (Jorg Sowa)

--0000000000002da4a8060ccf97fc
Content-Type: text/plain; charset="UTF-8"

Hey Derick,
Thank you for proposing this change. As a author of comment you mentioned I
believe this will help new maintainers to get all the information about the
RFC process from one place.

I have one question regarding the future changes. Do you see it would be
possible to make amendment to the accepted RFCs by the Pull Requests (and
formal RFC approach) making changes the existing policies or adding the new
policy replacing the old ones? In other words, this repository would server
as the collection of all ever accepted policies or it would contain the
unified policy documentation?

I'm asking because I saw the directory `archive`, and it contains expired
RFC. I don't think this would help new contributors. For the history
purposes it would be nice to have it in the git history, but for the PHP
development process is not relevant anymore and is little overhead.

Kind regards,
Jorg

--0000000000002da4a8060ccf97fc--