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: Wed, 10 Sep 2025 18:21:56 +0200
Message-ID: <CABGuwEnuwONJ0zCmyDs3Gw0fXp+T2Bd4_T-tDHxh5yDf9C5VFg@mail.gmail.com> (raw)
In-Reply-To: <20250910154845.GZ29660@pb2>

On Wed, 10 Sept 2025, 17:49 Michael Niedermayer via ffmpeg-devel, <
ffmpeg-devel@ffmpeg.org> wrote:

> Hi remi
>
> On Tue, Sep 09, 2025 at 07:29:02PM +0300, Rémi Denis-Courmont via
> ffmpeg-devel wrote:
> > 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.
>
> With souvereign tech fund we had contracts between people, STF and SPI.
>
> SPI did provide for the legal, accounting and paperwork services here.
> We should in fact donate to them for doing that for us. (if we did not yet)
>

SPI is not accountable to the GA.

It's (conveniently) accountable to you and Stefano.

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-10 16:22 UTC|newest]

Thread overview: 10+ 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
2025-09-10 15:48       ` Michael Niedermayer via ffmpeg-devel
2025-09-10 16:21         ` Kieran Kunhya via ffmpeg-devel [this message]
2025-09-10 20:52           ` 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=CABGuwEnuwONJ0zCmyDs3Gw0fXp+T2Bd4_T-tDHxh5yDf9C5VFg@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