Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] [RFC] Sponsors & Funding
@ 2025-09-09  8:19 Michael Niedermayer via ffmpeg-devel
  2025-09-09  9:02 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
  2025-09-09 11:49 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
  0 siblings, 2 replies; 7+ messages in thread
From: Michael Niedermayer via ffmpeg-devel @ 2025-09-09  8:19 UTC (permalink / raw)
  To: FFmpeg development discussions and patches; +Cc: Michael Niedermayer


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

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.

My suggestion would be:
 - The FFmpeg project should actively seek sponsors and funding.
 - The money would be used for FFmpeg (Maintenance, Development, Infra, Testing, Travel, Research, ...)
 - A fair selection process shall be used by the FFmpeg Community to select what the money is used for, which maximizes FFmpegs future.
 - The money would also be used to hire / employ FFmpeg Developers fulltime or whatever the preferrance of each Developer is.
 - Work / employment shall be preferrentially be given to FFmpeg Developers / FFmpeg community members.
    This preferrance for "FFmpeg Developers / FFmpeg community members" shall be the only preferrance.
    Outside that preferrance, a fair selection process shall be used by the General Assembly which
    only maximizes FFmpegs future.
 - Goals are
    * to provide secure full time employment for every major FFmpeg contributor, who wants to have that.
    * to accelerate growth and improve quality

suggestions ?

should we vote on this and then add it to web or docs ?

thx
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.

[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2025-09-09 16:29 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-09-09  8:19 [FFmpeg-devel] [RFC] Sponsors & Funding 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 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-09-09 12:10   ` Michael Niedermayer via ffmpeg-devel
2025-09-09 16:29     ` Rémi Denis-Courmont via ffmpeg-devel

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