Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Cc: "Michael Niedermayer" <michael@niedermayer.cc>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Tue, 09 Sep 2025 14:49:39 +0300
Message-ID: <4DFB0E74-15D3-4DFC-94FD-6F675BCE5190@remlab.net> (raw)
In-Reply-To: <20250909081926.GX1079928@pb2>

Hi,

Le 9 septembre 2025 11:19:26 GMT+03:00, Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> a écrit :
>Hi Everyone
>
>The subject of funding and sponsors came up a few times recently.
>
>I think FFmpeg needs a clear guideline on this matter. To avoid
>confusion, to avoid disagreements and to ensure community members
>can point potential sponsors in an aggreed direction without hesitation.

We already went through that before. There are two ways that companies might credibly sponsor an OSS project on a big enough scale to actually hire developers:

1) Developers are hired or contracted independently. This is already happening.

2) A legal entity with clear oversight rules that sponsors can trust and influence collects funding from sponsors and decides whom to pay for what.

AFAIU, several people including you don't want (2), so that's that.

Companies might be willing to sponsor events, hardware, hosting, or just make small donations. They can already do that via SPI. But it is extremely unlikely that they would just give money to the GA, "the community" or whoever Fabrice Bellard happens to trust with FFmpeg.org at a given point in time (currently, you).

And correct if I am wrong but I doubt that the GA members want to handle negotiating compensation, deliverables and deadlines, writing contracts and tracking progress.

To put it another way:
- If you can get sponsored to do maintenance, do it. You don't need to, and shouldn't ask the GA or the community, for anything other than code review.
- If you can't, then you should be pondering why that is, and what can be done about it, not how hypothetical funding should be spent.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  parent reply	other threads:[~2025-09-09 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09  8:19 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-09  9:02 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-09-09 12:02   ` [FFmpeg-devel] SDR debate again Was: " Michael Niedermayer via ffmpeg-devel
2025-09-09 12:11     ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-09-09 11:49 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-09-09 12:10   ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-09 16:29     ` Rémi Denis-Courmont 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=4DFB0E74-15D3-4DFC-94FD-6F675BCE5190@remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    --cc=remi@remlab.net \
    /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