From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: TC/CC elections Date: Tue, 28 Nov 2023 15:25:53 +0100 Message-ID: <CAPYw7P4V7G8+cFXkW7D1+JXZhedvSVGARMoOLKxsmXLnKy4Qmw@mail.gmail.com> (raw) In-Reply-To: <d7a787ee-ffb0-4340-8ddf-4d41778239c8@gmail.com> On Tue, Nov 28, 2023 at 3:10 PM Derek Buitenhuis <derek.buitenhuis@gmail.com> wrote: > On 11/28/2023 1:23 PM, Anton Khirnov wrote: > > The system will assume you want to maximise the sum of weights of > > selected candidates. E.g. if X is given a weight of 10 and Y and Z have > > weights 8 and 6 respectively, then the voting algorithm will assume you > > prefer a committee with both Y and Z over one with X, because 14 > 10. > > However, giving Y and Z weight of 4 and 2 instead would have expressed > > that X is preferred to a combination of Y and Z, because 6 < 10. > > This is the opposite of clear or concise, it is word soup. > > Given that some already voted the opposite of what they intende, and > this trainwreck of an explanation, I think these votes should be > nuked. > > Really. I *still* have trouble understanding what to enter even after > reading this. > > What drugs were the devs on when they thought "yes, having voters enter > free-form data is reasonable"? > Looks like average IQ dropped bellow room temperature. > > - Derek > _______________________________________________ > 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". > _______________________________________________ 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 14:17 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 [this message] 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=CAPYw7P4V7G8+cFXkW7D1+JXZhedvSVGARMoOLKxsmXLnKy4Qmw@mail.gmail.com \ --to=onemda@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