Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120166 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 17767 invoked from network); 30 Apr 2023 21:36:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Apr 2023 21:36:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D3C67180538 for ; Sun, 30 Apr 2023 14:36:12 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE,RCVD_IN_DNSWL_LOW, SPF_HELO_PASS,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS20857 136.144.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from outbound9.mail.transip.nl (outbound9.mail.transip.nl [136.144.136.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 30 Apr 2023 14:36:11 -0700 (PDT) Received: from submission10.mail.transip.nl (unknown [10.103.8.161]) by outbound9.mail.transip.nl (Postfix) with ESMTP id 4Q8fmB3sWHzTPNMc for ; Sun, 30 Apr 2023 23:36:10 +0200 (CEST) Received: from mail-vk1-f171.google.com (mail-vk1-f171.google.com [209.85.221.171]) by submission10.mail.transip.nl (Postfix) with ESMTPA id 4Q8fm90tx7z1gwrq for ; Sun, 30 Apr 2023 23:36:09 +0200 (CEST) Received: by mail-vk1-f171.google.com with SMTP id 71dfb90a1353d-44054215485so1325228e0c.3 for ; Sun, 30 Apr 2023 14:36:09 -0700 (PDT) X-Gm-Message-State: AC+VfDxhzZxHm+7BGnnMcHt2IzlnQ/C+qm3WBR9oZ6Gsg5DVix0MfLos u0QO/vgzMZbX7smq3t7IZGCIcKeRBJWExGL0DOQ= X-Google-Smtp-Source: ACHHUZ5lLbjPDzzIWkr00xN3Ir2KOPK4ouFvAJ7go3QQaexx0Apq7xbVnDzAtyG07EWE0F2AH/Um/JQodCrE8H9I3Jo= X-Received: by 2002:a1f:4f86:0:b0:43b:3fda:1fba with SMTP id d128-20020a1f4f86000000b0043b3fda1fbamr4254606vkb.6.1682890568058; Sun, 30 Apr 2023 14:36:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 30 Apr 2023 22:36:10 +0100 X-Gmail-Original-Message-ID: Message-ID: To: Jakub Zelenka Cc: PHP internals list Content-Type: multipart/alternative; boundary="000000000000814cee05fa947e49" X-Scanned-By: ClueGetter at submission10.mail.transip.nl DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; s=transip-a; d=pmmaga.net; t=1682890569; h=from:subject:to:cc: references:in-reply-to:date:mime-version:content-type; bh=bC6/13AGz+/X8VVcrZ1YEfRQes9gZr566a+lhLWGvU0=; b=A10NzY3Y3R90UK7o/1yRDHJJZscFlAoLm5xcBpJjPq+TilpNM9gS1VYE2CC8tL/6oL/ZSd keL/MWv3+vYLZvWM+J0DCtslgysiyZkjuPuY7OSGhEEjxwPs3MuvoOkBO5u/KqOM7ZSQ72 VurC4IegJbce74vB+W9sC07tlzOx88pimQpAcG5uBRXrw/hUGGDeT+FEe5YGENu5z8Rnrs 52y5+AW47dp3w/HFo5nofPrtfnBu1Bc65I0cmM33DEq08Zb1czJ2ONGcWFKidZFb+mY8qv r7ru8WgKoe1kbVZvJCf3jsmCEiXpfnLYbR9FDqOnI2Vs6rDYN7x3l2mGVCRUWg== X-Report-Abuse-To: abuse@transip.nl Subject: Re: [PHP-DEV] [VOTE] PHP Technical Committee From: mail@pmmaga.net (=?UTF-8?Q?Pedro_Magalh=C3=A3es?=) --000000000000814cee05fa947e49 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 28, 2023 at 11:00=E2=80=AFAM Jakub Zelenka 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 > > Regards > > Jakub > Hi Jakob. Sorry for not participating in the discussion phase but I would like to give my explanation on why I voted No. You made a good job in distinguishing the user-facing from the technical changes to say what can and can't be decided by the TC, but the first can't live with the second. Then, it allows the TC to have conversations and vote in private in matters that until today have always been public. Of course developers are allowed to talk to each other wherever they want, but what matters is said in public. "unless the provided implementation would result in introduction of new bugs, side effects not mentioned in the RFC, significant performance penalties not mentioned in RFC, or if there is an equivalent implementation in progress that the TC finds more appropriate." is ample enough that it can allow anything to be rejected. Overall, the idea of having a group of people that developers can ask for some guidance from is great, but that group shouldn't have any extra rights to block anything whatsoever. To demonstrate good faith and unequivocally show that this is not an attempt at a power grab, it would be a nice gesture for the authors of the RFC to include their withdrawal from ever holding a seat in the technical council in the text of the RFC itself. Best regards, Pedro --000000000000814cee05fa947e49--