Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60113
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
In-Reply-To: <DDE958BC-2C13-40F9-B61A-5616C95E0D17@gmail.com>
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
References: <4F8D1469.9030709@lerdorf.com>
 <CAKOpQSw6YoTEKh+qBbJQOqodeGhYhZmVL9rHpdvfejZZQE9DVA@mail.gmail.com>
 <4F8DC894.50804@lerdorf.com>
 <CAORXhGLLm5Yrbtb7mzXUNUOZODQZ9kckKY8voj=ymZ_c0jtoTQ@mail.gmail.com>
 <DDE958BC-2C13-40F9-B61A-5616C95E0D17@gmail.com>
To: internals@lists.php.net
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Date: Tue, 17 Apr 2012 23:42:36 +0200
Message-ID: <op.wcxilasdidpuyk@damnation.mshome.net>
User-Agent: Opera Mail/11.62 (Win32)
Subject: Re: [PHP-DEV] Some Stats
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

On Tue, 17 Apr 2012 23:23:35 +0200, Tjerk Meesters
<tjerk.meesters@gmail.com> wrote:

> Maybe this has been suggested before, but it would be nice if comments  
> in, ahem, request for comments could be consolidated into one spot, the  
> RFC page itself. Facebook comments come to mind, though I'm sure there  
> are other solutions based on OpenID, etc.
>

This list should remain the main place for discussing PHP development. The
volume of e-mails can be mitigated by sending more consolidated answers
(that cover several points discussed recently) and avoiding recycling
arguments.

It's of little use to bring the same issues over and over again, be it
with different or the same people. It doesn't matter if someone didn't
"get it", you don't have to convince him individually that you're right as
that will have a near null effect on the outcome of the RFC.

In my opinion, one of the problems with these RFC threads is that the
proposers are busy retorting over and over again instead of just
collecting the objections and address them either by changing the proposal
or responding *once* in a well thought-out manner. That objection and a
short response should also be included in the RFC to avoid it being
brought up again.

-- 
Gustavo Lopes