Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120169
MIME-Version: 1.0
References: <CAEKnhAEzEBRHO+=3KSLCveEWZ7ZwxtD0MJL-=VG6nz2xMcvbMA@mail.gmail.com>
In-Reply-To: <CAEKnhAEzEBRHO+=3KSLCveEWZ7ZwxtD0MJL-=VG6nz2xMcvbMA@mail.gmail.com>
Date: Mon, 1 May 2023 17:09:01 +0200
Message-ID: <CAEPJdumVSyuKgUT7J1oLfP901E393L7A_qwf0dMNjV3z5wThGA@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a2e9d105faa3349f"
Subject: Re: [PHP-DEV] [VOTE] PHP Technical Committee
From: kontakt@beberlei.de (=?UTF-8?Q?Benjamin_Au=C3=9Fenhofer?=)

--000000000000a2e9d105faa3349f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 28, 2023 at 12:01=E2=80=AFPM Jakub Zelenka <bukka@php.net> wrot=
e:

> Hi,
>
> The vote is now open for the RFC about introduction of the PHP Technical
> Committee:
>
> https://wiki.php.net/rfc/php_technical_committee


I found this idea of a TC interesting on the outset, but after carefully
consideirng I voted no on this RFC because

a.) i believe it to be too much bearucracy for the little benefit
b.) potentially harmful depending on who is on the TC.
c.) There is also no process of overuling the TC, or voting a TC out due to
no confidence or something. Without the votes known of TC members, voters
of the TC have no insights into who they might want to boot or keep in the
next election. However introducing these data points would make everything
even more complicated.

Ultimately, already at the moment each controversial change can be asked to
be RFCed and then the voters can decide with arguments made by people
knowledgable in the area. Yes, there is always some politics involved, but
the same would be true of the TC decisions.


>
> Regards
>
> Jakub
>

--000000000000a2e9d105faa3349f--