Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81127
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 74.125.82.45 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAPg3Xx+WguarCd66NsUchgp4FrgiaEO5qFTmD8_QAiW_7n-s5Q@mail.gmail.com>
References: <54C4A44F.2030902@gmail.com>
	<CAKxcST875eALqofUGfFgxN6fh1+1UVJUqY2W6Dd65x5d6STmZQ@mail.gmail.com>
	<CAPg3Xx+WguarCd66NsUchgp4FrgiaEO5qFTmD8_QAiW_7n-s5Q@mail.gmail.com>
Date: Sun, 25 Jan 2015 15:44:54 +0000
Message-ID: <CA+kxMuQe5SB6P4fDSVy1=DHyVMEHLFo_W2mW2e5p1x5xuWxv9g@mail.gmail.com>
To: Peter Cowburn <petercowburn@gmail.com>
Cc: Paul Dragoonis <dragoonis@gmail.com>, Stanislav Malyshev <smalyshev@gmail.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Vote results for default ctors RFC
From: danack@basereality.com (Dan Ackroyd)

On 25 January 2015 at 11:26, Peter Cowburn <petercowburn@gmail.com> wrote:
> That's what the mailing list threads are for, right?


If someone has already said a reason on the list for why an RFC should
be voted no, when someone else agrees with that reason it's not common
for them to email, as it could be viewed as generating noise.

Also having all the reasons why an RFC was declined in one place would
make it easier to revisit RFCs in the future. It would allow people to
see if RFCs were declined because people thought they were just a bad
idea, or if there was a problem with a small detail of the RFC,
without having to wade through email archives.

However I think there is a strong risk of people having to give a
reason why they voted no being abused, particularly if it is shown
while the voting was taking place, as people could be harassed for
choosing an 'invalid' reason to reject the RFC.

cheers
Dan