Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107056 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41850 invoked from network); 13 Sep 2019 10:54:38 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 13 Sep 2019 10:54:38 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 3A0A12C046B for ; Fri, 13 Sep 2019 01:30:44 -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.5 required=5.0 tests=BAYES_05,HTML_MESSAGE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS24940 159.69.0.0/16 X-Spam-Virus: No Received: from srv015.mail.ichtushosting.com (srv015.mail.ichtushosting.com [159.69.182.195]) (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 ; Fri, 13 Sep 2019 01:30:43 -0700 (PDT) Received: from srv010.web.ichtushosting.com ([78.46.201.44]) by srv015.mail.ichtushosting.com stage1 with esmtps (Exim MailCleaner) id 1i8gyY-00041l-T2 for from ; Fri, 13 Sep 2019 10:30:42 +0200 Received: from localhost (localhost.localdomain [127.0.0.1]) by srv010.web.ichtushosting.com (Postfix) with ESMTP id B4E7BC3CCE for ; Fri, 13 Sep 2019 10:30:42 +0200 (CEST) Received: from srv010.web.ichtushosting.com ([127.0.0.1]) by localhost (srv010.web.ichtushosting.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id I1J4bPcwEJnp for ; Fri, 13 Sep 2019 10:30:32 +0200 (CEST) Received: from [2a02:1812:c3c:3a00:400::] (ptr-fq9pjpho51b0q8sp6ws.18120a2.ip6.access.telenet.be [IPv6:2a02:1812:c3c:3a00:6994:52ab:6a5b:4b3c]) (Authenticated sender: brendt@stitcher.io) by srv010.web.ichtushosting.com (Postfix) with ESMTPSA id 9208CC3C88 for ; Fri, 13 Sep 2019 10:30:32 +0200 (CEST) X-MailCleaner-SPF: pass Date: Fri, 13 Sep 2019 10:30:20 +0200 To: PHP internals Message-ID: In-Reply-To: <39b23737-06f5-11d8-0587-23c7e8a24fb9@gmail.com> References: <39b23737-06f5-11d8-0587-23c7e8a24fb9@gmail.com> X-Readdle-Message-ID: b5350581-9c8d-44d4-9752-ccd4fe03b8af@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5d7b53a4_1e7ff521_543e" X-Envelope-From: Subject: Offtopic discussions From: brendt@stitcher.io (Brent) --5d7b53a4_1e7ff521_543e Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello all I've noticed a trend in many threads here on the internals list where an RFC is being discussed, but one way or another we always end up with the same offtopic conversation about how PHP should evolve. While I think this is a good conversation to have, I don't think it's beneficial for the RFC process to have the same discussion happening over and over again, effectively having the RFC discussion hijacked by another one. I can only imagine it must be quite difficult for the people working on these RFCs to filter out ontopic from offtopic content. Here are a few examples: - Reclassifying engine warnings (https://externals.io/message/106713) - Short open tags (https://externals.io/message/106384) - Namespaced scope declares (https://externals.io/message/101323) - Call-site send by ref (https://externals.io/message/101254) - PHP 7.4 deprecations (https://externals.io/message/106012) Maybe someone has a good suggestion on how people can voice their opinion on the future of PHP, without polluting several RFC discussions. Kinds regards Brent --5d7b53a4_1e7ff521_543e--