Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109148 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 93146 invoked from network); 19 Mar 2020 16:57:23 -0000 Received: from unknown (HELO localhost.localdomain) (76.75.200.58) by pb1.pair.com with SMTP; 19 Mar 2020 16:57:23 -0000 To: internals@lists.php.net References: <14383D05-EA33-4CD2-9648-40AA29A837A5@newclarity.net> <5e72b9a7.1c69fb81.7d447.f4f1SMTPIN_ADDED_MISSING@mx.google.com> <5e73304d.1c69fb81.7ae48.890cSMTPIN_ADDED_MISSING@mx.google.com> Date: Thu, 19 Mar 2020 15:20:34 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.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: 87.81.129.66 Subject: Re: [PHP-DEV] Capturing reasons for votes for historical sake? From: marandall@php.net (Mark Randall) Message-ID: On 19/03/2020 14:25, Kalle Sommer Nielsen wrote: > Why are we only attempting to harvest the negative thoughts (with the > word negative chosen carefully here as voting "No" is seemingly an > offense to some), why do we not also record why a feature was voted > in? Well a significant part of the purpose of the RFC is to make the case for why it *should* be done, and the benefits in doing so, and only to bring it to vote once the negatives have either been resolved, or are just down to personal preference. To vote yes is to state your overall agreement with the arguments made in the RFC. If you've read up and want to vote "no", I think that is perfectly fine and should be fully encouraged, but do the decent thing for your fellow developers and explain why so they're not left trying to guess. Ultimately, how can an RFC ever be improved to be more widely acceptable if the people voting in the negative don't give feedback?