From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Michael Niedermayer <michael@niedermayer.cc>
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
pal@sandflow.com, stefasab@gmail.com,
Thilo Borgmann <thilo.borgmann@mail.de>,
Kieran Kunhya <kieran618@googlemail.com>
Subject: [FFmpeg-devel] Re: Update on your FLOSS/fund application
Date: Sun, 16 Nov 2025 16:00:38 +0000
Message-ID: <CABGuwE=Y4PLJYUPCnBdDiso=SSYksksLJj21R5xuKj96-V-8Lg@mail.gmail.com> (raw)
In-Reply-To: <aRnpwP2W6A3pcty0@neo>
On Sun, 16 Nov 2025, 15:12 Michael Niedermayer, <michael@niedermayer.cc>
wrote:
>
> But theres a lot more. We need some sort of wiki page, call for people
> sending project proposals, I mean we want that money to be used for
> something.
> Or at least i assume we will try to handle this somewhat similar to STF.
> I need to read through this, maybe there are differences
>
To my knowledge there are no requirements for us to do this. It's a
donation.
Also we should allocate some of this to fund merging forks.
>
Sigh...
Kieran
>
_______________________________________________
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-16 16:02 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
2025-11-17 13:08 ` Michael Niedermayer via ffmpeg-devel
2025-11-16 16:00 ` Kieran Kunhya via ffmpeg-devel [this message]
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='CABGuwE=Y4PLJYUPCnBdDiso=SSYksksLJj21R5xuKj96-V-8Lg@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=michael@niedermayer.cc \
--cc=pal@sandflow.com \
--cc=stefasab@gmail.com \
--cc=thilo.borgmann@mail.de \
/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