Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Derek Buitenhuis <code@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH] doc/community: Update Community Committee section to reflect reality (PR #20224)
Date: Tue, 12 Aug 2025 16:06:21 +0300 (EEST)
Message-ID: <20250812130621.DD2E068CC6E@ffbox0-bg.ffmpeg.org> (raw)

PR #20224 opened by Derek Buitenhuis (dwbuiten)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20224
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20224.patch

It is not functional nor extant.

The members do not respond, enforce, or do anything. One actively ignores it on purpose.

I have sent *nine* emails to the CC since 25 July about the same individual, with the exact email they've sent included. Total radio silence. The individual in question continues to harass people.

I was told if I wanted the CC to enforce its own rules, I needed to notify them of problematic emails, but it seems to be routed to `/dev/null`.

So, update the docs to reflect the reality: There are no rules, and you are free to harass anyone.


From 93edc3cb01156cdbb148c238e7ef59e4675022a7 Mon Sep 17 00:00:00 2001
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
Date: Tue, 12 Aug 2025 13:58:29 +0100
Subject: [PATCH] doc/community: Update Community Committee section to reflect
 reality

It is not functional nor extant.

Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
---
 doc/community.texi | 17 -----------------
 1 file changed, 17 deletions(-)

diff --git a/doc/community.texi b/doc/community.texi
index 97a49f15ed..93330f362f 100644
--- a/doc/community.texi
+++ b/doc/community.texi
@@ -132,23 +132,6 @@ The decision from the TC should be published with a summary of the reasons that
 
 The decisions from the TC are final, until the matters are reopened after no less than one year.
 
-@anchor{Community Committee}
-@chapter Community Committee
-
-The Community Committee (CC) is here to arbitrage and make decisions when inter-personal conflicts occur in the project. It will decide quickly and take actions, for the sake of the project.
-
-The CC can remove privileges of offending members, including removal of commit access and temporary ban from the community.
-
-Decisions made by the CC can be re-opened after 1 year or by a majority vote of the General Assembly. Indefinite bans from the community must be confirmed by the General Assembly, in a majority vote.
-
-The CC is elected by the General Assembly for a duration of 1 year, and is composed of 5 members. Members can be re-elected if they wish. A majority vote in the General Assembly can trigger a new election of the CC.
-
-The members of the CC can be elected from outside of the GA. Candidates for election can either be suggested or self-nominated.
-
-The CC is governed by and responsible for enforcing the Code of Conduct.
-
-The CC can be contacted at <cc@@ffmpeg>.
-
 @anchor{Code of Conduct}
 @chapter Code of Conduct
 
-- 
2.49.1

_______________________________________________
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".

                 reply	other threads:[~2025-08-12 13:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250812130621.DD2E068CC6E@ffbox0-bg.ffmpeg.org \
    --to=code@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