From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Vote STF/SPI 2024-02 Date: Sun, 4 Feb 2024 11:11:38 +0100 Message-ID: <CAPYw7P6aS+nQA-ykERvSD4kvCvoe+awbFkiXU8aEof9W6rvMrA@mail.gmail.com> (raw) In-Reply-To: <20240204004231.GM6420@pb2> On Sun, Feb 4, 2024 at 1:42 AM Michael Niedermayer <michael@niedermayer.cc> wrote: > On Sat, Feb 03, 2024 at 04:37:54AM +0100, Michael Niedermayer wrote: > > On Thu, Feb 01, 2024 at 05:29:26AM +0100, Michael Niedermayer wrote: > > > Hi all > > > > > > To do the STF/SPI thing properly, and make sure we do what the > Community wants. > > > We should do this vote: (unless lots of people reply and say we should > skip the vote) > > > (i am also CCing jonatan to make sure the option in the vote actually > ask the GA the > > > right question) > > > > > > The vote description will be as follows: > > > The STF/SPI has suggested us to submit an Application / Scope of work > before their february meeting. > > > There are about 2 weeks left. > > > The minimum grant is 150 000 € > > > The next STF meeting is expected to be in may. If we submit in > february and are not selected > > > we can probably try again in may. Which would increase our chances > > > If we do not submit in february we can probably submit in may. > > > There is no guarantee that money will be available in may, for example > between october 2023 > > > and february 2024 no funds where available AFAIK. > > > Wiki page is here: > https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2024 > > > > > > > > > Option A. The Application and Scope of Work from the WIKI shall be > submitted to STF/SPI before the february 2024 meeting, disagreements in it > shall be decided by the TC. To achieve continuity, submission shall be done > by the same person as previous if possible. > > > > > > Option B. No Application and Scope of Work shall be submitted in > february 2024 > > > > > > > > > This is a RFC, so if you see errors in it please suggest changes > > > > I intend to start the vote in teh next 24h or so. > > Vote started, you should have received a mail if you are in the GA > and you should not have received a mail if you are not in the GA > 50 mails where sent and there are 50 in the script output. > I hope that no messup happened in this vote > > Please Vote! > Never vote for dead project. Controlled by money. > > thx > > [...] > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > The bravest are surely those who have the clearest vision > of what is before them, glory and danger alike, and yet > notwithstanding go out to meet it. -- Thucydides > _______________________________________________ > 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".
next prev parent reply other threads:[~2024-02-04 10:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-01 4:29 Michael Niedermayer 2024-02-01 17:45 ` Vittorio Giovara [not found] ` <686A824A-CF8F-4D38-ADFA-C84362DE866F@cosmin.at> 2024-02-01 17:49 ` Cosmin Stejerean via ffmpeg-devel 2024-02-01 19:13 ` Michael Niedermayer 2024-02-01 19:42 ` Jonatas L. Nogueira via ffmpeg-devel 2024-02-01 21:04 ` Michael Niedermayer 2024-02-01 20:10 ` Rémi Denis-Courmont 2024-02-06 15:14 ` Vittorio Giovara 2024-02-03 3:37 ` Michael Niedermayer 2024-02-03 12:13 ` Stefano Sabatini 2024-02-04 0:42 ` Michael Niedermayer 2024-02-04 10:11 ` Paul B Mahol [this message] 2024-02-11 12:38 ` Michael Niedermayer
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=CAPYw7P6aS+nQA-ykERvSD4kvCvoe+awbFkiXU8aEof9W6rvMrA@mail.gmail.com \ --to=onemda@gmail.com \ --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