Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124871
Feedback-ID: ia2404087:Fastmail
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Mime-Version: 1.0 (1.0)
Subject: Re: [PHP-DEV] Updates needed to various RFCs
Date: Sun, 11 Aug 2024 11:12:37 -0700
Message-ID: <5A1D9F33-D34B-4EFF-8B82-C09E44A3548D@trainedmonkey.com>
References: <6DF95BF3-C84E-4720-A000-1C401B596649@gmail.com>
In-Reply-To: <6DF95BF3-C84E-4720-A000-1C401B596649@gmail.com>
To: "internals@lists.php.net >> PHP internals" <internals@lists.php.net>
From: jimw@trainedmonkey.com (Jim Winstead)

On Aug 11, 2024, at 10:22=E2=80=AFAM, Marco Aur=C3=A9lio Deleu <deleugyn@gma=
il.com> wrote:
> On 11 Aug 2024, at 13:59, Christoph M. Becker <cmbecker69@gmx.de> wrote:
>>=20
>> On a general note, the whole administrative part of the RFC process
>> feels like we're stuck in the 20th century.  For instance, to start the
>> vote, you are supposed to:
>>=20
>> * update the RFC page to "voting" status
>> * add the doodle voting macro
>> * add the voting start and end dates to the text of the RFC
>> * move the RFC to "voting" on the RFC overview page
>> * send an email to the ML announcing the start of voting
>>=20
>> Wut?  Might as well ask me to send a punched card to someone.
>>=20
>=20
> I'd be willing to bet that PHP community members would gladly reimplement t=
he RFC system, voting, etc. and gift that to the PHP Group. However, wheneve=
r these conversations popup on internals, it is received with resistance to c=
hange and with unsound requirements such as "we can't use any PHP framework t=
o not seem like we favour one group over the other". What's left behind is e=
xactly what you described here: outdated process and implementation. The PHP=
 community spent a large chunk of work in the late 2010s just to phase out c=
orporate homemade frameworks for the usual maintenance reasons.

Work is underway, slowly because there are not many people involved and we a=
re trying to be careful, to document and clean up some of the underlying pro=
ject infrastructure. To get involved, I=E2=80=99d invite anyone to join the p=
hp-webmaster@lists.php.net list. Essential skills required right now: patien=
ce and a willingness to ask questions.

Jim=