From: ff--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ff@hawaiiantel.net
Subject: [FFmpeg-devel] Re: Update on your FLOSS/fund application
Date: Sun, 16 Nov 2025 21:16:03 -0800
Message-ID: <21f14243138cb80d3b632dd07191f2e4@hawaiiantel.net> (raw)
In-Reply-To: <aRn07cvAGV-u7zBb@neo>
On 2025-11-16 07:59, Michael Niedermayer via ffmpeg-devel wrote:
> On Sun, Nov 16, 2025 at 04:12:00PM +0100, Michael Niedermayer via
> ffmpeg-devel wrote:
>> On Sun, Nov 16, 2025 at 01:56:49PM +0000, Kieran Kunhya via
>> ffmpeg-devel wrote:
>> > On Sun, 16 Nov 2025, 05:04 Michael Niedermayer via ffmpeg-devel, <
>> > I could do this if I am given an SPI contact.
>> I think the SPI contact needs to be handled by Stefano and me
>> otherwise we will
>> have confusion and delays. Ill try to get that done today.
> ive sent the floss.fund mail to SPI asking for advice how to proceed
> As said, (on the assumtation that this all works) we will roughly need
> (this is not a hard exact list, just what i think we need)
from what i looked at, floss fund is just going to wire to an account
(our spi account). which means the spi account has to have some beefy
documentation behind it. and SPI has to send that documentation to them.
probably what you should do is just ask spi and floss to contact each
other to set it up. dont really need anyone to do much more else wise.
and since you and stefano are the spi contacts, its up to you two to get
it done.
cheers
-compn
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-17 5:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 6:15 [FFmpeg-devel] " FLOSS Fund via ffmpeg-devel
2025-11-16 5:01 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-16 13:56 ` Kieran Kunhya via ffmpeg-devel
2025-11-16 15:12 ` Michael Niedermayer via ffmpeg-devel
2025-11-16 15:59 ` Michael Niedermayer via ffmpeg-devel
2025-11-17 5:16 ` ff--- via ffmpeg-devel [this message]
2025-11-17 13:08 ` Michael Niedermayer via ffmpeg-devel
2025-11-16 16:00 ` Kieran Kunhya via ffmpeg-devel
2025-11-16 16:08 ` 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=21f14243138cb80d3b632dd07191f2e4@hawaiiantel.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ff@hawaiiantel.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