Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: Romain Beauxis <romain.beauxis@gmail.com>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Cc: ga@ffmpeg.org, "Michael Niedermayer" <michael@niedermayer.cc>,
	"Jean-Baptiste Kempf" <jb@videolan.org>,
	"Rémi Denis-Courmont" <remi@remlab.net>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Revoke social media delegation
Date: Sun, 02 Nov 2025 16:06:28 +0000
Message-ID: <9BD9F159-AA9B-4981-9766-3BB1D46473AC@remlab.net> (raw)
In-Reply-To: <CABWZ6OS-NbjKgESi5e2ZH+wgjnOuy5L1Np8gNURZf8prgaPh1g@mail.gmail.com>

Hi,

Le 2 novembre 2025 15:15:13 GMT+00:00, Romain Beauxis <romain.beauxis@gmail.com> a écrit :
>I like what JB is saying here.
>
>Is there a code of conduct or a set of rules for people representing the
>project?

No, and I've seen much more dubious behaviours in that respect. But it seems that any attempt to change the status quo there will cause more drama, so I am not at all convinced that we should change it at the moment.

Better wait for calmer times.

>If so, is there an agreed upon procedure to respond to cases where these
>are not respected?

Yes there is a code of conduct, at least for within FFmpeg.

The Twitter post that people complained about roughly looked like
"git-log | grep Surname
[Empty]"

I don't see a cause for action here under any reasonable code of conduct.

Meanwhile the YouTuber in question seems to have earned himself a reputation for a very large and easily bruised ego. Also they repeatedly called Kieran a "motherfucker" in a public video, something no serious code of conduct would ever tolerate. But obviously we cannot enforce our CoC on YouTube, so that point is moot.

Br,
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-02 16:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-26 15:26 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-26 15:51 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 17:13   ` Michael Niedermayer via ffmpeg-devel
2025-10-26 17:34     ` Kieran Kunhya via ffmpeg-devel
2025-10-26 17:45     ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-29 22:14       ` isellthegood--- via ffmpeg-devel
2025-10-26 16:50 ` Lynne via ffmpeg-devel
2025-10-27  2:22   ` Steven Liu via ffmpeg-devel
2025-10-27 11:22   ` Michael Niedermayer via ffmpeg-devel
2025-10-26 16:54 ` Tomas Härdin via ffmpeg-devel
2025-10-26 17:51   ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-26 18:18     ` Michael Niedermayer via ffmpeg-devel
2025-10-26 22:34     ` James Almer via ffmpeg-devel
2025-10-27 10:03       ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-27 11:12     ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-28 19:27       ` wsbalgotrader--- via ffmpeg-devel
2025-10-28 19:48         ` Nicolas George via ffmpeg-devel
2025-10-29 15:17         ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-30  2:51           ` wsbalgotrader--- via ffmpeg-devel
2025-11-01 12:36       ` Tomas Härdin via ffmpeg-devel
2025-10-26 22:38 ` James Almer via ffmpeg-devel
2025-10-27  1:39   ` Michael Niedermayer via ffmpeg-devel
2025-10-27 21:39     ` James Almer via ffmpeg-devel
2025-10-27 11:26 ` Vittorio Giovara via ffmpeg-devel
2025-10-27 19:53 ` Nicolas George via ffmpeg-devel
2025-10-27 20:59 ` jamessmithswe64--- via ffmpeg-devel
2025-10-27 22:52 ` Jean-Baptiste Kempf via ffmpeg-devel
2025-10-28 14:28   ` softworkz . via ffmpeg-devel
2025-11-02 15:15   ` Romain Beauxis via ffmpeg-devel
2025-11-02 16:06     ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-10-29 15:33 ` worldofmaps--- via ffmpeg-devel
2025-10-29 16:31   ` Nicolas George via ffmpeg-devel
2025-10-29 17:05   ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-29 22:12 ` isellthegood--- via ffmpeg-devel
2025-10-29 22:16 ` isellthegood--- 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=9BD9F159-AA9B-4981-9766-3BB1D46473AC@remlab.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ga@ffmpeg.org \
    --cc=jb@videolan.org \
    --cc=michael@niedermayer.cc \
    --cc=remi@remlab.net \
    --cc=romain.beauxis@gmail.com \
    /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