From: Gyan Doshi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Gyan Doshi <ffmpeg@gyani.pro>
Subject: [FFmpeg-devel] Re: [RFC] Sponsors & Funding
Date: Thu, 11 Sep 2025 13:41:24 +0530
Message-ID: <78cd76c5-7608-4b1c-8d3a-908ea2eda6c1@gyani.pro> (raw)
In-Reply-To: <20250910205251.GA29660@pb2>
On 2025-09-11 02:22 am, Michael Niedermayer via ffmpeg-devel wrote:
> Hi Kieran
>
> On Wed, Sep 10, 2025 at 06:21:56PM +0200, Kieran Kunhya via ffmpeg-devel wrote:
>> 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.
> Lets go down that rabbit hole.
>
> For this subject to make any sense, we need to have the entities
> (GA, the community, myself, stefano) disagree.
>
> I have to point out, that stefano and myself just pass the community
> decissions to SPI, so we will not disagree with the community.
>
> But let us for sake of this rabbit hole, assume, we all disagree.
>
> I say: green
> Stefano says: red
> The community says: blue with 90% majority
> The GA says: black with 90% majority
>
> So what will SPI do ?
> IMHO, SPI will see me and stefano disagree and consequently will check the
> public communication channels and see that the community in public and
> in a verifyable way has choosen: blue
What is the 'community' in this scenario? Who are the members (and who
decides), what is the voting mechanism, who is/are the adjudicators?
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-09-11 8:11 UTC|newest]
Thread overview: 11+ 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
2025-09-10 20:52 ` Michael Niedermayer via ffmpeg-devel
2025-09-11 8:11 ` Gyan Doshi 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=78cd76c5-7608-4b1c-8d3a-908ea2eda6c1@gyani.pro \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@gyani.pro \
/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