Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65308 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11183 invoked from network); 28 Jan 2013 22:24:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2013 22:24:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.180 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.210.180 mail-ia0-f180.google.com Received: from [209.85.210.180] ([209.85.210.180:54631] helo=mail-ia0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/FF-28517-2BAF6015 for ; Mon, 28 Jan 2013 17:24:52 -0500 Received: by mail-ia0-f180.google.com with SMTP id f27so4936671iae.39 for ; Mon, 28 Jan 2013 14:24:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7NorTAKUGCNr9r5fBeqw6mEAkL3VkCvsS6Vk6dnnoVM=; b=TVsJDHNHtm9uz4ICJtNGZoHnMsVk8+2wKLMuTgA1u5kNe8dHSizWtejULuIHKd2Vl4 guZcJ2f3LfN/MOu6f3rG8ngwuUzW2atEBFrKJcxq9LLa1vbus9essCiy5jlbPA7jitM6 PM2JgW+//Z3qBDZ0I5zcB+HNBDSnA4uxjVpnvzQXFmLomxDd+Uwyn3M/xsgayUCAT4+E 8fhUa9wIeTKhFmTAfBHjnjm0UL9tm0CVR1onrDVjT8dQ56J80rOm3E1KIyqfYzSN9D9/ PL7F0OVsQ0GX1jDW2fQmydxKBeJv52J1CtLiGKSh4/hZ3eydfXDyAa9SWDdH5Kpapx29 U8KQ== MIME-Version: 1.0 X-Received: by 10.50.196.130 with SMTP id im2mr6167019igc.17.1359411888618; Mon, 28 Jan 2013 14:24:48 -0800 (PST) Received: by 10.50.106.138 with HTTP; Mon, 28 Jan 2013 14:24:48 -0800 (PST) In-Reply-To: References: <8443b1f0eaec6316a3e5791c097d5c49@mail.gmail.com> Date: Mon, 28 Jan 2013 23:24:48 +0100 Message-ID: To: Patrick ALLAERT Cc: Zeev Suraski , Anthony Ferrara , PHP Development Content-Type: multipart/alternative; boundary=14dae9341071b97c1f04d460be8c Subject: Re: [PHP-DEV] Purpose of voting From: tyra3l@gmail.com (Ferenc Kovacs) --14dae9341071b97c1f04d460be8c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, Jan 28, 2013 at 11:11 PM, Patrick ALLAERT w= rote: > 2013/1/28 Zeev Suraski : > >> What should we be voting on when voting on an RFC: on the RFC proposed > >> feature, or on the patch itself? > > > > I think it should be exclusively on the concept. We never vote about > code > > changes anywhere - including when we refactor existing parts. Why woul= d > > we vote about the implementation here? > > Just to +1 Zeev's opinion here. > It's perfectly valid to accept an RFC and comment on the > implementation on what should be improved or what sucks in it. > > If one is voting "no" mostly because of the implementation, then I > would say that there is a lack of information in the voting process > when saying "no". (No why... ?) > > Side node: whatever the formal "process" we will use we will always > have to be flexible enough to listen to each other and not falling > into bureaucracy too much. > > Patrick > voting no based on the implementation would be that bad if the more voters could participate in the discussion phase, as that is where those problems should be laid out and addressed. as Client also said, knowing why a person voted no is much easier to bear for the author even if he doesn't agree with those. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --14dae9341071b97c1f04d460be8c--