Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [ANNOUNCE] Repeat vote: GA voters list updates
Date: Sun, 12 Nov 2023 15:10:10 +0100
Message-ID: <CAPYw7P46GcbsDPeT1xQbMEsQbawygQ7g15kpt83XeAWOO+8MfA@mail.gmail.com> (raw)
In-Reply-To: <2aa864c8-b15c-4ad8-9642-0f4982ee4721@mail.de>

On Sun, Nov 12, 2023 at 2:59 PM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:

> Hi,
>
> for privacy reasons I must use JB's quote as given in the archives and
> need to drag this reply up one level. If the addresses in the
> redacted part need to be referred to, they shall be referred to as
> AddressA and AddressB.
>
> I will address more replies once time allows, JB's reply is actually the
> one mail that addresses the cause of this whole mess so I reply to it now
> (asap).
>
> I will also start the repeat vote now and everybody can hold their horses
> before going to flamewar. Depending on JB's explanations, he might still
> prove that the old vote is valid and this repeat vote becomes void. Anyway,
> if he cannot, this needs to follow the given timeframe.
>
> On we go:
>
>
> Am 11.11.23 um 10:54 schrieb Jean-Baptiste Kempf:
> > On Sat, 11 Nov 2023, at 08:22, Thilo Borgmann via ffmpeg-devel wrote:
> >> Neither does this list of 51 people [1] correlate to the 54 authorized
> voters
> >> (distinct email addresses) the CIVS system actually counted, see [3].
> >
> > And instead of you ASKING for that, you launch another vote? That's your
> solution?
>
> Very well, then let me ask you to share, even privately if you have
> privacy concerns, the following data that might help to invalidate my
> claims and probably shortcut the whole when what and how questions in the
> other half of the mail:
> - The file(s) you used for the first and second batch. I'd assume you did
> the editing you mention below in the same file, so it's of course
> reasonable if you therefore could only share the one file used for the
> second batch after editing.
> - The mail the poll supervisor gets with the subject like "CIVS poll
> created: <poll name>" so that I can look at the control panel. The mail
> says you should keep it private so nobody can interrupt with the poll in
> progress. The vote is over, results known and a lockfile set so nothing can
> happen anymore to the vote.
>
>
> > Just as as remark, YOU are running the voting system, and have access to
> infra, so YOU can check it.
> >
>
>
> > The answer is simple, Linjie Fu has had several emails in use, (one with
> and one without justin) and one of them is bouncing. I remembered that
> after sending the first batch, so I added it back, knowing that he/she
> could only vote once.
> > Same reason for Ruiling Song who has both an Intel and a gmail email.
> > Finally, in the emails, there was REDACTED FOR GDPR/PRIVACY. It was
> probably the reason.
>
> This is not completely clear to me so let me ask for clarification here as
> well.
>
> The logfile (attached) says:
> The first batch sent out were 53 mails (from 10:11:19 to 10:12:20)
> The second batch sent out were 53 mails (from 10:16:20 to 10:16:48)
> One single mail was sent (at 12:55:40)
> In the end, the counter is at 54.
> In the end, you named 51 distinct people.
>
> So the first batch must have been 53 distinct mail addresses, raising the
> counter from 0 to 53.
> The second batch must also have contained 53 distinct mail addresses
> because 53 mails have been sent.
> After the second batch, the counter must have been at 53 or 54 already,
> depending on wether or not the one single mail that was sent afterwards was
> already in one of the batches or yet another distinct mail address
> (counter++).
>
> What I understand from your simple answer, is you changed two mail
> addresses in between batch one and two (Linjie & Ruiling).
> That would have risen the counter from 53 to 55 after sending the second
> batch because the two corrected addresses are distinct and counted.
> Depending on wether or not the one single mail that was sent afterwards
> was already in one of the batches or yet another distinct mail address
> (counter++),
> the counter would have to be 55 or 56.
>
> Can you clarify what mail addresses you changed from what into what
> between batch one and batch two?
> Can you clarify if the single mail that was sent afterwards was already in
> one of the batches or yet another distinct mail address?
>
>
Thank you for officially killing project.


>
> >
> > And that's why you see 3 more emails than names. And that cannot change
> anything to the vote.
> >
> > jb
> >
>
> -Thilo_______________________________________________
> 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".

  parent reply	other threads:[~2023-11-12 14:02 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
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 [this message]
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=CAPYw7P46GcbsDPeT1xQbMEsQbawygQ7g15kpt83XeAWOO+8MfA@mail.gmail.com \
    --to=onemda@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=thilo.borgmann@mail.de \
    /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