[FFmpeg-devel] [PATCH] [RFC] [GA Vote required] Code of Conduct change re step down requests

[Vittorio Giovara]

On Fri, Nov 22, 2024 at 7:49 PM Michael Niedermayer <michael at niedermayer.cc>
wrote:

> On Fri, Nov 22, 2024 at 09:41:02AM -1000, compn wrote:
> > Hello,
> >
> > as the CoC rules over the GA, then the GA probably has to vote on this
> > change? i didnt find any process for changing the CoC, so i send this
> > mail. I kindly ask someone more familiar with the voting system to start
> > a vote on the vote.ffmpeg.org for this proposed change to the Code of
> > conduct.
> >
> >
> > Reasons for this change:
> > i am tired of seeing these step down calls for the last 15+ years.
> > none of these step down calls help anyone.
> > most people get upset when asked to step down.
> > new contributors are dissuaded when there are a bunch of people calling
> > for each others' heads.
> >
> >
> > Reasons against this change:
> > "but i really like asking people to step down!"
> > "the mailing list is more active with more flames!"
> > "its my last way to be mean on the list, without overtly breaking the
> > CoC!"
> > "its not mean to ask someone to step down! its just (insert reason
> > here)"
> >
> >
> > shouldnt it already be covered by another rule in the CoC?
> > specifying it out , and having the GA vote on it, will give the CC more
> > guidance for easier enforcement and less ambiguity.
> >
> >
> > thank you for your time.
> > -compn
> >
> >
> >
> > diff --git a/doc/community.texi b/doc/community.texi
> > index 97a49f15ed..1e5e93c227 100644
> > --- a/doc/community.texi
> > +++ b/doc/community.texi
> > @@ -162,6 +162,8 @@ Looking at issues from a different perspective
> assists development.
> >  Do not assume malice for things that can be attributed to incompetence.
> Even if
> >  it is malice, it's rarely good to start with that as initial assumption.
> >
> > +Do not ask any developer to step down from any position.
> > +
>
> i would add these:
>
> Stay On-Topic: Ensure your messages relate to software development or the
> specific purpose of the mailing list. Avoid unrelated discussions.
>
> Be Respectful: Treat all members with courtesy and respect. Personal
> attacks, insults, or harassment of any kind are not tolerated.
>
> Avoid Provocation: Refrain from posting inflammatory, controversial, or
> intentionally provocative messages. Focus on constructive discussions.
>
> No Trolling: Messages intended to provoke an emotional response or disrupt
> the discussion are prohibited.
>
> Professional Language: Use clear, professional, and inclusive language.
> Avoid offensive or derogatory remarks, even in jest.
>
> Constructive Criticism Only: Offer feedback in a constructive and
> solution-oriented manner. Criticize ideas, not people.
>
> Handle Disagreements Professionally: Disagreements are normal but should
> be handled respectfully. Assume good intentions and avoid escalating
> conflicts.
>
> Report Issues: If you encounter behavior that violates these rules, report
> it to the list moderators rather than engaging directly.
>
> Moderators’ Authority: Moderators have the final say on rule enforcement.
> Non-compliance may result in warnings, moderated posts, or removal from the
> list.
>

Hey Micheal,

Instead of flooding the CoC with a series of ad-personam rules that will
grant immunity to you and stifle any voice of dissent, can you answer
whether you're a professional admin or not? Ignoring the question will only
make your optics worse.

Last I heard, you stepped down already
https://ffmpeg.org/pipermail/ffmpeg-devel/2015-July/176489.html, why are
you still behaving as project lead?

Deciding what information on the infra is public or not, keeping the
MAINTAINERS file around, adding duties to the role, deciding the funding
amounts of the projects you're working on 1h before submission, and so on,
all seem to make you the de-facto leader, ***in my opinion***.

Did something or someone made you change your mind?
Cheers
-- 
Vittorio