From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: TC/CC elections
Date: Tue, 28 Nov 2023 09:42:43 -0300
Message-ID: <c0aa3295-3cd6-41fd-b3c6-9a5bebe4eba7@gmail.com> (raw)
In-Reply-To: <170117485768.1197.12665624837204920462@lain.khirnov.net>
On 11/28/2023 9:34 AM, Anton Khirnov wrote:
> Quoting Ronald S. Bultje (2023-11-28 13:19:00)
>> Hi,
>>
>> On Tue, Nov 28, 2023 at 6:58 AM Anton Khirnov <anton@khirnov.net> wrote:
>>
>>> There are reports from people on IRC that they got confused by the
>>> change and voted the reverse of what they meant. Sadly there is no way
>>> to change your vote after it's been case, so if there is a nontrivial
>>> number of such people, we may want to redo the vote.
>>>
>>
>> Serious suggestion: maybe the vote invitation email (or something similar)
>> should explain in more detail how the voting is to be done if it is
>> non-trivial?
>
> 1) I did not expect that picking proportional representation would
> change the UI so dramatically. And since I did not know what it would
> look like, I could hardly describe it in detail.
> 2) The UI in general could be improved, to put it mildly. Even for
> "normal" votes there is the potential point of confusion that more
> preferred candidates are higher visually, but have a lower numerical
> rank. So a statements like "X ranks higher than Y" could potentially
> be interpreted either way.
> 3) People generally dislike parsing long detailed explanations. Making
> the text longer could cause more voters to misinterpret it, or not
> bother reading it at all.
>
> So while I'm all for improving descriptions, it's not all that easy to
> do. Patches welcome.
Unlike in the previous vote, this one had you write a number. That alone
made me double check, and it indeed gives you an explanation of how
weight value works.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-28 12:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 10:02 Anton Khirnov
2023-11-06 20:06 ` Vittorio Giovara
2023-11-07 17:00 ` Anton Khirnov
2023-11-11 12:14 ` Rémi Denis-Courmont
2023-11-11 18:34 ` Michael Niedermayer
2023-11-11 18:37 ` James Almer
2023-11-11 18:48 ` Michael Niedermayer
2023-11-11 18:52 ` Nicolas George
2023-11-11 18:58 ` Vittorio Giovara
2023-11-11 19:01 ` Michael Niedermayer
2023-11-21 18:38 ` Anton Khirnov
2023-11-28 8:48 ` Anton Khirnov
2023-11-28 11:58 ` Anton Khirnov
2023-11-28 12:19 ` Ronald S. Bultje
2023-11-28 12:32 ` Paul B Mahol
2023-11-28 12:34 ` Anton Khirnov
2023-11-28 12:42 ` James Almer [this message]
2023-11-28 13:23 ` Anton Khirnov
2023-11-28 13:59 ` Devin Heitmueller
2023-11-28 14:10 ` Derek Buitenhuis
2023-11-28 14:25 ` Paul B Mahol
2023-11-28 14:30 ` Derek Buitenhuis
2023-11-28 14:32 ` Derek Buitenhuis
2023-11-28 14:49 ` Paul B Mahol
2023-11-28 15:50 ` Anton Khirnov
2023-11-28 20:30 ` Derek Buitenhuis
2023-11-29 12:22 ` Thilo Borgmann via ffmpeg-devel
2023-11-30 8:13 ` Anton Khirnov
2023-11-30 8:08 ` Anton Khirnov
2023-11-29 23:14 ` Michael Niedermayer
[not found] ` <927D5462-6DC7-4388-9F9A-3BD91CDEA460@cosmin.at>
2023-11-30 0:01 ` Cosmin Stejerean via ffmpeg-devel
2023-11-30 1:42 ` Ronald S. Bultje
[not found] ` <D4D0C816-A1A5-4D3B-A3CD-BA98EE8996E7@cosmin.at>
2023-11-30 7:16 ` Cosmin Stejerean via ffmpeg-devel
2023-11-30 21:24 ` Michael Niedermayer
2023-11-30 20:43 ` Alexander Strasser
2023-12-02 10:24 ` Anton Khirnov
2023-12-02 10:46 ` Niklas Haas
2023-12-03 18:13 ` Anton Khirnov
2023-12-05 10:07 ` Anton Khirnov
2023-12-05 10:16 ` Steven Liu
2023-12-05 11:01 ` Niklas Haas
2023-12-06 8:25 ` Anton Khirnov
2023-12-06 18:54 ` Michael Niedermayer
2023-12-05 13:28 ` James Almer
2023-12-05 14:04 ` Rémi Denis-Courmont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0aa3295-3cd6-41fd-b3c6-9a5bebe4eba7@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git