[FFmpeg-devel] [PATCH] doc/developer.texi: Add a code of conduct
Paul B Mahol
onemda at gmail.com
Fri May 20 16:23:23 CEST 2016
Dana 20. 5. 2016. 15:21 osoba "Michael Niedermayer" <michael at niedermayer.cc>
> On Fri, May 20, 2016 at 02:50:17PM +0200, Christophe Gisquet wrote:
> > Hi,
> > 2016-05-20 2:38 GMT+02:00 Timothy Gu <timothygu99 at gmail.com>:
> > >> > Note how it has a list of specific violations, instead of vague
> > >> > "Be excellent" that the FFmpeg one has.
> > >> > Note how it has a huge section on disciplinary procedures.
> > [...]
> > > I have to agree with Kieran here. I believe that as a community, we
> > > _want_ to assume good faith, etc. But conflict resolution requires
> > > codified consequences for violations of the CoC, to ensure fairness.
> > > language needs to be made more serious so that people actually take
it in the
> > > way it is intended.
> > Completely agree. Without sanctions, I fear it won't help mitigate
> I belive that people simply not accepting aggression and _politely_
> pointing it out to their peers when they treat others disrespectful
> alone would already have a big effect
> on (i belive) debian lists i saw multiple people politely point out
> that an attack was inappropriate and it stoped, no one was banned
> I thus think similar stern but respectfull&polite community opposition
> alone could be effective for ffmpeg
> I think a big part of the problem is that if one insults another
> the friends of both support the seperation (that is we good vs. they
> bad thinking). People should instead oppose the disrespect itself but
> support people on both sides (we are all good, the language used / act
> there was bad)
Sorry, by you are simply wrong. This is about not following dev guide for
patch submission and then attacking anyone, but that is less important now.
Biggest problem is irrational thinking and spreading lies.
> > Also, because a text is subject to interpretation, the CoC could maybe
> > state how this is arbitrated.
> This is a very hard problem and also part of why i suggest to wait
> with adding penalties/sanctions.
> Note iam suggesting to wait with adding penalties NOT to
> not add penalties if it doesnt work without
> also if penalties are used they will in practice probably end up
> being applied to both sides as "who started" is likely often another
> very hard problem people would have very heated oppinions about
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> Opposition brings concord. Out of discord comes the fairest harmony.
> -- Heraclitus
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel