Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:129166
Feedback-ID: ifab94697:Fastmail
Precedence: list
MIME-Version: 1.0
Date: Sun, 09 Nov 2025 16:15:59 +0100
To: internals@lists.php.net
Message-ID: <e4bfc289-8dd0-4e04-a3f2-6eef4a7701d9@app.fastmail.com>
In-Reply-To: <a273ffad38634db9606d3c529ad9e544@bastelstu.be>
References: <a273ffad38634db9606d3c529ad9e544@bastelstu.be>
Subject: Re: [PHP-DEV] [VOTE] Clarify discussion and voting period rules
Content-Type: multipart/alternative;
 boundary=5212481f831e4e9c9f7feb922da66758
From: rob@bottled.codes ("Rob Landers")

--5212481f831e4e9c9f7feb922da66758
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On Thu, Nov 6, 2025, at 10:02, Tim D=C3=BCsterhus wrote:
> Hi
>=20
> I just opened voting on the "Clarify discussion and voting period rule=
s"=20
> RFC. Please find the following resources:
>=20
> - RFC Text: https://wiki.php.net/rfc/rfc_discussion_and_vote
> - Implementation PR: https://github.com/php/policies/pull/23
> - Discussion Thread: https://news-web.php.net/php.internals/128594
>=20
> The RFC contains a single primary vote requiring a 2/3 majority. Votin=
g=20
> will close 2025-11-20 09:30:00 UTC.
>=20
> ----------------
>=20
> As during the discussion, I'd like to explicitly spell out some of the=20
> things that I took into account.
>=20
> It is now 2025-11-06 08:54 UTC (and will be a little later when I=20
> actually hit send).
>=20
> - The last change to the RFC was a Major Change on 2025-10-23 07:37:43=20
> UTC: https://news-web.php.net/php.internals/128921
> - The Intent to Vote announcement was sent on 2025-11-04 08:45:24 UTC:=20
> https://news-web.php.net/php.internals/129063
> - There was no further feedback to take into account after the last=20
> Major Change (and thus neither after the Intent to Vote).
>=20
> A little more than 14 days have passed since the last major change. A=20
> little more than 2 days have passed since the Intent to Vote=20
> announcement. Both is strictly within the proposed rules. The RFC was=20
> not inactive, since the last email was my Major Change announcement,=20
> which happened less than 42 days ago.
>=20
> This email contains all the necessary information, namely the link to=20
> the RFC text, Discussion Thread, a list of the number of votes to cast=20
> and the end date. I also included a link to the implementation, since=20
> this is the main relevant thing for a policy RFC. Voting will close a=20
> little over 14 days from now. I have specified some buffer room to=20
> account for =E2=80=9Cmail delivery delay=E2=80=9D.
>=20
> I will make sure to add a link to the archives of the voting thread as=20
> soon as I see it appear in the archives.
>=20
> Best regards
> Tim D=C3=BCsterhus

May I ask, as a follow-up task, to add some kind of copy/pastable templa=
tes to the rfc:howto (https://wiki.php.net/rfc/howto)? For example, what=
 information needs to be sent in major/minor/editorial changes? Do you n=
eed to declare which type of change it is and its effect, or is it simpl=
y assumed everyone knows?

I'm just asking because the proceedure isn't clear (I was trying to foll=
ow it):

> _Major and minor changes MUST be announced in the official discussion =
thread, either in a dedicated email summarizing a list of changes or in =
a reply to another email that clearly indicates that changes to the RFC =
text have been made in response to that email._

Does this mean "A major change has been made" as in literally announcing=
 the type of change, or just that the change must be announced?

=E2=80=94 Rob
--5212481f831e4e9c9f7feb922da66758
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title></head><body><div>On Thu, Nov =
6, 2025, at 10:02, Tim D=C3=BCsterhus wrote:</div><blockquote type=3D"ci=
te" id=3D"qt" style=3D""><div>Hi</div><div><br></div><div>I just opened =
voting on the "Clarify discussion and voting period rules"&nbsp;</div><d=
iv>RFC. Please find the following resources:</div><div><br></div><div>- =
RFC Text:&nbsp;<a href=3D"https://wiki.php.net/rfc/rfc_discussion_and_vo=
te">https://wiki.php.net/rfc/rfc_discussion_and_vote</a></div><div>- Imp=
lementation PR:&nbsp;<a href=3D"https://github.com/php/policies/pull/23"=
>https://github.com/php/policies/pull/23</a></div><div>- Discussion Thre=
ad:&nbsp;<a href=3D"https://news-web.php.net/php.internals/128594">https=
://news-web.php.net/php.internals/128594</a></div><div><br></div><div>Th=
e RFC contains a single primary vote requiring a 2/3 majority. Voting&nb=
sp;</div><div>will close 2025-11-20 09:30:00 UTC.</div><div><br></div><d=
iv>----------------</div><div><br></div><div>As during the discussion, I=
'd like to explicitly spell out some of the&nbsp;</div><div>things that =
I took into account.</div><div><br></div><div>It is now 2025-11-06 08:54=
 UTC (and will be a little later when I&nbsp;</div><div>actually hit sen=
d).</div><div><br></div><div>- The last change to the RFC was a Major Ch=
ange on 2025-10-23 07:37:43&nbsp;</div><div>UTC:&nbsp;<a href=3D"https:/=
/news-web.php.net/php.internals/128921">https://news-web.php.net/php.int=
ernals/128921</a></div><div>- The Intent to Vote announcement was sent o=
n 2025-11-04 08:45:24 UTC:&nbsp;</div><div><a href=3D"https://news-web.p=
hp.net/php.internals/129063">https://news-web.php.net/php.internals/1290=
63</a></div><div>- There was no further feedback to take into account af=
ter the last&nbsp;</div><div>Major Change (and thus neither after the In=
tent to Vote).</div><div><br></div><div>A little more than 14 days have =
passed since the last major change. A&nbsp;</div><div>little more than 2=
 days have passed since the Intent to Vote&nbsp;</div><div>announcement.=
 Both is strictly within the proposed rules. The RFC was&nbsp;</div><div=
>not inactive, since the last email was my Major Change announcement,&nb=
sp;</div><div>which happened less than 42 days ago.</div><div><br></div>=
<div>This email contains all the necessary information, namely the link =
to&nbsp;</div><div>the RFC text, Discussion Thread, a list of the number=
 of votes to cast&nbsp;</div><div>and the end date. I also included a li=
nk to the implementation, since&nbsp;</div><div>this is the main relevan=
t thing for a policy RFC. Voting will close a&nbsp;</div><div>little ove=
r 14 days from now. I have specified some buffer room to&nbsp;</div><div=
>account for =E2=80=9Cmail delivery delay=E2=80=9D.</div><div><br></div>=
<div>I will make sure to add a link to the archives of the voting thread=
 as&nbsp;</div><div>soon as I see it appear in the archives.</div><div><=
br></div><div>Best regards</div><div>Tim D=C3=BCsterhus</div></blockquot=
e><div><br></div><div>May I ask, as a follow-up task, to add some kind o=
f copy/pastable templates to the rfc:howto (<a href=3D"https://wiki.php.=
net/rfc/howto">https://wiki.php.net/rfc/howto</a>)? For example, what in=
formation needs to be sent in major/minor/editorial changes? Do you need=
 to declare which type of change it is and its effect, or is it simply a=
ssumed everyone knows?</div><div><br></div><div>I'm just asking because =
the proceedure isn't clear (I was trying to follow it):</div><div><br></=
div><blockquote type=3D"cite"><div><span class=3D"color" style=3D"color:=
rgb(31, 35, 40);"><u>Major and minor changes MUST be announced in the of=
ficial discussion thread, either in a dedicated email summarizing a list=
 of changes or in a reply to another email that clearly indicates that c=
hanges to the RFC text have been made in response to that email.</u></sp=
an></div></blockquote><div><br></div><div>Does this mean "A major change=
 has been made" as in literally announcing the type of change, or just t=
hat the change must be announced?</div><div><br></div><div id=3D"sig1212=
29152">=E2=80=94 Rob</div></body></html>
--5212481f831e4e9c9f7feb922da66758--