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] [RFC] Sponsors & Funding
Date: Tue, 9 Sep 2025 10:19:26 +0200
Message-ID: <20250909081926.GX1079928@pb2> (raw)
[-- 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
next reply other threads:[~2025-09-09 8:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:19 Michael Niedermayer via ffmpeg-devel [this message]
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
2025-09-10 15:48 ` Michael Niedermayer via ffmpeg-devel
2025-09-10 16:21 ` Kieran Kunhya via ffmpeg-devel
2025-09-10 20:52 ` Michael Niedermayer via ffmpeg-devel
2025-09-11 8:11 ` Gyan Doshi via ffmpeg-devel
2025-09-11 22:26 ` Michael Niedermayer via ffmpeg-devel
2025-09-12 0:13 ` Kieran Kunhya via ffmpeg-devel
2025-09-12 6:41 ` Gyan Doshi via ffmpeg-devel
2025-09-12 16:06 ` Michael Niedermayer via ffmpeg-devel
2025-09-28 10:54 ` Michael Niedermayer via ffmpeg-devel
2025-09-28 11:31 ` Kieran Kunhya 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=20250909081926.GX1079928@pb2 \
--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