Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107240 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 5123 invoked from network); 19 Sep 2019 20:33:36 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 19 Sep 2019 20:33:36 -0000 To: internals@lists.php.net References: Date: Thu, 19 Sep 2019 19:11:19 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Posted-By: 5.69.57.161 Subject: Re: [PHP-DEV] [RFC] Prevent disruptions of conversations From: marandall@php.net (Mark Randall) Message-ID: On 19/09/2019 18:38, Chase Peeler wrote: > So, in other words, if the majority of core members decide they want to > force strict typing in PHP 9, and non-core PHP developers voice their > opposition to such a change, there would be nothing to prevent those core > members from voting to suspend the non-core members from the list, except > to hope that such power wouldn't abused? You may be misinterpreting the intent of the RFC. I don't believe this RFC is aimed at silence productive debate, it is clearly aimed at limiting the access of what I can only imagine is a small number of people whose continued involvement would be severely detrimental the proper functioning of internals. For example, if one person were to be responsible for between 30% to 40% of all posts in a given high-volume day, that person would, quite rightly, be seen as entering the realms of disruptive behaviour in light of the existing internals guidelines regarding considerate posting, and they may find themselves prevented from continuing those actions. Something I think most people would consider entirely reasonable. Mark Randall