Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] AG (GA?) VOTE
Date: Tue, 10 Oct 2023 14:32:57 +0200
Message-ID: <169694117745.6638.18128071000996447834@lain.khirnov.net> (raw)
In-Reply-To: <20231010115645.GE3543730@pb2>

Quoting Michael Niedermayer (2023-10-10 13:56:45)
> Hi all
> 
> a vote on the General Assembly composition was apparently initiated with
> a duration of 6 days, i saw this in my inbox:
> "1009 23:49 Jean-Baptiste K (3,4K) Poll: FFmpeg AG members rules"
> 
> There was no real prior discussion on the mailing list about this.
> There are 2 choices which are similar
> (update the list before each vote and update it twice a year)
> And a 3rd option that is probably not what the "opposition" wants I think
> (use the 2020 version, never update)

"opposition"?
Who is this opposition, who are they opposed to, and why the scare quotes?

> First its neccessary to give the community a chance to discuss the GA composition
> choices, collect suggestions and then do a vote

The community did have the chance to discuss this. The point was raised
at VDD over 2 weeks ago, at the developer meeting you participated in.
You even commented on this specific point.

Then a summary of the meeting (including the intent to have a vote on
this) was sent to this mailing list. If there was no discussion then
perhaps it was because nobody was interested in discussing it.

> Now iam quite unprepared to really suggest something as i also didnt think about this
> much or expect this vote now but at least something like
> * keep everyone who had vote rights but add active developers each jan/july
> 
> Is a more honest choice for the "opposition" than "never update"

Why did you not suggest this choice before? You had more than two weeks
to do so.

> But hey why this matters, you might ask ?
> just recently we discussed having the domain be controlled by the GA
> now someone started a vote with no prior discussion on the ML (there was discussion in VDD only)
> basically only one real option to choose and 6 days duration.
> You might be happy with this specific change here in this case but
> This is one reason why I was so scared in relation to the GA controlling
> the domain. The GA composition is a dynamic thing with the way its setup
> currently and with this, can easily become very different from what anyone
> expects.
> This year you spend all your time in FFmpeg and are part of the GA, next
> someone else makes all decissions about FFmpeg and you have no vote in it.
> 
> ABout this vote, I think this vote should be paused and proper disscussion
> should start, IF there is a need to do this vote now.
> Debian uses 2 weeks minimum discussion and 2 weeks voting IIRC so thats a
> start point for important votes like this one.
> For unimporatnt things (like SDR) something like a 7 day vote if noone minds
> should be fine but for things critical to FFmpegs decission making, i do not
> think these should be rushed.

I see no reason to pause anything. There were over two weeks to discuss
this point.

-- 
Anton Khirnov
_______________________________________________
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-10-10 12:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 11:56 Michael Niedermayer
2023-10-10 12:32 ` Anton Khirnov [this message]
2023-10-10 12:58   ` Michael Niedermayer
2023-10-10 13:33     ` Anton Khirnov
2023-10-10 17:02       ` Michael Niedermayer
2023-10-10 13:21   ` Michael Niedermayer
2023-10-10 13:38     ` Anton Khirnov
2023-10-10 17:33       ` Michael Niedermayer
2023-10-24 21:28         ` Anton Khirnov
2023-10-10 12:42 ` Jean-Baptiste Kempf
2023-10-10 12:44   ` Jean-Baptiste Kempf
2023-10-10 13:04   ` Michael Niedermayer
2023-10-10 14:05 ` Derek Buitenhuis
2023-10-10 14:09   ` James Almer
2023-10-10 14:23     ` Derek Buitenhuis
2023-10-10 14:42     ` Nicolas George
2023-10-10 14:54       ` James Almer
2023-10-10 15:16         ` Zhao Zhili

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=169694117745.6638.18128071000996447834@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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