Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Zhao Zhili" <quinkblack@foxmail.com>
To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
Date: Sat, 11 Nov 2023 17:31:43 +0800
Message-ID: <tencent_A3737295C9E91E2EA945471308E858F3E805@qq.com> (raw)
In-Reply-To: <169968950180.11195.280265863451995150@lain.khirnov.net>


> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Anton Khirnov
> Sent: 2023年11月11日 15:58
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
> 
> Quoting Thilo Borgmann via ffmpeg-devel (2023-11-11 08:22:19)
> > 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].
> 
> The word 'correlate' does not mean what you seem to think it means. The
> list does correlate.
> 
> > 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.
> >
> > 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.
> 
> I am not aware of anyone having given you the right to do this.
> 
> > michael@niedermayer.cc
> > onemda@gmail.com
> > jamrial@gmail.com
> > andreas.rheinhardt@gmail.com
> > sw@jkqxz.net
> > cus@passwd.hu
> > ceffmpeg@gmail.com
> > barryjzhao@tencent.com
> > liuqi05@kuaishou.com
> > lance.lmwang@gmail.com
> > martin.vignali@gmail.com
> > ffmpeg@gyani.pro
> > aman@tmm1.net
> > martin@martin.st
> > diego@biurrun.de
> > lizhong1008@gmail.com
> > dev@lynne.ee
> > nfxjfg@googlemail.com
> > anton@khirnov.net
> > atomnuker@gmail.com
> > timo@rothenpieler.org
> > u@pkh.me
> > george@nsup.org
> > yejun.guo@intel.com
> > linjie.fu@intel.com
> > kaustubh.raste@imgtec.com
> > stebbins@jetheaddev.com
> > philipl@overt.org
> > andriy.gelman@gmail.com
> > vittorio.giovara@gmail.com
> > jerome.borsboom@carpalis.nl
> > derek.buitenhuis@gmail.com
> > pross@xvid.org
> > jdek@itanimul.li
> > kjeyapal@akamai.com
> > dalecurtis@chromium.org
> > jeebjp@gmail.com
> > t.rapp@noa-archive.com
> > vdixit@akamai.com
> > zhilizhao@tencent.com
> > matthieu.bouron@gmail.com
> > yinshiyou-hf@loongson.cn
> > zane@zanevaniperen.com
> > ruiling.song@intel.com
> > kjeyapal@akamai.com
> > hwrenx@126.com
> > modmaker@google.com
> > cand@gmx.com
> > foobaz86@gmail.com
> > baptiste.coudurier@gmail.com
> 
> This list contains at least two duplicates, easily found by inspection.
> This gives me zero confidence that any hypothetical new vote would be
> any more reliable than the old one.
> 
> Also as I said before, option A won its contests against options B/C/D
> by 17/7, 23/1, and 17/7, respectively. You would thus need to change 10
> votes to have any chance of a different result. As the number of
> disputed voters is nowhere near 10, there is no point in repeating
> anything.

I abstain if there will another vote. I can't believe how much time have been taken
on this than do some real work, like coding and patch review, and improve the
situation of patch review.

_______________________________________________
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-11-11  9:32 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 [this message]
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
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=tencent_A3737295C9E91E2EA945471308E858F3E805@qq.com \
    --to=quinkblack@foxmail.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