Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113628
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
In-Reply-To: <e46ee3b5-bfef-de67-adc9-01f5605c223c@gmx.de>
Date: Fri, 19 Mar 2021 14:51:40 -0400
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <D73364D4-76A6-4126-889A-3C54E3648B35@newclarity.net>
References: <CAF+90c-CEZycXeigN9zqsFyZGMxDWVT_YU6h_OMrvORE_qLk3A@mail.gmail.com>
 <341E78A4-B42C-4C4C-B0C5-A190187D6920@newclarity.net>
 <e46ee3b5-bfef-de67-adc9-01f5605c223c@gmx.de>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Subject: Re: [PHP-DEV] [RFC] Namespaced in bundled extensions
From: mike@newclarity.net (Mike Schinkel)

> On Mar 19, 2021, at 2:44 PM, Christoph M. Becker <cmbecker69@gmx.de> =
wrote:
>=20
> On 19.03.2021 at 19:28, Mike Schinkel wrote:
>=20
>> The registration process would be as simple as submitting a PR that =
includes the requested namespace added to both the README.md and the =
namespaces.json file along with a link for more information.
>>=20
>> There would not be any approval process per se other than merging the =
PR, and there would not be any "owner" of the registration per se as =
registration would merely be a stake in the ground to recommend others =
not use that same namespace.
>=20
> I wonder how long it would take for somebody to submit a PR which
> registers several millions of arbitrary namespaces.

A good bit longer than it would take to deny the PR and not merge it, =
I'm sure.

So I guess to be explicit, one namespace per PR.

-Mike