Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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] SDR debate again Was: Re: [RFC] Sponsors & Funding
Date: Tue, 9 Sep 2025 14:02:10 +0200
Message-ID: <20250909120210.GX29660@pb2> (raw)
In-Reply-To: <CABGuwEmAu8ZKyb3-kNg8rao5URT_RgYDCN_E9XqSfxH3C4QSmw@mail.gmail.com>


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

Hi Kieran

On Tue, Sep 09, 2025 at 10:02:22AM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Tue, 9 Sept 2025, 09:19 Michael Niedermayer via ffmpeg-devel, <
[...]

> 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.
> >
> 
> What work though?

> Who decides this?

The FFmpeg Community, and the General Assembly. I think thats the only
option we have.


> Would sponsors really want their funds
> going on SDR or game codecs.

Lets discuss this in this little subthread, because why not

Had my SDR patch been applied, what would have been different ?
1. a few kilobytes of optional source code that affects noone
   because its disabled by default
2. I would have had 3 months more time to work on FFmpeg, which i spend
   arguing over SDR and subsequently spending also less time on FFmpeg
3. Maybe Paul or Anton would still be in FFmpeg
4. I would not have to go over the whole SDR code again and maintain it
   as a plugin (which will take more time away from FFmpeg)

So what did it achieve to block SDR in main ffmpeg git ? please tell me

And why would a company have the same preferrance ? IMO any
good manager will want their employee to be happy and efficiently working.
Not pissing them off, so in fact i expect support in favor
of SDR by many companies.
Not because they care about SDR, but because they care about me working on
the FFmpeg code and SDR has no cost to them.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I do not agree with what you have to say, but I'll defend to the death your
right to say it. -- Voltaire

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

  reply	other threads:[~2025-09-09 12:02 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   ` Michael Niedermayer via ffmpeg-devel [this message]
2025-09-09 12:11     ` [FFmpeg-devel] Re: SDR debate again Was: " 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

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=20250909120210.GX29660@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