From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg Community Committee – Updates & Next Steps
Date: Fri, 28 Feb 2025 20:27:12 +0100
Message-ID: <20250228192712.GU4991@pb2> (raw)
In-Reply-To: <CAAhd_PVhT12oJ6o4=Gxs3ye_A2jURVKbxOrmzoQPcGAdGC-RTw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2054 bytes --]
Hi Marth64
On Thu, Feb 27, 2025 at 05:00:30PM -0600, Marth64 wrote:
> Hi Michael,
>
> Thanks for the reply & thoughts.
>
> To clarify on "internal panel" and "structured issue resolution", this
> is with regards to unresolved complaints sent to CC, such as publicly
> or privately reported interpersonal/CoC issues.
> Some high ticket items directed to the CC from last year remain
> unaddressed and we were elected to be accountable for this, so we have
> to move forward in some way.
> There are tough problem statements to unpack and it is not always simple.
The mandate of the CC is 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 has ignored the mobbing from 2 developers
In fact it has blocked moderators from helping.
(not even mentioning the wasted time, blocking of STF 2025,
delays in security fixes, ...) that where conseuqences of that
This went on for 2-3 months and one can easily write dozends of independant
complaints. But given that some hostility came directly from a CC member.
And the CC did little. Few complaints where actually submitted.
So what is this all now about exactly ?
It smells like some complaint will be used as pretext for the CC to extend
its mandate.
Something like "Theres a interpersonal conflict related to FFmpeg funds,
now the CC can write an oppinon on funds"
And a disagreement on funds isnt a interpersonal conflict in the first place
Whatever the exact cases this is about, it will take time away
from FFmpeg development. Even if we just have to go over
the past 4 months of debates and mails again and argue about it again
I just dont understand what this is supposed to be good for
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The difference between a dictatorship and a democracy is that every 4 years
the population together is allowed to provide 1 bit of input to the government.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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 prev parent reply other threads:[~2025-02-28 19:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 23:04 Marth64
2025-02-26 1:51 ` Michael Niedermayer
2025-02-26 14:22 ` Vittorio Giovara
2025-02-26 22:33 ` Kieran Kunhya via ffmpeg-devel
2025-02-26 23:11 ` Jean-Baptiste Kempf
2025-02-27 18:18 ` Michael Niedermayer
2025-02-27 22:41 ` Vittorio Giovara
2025-02-28 7:13 ` compn
2025-02-28 13:48 ` Vittorio Giovara
2025-02-27 23:00 ` Marth64
2025-02-28 19:27 ` Michael Niedermayer [this message]
2025-02-28 20:35 ` Vittorio Giovara
2025-02-28 19:29 ` Michael Niedermayer
2025-03-02 10:16 ` Rémi Denis-Courmont
2025-02-26 23:51 ` James Almer
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=20250228192712.GU4991@pb2 \
--to=michael@niedermayer.cc \
--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