Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Thilo Borgmann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Thilo Borgmann <thilo.borgmann@mail.de>
Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote
Date: Thu, 26 Oct 2023 12:59:28 +0200
Message-ID: <8159f596-934e-460f-af14-a504511b94c7@mail.de> (raw)
In-Reply-To: <AS8P250MB0744C111427FAF5BD0EB27BD8FDDA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>

Am 26.10.23 um 12:57 schrieb Andreas Rheinhardt:
> Thilo Borgmann via ffmpeg-devel:
>> Hi,
>>
>> Am 24.10.23 um 23:15 schrieb Anton Khirnov:
>>> Hi all,
>>> as discussed at the dev meeting at VDD, we need to have a series of
>>> votes, the first of which concerns defining when is the GA voter list to
>>> be updated.
>>>
>>> As the previous attempt to vote on this was hampered by email delivery
>>> issues, and also criticized due to inadequate advance announcement, the
>>> vote was closed and we are going to try again.
>>>
>>> This time, to avoid any confusion, let me clearly state that this is a
>>> declaration of intent to initiate a GA vote next Monday (2023-10-30),
>>> unless there are substantial objections.
>>>
>>> The vote question will be:
>>>      How do we update the list of active members of the general assembly?
>>>
>>> Proposed possibilities so far are:
>>> * twice a year (1st Jan & 1st July)
>>>     (suggested at VDD)
>>> * before each vote
>>>     (suggested at VDD)
>>> * never (keep the 2020 version)
>>>     (suggested at VDD)
>>> * keep everyone who had vote rights but add active developers each
>>> jan/july
>>>     (suggested by Michael on the ML)
>>>
>>> Feel welcome to propose additional possibilities until Friday
>>> 2023-10-27.
>>>
>>> Other constructive comments also welcome.
>>>
>>
>> To test the voting beforehand this time, I created a test vote with a
>> fake-GA member list. All of the following people should have received a
>> corresponding mail. If you are part of this list, but did not receive an
>> email, check your spam folder for the sender: ffmpeg.voting@mail.de.
>> Please comment if you didn't get the mail.
>>
>> The list is as follows:
>>
>> andreas.rheinhardt@gmail.com
> 
> Please use my outlook mail address.

I used what is given by tools/general_assembly.pl.
I think you just need to patch your .mailmap entry.


>> andriy.gelman@gmail.com
>> anton@khirnov.net
>> barryjzhao@tencent.com
>> ceffmpeg@gmail.com
>> cus@passwd.hu
>> dcnieho@gmail.com
>> derek.buitenhuis@gmail.com
>> dev@lynne.ee
>> devin.heitmueller@ltnglobal.com
>> epirat07@gmail.com
>> ffmpeg@gyani.pro
>> george@nsup.org
>> git@haasn.dev
>> haihao.xiang@intel.com
>> jamrial@gmail.com
>> jan.ekstrom@24i.com
>> jdek@itanimul.li
>> jianhua.wu@intel.com
>> lance.lmwang@gmail.com
>> leo.izen@gmail.com
>> linjie.justin.fu@gmail.com
>> liuqi05@kuaishou.com
>> martin@martin.st
>> michael@niedermayer.cc
>> nuomi2021@gmail.com
>> onemda@gmail.com
>> pal@palemieux.com
>> philipl@overt.org
>> pross@xvid.org
>> rcombs@rcombs.me
>> remi@remlab.net
>> shubhanshu.e01@gmail.com
>> softworkz@hotmail.com
>> stefasab@gmail.com
>> sw@jkqxz.net
>> thilo.borgmann@mail.de
>> timo@rothenpieler.org
>> u@pkh.me
>> vittorio.giovara@gmail.com
>> wenbin.chen@intel.com
>> yejun.guo@intel.com
>> zane@zanevaniperen.com
>> zhilizhao@tencent.com
>>
>>
> 
> _______________________________________________
> 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".

  reply	other threads:[~2023-10-26 10:59 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 21:15 Anton Khirnov
2023-10-25 13:14 ` Thilo Borgmann via ffmpeg-devel
2023-10-25 14:22   ` Rémi Denis-Courmont
2023-10-25 14:23     ` Thilo Borgmann via ffmpeg-devel
2023-10-25 15:52       ` Thilo Borgmann via ffmpeg-devel
2023-10-25 17:39         ` Rémi Denis-Courmont
     [not found]           ` <2CFD7743-D703-4180-9D25-DE993B827ACB@cosmin.at>
2023-10-25 19:25             ` Cosmin Stejerean via ffmpeg-devel
2023-10-25 19:31           ` Thilo Borgmann via ffmpeg-devel
2023-10-26  8:43             ` Thilo Borgmann via ffmpeg-devel
2023-10-25 15:57     ` Ridley Combs via ffmpeg-devel
2023-10-26 10:57   ` Andreas Rheinhardt
2023-10-26 10:59     ` Thilo Borgmann via ffmpeg-devel [this message]
2023-10-26 18:58   ` Derek Buitenhuis
2023-10-26 19:35     ` Vittorio Giovara
2023-10-27 11:24   ` Jan Ekström
2023-10-27 12:39     ` Thilo Borgmann via ffmpeg-devel
     [not found]       ` <C3E67DF6-B1F8-41F9-9953-AD61EC528011@cosmin.at>
2023-10-27 18:36         ` Cosmin Stejerean via ffmpeg-devel
2023-10-27 18:36         ` Cosmin Stejerean via ffmpeg-devel
2023-10-29 10:25   ` Thilo Borgmann via ffmpeg-devel
2023-10-25 19:30 ` Michael Niedermayer
2023-10-27  9:09   ` Anton Khirnov
2023-10-27  9:17 ` Anton Khirnov
2023-10-29  9:33 ` Anton Khirnov
2023-10-30  8:18   ` Jean-Baptiste Kempf
2023-10-30 10:33     ` Thilo Borgmann via ffmpeg-devel
2023-10-30 10:50       ` Jean-Baptiste Kempf
2023-10-30 11:16         ` Thilo Borgmann via ffmpeg-devel
2023-11-01 17:19         ` Michael Niedermayer
2023-11-01 22:07           ` Jean-Baptiste Kempf
2023-11-01 23:55             ` Gerion Entrup via ffmpeg-devel
2023-11-03 17:33             ` Michael Niedermayer
2023-11-04 22:36               ` Jean-Baptiste Kempf
2023-11-05 20:49                 ` Michael Niedermayer
2023-11-02 19:53   ` Michael Niedermayer
2023-11-04 17:58     ` Anton Khirnov
2023-11-05 12:18       ` Michael Niedermayer
2023-11-04 17:59   ` Anton Khirnov

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=8159f596-934e-460f-af14-a504511b94c7@mail.de \
    --to=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