Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:110559
MIME-Version: 1.0
References: <BY5PR15MB3729227C6536FA3D0EBE2335929C0@BY5PR15MB3729.namprd15.prod.outlook.com>
 <4b921c5f-db2b-1e2a-ed2a-1add5c9b6663@gmail.com> <20200615174645.GP14030@phcomp.co.uk>
 <CANS-=peH1x-1LAr6pxp4bvToVB8hQ7GT_2xynsDmp1W7bDR7ag@mail.gmail.com>
 <CADK1yXJEV_Kuxhr6LqLd+9sXkaboXH5cLW3NnJBaa7=Op72ZXg@mail.gmail.com>
 <CAJW__o12mwJ68=yKQzNTAGf+ViFV-=TMhhtRPw9weP1wJ+at5g@mail.gmail.com>
 <CADK1yXLhKubQXvQrt4-zgS4BftyAyXeMHvYm+=qsH+UB8os3+Q@mail.gmail.com>
 <CAJW__o2+4r3BZ9_ieCAFjo5KA5Pde7seJNJ467ntkFR+kBJ1vA@mail.gmail.com>
 <BY5PR15MB372932B9BCA1637E74D427CB929C0@BY5PR15MB3729.namprd15.prod.outlook.com>
 <CAJW__o0hO=94K76eVkaDYyQOM2qA5am2u=_xwrs0sQdysK4O3A@mail.gmail.com>
 <BY5PR15MB3729D75E6FC997BC50CCEC42929D0@BY5PR15MB3729.namprd15.prod.outlook.com>
 <CAJW__o3uEjRbFk8ta6ALV3ay7dZE8y_K7742QNxVNOM8YcgHJg@mail.gmail.com> <BY5PR15MB37291D4CC1700937E5EC9CCE929D0@BY5PR15MB3729.namprd15.prod.outlook.com>
In-Reply-To: <BY5PR15MB37291D4CC1700937E5EC9CCE929D0@BY5PR15MB3729.namprd15.prod.outlook.com>
Date: Tue, 16 Jun 2020 03:43:57 +0300
Message-ID: <CAJW__o0s+929EXCuOO9Xjkv7+a3ROKYd7VMsa0HuV8ixDJ4GJQ@mail.gmail.com>
To: Daniel Rodrigues Lima <danielrodrigues-ti@hotmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] About the use of the terms master/slave and blacklist,
 proposal to replace.
From: kalle@php.net (Kalle Sommer Nielsen)

Den tir. 16. jun. 2020 kl. 03.30 skrev Daniel Rodrigues Lima
<danielrodrigues-ti@hotmail.com>:
>
> How is it in the process of creating an RFC...
>
> "1. Email internals@lists.php.net to measure reaction to your intended pr=
oposal. "

That is the thing, do you intend to provide no upgrade path for your
proposal? You don't mention what version of PHP you are even
targeting, or am I to understand that your proposal has none? Does it
mean that these changes goes into the next releases of 7.3.x, 7.4.x
and 8.0.0? Is it only 8.0.0? etc. these are all basic questions that
any other RFC proposal answers when it is brought to the mailing list.
You can search the mail archives to get some examples of how it
usually is laid out.

To clarify, you sent a discussion topic. There is nothing about any
RFC intention in your first post (or subject line that most others
do). Before a proposal can begin to be understood it has to be fleshed
out, you need to have a solid argument for, upgrade paths, solutions
to potential problems, open quests (you got a fair few from this
thread alone) and so on, there is plenty of RFCs on the wiki you can
use as a base example for yours. I think the confusion here is the
misunderstanding of what the term "proposal" mean in the copied list
point you sent me above. A proposal means the actual first version of
the RFC, a soft version if you will.

The complete list point is:
Email internals@lists.php.net to measure reaction to your intended
proposal. State who would implement the feature, or whether the
proposal is only a =E2=80=9Cconcept=E2=80=9D. Proceed with an RFC if feedba=
ck is not
negative or if a detailed RFC will clarify the proposal. Mail list
subscription is at http://php.net/mailing-lists.php. (Reminder: always
"bottom post" your replies. Never =E2=80=9Ctop post=E2=80=9D.)

Your initial post does not state who should implement this feature
either, or if this is only a concept.

--=20
regards,

Kalle Sommer Nielsen
kalle@php.net