Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>, Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Mailinglist conduct (was: [EXT] Re: Query from Reuters on XZ, open source, and Microsoft)
Date: Wed, 17 Apr 2024 15:05:28 -0400
Message-ID: <CAEEMt2nDQht+FUFWdjGrMNL6f1PAexxrWKVviqLR-aEz4Q88+g@mail.gmail.com> (raw)
In-Reply-To: <ZhQB+c5Ox288AGaa@phare.normalesup.org>

Nicolas,

On Mon, Apr 8, 2024 at 10:41 AM Nicolas George <george@nsup.org> wrote:

> This, sadly, your ilk has the power to enforce.
>

Some CC members believe it would be helpful for you (and maybe to others)
if we explicitly laid out some ground rules more explicitly, so let us try:
- you are entitled to any opinion or belief you wish to hold. We are no
thought police.
- you are allowed to express non-defamatory versions of these opinions when
it is relevant to the discussion, or in new discussions, on our mailinglist.
- you are explicitly asked to *not* derail ongoing (e.g. technical)
discussions with these opinions where they are not relevant; do not bring
up Libav-vs-FFmpeg history or other us-vs-them conspiracies.

The CC has previously requested that you refrain from such conduct [1].
Therefore, we have decided to remove your mailinglist participation
privilege for 2 weeks.

Yours,
the CC [Ronald, JB & James supporting the decision and Michael dissenting]
(Michael mentioned that he is in favor of pointing out the "negative
interactions" but only for a ban if a further "negative interaction" occurs
after that.)

[1] https://ffmpeg.org//pipermail/ffmpeg-devel/2023-December/318316.html
_______________________________________________
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:[~2024-04-17 19:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 15:51 [FFmpeg-devel] Query from Reuters on XZ, open source, and Microsoft Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 16:38 ` Kieran Kunhya via ffmpeg-devel
2024-04-03 16:42   ` [FFmpeg-devel] [EXT] " Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:26   ` Satter, Raphael (Reuters) via ffmpeg-devel
2024-04-03 19:43     ` Kieran Kunhya via ffmpeg-devel
2024-04-08 11:02     ` Tomas Härdin
2024-04-08 14:40       ` Nicolas George
2024-04-08 17:56         ` Paul B Mahol
2024-04-09 19:08         ` Tomas Härdin
2024-04-17 19:05         ` Ronald S. Bultje [this message]
2024-04-08 18:13   ` [FFmpeg-devel] " Romain Beauxis
2024-04-08 21:29     ` Vittorio Giovara
2024-04-09  3:09     ` Rémi Denis-Courmont
2024-04-09  8:36       ` Nicolas George
2024-04-10  9:27         ` Stefano Sabatini
2024-04-10 13:15           ` Gyan Doshi
2024-04-09 19:05     ` Tomas Härdin
2024-04-09 20:57       ` Romain Beauxis
2024-04-09 23:46         ` Paul B Mahol
2024-04-10  1:43           ` Romain Beauxis
2024-04-10 12:40           ` Ronald S. Bultje
2024-04-10 11:38         ` Tomas Härdin
2024-04-11  1:19         ` Michael Niedermayer
2024-04-11  3:59           ` Vittorio Giovara
2024-04-11  7:27             ` Paul B Mahol
2024-04-17 19:24             ` epirat07

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=CAEEMt2nDQht+FUFWdjGrMNL6f1PAexxrWKVviqLR-aEz4Q88+g@mail.gmail.com \
    --to=rsbultje@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=george@nsup.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