From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Funding Proposals
Date: Fri, 23 May 2025 18:33:08 +0900
Message-ID: <CAF_7JxAasNfYtBtoL_3+=D7CMRhxwPnHjuqUROeevP3kHKnpCg@mail.gmail.com> (raw)
In-Reply-To: <CACxOw_bEy0qJ5YOMM38FOiT21Cvh88OR_+DgmzYsUf_NuQ8E4A@mail.gmail.com>
On Fri, May 23, 2025 at 11:38 AM Leo Izen <leo.izen@gmail.com> wrote:
>
> I'm actually quite out of the loop on how to request funding. I've been
> meaning to do it since I'm putting a lot of hours into my EXIF work, and
> still got a bunch more. A lot of code is written but much of it is not
> tested, and that's important.
>
> Can someone explain the process, in a nutshell, along with reasonable
> numbers for requests?
Assuming (a) there is a critical mass of projects and (b) STF funding
is still available, "we" could request such additional funding.
The first step would be to add your request at the following wiki page:
https://trac.ffmpeg.org/wiki/SponsoringPrograms/STF/2025
Recall that STF focuses on maintenance/bug/security fixes.
>
> - Leo Izen (Traneptora)
> _______________________________________________
> 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".
prev parent reply other threads:[~2025-05-23 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 2:38 Leo Izen
2025-05-23 9:33 ` Pierre-Anthony Lemieux [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='CAF_7JxAasNfYtBtoL_3+=D7CMRhxwPnHjuqUROeevP3kHKnpCg@mail.gmail.com' \
--to=pal@sandflow.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