Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85137
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <55089008.8010302@gmail.com>
References: <CAMc0WS5TRMGtFkPAJ5rrxyu+96GPnbMrOwUEd7+PaDnt8UXJZw@mail.gmail.com>
	<55089008.8010302@gmail.com>
Date: Tue, 17 Mar 2015 21:58:46 +0100
Message-ID: <CAOjCV8wWV+WqvnNwS3LP--8xk2ON2WBv1NUYFJD9KOd10sdRLg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: Stelian Mocanita <stelian.mocanita@gmail.com>, 
	PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Vote process change proposal
From: sbj.ml.read@gmail.com ("Sebastian B.-Hagensen")

Hi,

2015-03-17 21:35 GMT+01:00 Stanislav Malyshev <smalyshev@gmail.com>:
> Or, even worse, given current tendencies, somebody submits a proposal,
> couple of people say "yeah good idea", then vote happens and somehow
> there's 30 "no" votes without any explanation - and without possibility
> to fix it since by the time the proposer knows it the proposal is
> already declined. It wouldn't be very encouraging to submit RFCs with
> such process.

Unrelated to the suggestion of hiding votes:

How about adding an *optional* field next to the vote, where a voter
can link to his reasoning (a link to a mail to the list preferably).
This might make picking up older rfcs (,that were declined for earlier
versions easier if the general idea of the rfc isn't flawed) and
collects reasons for the outcome of an rfc without searching through
months of discussions. This change might also make it easier for the
author to chase down, why a vote failed, even if the prior discussion
didn't point into that direction.