Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
Date: Sat, 11 Nov 2023 09:08:19 -0300
Message-ID: <4179fa31-46fa-47fe-962b-239f074de433@gmail.com> (raw)
In-Reply-To: <2e3245e3-e71d-4f17-9c5b-ba2087d30049@mail.de>

On 11/11/2023 4:22 AM, Thilo Borgmann via ffmpeg-devel wrote:
> Hi,
> 
> in [1] JB listed his list of authorized voters for the "GA voters list 
> updates"
> vote.
> 
> This list does not correlate with the list Josh provided in [2].
> Neither does this list of 51 people [1] correlate to the 54 authorized 
> voters
> (distinct email addresses) the CIVS system actually counted, see [3].
> 
> This can mean only one of two things, either some people on the list in 
> [1] did
> receive more than one ballot, or JB failed to list all the authorized 
> voters and
> ballots have been given to unknown people. Both possibilities are 
> unacceptable
> flaws for a democratic vote.

Neither of these happened. It was already explained what happened.

> 
> As the admin responsible of the votes it is my duty to have supervision 
> of all
> polls and thus it is my duty to declare this vote null and void for the 
> flaws
> given above.

No, this is completely unacceptable.

> 
> This vote will be repeated from Sun 12th of November to Sunday 19th of 
> November
> so we don't have to move the following votes yet another time.

As others pointer out, not only would such a vote not give a different 
result if run with the list you shared in this email, as it's the same 
people + duplicate addresses, but a repeated vote knowing the result 
beforehand might affect people's choice, or outright have people not 
bother voting at all.

So again, this is not ok at all and it damages the credibility of the 
entire system.
_______________________________________________
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".

  parent reply	other threads:[~2023-11-11 12:08 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11  7:22 Thilo Borgmann via ffmpeg-devel
2023-11-11  7:58 ` Anton Khirnov
2023-11-11  9:31   ` Zhao Zhili
2023-11-11  9:39   ` Lynne
2023-11-11  9:42 ` Jean-Baptiste Kempf
2023-11-14  9:28   ` Tomas Härdin
2023-11-14 12:49     ` Thilo Borgmann via ffmpeg-devel
2023-11-14 15:56       ` Tomas Härdin
2023-11-14 16:17         ` Vittorio Giovara
2023-11-14 16:46         ` Rémi Denis-Courmont
2023-11-14 18:44           ` Nicolas George
2023-11-14 19:15             ` Rémi Denis-Courmont
2023-11-14 20:12               ` Nicolas George
2023-11-14 19:19             ` Ronald S. Bultje
2023-11-14 19:28               ` Nicolas George
2023-11-14 19:32                 ` Ronald S. Bultje
2023-11-14 20:10                   ` epirat07
2023-11-14 19:34                 ` Vittorio Giovara
2023-11-14 21:02           ` Tomas Härdin
2023-11-11  9:54 ` Jean-Baptiste Kempf
2023-11-11 15:35   ` Michael Niedermayer
2023-11-11 16:58     ` Nicolas George
2023-11-11 18:29       ` Jean-Baptiste Kempf
2023-11-11 18:38       ` Michael Niedermayer
2023-11-11 10:28 ` Rémi Denis-Courmont
2023-11-11 11:15   ` Nicolas George
2023-11-11 11:49     ` Rémi Denis-Courmont
2023-11-11 12:08 ` James Almer [this message]
2023-11-11 18:43 ` Vittorio Giovara
2023-11-12 13:59 ` Thilo Borgmann via ffmpeg-devel
2023-11-12 14:03   ` James Almer
2023-11-12 14:08     ` [FFmpeg-devel] Poll: " Anton Khirnov
2023-11-12 16:23       ` Nicolas George
2023-11-12 17:31     ` [FFmpeg-devel] [ANNOUNCE] " Michael Niedermayer
2023-11-12 17:43       ` J. Dekker
2023-11-12 18:02         ` Michael Niedermayer
2023-11-12 18:34           ` Anton Khirnov
2023-11-12 21:38             ` Michael Niedermayer
2023-11-12 14:10   ` Paul B Mahol
2023-11-20 15:44 ` Thilo Borgmann via ffmpeg-devel
2023-11-20 16:06   ` Derek Buitenhuis
2023-11-20 16:08     ` J. Dekker

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=4179fa31-46fa-47fe-962b-239f074de433@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