Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: TC/CC elections
Date: Sat, 2 Dec 2023 11:46:23 +0100
Message-ID: <20231202114623.GB5092@haasn.xyz> (raw)
In-Reply-To: <170151267933.8914.8672128983028813738@lain.khirnov.net>

On Sat, 02 Dec 2023 11:24:39 +0100 Anton Khirnov <anton@khirnov.net> wrote:
> So, given that we've had no further reports about voting mistakes, I'm
> leaning towards NOT redoing the vote. If anyone has strong opinions one
> way or another, feel welcome to comment. Either way we should make a
> decision before the vote is closed on Tuesday.

One wrong vote out of 51 eligible is an error rate substantially below
the average for any kind of vote, ever. I would assume this has a lower
impact on the overall results than other sources of noise (mood,
weather, recent events, ...), and certainly less error than trying to
re-do the vote would introduce.

Also, if we now start to question a vote's validity over such minor
inconsistensies, after all the recent vote drama, we will begin to set
a rather nasty precedent for how future votes should be treated.

Finally, remember that human beings make mistakes and can misread even
the most basic of instructions. That somebody voted incorrectly is
neither fault of the explanation nor of the person voting, and IMO
bikeshedding how many ways to rephrase "higher number = more good" is
not a productive use of anybody's time.
_______________________________________________
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".

  reply	other threads:[~2023-12-02 10:46 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
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 [this message]
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=20231202114623.GB5092@haasn.xyz \
    --to=ffmpeg@haasn.xyz \
    --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