From: "Rémi Denis-Courmont via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: "Rémi Denis-Courmont" <remi@remlab.net>
Subject: Re: [FFmpeg-devel] [PATCH] doc/community: Update Community Committee section to reflect reality (PR #20224)
Date: Sun, 17 Aug 2025 12:19:30 +0300
Message-ID: <2240557.Mh6RI2rZIc@basile.remlab.net> (raw)
In-Reply-To: <20250812130621.B69EA68C155@ffbox0-bg.ffmpeg.org>
Le tiistaina 12. elokuuta 2025, 16.06.21 Itä-Euroopan kesäaika Derek
Buitenhuis a écrit :
> 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.
Who?
> 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.
Did you even read the text you're removing?
The CC has already stated several times that it could do nothing in this
particular case and that it was up to the GA instead, as per the text you are
removing:
"Indefinite bans from the community must be confirmed by the General Assembly,
in a majority vote."
> 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.
For this, complain to the GA, or at least make a clear actionable request to
the CC rather than just quoting mails.
To the extent that this can be blamed on the previous or current CC, vote for
better candidates in December. Don't kill it.
From my standpoint, 2 members who are inactive, one is extremely busy and one
has had to deal with a bunch of different personal issues, and I can't make
decisions alone.
--
德尼-库尔蒙‧雷米
Tapio's place new town, former Finnish Republic of Uusimaa
_______________________________________________
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 parent reply other threads:[~2025-08-17 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250812130621.B69EA68C155@ffbox0-bg.ffmpeg.org>
2025-08-17 9:19 ` Rémi Denis-Courmont via ffmpeg-devel [this message]
2025-08-12 13:06 Derek Buitenhuis
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=2240557.Mh6RI2rZIc@basile.remlab.net \
--to=ffmpeg-devel@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