Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
	Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Tue, 9 Sep 2025 10:02:22 +0100
Message-ID: <CABGuwEmAu8ZKyb3-kNg8rao5URT_RgYDCN_E9XqSfxH3C4QSmw@mail.gmail.com> (raw)
In-Reply-To: <20250909081926.GX1079928@pb2>

On Tue, 9 Sept 2025, 09:19 Michael Niedermayer via ffmpeg-devel, <
ffmpeg-devel@ffmpeg.org> wrote:

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

I don't disagree ffmpeg needs funding.

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? Would sponsors really want their funds
going on SDR or game codecs.

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

A goal without a practical way of getting there. Big companies want their
name associated with a project without insanity (paranoid conspiracy
theories largely coming from one person about people in the project, other
companies, the CIA etc).

Kieran

Kieran

>
_______________________________________________
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  9:03 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 ` Kieran Kunhya via ffmpeg-devel [this message]
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

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=CABGuwEmAu8ZKyb3-kNg8rao5URT_RgYDCN_E9XqSfxH3C4QSmw@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    --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