Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85232 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27245 invoked from network); 19 Mar 2015 18:28:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Mar 2015 18:28:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.180 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.180 mail-wi0-f180.google.com Received: from [209.85.212.180] ([209.85.212.180:38465] helo=mail-wi0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/87-25408-F551B055 for ; Thu, 19 Mar 2015 13:28:52 -0500 Received: by wifj2 with SMTP id j2so77029888wif.1 for ; Thu, 19 Mar 2015 11:28:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=nuk+6dbSIKVZpw/dVj9/psSaOJjcZiBMxOysqT7XhME=; b=E+iaK1lJR4Z994MrvocETd8xNVRZ0Yy32vmvKfpkt6YSgB5LWVeWw2DI4xEFrh6sWv qvu+m2uwI+AUTJw8QE4iTBCNOCVBRKkGY/yryLah4Um2JAi7IvneTls6FX+dhW7zjf3y /599YiZrc1p39/ai1u9FLeRBxkOyrSkaZczLUjdLiXED4Prb7fYwopnafH+CsmBdziu5 g1Ms6rn7wQpFNhF24NVY4qzaXNAcg0CtdT1ALLJwITSlNEN3rNXBM1dia4w1P+NJTOSm +glWpSgLCnr0ZMRE6cBSvfM+7KSQrOsBquTPnn+MxfMy1IXNqcZSOKLRT/pU85fhjIoj Rmow== X-Received: by 10.194.9.98 with SMTP id y2mr158112850wja.85.1426789724041; Thu, 19 Mar 2015 11:28:44 -0700 (PDT) Received: from [192.168.0.159] ([62.189.198.114]) by mx.google.com with ESMTPSA id 14sm3003343wjv.29.2015.03.19.11.28.43 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Mar 2015 11:28:43 -0700 (PDT) Message-ID: <550B154F.9000000@gmail.com> Date: Thu, 19 Mar 2015 18:28:31 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: internals@lists.php.net References: <885a29db28bc96b2d3cd2ac96907e39f@mail.gmail.com> <077401d06268$2b597c30$820c7490$@php.net> <28871A37-A2F8-465F-8717-A116B8AA78C7@zend.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Question/comment about the Array to String conversion RFC From: rowan.collins@gmail.com (Rowan Collins) Dan Ackroyd wrote on 19/03/2015 18:11: > Rowan wrote: >> >you should pause, make a cup of tea, and redraft the e-mail. > That was the redrafted version. And yet it still accused another contributor of "being dumb", and demanded they have access revoked. That is not a respectful or proportional response to the situation. > The edits to the RFC were made two weeks ago. In Francois' defence he > himself alerted the list to the changes. But the unapproved editing > also meant that if there was someone else who was concerned about the > BC break, they might not have raised an RFC to revert the RFC, before > the cut off time for RFCs. This is one of the reasons why someone > editing the text of a passed RFC is utterly unacceptable. Anyone knowledgeable enough about the process to raise such an RFC would, at worst, have expressed confusion about the validity of the edit. Note that the text of the vote remains "Yes to replace E_NOTICE with E_RECOVERABLE_ERROR, No for no change." so it's kind of obvious that's what was agreed to. There is no inline editing of the text to make it look like this was always the case, and the wiki provides full history to anyone who cares to check. Again, I agree that editing the RFC was wrong here, but I think a "please don't do this again" would have been sufficient. Regards, -- Rowan Collins [IMSoP]