From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [ANNOUNCE] upcoming GA vote Date: Thu, 2 Nov 2023 20:53:46 +0100 Message-ID: <20231102195346.GA3543730@pb2> (raw) In-Reply-To: <169857199222.11195.9532846278486176911@lain.khirnov.net> [-- Attachment #1.1: Type: text/plain, Size: 1509 bytes --] On Sun, Oct 29, 2023 at 10:33:12AM +0100, Anton Khirnov wrote: > Hi all, > updating the answers according to received comments: > > vote question (unchanged): > How do we update the list of active members of the general assembly? > > Available answers: > * twice a year (1st Jan & 1st July, 0:00 UTC); > as an exception, the list will also be updated immediately after this > vote > (suggested at VDD, added time and the exceptional update clause) > * before each vote > (suggested at VDD) This is not well defined https://en.wikipedia.org/wiki/Well-defined_expression "before each vote" is not a single unique point in time First what is meant by "vote", theres a annoucement of some intend to make a vote, there would be a discussion, there could be a 2nd annoucement theres a period where people can propose new options. Then the vote start is announced at some point the actual vote start then also happens. So we have many reference points then "before" is everything before, even a year is "before" and exactly at the time when the vote actually starts is impossible because at that time the list must already be known and entered into the vote system I guess this doesnt matter if the option doesnt win ... thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Its not that you shouldnt use gotos but rather that you should write readable code and code with gotos often but not always is less readable [-- 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".
next prev parent reply other threads:[~2023-11-02 19:53 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 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 [this message] 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=20231102195346.GA3543730@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