From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [PATCH] web: Add funding.json
Date: Fri, 29 Aug 2025 17:15:33 +0200
Message-ID: <20250829151533.GI29660@pb2> (raw)
In-Reply-To: <1d1cc0a2-a53d-4189-8ec2-06cc6aa3e47b@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2017 bytes --]
Hi Derek
On Fri, Aug 29, 2025 at 01:48:07PM +0100, Derek Buitenhuis via ffmpeg-devel wrote:
> On 8/29/2025 2:08 AM, Kieran Kunhya via ffmpeg-devel wrote:
> We'll see if this is pushed without consent like funding.json
> was to the main git repo, which has yet to be removed.
Implying that a funding.json was pushed without consent is unacceptable
The patch was on the mailing list,
Do 19 Jun 2025 21:12:23 CEST Michael Niedermayer <michael@niedermayer.cc> [FFmpeg-devel] [PATCH] Add FUNDING.json
The General Assembly was informed about the potential donation from
the etherum foundation, that needed this FUNDING.json file
Mo 09 Jun 2025 21:30:27 CEST Michael Niedermayer <michael@niedermayer.cc> Donation from the etherium foundation
Mi 18 Jun 2025 23:23:31 CEST Michael Niedermayer <michael@niedermayer.cc> Re: Donation from the etherium foundation
Normally this would call for a private one on one discussion but as you
make these statments in public, it requires a public response.
What you do here is damaging to the FFmpeg project. Including a potential
loss of sponsors. And also very damaging to the Team.
This comes after, you yourself already stated that you would limit yourself
to code and reviews: https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2024-November/336263.html
"The only mails you'll see from me in the future are code or reviews. I
am sure certain community members will appreciate that."
And id like to emphasize, even IF something wrong happened with funding.json
thats a matter to be discussed and resolved privatly.
First with the involved parties, and if that fails with the GA.
None of that happened
Posting such claims in public is damaging to the project and team.
And is completely unacceptable
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Its not that you shouldnt use gotos but rather that you should write
readable code and code with gotos often but not always is less readable
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
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-08-29 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 21:10 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-08-29 1:08 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2025-08-29 12:48 ` Derek Buitenhuis via ffmpeg-devel
2025-08-29 15:15 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-08-29 15:31 ` Derek Buitenhuis via ffmpeg-devel
2025-08-29 17:35 ` Rémi Denis-Courmont via ffmpeg-devel
2025-08-29 20:40 ` Michael Niedermayer via ffmpeg-devel
2025-08-31 8:53 ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-02 13:10 ` Michael Niedermayer via ffmpeg-devel
2025-09-05 15:13 ` Rémi Denis-Courmont 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=20250829151533.GI29660@pb2 \
--to=ffmpeg-devel@ffmpeg.org \
--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