From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: cc@ffmpeg.org, "Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] FFmpeg "supporters" doxing
Date: Tue, 28 Oct 2025 09:48:24 +0200
Message-ID: <9D06078E-2F3B-44B1-8A81-4E27842B1E46@remlab.net> (raw)
In-Reply-To: <CANJ8oft9csg8HueRKu+FqufgL6HA5a_0cMNFqXkhbo7CHL8gwQ@mail.gmail.com>
Hello all,
It has come to the attention of the FFmpeg Community Council that the owner of the YouTube channel @t3dotgg is being "doxxed". In consideration of the timeline, this is suspected to be an act of retaliation for their recent video "FFmpeg needs to change" and/or other statements.
Many people in the community disagree with him, and some (including myself) have even been upset by the video. That is **NOT** a justification for doxxing.
Such activity is not acceptable or even tolerable in any circumstances. Period. The people involved are not welcome in FFmpeg, and I think that they are in fact not welcome in the broader open-source community. Besides, this sort of action gives us a bad name and is doing us a disservice.
The CC reserves the option to take further action under the FFmpeg CoC.
Thanks for your attention,
Br,
N.B.: This message is my personal opinion, but I doubt that anyone else in the CC will disagree.
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next parent reply other threads:[~2025-10-28 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANJ8oft9csg8HueRKu+FqufgL6HA5a_0cMNFqXkhbo7CHL8gwQ@mail.gmail.com>
2025-10-28 7:48 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-10-28 10:01 ` [FFmpeg-devel] " Jean-Baptiste Kempf 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=9D06078E-2F3B-44B1-8A81-4E27842B1E46@remlab.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=cc@ffmpeg.org \
--cc=remi@remlab.net \
/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