Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121982
Date: Mon, 11 Dec 2023 09:31:38 +0000 (GMT)
To: Larry Garfield <larry@garfieldtech.com>
cc: php internals <internals@lists.php.net>
In-Reply-To: <1ad1b73d-3c67-46d5-b203-dbf9c637d836@app.fastmail.com>
Message-ID: <8c1fdc96-86ba-789a-9127-1dfad1032a80@php.net>
References: <21ed7837-3cd4-98e5-8ec7-c97b0e2a2146@php.net> <1ad1b73d-3c67-46d5-b203-dbf9c637d836@app.fastmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1738914721-1702287099=:6327"
Subject: Re: [PHP-DEV] [RFC] Collecting All Policies Into One Repository
From: derick@php.net (Derick Rethans)

--8323329-1738914721-1702287099=:6327
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Tue, 5 Dec 2023, Larry Garfield wrote:

> 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 we=
=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 lives=
=20
> > easier by having one place where all these documents are located.
> >
> > Hence I have created a (beta) repository and collected that information=
:
> > 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 greatful=
=20
> > if you could have a look at the RFC, the collated documents, and let me=
=20
> > know whether I missed anything, or whether you are missing something we=
=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.
>=20
> Thank you for this, Derick!  I very much support this initiative and=20
> look forward to it.
>=20
> > Should the historical information in =E2=80=9Crelease process=E2=80=9D =
be moved out=20
> > of release-process to a dedicated file?
>=20
> I would say yes.  The ideal structure of the document (once edited=20
> down) would be a snapshot of "how things work right now."  Historical=20
> alternatives should either be just git history or a separate=20
> non-normaitive set of files.

Fair enough. I also tended to go that way.

> I would also ask, does this mean future changes to process would be=20
> submitted and reviewed as a PR against this repo, with the RFC for it=20
> being mostly a placeholder for "vote on this PR", with explanation? =20
> I would assume so, but it would be good to make that explicit.

The RFC currently has "RFCs to add or amend to policy would then target=20
additions or modification of the documents in this repository, instead=20
of having them just as RFC text." so that was my intention. I've updated=20
the text to make this a little clearer though.

cheers,
Derick

--=20
https://derickrethans.nl | https://xdebug.org | https://dram.io

Author of Xdebug. Like it? Consider supporting me: https://xdebug.org/suppo=
rt
Host of PHP Internals News: https://phpinternals.news

mastodon: @derickr@phpc.social @xdebug@phpc.social
twitter: @derickr and @xdebug
--8323329-1738914721-1702287099=:6327--