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: [RFC] Funded Task Ideas
Date: Sun, 2 Nov 2025 00:09:34 +0100
Message-ID: <aQaTLkBDv7rIbeFe@neo> (raw)
In-Reply-To: <aQO_nIg5yoqjvt8p@phare.normalesup.org>
[-- Attachment #1.1: Type: text/plain, Size: 3274 bytes --]
Hi Nicolas
On Thu, Oct 30, 2025 at 08:42:20PM +0100, Nicolas George via ffmpeg-devel wrote:
> Hi.
>
> Michael Niedermayer via ffmpeg-devel (HE12025-10-16):
> > I like that this would result in a steady income stream.
> > I think its a good idea, and iam happy to provide companies with
> > extended security support on old releases.
>
> I think it is naïve for nerds like us to expect being able to interact
> with companies and coming out ahead. They would sic their lawyers on us
> to make sure they have warranties that we deliver what they want.
We have people in the community who have experience with company stuff
[...]
> > I mean, We have companies who want releases (cant say who and what
> > exactly because its non public info)
> > These companies will pay for releases, so someone will continue making
> > releases. Its better if that someone is us, better for the quality of
> > releases and better for our income
>
> Why should we care if the releases are good if we do not slap our names
> on them?
>
> The core of the issue is that FFmpeg is a Libre Software project, not an
> Open Source project: it is before anything else the work of people in
> their free time to make beautiful code, not the work of a company that
> is planning to eventually turn a profit. This is important also for our
> own freedom to experiment, to write code differently, to take the risk
> of failing.
>
> What you propose effectively turns FFmpeg into a company in all but
> legal status. That would be detrimental to our freedom to experiment,
> and eventually to the quality of the code. Not counting being halfway
> between two status, i.e. getting the problems of both.
I care about money, so i dont have to care about money
You can either
A. work 40h a week to make enough money to live and use the remaining time to
build beautifull code
B. be rich enough so you can fulltime build beautifull code
C. work 40h a week building beatifull code
We want to achieve something between B and C here
If we can get about 2M$ / year in donations then maintaince of FFmpeg can be
funded.
Why do we want to fund it ? Because we need more manpower, we need people spending
more time working on FFmpeg.
If you can make it happen without $, please do
How unrealistic is funding some of the maintaince ?
Lets do a quick check, almost everyone on this planet uses FFmpeg in some form
(youtube alone has ~3 billion users)
imagine each of youtubes users gives FFmpeg 1 cent once in their life
instant 30million $
invest in S&P500, subtract inflation you get a fresh 2M$ each year.
While this is a thought experiment, if everyone who used FFmpeg gave us 1 cent
once in their life we could fund FFmpegs maintaince indefinitly. With zero
requiremets, we would be 100% free to choose what to work on.
Above is not a plan, its just to show the scale of what we need.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary, page 1
"Used only once" - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."
[-- 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 prev parent reply other threads:[~2025-11-01 23:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 2:40 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 19:16 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-14 20:35 ` Michael Niedermayer via ffmpeg-devel
2025-10-14 22:28 ` Timo Rothenpieler via ffmpeg-devel
2025-10-14 22:52 ` Michael Niedermayer via ffmpeg-devel
2025-10-15 4:39 ` Kieran Kunhya via ffmpeg-devel
2025-10-15 8:31 ` Nicolas George via ffmpeg-devel
2025-10-16 9:28 ` Kieran Kunhya via ffmpeg-devel
2025-10-16 11:20 ` Michael Niedermayer via ffmpeg-devel
2025-10-30 19:42 ` Nicolas George via ffmpeg-devel
2025-11-01 23:09 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-10-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59 ` Michael Niedermayer via ffmpeg-devel
2025-11-01 23:38 ` Niklas Haas via ffmpeg-devel
2025-11-02 0:50 ` Timo Rothenpieler via ffmpeg-devel
2025-11-02 2:09 ` 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=aQaTLkBDv7rIbeFe@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