From: FLOSS Fund via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org, michael@niedermayer.cc,
thilo.borgmann@mail.de, pal@sandflow.com, stefasab@gmail.com
Cc: FLOSS Fund <info@floss.fund>
Subject: [FFmpeg-devel] Update on your FLOSS/fund application
Date: Tue, 4 Nov 2025 11:45:40 +0530
Message-ID: <CANLjDM2zofEDbZGNHkG3m1bnJtvQ_gYHo-xybsCrm+=RSp0G8Q@mail.gmail.com> (raw)
Dear *FFmpeg*
We are pleased to inform you that *FFmpeg* is being awarded *100,000 USD*
by FLOSS/fund to support its continued development. We deeply appreciate
the work you do and its impact, and are happy to be a small part of
something that all of us derive immense value from.
You can read more about our second tranche, learnings from this year, and
future plans on our anniversary blog post
<https://floss.fund/blog/second-tranche-2025-anniversary/>. Please find the
list of projects that we supported in the first year here
<https://floss.fund/projects/2025/>. From our experience with the previous
tranche, we anticipate taking anywhere between 1-3 months to complete the
disbursal process owing to complexities in cross-border payments and
paperwork. We apologize in advance for any inconvenience this may cause and
appreciate your patience as we work through the process.
The payment will be made out of India, where we are headquartered. The
following modes of payment are available:
- *Wire Transfer*: Please note that as per Indian regulations, we will
require digitally signed copies of a few documents, like Tax Residency
Certificate, Project Development Agreement, an invoice, etc. We’ll share
detailed instructions and copies of the documents required if you opt for a
wire transfer.
- *GitHub Sponsors*: If you prefer to receive sponsorship via the GitHub
Sponsors Program, please ensure that the project is enabled for one-time
sponsorships. We are currently in discussions with the GitHub team to
streamline this process, and we will keep you posted about the progress.
You can read about this in our anniversary blog post
<https://floss.fund/blog/second-tranche-2025-anniversary/>.
Kindly let us know your preferred mode of payment by replying to this
e-mail.
*Public announcements*
If you have a public communications channel or a mailing list, we kindly
request you to consider an announcement of FLOSS/fund’s support with a link
to the floss.fund website. We are relying on word-of-mouth and referrals to
enable projects in the FOSS ecosystem to discover the fund and apply. Here
<https://floss.fund/faq/#what-is-expected-from-a-project-that-receives-funding>
are embeddable badges, in case you would like to add one to your project's
website.
If you have any questions, please feel free to write to us.
Thank you.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-11-04 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CANLjDM2zofEDbZGNHkG3m1bnJtvQ_gYHo-xybsCrm+=RSp0G8Q@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=info@floss.fund \
--cc=michael@niedermayer.cc \
--cc=pal@sandflow.com \
--cc=stefasab@gmail.com \
--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