Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120153
MIME-Version: 1.0
References: <CAEKnhAEzEBRHO+=3KSLCveEWZ7ZwxtD0MJL-=VG6nz2xMcvbMA@mail.gmail.com>
In-Reply-To: <CAEKnhAEzEBRHO+=3KSLCveEWZ7ZwxtD0MJL-=VG6nz2xMcvbMA@mail.gmail.com>
Reply-To: Levi Morrison <levi.morrison@datadoghq.com>
Date: Fri, 28 Apr 2023 09:17:21 -0600
Message-ID: <CAAKU0unGGoN4-u0kUHB7DvjKHZgSgSTRkUywbx==Uzzt+skNxQ@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [VOTE] PHP Technical Committee
From: internals@lists.php.net ("Levi Morrison via internals")

On Fri, Apr 28, 2023 at 4:01=E2=80=AFAM Jakub Zelenka <bukka@php.net> wrote=
:
>
> Hi,
>
> The vote is now open for the RFC about introduction of the PHP Technical
> Committee:
>
> https://wiki.php.net/rfc/php_technical_committee
>
> Regards
>
> Jakub

Do we really need this level of bureaucracy? I mean... I know
someone's work got rejected and that wasn't a great situation, and I
feel for them because it was handled poorly IMO. But this committee
seems like a lot of work for... what? Being able to solve an
occasional disagreement? This seems like more work than it solves,
with some bad downsides if "the wrong people" get in there. You know,
the power-hungry egotistical kind of people.