From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [RFC] Funded Task Ideas
Date: Thu, 30 Oct 2025 20:42:20 +0100
Message-ID: <aQO_nIg5yoqjvt8p@phare.normalesup.org> (raw)
In-Reply-To: <aPDU6cyWwFSGnyzm@neo>
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.
> I certainly can relate to the "no releases" design, and like this too
> But i think FFmpeg is too big to have no releases
There are big projects that have no releases. They have coined “rolling
releases” to spin it as a positive thing.
> 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.
Regards,
-- 
  Nicolas George
_______________________________________________
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-10-30 19:43 UTC|newest]
Thread overview: 12+ 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 [this message]
2025-10-15 14:53 ` Nicolas George via ffmpeg-devel
2025-10-16 11:59   ` 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=aQO_nIg5yoqjvt8p@phare.normalesup.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=george@nsup.org \
    /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