Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76154
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.169 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
Date: Fri, 25 Jul 2014 21:42:55 -0400
Message-ID: <CAEYWF=4JLN+byMP3AmKY94639YDfNmg4e5=D_OGCcsrLchTfkQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>, Peter Cowburn <petercowburn@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1134990610205704ff0ecf40
Subject: Re: [PHP-DEV] On voting, including the next release name.
From: bishop@php.net (Bishop Bettini)

--001a1134990610205704ff0ecf40
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello all.

TL;DR: Tweak how the voting is displayed to address some minor human factor
concerns: (1) Keep all existing functionality. (2) On RFC page, show my
vote stuff at top, and collapse the current results table just below my
voting stuff. (3) With one click, expand the current results. Sample
screenshot links below.  Makes accessing my vote a little more convenient.
 With respect to the bandwagon effect, if there isn't one nothing is lost
and if there is we reduce it some.

.

So I'm all for open information. My point is about human factors. When the
results are listed alongside the argument, the results themselves *become
part of the argument*.  That is the nature of the bandwagon effect.  *The
brain treats the results as a data point.*  While $personA might be able to
compartmentalize, $personB might not. To the extent we can help people stay
focused on the issue, we should, to preserve the essence of the vote.

Alright, so holding results until the poll closes has larger implications.
 Let's focus on the human factors, because this ain't politics as (Andrea?)
pointed out in an earlier thread.  I believe we should keep it easy to
vote, to modify my vote, and to see who has voted which way and totals...
but insert a small visual "wedge" between the argument and the results.

So here's a little mock-up of what I feel would be a good presentation that
considers the human factor.  These mocks are based on the PHP6 RFC.

=3D=3D=3D "I HAVE NOT VOTED" STATE =3D=3D=3D
Scenario: I load the page. I read the RFC. I am prompted to vote clearly.
I have the option to see everybody else's vote (to date) with one click.

[Image] Let me vote, other people's responses collapsed.
<https://drive.google.com/file/d/0B1kt0xDsN4tCREotS25qSi1aNUk/edit?usp=3Dsh=
aring>


[Image] Let me vote, I have expanded to see other people's responses.
<https://drive.google.com/file/d/0B1kt0xDsN4tCcXFYVDc1MDVlRG8/edit?usp=3Dsh=
aring>
=E2=80=8B=E2=80=8B

=3D=3D=3D "I HAVE VOTED" STATE =3D=3D=3D
My vote is listed, at the top, with the controls to alter my vote.
Everybody else's vote is listed below mine, in alphabetical order, same as
now.  No click necessary to see the results.

[Image] Show me my vote. I can change or delete it. I see everybody's
responses and counts.
<https://drive.google.com/file/d/0B1kt0xDsN4tCZHpsVF9iOVJiWHc/edit?usp=3Dsh=
aring>
=E2=80=8B

This preserves the existing functionality, just shuffles it around a little
bit in light of some human factors.  If we suppose there isn't a bandwagon
effect, then at least this makes it a tiny bit easier to change my results
(always at top) and see totals (also at top).  If we suppose there IS a
bandwagon effect, then we get those benefits PLUS the benefit of holding
back the effect some.


Regards,
bishop

--001a1134990610205704ff0ecf40--