From: Vittorio Giovara <vittorio.giovara-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Revert "Add FUNDING.json"
Date: Tue, 24 Jun 2025 01:14:10 -0400
Message-ID: <CABLWnS-MubRSG0OL4tZTVhsyTyzOCn=FpEudqU4kZsL08DV6zQ@mail.gmail.com> (raw)
In-Reply-To: <20250624011224.GQ29660@pb2>
On Mon, Jun 23, 2025 at 9:12 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:
> 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
>
FWIW I read the message but I thought it was a hoax/joke, not something
that would be committed.
I didn't reply because there are a lot of unanswered questions in the GA
mailing list that are pending a response from you, and it seemed pointless
to add to the pile of ignored emails.
This should never have been committed, please revert.
reverting FUNDING.json will reduce trust by donators in FFmpeg.
What reduces the trust by donors in FFmpeg is the lack of governance and
accountability.
Hope this helps
--
Vittorio
_______________________________________________
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:[~2025-06-24 5:14 UTC|newest]
Thread overview: 9+ 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 [this message]
2025-06-24 5:24 ` Derek Buitenhuis
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
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='CABLWnS-MubRSG0OL4tZTVhsyTyzOCn=FpEudqU4kZsL08DV6zQ@mail.gmail.com' \
--to=vittorio.giovara-at-gmail.com@ffmpeg.org \
--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