Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Tue, 09 Sep 2025 19:29:02 +0300
Message-ID: <4675511.LvFx2qVVIh@basile.remlab.net> (raw)
In-Reply-To: <20250909121037.GY29660@pb2>

Le tiistaina 9. syyskuuta 2025, 15.10.37 Itä-Euroopan kesäaika Michael 
Niedermayer via ffmpeg-devel a écrit :
> > 2) A legal entity with clear oversight rules that sponsors can trust and
> > influence collects funding from sponsors and decides whom to pay for
> > what.
> We have that:
> "Software in the Public Interest (SPI) is a non-profit corporation
> registered in the state of New York founded to act as a fiscal sponsor for
> organizations that develop open source software and hardware. Our mission
> is to help substantial and  significant open source projects by handling
> their non-technical administrative tasks so that they aren't required to
> operate their own legal entity."

How does that enable large sponsors to influence what gets done with the money? 
How does that take care of drafting and reviewing contracts? That just takes 
care of fiscal and admin problems. It's great that they do it at all, but it's 
not remotely sufficient in this context.

There is an argument that sponsors should not be allowed that influence. But 
the flip side is that they won't make big donations without it. It's not a 
sufficient condition, but it's essentially necessary.

AFAICT, you would need an actual FFmpeg legal entity with proper legal 
statutes and formal governance, and as part of that governance, a significant 
place for big sponsors. No offense, but you don't strike me as the type of 
person with the expertise and skillset to do set up and run such an 
organisation (me neither).

So maybe let's not waste time and arguing about hypotheticals. Focus on 
funding that you can likely obtain and don't unnecessarily involve the 
community. It's not that complicated:
- do not claim to represent the whole FFmpeg community, just whoever you are,
- do not force features in on the sole basis of funding and/or contract to 
implement them.
(Generic you aimed at everyone and no one in particular)

-- 
Rémi Denis-Courmont
Hagalund ny stad, f.d. Finska republik Nylands



_______________________________________________
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 16:29 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   ` [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 [this message]

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=4675511.LvFx2qVVIh@basile.remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=remi@remlab.net \
    /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