[FFmpeg-devel] [RFC][ALT PATCHES] Code of Conduct Enforcement

Tomas Härdin tjoppen at acc.umu.se
Tue May 15 13:30:08 EEST 2018

mån 2018-05-14 klockan 17:50 +0100 skrev Derek Buitenhuis:
> Hello all.
> [...]
> So, I present to you two possible options:
>     1. Implement a formal CoC enforcement system. This has been mostly copypasted
>        from VideoLAN's, and is meant as more of a blueprint. This will no doubt
>        be controversial.
>     2. Remove the CoC. If you're not going to enforce it, ever, there is literally
>        no point in having one. I know some members of this community object to the
>        very notion of a CoC, so this should please them, I am sure.

Unfortunately, none of these options are particularly good..

I've been involved in this project since 2010 and it seems it's been
plagued with an inability to deal with conflict even before that. I'd
say it's almost endemic to the FLOSS movement due to a combination of
strong egos, poor social skills, text being an awful way to express
nuance, sexism and a whole bunch of other crap.

When it comes to FFmpeg specifically, the tendency to hold votes rather
than seek consensus has been a problem since at least the day Libav
forked off. I know from being involved in non-profits that you
typically don't want things to escalate to there having to be a vote,
since that tends to leave the losing side bitter.

I'm leaning toward 2, but there would need to be some other way to deal
with people not getting along. Maybe Mumble conferences where the
involved parties get to air their feelings on whatever is at issue? I

End stream of thought


More information about the ffmpeg-devel mailing list