Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:97012 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 36536 invoked from network); 19 Nov 2016 02:11:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Nov 2016 02:11:22 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@ohgaki.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@ohgaki.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ohgaki.net designates 180.42.98.130 as permitted sender) X-PHP-List-Original-Sender: yohgaki@ohgaki.net X-Host-Fingerprint: 180.42.98.130 ns1.es-i.jp Received: from [180.42.98.130] ([180.42.98.130:39984] helo=es-i.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B6/00-35487-7C4BF285 for ; Fri, 18 Nov 2016 21:11:21 -0500 Received: (qmail 127631 invoked by uid 89); 19 Nov 2016 02:11:16 -0000 Received: from unknown (HELO mail-wm0-f54.google.com) (yohgaki@ohgaki.net@74.125.82.54) by 0 with ESMTPA; 19 Nov 2016 02:11:16 -0000 Received: by mail-wm0-f54.google.com with SMTP id t79so69625219wmt.0 for ; Fri, 18 Nov 2016 18:11:15 -0800 (PST) X-Gm-Message-State: AKaTC03oEhBIY5qR8LWaFhD8qvYw1qQI3HaahYtZsl25plZxwANVTyI/MxH8RNvsd0yRysUrimzUYBKUh82HgA== X-Received: by 10.28.67.69 with SMTP id q66mr1293319wma.22.1479521468918; Fri, 18 Nov 2016 18:11:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.190.200 with HTTP; Fri, 18 Nov 2016 18:10:28 -0800 (PST) In-Reply-To: References: Date: Sat, 19 Nov 2016 11:10:28 +0900 X-Gmail-Original-Message-ID: Message-ID: To: Joe Watkins Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Re: [RFC] Abolish 50%+1 Votes From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Joe, On Sat, Nov 19, 2016 at 12:28 AM, Joe Watkins wrote: > I think most people would be happy to provide a reason, if you have it > listed. > It should be listed, because it should have been brought up during > discussion. > > Obviously we don't live in an ideal world, and you may get lots of no votes > still that don't provide a reason. There are clear cases that people misunderstand proposals. Recent example is PRNG adoption for uniqid(). I proposed patch does not have any BC, but there were people opposed based on false FUD. i.e. RPNG device access causes access error which is _nothing_ to do with internal function. Another example is session ID validation. It is mandatory to keep session as secure as possible, yet there are some people do not realize(?) why it is mandatory. There is workaround, but I haven't seen implementation does it correctly. I would rather just fix the issue rather than trying to teach how to do it. Anyway, regardless of opposition is reasonable or not, disclosing the reason why it is not preferred is valuable. Could you at least state in the RFC that all voters who are not in favor of the proposal should disclose the reason? Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net