Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming vote: extra members for GA
Date: Thu, 9 Nov 2023 17:21:12 +0100
Message-ID: <20231109162112.GX3543730@pb2> (raw)
In-Reply-To: <169953247356.11195.1507797262881301434@lain.khirnov.net>


[-- Attachment #1.1: Type: text/plain, Size: 3001 bytes --]

On Thu, Nov 09, 2023 at 01:21:13PM +0100, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2023-11-09 12:55:25)
> > On Thu, Nov 09, 2023 at 10:44:12AM +0100, Anton Khirnov wrote:
> > > As nobody expressed a preference, the vote will start next Monday
> > > (2023-11-13). It should run for a week, and will be followed by TC/CC
> > > elections.
> > > 
> > > The only extra GA candidate I see proposed so far is Ronald. If anyone
> > > wants to suggest further people, please do so in this thread ASAP.
> > 
> > IMHO the question of the relation of the list of people who could vote
> > in the last GA vote and the people who where in the general assembly
> > in 2020 should be awnsered before further votes.
> > https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316609.html
> 
> As far as I can tell, the voter list in the last vote should be the same
> as the GA from 2020, except for the extra members whose voting rights
> expire after 2 years.
> 
> Do you dispute that? 

There are at least 3 issues here

* The first and maybe the biggest, is that our vote superviser can reply to
  mails within 20min (like in this thread here) but is not replying to a simple
  question within days where the list of voters comes from he used and how it
  relates to the 2020 GA. It gives one the feeling he has some sort of
  difficulty with awnsering that question
  you took a guess here and replied, and i appreciate that. But really JB
  choose this list and also the one in 2020. Only he can explain where these
  lists come from and how they relate.
* The 2nd issue is that there are rules how to change the GA over time
  like that after 2 years there needs to a confirmation AND that the
  other members represent the "active" developers in the last 36 months.
  I can see an argument to leave the 2020 GA untouched and use it as is
  I can also see an argument to update it, and exactly this was done in a
  vote in 2021 by JB. Now we are here trying the 3rd variant of applying
  only half the rules.
  But whats more so, we actually are not. What you are doing here is
  looking at what happened and trying to rationalize it, trying to find
  an explanation for the list. Not stating upfront what this list is
  IMO this is not acceptable for a vote. Uhm we found this list, lets see
  where that might have come from ....
* I know for a fact that at least zane was not in the 2020 GA as i talked
  with him and i know he did cast a vote in 2023 because again he told me.
  So even if you partially apply the rules these lists do not match

will write a seperate reply to the 2nd part of your mail

[...]

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-09 16:21 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05  9:24 Anton Khirnov
2023-11-05 19:57 ` Ronald S. Bultje
2023-11-05 23:25   ` James Almer
2023-11-05 23:39     ` Ronald S. Bultje
2023-11-09  9:44 ` Anton Khirnov
2023-11-09 11:55   ` Michael Niedermayer
2023-11-09 12:11     ` Vittorio Giovara
2023-11-09 15:40       ` Michael Niedermayer
2023-11-09 16:39         ` Vittorio Giovara
2023-11-09 12:14     ` Jean-Baptiste Kempf
2023-11-09 12:21     ` Anton Khirnov
2023-11-09 12:24       ` James Almer
2023-11-09 12:28         ` Anton Khirnov
2023-11-10 12:50           ` Reimar Döffinger
2023-11-10 10:57         ` Hendrik Leppkes
2023-11-09 16:21       ` Michael Niedermayer [this message]
2023-11-09 16:36         ` Jean-Baptiste Kempf
2023-11-09 17:24           ` Michael Niedermayer
2023-11-09 17:31             ` Jean-Baptiste Kempf
2023-11-09 17:50               ` Michael Niedermayer
2023-11-09 18:09                 ` Thilo Borgmann via ffmpeg-devel
2023-11-10 11:33               ` Michael Niedermayer
2023-11-10 12:39                 ` Kieran Kunhya via ffmpeg-devel
2023-11-10 13:04                   ` Thilo Borgmann via ffmpeg-devel
2023-11-11 23:45                   ` Michael Niedermayer
2023-11-11 23:49                     ` Kieran Kunhya
2023-11-11 23:59                     ` Kieran Kunhya via ffmpeg-devel
2023-11-09 17:06         ` Anton Khirnov
2023-11-09 17:39           ` Michael Niedermayer
2023-11-09 18:12             ` Anton Khirnov
2023-11-09 18:50               ` Michael Niedermayer
2023-11-09 19:15                 ` Anton Khirnov
2023-11-09 22:01                   ` Michael Niedermayer
2023-11-09 17:39           ` Kieran Kunhya via ffmpeg-devel
2023-11-09 16:50       ` Michael Niedermayer
2023-11-09 17:04         ` Rémi Denis-Courmont
2023-11-09 17:41           ` Michael Niedermayer
2023-11-09 17:53             ` Rémi Denis-Courmont
     [not found]               ` <2D211056-1560-4869-9279-7CEC9BA25AC4@cosmin.at>
2023-11-09 18:11                 ` Cosmin Stejerean via ffmpeg-devel
2023-11-09 18:38                   ` Rémi Denis-Courmont
2023-11-09 18:15               ` Michael Niedermayer
2023-11-09 18:34                 ` Anton Khirnov
2023-11-09 18:41                 ` Martin Storsjö
2023-11-09 19:30                 ` Jean-Baptiste Kempf
2023-11-09 20:17                   ` Michael Niedermayer
2023-11-09 20:27                     ` Anton Khirnov
2023-11-09 22:45                     ` Vittorio Giovara
2023-11-09 22:49                   ` Michael Niedermayer
2023-11-09 22:58                     ` Jean-Baptiste Kempf
2023-11-10 11:06                       ` Michael Niedermayer
2023-11-10 13:16                       ` Michael Niedermayer
2023-11-10 13:37                         ` Jean-Baptiste Kempf
2023-11-11  2:24                       ` Michael Niedermayer
2023-11-11  3:06                         ` James Almer
2023-11-11 17:28                           ` Michael Niedermayer
2023-11-11 18:02                             ` Paul B Mahol
2023-11-11 18:40                               ` James Almer
2023-11-11 18:25                             ` Anton Khirnov
2023-11-12 17:14                               ` Michael Niedermayer
2023-11-12 17:53                                 ` Anton Khirnov
2023-11-10 10:54           ` Hendrik Leppkes
2023-11-10 12:24             ` Rémi Denis-Courmont
2023-11-10 19:31               ` Michael Niedermayer
2023-11-10 19:42                 ` Martin Storsjö
2023-11-10 19:50                   ` Michael Niedermayer
2023-11-10 20:21                 ` Vittorio Giovara
2023-11-09 12:45     ` Paul B Mahol
2023-11-09 22:00     ` Alexander Strasser
2023-11-10  0:18       ` James Almer
2023-11-10 10:41     ` Tobias Rapp

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=20231109162112.GX3543730@pb2 \
    --to=michael@niedermayer.cc \
    --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