Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Sara Tazari via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Sara Tazari <stazari@spotify.com>
Subject: [FFmpeg-devel] FFmpeg has been selected for the 2025 Spotify FOSS
Date: Mon, 22 Dec 2025 10:38:57 -0500
Message-ID: <CAH5L3QksHft=w5qbvudF=PY_dPALyhwp+fP3=eiPXK0uVvkndA@mail.gmail.com> (raw)

Hi FFmpeg maintainers,

I’m Sara, a member of the open source team at Spotify, along with Dave
Zolotusky, Principal Engineer. In 2022, we started the Spotify FOSS Fund
<https://engineering.atspotify.com/2024/11/congratulations-to-the-recipients-of-the-2024-spotify-foss-fund>
as
a way of giving back to the open source community and to provide
maintainers with funds that will allow them to continue the maintenance of
their projects. Recipients were nominated and voted on by Spotify employees
and selected by an internal committee.

We’re excited to let you know that FFmpeg has been selected as a recipient
of the 2025 Spotify FOSS Fund!

We are in the process of providing you, the maintainers, with 30,000 Euros
to put towards maintaining and continuing the success of FFmpeg. We will be
announcing the winners on our public Spotify channels by the end of January
2026. For the purposes of our announcement, could you provide responses to
any of the following questions:


   -

   What is the vision for the project?
   -

   How will these funds go toward supporting the future of the project?
   -

   What kind of impact do you think FOSS funds have on the open source
   ecosystem in general? Is any amount welcome? In addition to the money, does
   exposure from the fund provide value, as well?
   -

   What are other ways you think the community and/or companies can better
   support open source?


Thank you for your work and congratulations!

Best,

Sara
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

             reply	other threads:[~2025-12-24 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 15:38 Sara Tazari via ffmpeg-devel [this message]
2025-12-28 19:51 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-12-28 20:57   ` Timo Rothenpieler via ffmpeg-devel
2025-12-30  0:29   ` Michael Niedermayer via ffmpeg-devel

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='CAH5L3QksHft=w5qbvudF=PY_dPALyhwp+fP3=eiPXK0uVvkndA@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=stazari@spotify.com \
    /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