From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: TC/CC elections Date: Thu, 30 Nov 2023 09:08:06 +0100 Message-ID: <170133168699.8914.16014180573162512194@lain.khirnov.net> (raw) In-Reply-To: <689cf145-9211-4786-afe8-943f80c895f3@gmail.com> Quoting Derek Buitenhuis (2023-11-28 21:30:12) > On 11/28/2023 3:50 PM, Anton Khirnov wrote: > > Calling things generically bad is the opposite of helpful. > > I cannot offer help on making a paragraph that I don't fully > understand become more comprehensible, as that would require > I understand it fully. Consider the following: 1) I am neither a UI nor a voting system expert. 2) Explaining complex topics (like sophisticated voting systems) in a clear and easy to understand way is a very rare and highly nontrivial skill. 3) If you want an explanation that can be understood with no effort from your side, the best I can give you is: higher number = more preference (which is in the text already). 4) As this is a collaborative project, you are very much welcome to read the official documentation and supply a better explanation yourself, or find someone else who does. 5) As you're doing neither of these, your "word soup" and "trainwreck" amount just to your being an asshole to no purpose. > But, I would again like to state these votes should be scrapped > and redone. People literally voted the opposite of what they wanted > to by accident, due to this. So far we have exactly one person to whom this happened, who has notably NOT asked to redo the vote yet. While I don't oppose redoing the vote in principle, I also don't think it's realistic to expect a vote with 50+ voters to run with zero issues. Voting fatigue is also a real thing, so we risk some people not voting at all in hypothetical repeat votes. -- Anton Khirnov _______________________________________________ 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-30 8:08 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 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 [this message] 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=170133168699.8914.16014180573162512194@lain.khirnov.net \ --to=anton@khirnov.net \ --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