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 17:06:36 +0200
Message-ID: <20250624150636.GT29660@pb2> (raw)
In-Reply-To: <CAG5bCYuDvkiZpab_EQe5cLO6oo=kpgxqgbfFDmf28Vr40XaQLg@mail.gmail.com>


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

Hi Derek

On Tue, Jun 24, 2025 at 06:24:32AM +0100, Derek Buitenhuis wrote:
> On Monday, June 23, 2025, Michael Niedermayer <michael@niedermayer.cc>
[...]
> > The wallet can be handed over to the SPI treassurer, if the SPI treassurer
> > accepts it.
> 
> 
> Did you consult SPI?

There are long discussions between me and SPI about crypto because of this
very donation

This lead to them discussing it on their last meeting and i guess also
internally since then

I suspect that they will have a vote about adding stablecoin donation support
to SPI through stripe on their next meeting. But i dont know this

discussion about them directly managing the wallet would come after that i assume


> 
> 
> 
> > The community can also discuss other ways to manage this wallet, it is
> > the FFmpeg communities wallet after all.
> 
> 
> Should have, before.

Noone stoped anyone from discussing, not before, not now, not tomorrow

also the FF in ffmpeg stands for fast forward.


> 
> 
> >
> > 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
> 
> 
> WTF? 1-2 hr is insane.

yes, i overdid it especially for a wallet with 0$ in it

switched on even debug mode on the ledger and went though 40+ screens
and compared the arguments


-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides

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

  parent reply	other threads:[~2025-06-24 15:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 20:20 Derek Buitenhuis
2025-06-24  1:12 ` Michael Niedermayer
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 14:53     ` Michael Niedermayer
2025-06-24 14:59       ` Kieran Kunhya via ffmpeg-devel
2025-06-24 17:48       ` Vittorio Giovara
2025-06-24 15:02     ` Michael Niedermayer
2025-06-24 15:06     ` Michael Niedermayer [this message]
2025-06-24  5:59 ` compn
2025-06-24  6:48   ` Kieran Kunhya via ffmpeg-devel
2025-06-24  7:28     ` compn
2025-06-24  8:22       ` Kieran Kunhya via ffmpeg-devel
2025-06-25  0:09         ` compn
2025-06-25  0:31           ` Kieran Kunhya via ffmpeg-devel
2025-06-24 14:06   ` softworkz .
     [not found]   ` <CABGuwE=5LbscbsJKi2XQTO31_Pn1459txrtkE1KnjDmGKqOQWA@mail.gmail.com>
2025-06-24 22:14     ` 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=20250624150636.GT29660@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