* [FFmpeg-devel] The Concept for the CC Installment is broken by Design
@ 2025-03-07 4:36 Soft Works
2025-03-07 4:55 ` Soft Works
2025-03-08 10:50 ` Soft Works
0 siblings, 2 replies; 7+ messages in thread
From: Soft Works @ 2025-03-07 4:36 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Hello everybody,
this is not the kind of e-mail you might be expecting from the title. I think we had enough of those. Nobody will be blamed; nobody will be criticized. This is meant to address everybody equally, specifically not meant to be supportive of those who had brought up doubts about the CC before and it’s also not against those who believe the CC is a reasonable idea. Even less is it about any past or current members of the CC. The error is not on their side.
The Community Committee Concept is broken by Design
===================================================
A BUG REPORT
============
1. Principles of Operation
The core procedure in the CC operations is designed as follows:
- A community member X can file a complaint to the CC about
inappropriate behavior of another user Y
- The CC looks at the case and decides about whether to take certain actions
- The decision and the applied actions are made public
There is hardly any precedent for this type of procedure in democratic countries. It is a fundamental element of justice that a defendant knows who is suing him and that the trial is public. Anonymous tips only have a place when it comes to crimes, but not in civil law.
In companies and other organizations, there are sometimes procedures in place where hints and complaints can be made privately, but in those cases, these are managed and resolved privately, not publicly.
Private accusations followed by public punishment are more common in totalitarian systems.
Experience has shown that such systems lead to high distrust among people. Everybody needs to be careful and watching out continuously for making no mistakes, as anybody could denunciate you for something.
Evaluation in our context:
- Community Members: => loses
(causes bad atmosphere and public appearance)
- Complainer: Neutral
Privacy may sometimes protect the complainer, but in most cases it's obvious anyway, and playing/acting as if it wouldn't be the case, creates an
atmosphere of dishonesty on top of the trouble.
2. Expectations
So, you are upset about another community member that is very unfriendly to you or making accusations and the whole range of bad behavior (and maybe you did similar but think you did right and the other one did wrong).
You heard about the CC and you think it's really time that some action is being taken, so you file a complaint to the CC right away.
But nothing happens. The CC is not like police that you can call. It's rather made up to work as a kind of court, working on one case after another. And when it gets to your case, you might either have forgotten about it already - or waiting really desperately for it to look into the case.
But why did you actually complain at the CC in the first place?
What do you want to achieve? That the other person changes mind? Unlikely to happen. The other person been given a formal warning? Sounds not much exciting neither resolving anything.
What you really want (almost always) is that someone officially says you were right and the other one wrong - which is unlikely to happen as the CC shall aim for equalization, not dividing.
Evaluation: Case 1: CC is in favor of yours
- Defendant: Gets a formal warning issued,
shrugs with his shoulders,
will care about CC even less in the future
- Community: => loses
- Complainer: The CC didn't say you were right,
the defendant doesn't care about the warning
You're frustrated, even though you won
=> loses
Evaluation: Case 2: CC rejects your complaint
- Complainer: Is more frustrated than ever about everything
=> loses
3. Blame
The fact that the CC is set up like a kind of court is one of the primary flaws. You cannot install a kind of court which doesn't have appropriate powers like a court has. Without such powers, nobody will ever respect it in the way that would be needed.
Also, a court cannot have judges elected by the community. Would you want the politicians that you elect be your judge on court? Or some of your friends suddenly being your judge?
Judges need to be neutral - ideally unknown and independent persons. Nobody in the ffmpeg community would qualify for such a position.
But that's what we have: elected community members which were keen and crazy enough to volunteer for such a position.
Evaluation
As a result of the CCs verdict on an issue between two members, there's usually a winning (even if it's a nuance, one would think to have "won").
Now, simple Math:
- Winning Member: Might be happy for a short time
Then realizing that the relationship with the
losing member might have received irreparable damage
=> lose
- Losing Member: Starts hating the Winning member
Starts hating the CC and its members
=> lose
- CC Members: No matter what they do and how they judge
Almost always at least one of the combatants will start
hating (the cc, its members or both)
4. Distrust
But it's not only hatred that is caused by the CC installment (not its members). It has created a high amount of distrust. From what I've read, it's been like that in the last year already and in the past few months it has been a frequently repeating pattern that people have voiced distrust towards the CC, to all of its members or to individual members, often alluding to conspiracies, forming of groups, etc.
Distrust lead to questions about transparency, which actions or consultations should be public or private.
Such distrust is lethal poison for a community. While the CC installment (not its members) is not the only source of distrust, it still takes a substantial part as many conversations in this new year have shown.
Evaluation
- CC Members: => lose
- Community: => lose
5. Verdict: Everybody loses
The CC installment in its current form has turned out to be creating a lose-lose-lose-lose situation.
There are no winners in this game, but it makes all of us lose, if not directly then indirectly at least.
This is doing no good to the community and further damages the public appearance of the project.
Kudos to those who have volunteered to be CC members, you have taken a position where there's nothing much to gain but a lot to lose, and the more you engage, the worse it gets, so it's natural that its members are trying to be careful.
In the first section I said there's nothing like the model we have for the CC when looking at democratic countries, but there's actually something where complaints can be made in-private but punishment is usually public.
I'm talking about kindergarten and elementary school. The difference is that Kids are forgetting and forgiving quickly, but we grown-ups, we keep chewing the same old bone until its broken 😊
When you think about it: that's really what we have: a child-level system applied to grown-ups. I don't think that this is something we need or something that can help this community.
Which benefits does it really provide? Does it have a positive influence on this community? I don't see that, but I see a lot of the opposite.
6. What's needed?
What I see though is which problem it doesn't solve: it doesn't improve much regarding the mailing list. When there's a heated discussion, it's normal in all communities that those are moderated in some form. Since there's so much distrust - maybe an AI based auto moderation could help.
This would allow preventing bad e-mails from being distributed in the first place.
What's for sure at least is that what we have at the moment is totally unsuitable to solve that problem. Instead of preventing the mess early, we are letting it happen, long chains of despicable ML conversations are flowing through the ML system.
And what are we doing then? We are letting people do another endless conversation which criticizes what happened, but does that by repeating the same content once again in another long conversation.
After all this has happened already, we are starting a tribunal where the CC needs to judge about who did say what and what was bad and what not.
Then, warnings are issued (or not), but in either case, everybody is dissatisfied anyway.
So, my conclusion is: the CC is an unsuitable solution to a problem we don't even have, and the way of how its sole existence is negatively impacting the community is alarming IMO.
Let's end this chapter and try to find something that solves the actual problems.
Regards,
sw
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-07 4:36 [FFmpeg-devel] The Concept for the CC Installment is broken by Design Soft Works
@ 2025-03-07 4:55 ` Soft Works
2025-03-07 22:42 ` Marth64
2025-03-08 10:50 ` Soft Works
1 sibling, 1 reply; 7+ messages in thread
From: Soft Works @ 2025-03-07 4:55 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> The core procedure in the CC operations is designed as follows:
>
> - A community member X can file a complaint to the CC about
> inappropriate behavior of another user Y
Erratum: the word "privately" got lost: "..can privately file.."
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-07 4:55 ` Soft Works
@ 2025-03-07 22:42 ` Marth64
2025-03-07 23:56 ` Soft Works
0 siblings, 1 reply; 7+ messages in thread
From: Marth64 @ 2025-03-07 22:42 UTC (permalink / raw)
To: FFmpeg development discussions and patches
You can criticize the CC structure all you want, but I will absolutely
not accept thinly veiled personal attacks, including being called a
child. Your email is condescending and dismissive, completely
disregarding the time and effort that volunteers like myself have put
into this work. I did not volunteer to this role because I was "keen
and crazy enough to" but because I wanted to actually try and make a
difference. Whether or not I have, that is for the people to decide.
But I will not have it being publicly ridiculed and called a "child".
I have been nothing but polite to you and others even if we have
disagreements.
Frankly, beyond this example, you have shown to be generally rude,
gatekeeping to others, and are unpleasant to engage with. You also
seem unaware that not all CC matters are handled publicly.
I have no further comment for you.
Sincerely,
Marth64, without the CC hat.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-07 22:42 ` Marth64
@ 2025-03-07 23:56 ` Soft Works
2025-03-08 0:21 ` Marth64
0 siblings, 1 reply; 7+ messages in thread
From: Soft Works @ 2025-03-07 23:56 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Marth64
> Sent: Freitag, 7. März 2025 23:42
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The Concept for the CC Installment is broken
> by Design
>
> You can criticize the CC structure all you want, but I will absolutely
> not accept thinly veiled personal attacks, including being called a
> child. Your email is condescending and dismissive, completely
> disregarding the time and effort that volunteers like myself have put
> into this work. I did not volunteer to this role because I was "keen
> and crazy enough to" but because I wanted to actually try and make a
> difference. Whether or not I have, that is for the people to decide.
> But I will not have it being publicly ridiculed and called a "child".
> I have been nothing but polite to you and others even if we have
> disagreements.
>
> Frankly, beyond this example, you have shown to be generally rude,
> gatekeeping to others, and are unpleasant to engage with. You also
> seem unaware that not all CC matters are handled publicly.
This was not meant to attack anybody. Neither did I call anybody a child.
By saying "keen and crazy" enough I wanted to express my respect for volunteering for such a role, given the fact that this is all the members of the CC to criticism and accusations.
Everything I had written was about the concept of the CC - ONLY.
Not about any human being.
I don't have any reason to think or say anything bad about you or other members of the CC.
sw
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-07 23:56 ` Soft Works
@ 2025-03-08 0:21 ` Marth64
2025-03-08 1:16 ` Soft Works
0 siblings, 1 reply; 7+ messages in thread
From: Marth64 @ 2025-03-08 0:21 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> I don't have any reason to think or say anything bad about you or other members of the CC.
Then I apologize if I misunderstood. I have no issue hearing criticism
of our structures but the comparison to kindergartners came off the
wrong way.
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-08 0:21 ` Marth64
@ 2025-03-08 1:16 ` Soft Works
0 siblings, 0 replies; 7+ messages in thread
From: Soft Works @ 2025-03-08 1:16 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Marth64
> Sent: Samstag, 8. März 2025 01:22
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] The Concept for the CC Installment is broken
> by Design
>
> > I don't have any reason to think or say anything bad about you or
> other members of the CC.
>
> Then I apologize if I misunderstood. I have no issue hearing criticism
> of our structures but the comparison to kindergartners came off the
> wrong way.
> _______________________________________________
Hi Marth64,
thanks and nevermind. I truly don't want to accuse anybody of anything and at the very least the members of the CC. I know about your intentions to improve the community and totally appreciate that.
I also have no doubts that you have done some good things which haven't become public. It's important to have community members like you who are trying to keep people together.
My criticism is solely on the structure of the CC operations, which is based on many observations I had made during the past months. You - and the members of the CC - are taking your perceived integrity at stakes, solely for taking that role, not even due to any action that was taken. And when you take any (public) actions, some will always think it was wrong or will be dissatisfied. It's really a tough position to fulfil.
My overall impression is that the sole existence of the CC in the current form is more dividing than unifying, no matter what the CC does - and even when it would to nothing at all, the distrust that has emerged wasn't based on anything the CC has done, just about what it might be doing. Similar, the disregarding or CC members like being from this or that "group" or "party", like it had been alluded from various sides recently.
I wanted to illustrate the mechanism of and effects of the CC concept and how it can hardly fulfill the intended purposes in a beneficial way (in total sum) - no matter how good and faithful and passionate the people are who are taking those roles. Or let me put it this way: The CC structure is too much overshadowing the good things you are really intending to do.
The elementary school comparison is intended to illustrate which kind of system we have: making complaints privately and expecting the target being sanctioned publicly - that's not a healthy pattern.
Btw. if you would really want to take it literally, you would be a teacher, not a child, but again, it was really not meant to call anybody a child or anything else, it was meant to make people think about the current system and how much sense it makes for this community.
Best wishes
sw
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [FFmpeg-devel] The Concept for the CC Installment is broken by Design
2025-03-07 4:36 [FFmpeg-devel] The Concept for the CC Installment is broken by Design Soft Works
2025-03-07 4:55 ` Soft Works
@ 2025-03-08 10:50 ` Soft Works
1 sibling, 0 replies; 7+ messages in thread
From: Soft Works @ 2025-03-08 10:50 UTC (permalink / raw)
To: FFmpeg development discussions and patches
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Soft
> Works
> Sent: Freitag, 7. März 2025 05:36
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: [FFmpeg-devel] The Concept for the CC Installment is broken by
> Design
[..]
> The Community Committee Concept is broken by Design
> ===================================================
To be honest - I've been a bit shocked that my message could have been misunderstood so badly, but I hope it has become clear enough how I mean it.
As it is my belief that one should not criticize without offering any suggestions, I want to share my ideas on the subject. I don't have a full-blown concept in all detail, but a number of core elements that could serve as building blocks for a re-design of the current structures.
1. Clear separation of activities
I see two major areas of activity with regards to - let's say - "Community Management"
- Resolution of Interpersonal Conflicts between Members
- Moderation of Public Communications
like on the ML or in a future Git Portal environment
Whether the same persons should be in charge for both of these - I don't think that. It's important to avoid any collisions of interest and put everything on more and different shoulders, with a clear definition of the kind of actions that each activity involves and which not.
2. Resolution of Interpersonal Conflicts between Members
The GA elects 3 "Persons of Trust" => PoTs
The PoTs are working only loosely together.
There are no formal measures (like a "warning") issued, neither publicly nor privately.
All activity remains always and forever private.
When a member is facing an interpersonal issue s/he can contact a PoT of her/his choice.
They discuss the problem and talk about how to proceed, individually, on a case-by-case basis.
The PoT may suggest to involve other PoTs (e.g. like when another PoT has a better relationship with the target person).
The member may agree or may not agree. In the latter case, the contacted PoT will not share any information about the case with the other PoTs.
It may sound somewhat similar at first glance - but it's fundamentally different and eliminates pretty much all of the bad effects that I've laid out in the previous message.
3. Moderation of Public Communications
Core Points:
- Moderation team members should not be well-known persons => people from the GA do not qualify
- Moderation activity is not driven by hints or complaints
- Moderators are working proactively, i.e. they have to read everything and are not acting
on request from others; they must ignore any such requests
- Moderators can issue warnings of different severity levels
A warning includes:
- An amount of warning points
- A number of hours for which the member is blocked from posting/sending.
- Warning points are publicly visible
- Actions of moderators cannot be questioned or disputed
- Moderation activity is public and transparent
except:
- The moderators are working and appearing as a team and this is where
transparency ends: it will never become public which member of the team
has taken a specific action
Thoughts and Ideas
The above is loosely based on the way things are done in our forums. These are moderated very well by volunteers (plus one admin who oversees them). No matter which time of day, I've never seen a spam post surviving more than 10 minutes. The way how warnings are issued is consistent - i.e. not different depending on which of the mods did it.
From that I know that it's normally feasible do it that way. But I'm not sure whether it could work here as well, without causing more dystonia in the community again.
Sentiment analysis has almost become a standard measure for protecting communication these days. That made me wonder whether it might not be a better solution (or one component of a concept) for ML moderation. The problem is that such moderation is rather pointless when it's not done right in the moment when a conversation goes off rails. Blocking members from posting is in such situations is the best and most proven way to avoid escalations. In almost all cases, participants of such conversations will write a different kind of text on the next day than they would have in that moment. That's why instant moderation is an inevitable element IMO.
Those suggestions are not arbitrary. I really don't know why I've spent so much thought on this subject, but almost all the details I mentioned have a specific intention and a match in the range of problems I had described before.
I hope it makes sense to somebody, thanks for reading
sw
_______________________________________________
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".
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2025-03-08 10:51 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-03-07 4:36 [FFmpeg-devel] The Concept for the CC Installment is broken by Design Soft Works
2025-03-07 4:55 ` Soft Works
2025-03-07 22:42 ` Marth64
2025-03-07 23:56 ` Soft Works
2025-03-08 0:21 ` Marth64
2025-03-08 1:16 ` Soft Works
2025-03-08 10:50 ` Soft Works
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