Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: FFmpeg has been selected for the 2025 Spotify FOSS
Date: Tue, 30 Dec 2025 01:29:48 +0100
Message-ID: <aVMc_GZDDqvANQ3u@neo> (raw)
In-Reply-To: <CABGuwEn-77YXJysBYMMQiXsTC4VBkqVXX7L0zQQEjmR4L4JA9A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3305 bytes --]

Hi Kieran

On Sun, Dec 28, 2025 at 07:51:45PM +0000, Kieran Kunhya via ffmpeg-devel wrote:
> On Wed, Dec 24, 2025 at 4:56 PM Sara Tazari via ffmpeg-devel
> <ffmpeg-devel@ffmpeg.org> wrote:
> >
> > 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:
> 
> Hello,
> 
> Thank you for your donation!
> Here are my comments (which hopefully are a fair reflection of the
> opinion of the community)
> 
> >    What is the vision for the project?
> 
> FFmpeg aims to play every multimedia file ever made. As a result of
> this goal it is used widely, from both hobbyists encoding their
> personal videos to some of the largest streaming services like
> Youtube, Netflix, X, Spotify etc.
> 
> >    How will these funds go toward supporting the future of the project?
> 
> FFmpeg is written almost entirely by volunteers and so funding is important.
> Funding will be used for:
> 
> Hardware purchases
> Travel to conferences
> Funding development projects
> 
> >    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?
> 
> Many FOSS projects like FFmpeg are developed by volunteers and so
> funding helps pay for day-to-day expenses.
> 
> FFmpeg has received donations from well known names like Spotify,
> Bloomberg and Zerodha and their association helps increase awareness
> of the importance of FFmpeg. It also provides value to these companies
> as it shows they care about the wider open source projects they rely
> upon in their businesses.
> 
> >    What are other ways you think the community and/or companies can better
> >    support open source?
> 
> While we are extremely thankful for the donation from Spotify, there
> continues to be sustainability challenges in open source projects,
> especially with long-term and reliable funding to pay for full-time
> developers. We hope companies can provide dedicated developers and/or
> repeatable funding to pay for this.

well written, better than my draft

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

There will always be a question for which you do not know the correct answer.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

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

      parent reply	other threads:[~2025-12-30  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 15:38 [FFmpeg-devel] " Sara Tazari via ffmpeg-devel
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 [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=aVMc_GZDDqvANQ3u@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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