Re: [PHP-DEV] Re: [RFC] [VOTE] Literal Scalar Types
Juris Evertovskis <[email protected]> Sun, 26 Jul 2026 21:15:55 +0300
| Newsgroups | gmane.comp.php.devel |
|---|---|
| Organization | SIA "Glaive.pro" |
| Message-ID | <[email protected]> |
--=_93d70e760fd37980657886d73f8f5dce Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On 2026-07-23 08:44, Seifeddine Gmati wrote: > Hello internals, > > I am retracting this vote: I opened it prematurely, in violation of the > voting prerequisites in the Feature Proposals policy. I did not post an > Intent to Vote message at least two days in advance, and today's 1.0 > update to the RFC text is a Minor change announcement, which starts a > seven-day Cooldown Period during which no vote may be called. Hey all, I'm a frequent reader/follower of this list as well as an occasional participant and a one-time RFC-attempter. As such I never felt like I'm "internal enough" to comment on the process. But since no one else seems to be bothered by it, I would like to bring this up after all... The "new" process (https://wiki.php.net/rfc/rfc_discussion_and_vote) feels very discouraging to me. All the mandatory cooldowns, cooldown resets on minor changes, announcements to vote, cooldown resets on inactive discussions appears to me like bureaucratic hoops that people have to jump through. The process was hard and daunting enough before this. I understand the extremes that the rules are preventing like someone suddenly launching a vote for an RFC that has been dormant for 20 months. But in practice many of the mandatory cooldown resets, activity bumps and other formal messages appear like only serving the process. This case in particular feels very disappointing to me. The discussion was done, the RFC text got finalized and it was a great point in time to launch the vote on the finalized RFC. I see no benefit of this setback of another week. BR, Juris --=_93d70e760fd37980657886d73f8f5dce Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset= =3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen= eva,sans-serif'> <p id=3D"reply-intro">On 2026-07-23 08:44, Seifeddine Gmati wrote:</p> <blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2= px solid; margin: 0"> <div id=3D"replybody1"> <div dir=3D"ltr"> <div dir=3D"ltr">Hello internals,<br /><br />I am retracting this vote: I o= pened it prematurely, in violation of the voting prerequisites in the Featu= re Proposals policy. I did not post an Intent to Vote message at least two = days in advance, and today's 1.0 update to the RFC text is a Minor change a= nnouncement, which starts a seven-day Cooldown Period during which no vote = may be called.</div> </div> </div> </blockquote> <p>Hey all,</p> <p>I'm a frequent reader/follower of this list as well as an occasional par= ticipant and a one-time RFC-attempter. As such I never felt like I'm "= internal enough" to comment on the process. But since no one else seems to = be bothered by it, I would like to bring this up after all...</p> <p>The "new" process (<a href=3D"https://wiki.php.net/rfc/rfc_discussion_an= d_vote">https://wiki.php.net/rfc/rfc_discussion_and_vote</a>) feels very di= scouraging to me. All the mandatory cooldowns, cooldown resets on minor cha= nges, announcements to vote, cooldown resets on inactive discussions appear= s to me like bureaucratic hoops that people have to jump through. The proce= ss was hard and daunting enough before this.</p> <p>I understand the extremes that the rules are preventing like someone sud= denly launching a vote for an RFC that has been dormant for 20 months. But = in practice many of the mandatory cooldown resets, activity bumps and other= formal messages appear like only serving the process. This case in particu= lar feels very disappointing to me. The discussion was done, the RFC text g= ot finalized and it was a great point in time to launch the vote on the fin= alized RFC. I see no benefit of this setback of another week.</p> <p>BR,<br />Juris </p> </body></html> --=_93d70e760fd37980657886d73f8f5dce--