Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107243 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 37174 invoked from network); 19 Sep 2019 23:12:36 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 19 Sep 2019 23:12:36 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id CFD842C0478 for ; Thu, 19 Sep 2019 13:50:19 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_40,DKIM_INVALID, DKIM_SIGNED,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS36351 199.187.172.0/22 X-Spam-Virus: No Received: from tbjjbihbhebb.turbo-smtp.net (tbjjbihbhebb.turbo-smtp.net [199.187.174.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Thu, 19 Sep 2019 13:50:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=php.net; s=turbo-smtp; x=1569531019; h=DomainKey-Signature:Received: Received:MIME-Version:References:In-Reply-To:From:Date: Message-ID:Subject:To:Cc:Content-Type; bh=zTbQN/mbYY1MYeMyilNUmv 0+F0WoZzEYvkpNh1rD3+Q=; b=DziwtsrItVI77yNrpHo32ca2zYxVkTolyP4137 Mnj8PRZrZp49Ecrv7aTa4GIkj9eCsnMHUzBv15OWTensUnAsBYn0msdLHtOjRhu6 5jHZL96rXUDPqVMEbchC3y87OHwAll69Exc7qrgOz+HLwhNZwBh/i+zIn+jdhafo D8Qc4= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=turbo-smtp; d=php.net; h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type; b=jcqaGdl3wso1gJNDEXeHwq1RxDjog5GTYFMji4whFLVrZ1pdvA7ihEjI978Mzo iUqsIzRYYf7MIxCp2JSPNzk2Ws57k5XGKgt3hv1PzMS+mJAt2q9o3PdxVXVSMuHi +XLxTfVGuPJUMaQq/Tqq4vQvTw6ZYUjtu56NU55TeDn/M=; Received: (qmail 9433 invoked from network); 19 Sep 2019 20:50:18 -0000 Received: X-TurboSMTP-Tracking: 5294532780 X-Gm-Message-State: APjAAAX4HgL9ezBBsSBq7j925jLXYpzXK2VBjI0nE47uQgxpxOYn/SH6 h/H1YVopLEfhfInpLqABWqZDVggUkRCRVaRrz+8= X-Google-Smtp-Source: APXvYqx6zQ1Nd3lDj4J7Apuh/NwcaP1TnXSFIhbNTv18U7CEt8fvE63w362SkaX5YdlQf6s9LWdOfkFmdeo9A4PpXtY= X-Received: by 2002:a37:7d82:: with SMTP id y124mr5116663qkc.264.1568926218125; Thu, 19 Sep 2019 13:50:18 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 19 Sep 2019 23:50:06 +0300 X-Gmail-Original-Message-Id: Message-ID: To: Olumide Samson Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000e906e00592ee199c" X-Envelope-From: Subject: Re: Within 2 weeks, everything In PHP internals questioned From: zeev@php.net (Zeev Suraski) --000000000000e906e00592ee199c Content-Type: text/plain; charset="UTF-8" On Thu, Sep 19, 2019 at 1:44 AM Olumide Samson wrote: > I've been following closely lately and have seen you(Zeev Suraski) > question *RFC authority*(what it was meant for or not, even though your > facts weren't written as facts anywhere). > You've questioned the *mailing list* rules(be it binding or not), maybe it > should be followed or disregarded and just follow my/your-style rules. > There's a reason of why you're suddenly seeing those recently, and it's not me waking up one day deciding to question the authority of the RFC process or the mailing list rules. They have to do with new occurrences that me and some others are *reacting *to. Applying the RFC process to areas that until very recently were simply not even up for discussion, let alone a vote. Applying mailing list rules and/or the RFC process to shutdown dissenting voices and threaten them. This is unprecedented and unacceptable. To be clear, I'm not 'questioning' neither the RFC process nor the mailing list rules. But they are what they are - documents written by humans (very flawed ones, at least in the former case) in certain contexts and for certain purposes (and in a very short time with almost no discussion). While the RFC process has been used extensively in the last few years with a good degree of success - it was never meant to be used as an exclusive way to govern all aspects of the PHP project, and other tenets (which weren't codified, as they were obvious at the time the RFC process was introduced) for which we have a de-facto written track record are just as important (bias for BC, PHP as a lenient and dynamic language, open discussion, etc.). The mailing list rules were meant as a first stab at creating a nicer atmosphere for internals@ - not as a tool to limit people's ability to respectfully express themselves. Both are very useful. But they did not descend from heaven to rule everything (RFC process) nor to force everyone into submission (mailing list rules). Zeev P.S.: Regarding the 3rd thing you mentioned, the description of my position was completely off; If interested, you're very welcome to follow up with me off list, as I don't want to bug everyone with it. --000000000000e906e00592ee199c--