From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] STF 2025 grant request (2025-09-01 target)
Date: Wed, 30 Jul 2025 21:04:27 +0900
Message-ID: <98056daa-4abb-4c76-aa1c-0b6acd9d7ee3@lynne.ee> (raw)
In-Reply-To: <CAF_7JxCrLnzt6AwPfqO=r-8v0c0q_AigLkC0-6JUPPf95qTA+A@mail.gmail.com>
On 30/07/2025 06:20, Pierre-Anthony Lemieux wrote:
> Hi all,
>
> As with last year, Michael asked me to help coordinate the creation of
> grant request to the STF:
>
> https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2025
>
> The objective remains to unlock funds for individuals that are
> interested in contributing to the FFMPEG codebase.
>
> The proposed deadline for individuals to submit their proposal is
> 2025-09-01. The proposals will be published at the link above upon
> submission.
>
> I am happy to collate the proposals and forward the grant request to
> SPI, who would handle the submission to STF and payments to
> contributors as the case may be. I am also happy to do nothing.
>
> This activity is completely voluntary, there is no guarantee that all
> (or any) proposals will be accepted by SPI and/or STF, and the chances
> of success are unknown (to me). The activity was reasonably successful
> last year.
Could you bump the deadline up and submit them in a week or two? Its
been many months since Michael urged those wanting to apply to do so.
Waiting for a month probably won't result in much, and I'd like to start
working already.
_______________________________________________
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".
prev parent reply other threads:[~2025-07-30 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:20 Pierre-Anthony Lemieux
2025-07-30 12:04 ` Lynne [this message]
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=98056daa-4abb-4c76-aa1c-0b6acd9d7ee3@lynne.ee \
--to=dev@lynne.ee \
--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