From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg at NAB 2024
Date: Sun, 19 Nov 2023 22:46:06 +0100
Message-ID: <20231119214606.GW3543730@pb2> (raw)
In-Reply-To: <CABGuwEnJ-rhMRsxkoCfjWBdruo8+zH6337vCGr-YEyQigoeDMw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1024 bytes --]
On Sun, Nov 19, 2023 at 02:26:22PM +0000, Kieran Kunhya via ffmpeg-devel wrote:
[...]
> I would not find it acceptable for SPI to pay these costs. I do not feel
> donors would want their money spent on a corporate show in Las Vegas.
all SPI refunds must be posted to the mailing list and approved by the
FFmpeg community.
I have 0 clue if anything like this will be posted by anyone. But if its
not, there is no way SPI can pay it and if it is then everyone has an
oppertunity to object.
If theres no consensus to fund something then stefano and me will not
approve it. And SPI will not pay it.
So if a few people are against it and they state that publically in
the corresponding REFUND thread then there is NO way SPI can pay it
I cannot comment on anything else
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-11-19 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 20:37 Thilo Borgmann via ffmpeg-devel
2023-11-01 21:25 ` Derek Buitenhuis
2023-11-19 14:05 ` Derek Buitenhuis
2023-11-19 14:19 ` Derek Buitenhuis
2023-11-19 14:20 ` Derek Buitenhuis
2023-11-19 14:26 ` Kieran Kunhya via ffmpeg-devel
2023-11-19 21:46 ` Michael Niedermayer [this message]
2023-11-19 23:49 ` Kieran Kunhya via ffmpeg-devel
2024-03-31 11:48 ` Derek Buitenhuis
2023-11-01 21:25 ` Kieran Kunhya
2023-11-02 7:58 ` Rémi Denis-Courmont
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=20231119214606.GW3543730@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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