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: Tue, 2 Sep 2025 15:10:04 +0200
Message-ID: <20250902131004.GM29660@pb2> (raw)
In-Reply-To: <12730799.O9o76ZdvQC@basile.remlab.net>
[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]
Hi Remi
On Sun, Aug 31, 2025 at 11:53:01AM +0300, Rémi Denis-Courmont via ffmpeg-devel wrote:
[...]
> > And the General Assembly can change the person(s) who control the wallet
> > For example the GA could simply choose any people it wants
> > these people then could make a transaction. for example it could be setup as
> > a 2 of 3 multisig, so that 2 of 3 people have to agree on a transaction.
> >
> > (of course once the GA does that, only these people can make future changes)
> >
> > Currently the wallet is intended to only serve as a intermediate to move
> > money from crypto USDC to USD on SPIs/FFmpeg. This is not a taxable
> > operation here according to the tax adviser i have asked.
>
> Currency conversion is not taxable in some jurisdictions (including mine,
> AFAIK), but then why does it say that this should be limited to small sums?
> Simply, either there is a tax problem and we should not allow it at all, or
> there is no tax problem at all.
Simple awnser: because iam not 100% sure
Long awnser:
I had asked a tax expert about forwarding USDC from the etherium foundation grant
to SPI stripe,
But he was quite busy that moment, so the advice that its "ok" doesnt give me 100%
confidence.
Id like an actual transaction with a "small" sum to happen (and this
requires SPI to accept USDC by some means first).
And then have that tax expert look at that specific case and confirm.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
[-- 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
prev parent reply other threads:[~2025-09-02 13:10 UTC|newest]
Thread overview: 9+ 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
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 [this message]
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=20250902131004.GM29660@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