Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"
Date: Tue, 24 Jun 2025 03:12:24 +0200
Message-ID: <20250624011224.GQ29660@pb2> (raw)
In-Reply-To: <20250623202056.46005-1-derek.buitenhuis@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2206 bytes --]

Hi Derek

You said
"The only mails you'll see from me in the future are code or reviews."

On Mon, Jun 23, 2025 at 09:20:56PM +0100, Derek Buitenhuis wrote:
> This was pushed with outstanding reservations,

there where 2 comments in one mail but no objection
    The first was about SPI and taxes
    The second was about the domain owner of avcodec.org


> with no positive
> affirmation or review from any other devs,

The General Assembly was informed about the donation on the 9th june
and on the 18th about the solution with the json file
as well as my intend to implement this within 48h
that would be the 20th. i waited 3 more days both for members
of the GA as well as the public to comment


> and without a push noticed
> to say it was going to be pushed.

All members of the GA knew i intended to move forward
with this. And they also knew that there was a deadline of june 27th
for this. So everyone knew it would be pushed if theres no objection
because they saw the deadline date


> Further, the wallet is controlled by a single individual, and not
> FFmpeg.

The wallet belongs to the FFmpeg community. And its content, if it ever
has any content. Also belongs to FFmpeg.

It is currently managed by me. Which brings me tax complexities and work.

The wallet can be handed over to the SPI treassurer, if the SPI treassurer
accepts it.
The community can also discuss other ways to manage this wallet, it is
the FFmpeg communities wallet after all.

But the antagonizing and accusational tone of your mail is unacceptable.
Manging this wallet costs time, costs money, means responsibility.
Today alone i spend like 1-2 hours manually verifying the transaction
to connect this thing to the drips network.

reverting FUNDING.json will reduce trust by donators in FFmpeg.

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.

[-- 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".

  reply	other threads:[~2025-06-24  1:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 20:20 Derek Buitenhuis
2025-06-24  1:12 ` Michael Niedermayer [this message]
2025-06-24  4:29   ` Kieran Kunhya via ffmpeg-devel
2025-06-24  5:14   ` Vittorio Giovara
2025-06-24  5:24   ` Derek Buitenhuis
2025-06-24  5:59 ` compn
2025-06-24  6:48   ` Kieran Kunhya 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=20250624011224.GQ29660@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