Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121932
Feedback-ID: i8414410d:Fastmail
User-Agent: Cyrus-JMAP/3.9.0-alpha0-1178-geeaf0069a7-fm-20231114.001-geeaf0069
MIME-Version: 1.0
Message-ID: <1ad1b73d-3c67-46d5-b203-dbf9c637d836@app.fastmail.com>
In-Reply-To: <21ed7837-3cd4-98e5-8ec7-c97b0e2a2146@php.net>
References: <21ed7837-3cd4-98e5-8ec7-c97b0e2a2146@php.net>
Date: Tue, 05 Dec 2023 17:26:59 +0000
To: "php internals" <internals@lists.php.net>
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Collecting All Policies Into One Repository
From: larry@garfieldtech.com ("Larry Garfield")

On Tue, Dec 5, 2023, at 11:06 AM, Derick Rethans wrote:
> Hi!
>
> A while ago I started looking into all the documents (RFCs etc) that w=
e=20
> have that relate to all sort of policies. From RFCs, to who can vote,=20
> naming, and security classifications as a result of a discussion with=20
> the foundations folk.
>
> Now there was another small confusion during a recent vote, we came up=20
> with the idea to actually go forwards with this, and make all our live=
s=20
> easier by having one place where all these documents are located.
>
> Hence I have created a (beta) repository and collected that informatio=
n:
> https://github.com/php/policies
>
> The contents are copied verbitim from RFCs, without any editing. Some=20
> RFCs made it into a single file as IMO they belonged together.
>
> I have also created an RFC to establish this location, as changing=20
> policies and RFCs require an RFC:
> https://wiki.php.net/rfc/policy-repository
>
> The contents are probably not exhaustive, and it is entirely possible=20
> that it does not include all information. I would therefore be greatfu=
l=20
> if you could have a look at the RFC, the collated documents, and let m=
e=20
> know whether I missed anything, or whether you are missing something w=
e=20
> might not even have written down yet.
>
> I am hoping that the discussion to establish this repository is=20
> straightforwards. Further steps will include: editing the documents so=20
> that they read as documents, and not copy-pasted content with RFC=20
> language, and including our existing coding standards.
>
>
> cheers,
> Derick

Thank you for this, Derick!  I very much support this initiative and loo=
k forward to it.

> Should the historical information in =E2=80=9Crelease process=E2=80=9D=
 be moved out of release-process to a dedicated file?

I would say yes.  The ideal structure of the document (once edited down)=
 would be a snapshot of "how things work right now."  Historical alterna=
tives should either be just git history or a separate non-normaitive set=
 of files.

I would also ask, does this mean future changes to process would be subm=
itted and reviewed as a PR against this repo, with the RFC for it being =
mostly a placeholder for "vote on this PR", with explanation?  I would a=
ssume so, but it would be good to make that explicit.

--Larry Garfield