Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91032 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54173 invoked from network); 31 Jan 2016 02:43:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jan 2016 02:43:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-yk0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:35207] helo=mail-yk0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 60/62-35275-4B47DA65 for ; Sat, 30 Jan 2016 21:43:01 -0500 Received: by mail-yk0-f170.google.com with SMTP id r207so67763527ykd.2 for ; Sat, 30 Jan 2016 18:43:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=dWfmeJribCkA350Jnm+mqH1fz5EkP6E87qj2nO9FMfQ=; b=EZniJPd2ELzWRX2WkHXsiDS34fUSSU8ADYHgrs20Ft6v9A2tmyBgYGcgg4jZh8SrIi FR5u/PnVdvzfp0C2JXw404gMW6+j7YLO0xalTxBAMyMseVEptcOrTIxKB3yu8NlpMyiy ZSO/hYFL/BekcsK7HzWQbFmfeX3F2mkKtuEfGGmERM16wJUIvFtXtXAyx9An+QqNGu6n s9x03j6+s8nWVnZB0OM87x5ZHxHWMHqmh2yW+3akNKGshf3upHxWsYG7cxu8Drc09Jic ZNoMKJgbtp5ODSLoYqGTZxvYGq6Jqy/5g1NDyHBUmR51YBnywPDBhyOzfCoReqiAwJK+ bcqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type; bh=dWfmeJribCkA350Jnm+mqH1fz5EkP6E87qj2nO9FMfQ=; b=PS5fy9q8oi4HV+0sIYjXSi+NAtrHaKn6+1yUgyCufqApQZdYpL6b1mbydTiNSoqGzs vNbmE96sm8hL8lYsdvLAkDU5x2UY1efOdMBrIHks5MZYYjslZn2hzEUNQL30mJV7RmP5 /2MrIepwNv0Oe+SBeFccPq/5n5Ag1YlMIKpuYeA5ngP49xcwwice+0Ddfa8umA8R/eu1 ilVmi5nl3JXeX6X/jCUtnzl1QQOErl7iC4IRxg3tdNnyqm3JQzbY44AokcvCo37WGYwj nUgeAxYdct/CXWbGIAQdhdZN4AMX80cXGidOsXRVUJoSPJcjHNCDzn6U417EPBVFH4iO 1jOQ== X-Gm-Message-State: AG10YOSi3/JKjS8jF3oxPDM+nxKCCIXqR9/NT6WI0WTx7QAwhQW570Ab90zFIv1alTIj68Yn9YsyAzxV/dOXiA== X-Received: by 10.129.137.193 with SMTP id z184mr9074645ywf.257.1454208178363; Sat, 30 Jan 2016 18:42:58 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.129.109.22 with HTTP; Sat, 30 Jan 2016 18:42:18 -0800 (PST) In-Reply-To: <58.11.35275.ADC3DA65@pb1.pair.com> References: <6F.D4.55829.C14FCA65@pb1.pair.com> <58.11.35275.ADC3DA65@pb1.pair.com> Date: Sun, 31 Jan 2016 11:42:18 +0900 X-Google-Sender-Auth: pPrUj_Zegf4EmIjLzBgHa5iHWxk Message-ID: To: Andrea Faulds Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Should we rethink the 50%+1 requirement fornon-"language changes"? From: yohgaki@ohgaki.net (Yasuo Ohgaki) Hi Andrea, On Sun, Jan 31, 2016 at 7:44 AM, Andrea Faulds wrote: > Nikita Popov wrote: >> >> On Sat, Jan 30, 2016 at 6:34 PM, Andrea Faulds wrote: >> >> I'm definitely in favor of requiring a 2/3 majority in all cases. An RFC >> that passes with 51:50 votes is clearly not an RFC that a consensus exists >> on. On the contrary, it indicates a very controversial change which >> requires further deliberation. > > > This is a good point. If something can only pass with the 50%+1 rule, that's > not a point in its favour. I agree it's good to have 2/3 majority in all cases in general. It means people who vote against a proposal have twice worth of vote than supporters. It's ok to have twice value if the reason why he/she opposed is solid, reasonable and disclosed. Disclosure is mandatory for RFC improvement, what's missing - description and/or feature, what's not preferred, what's the better way to do it, etc. It's ok to reject a RFC by "I don't think it is not needed" for simple additions like array_find_recursive() - it's imaginably RFC. However, it is not ok for some change/addition like mine https://wiki.php.net/rfc/precise_session_management This RFC includes mandatory session management behaviors and not disclosing why someone objects it, is not nice thing to see. Opposing votes for "Precise Session Management" would mean most likely, "My description was not good enough to be understood by everyone" or "Some implementation is not preferred" or even "There are better ways to do this". 2/3 majority sounds good, if people who against a proposal explicitly disclose the reason why. Reasons for opposition are required for RFC/implementation improvements if it is needed. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net