Re: [FFmpeg-devel] CoC enforcement activated

[Compn]

On Sun, 17 Dec 2017 22:16:50 +, Josh de Kock 
wrote:

> On Sun, 17 Dec 2017 17:12:24 -0500
> Compn  wrote:
> 
> > On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock 
> > wrote:
> > 
> > > On Sun, 17 Dec 2017 15:36:53 -0500
> > > Compn  wrote:
> > > 
> > > > [...]
> > > >
> > > > emergency moderation has now been enabled.
> > > > 
> > > > why do i have to enforce the COC?
> > > > 
> > > > the ffmpeg-devel mailing list is for technical discussions of
> > > > developing ffmpeg. personal insults will not be tolerated.
> > > > 
> > > 
> > > Note that there is nothing on how the CoC should be 'enforced'. Also 
> > > consider that the CoC in our case is more of guidelines than strict rules 
> > > to be followed. There has also been no consensus on moderation being 
> > > enabled under what circumstances. 
> > 
> > right, i brought this up in april.
> > 
> > http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/210519.html
> > 
> 
> My point is: You should turn off this 'emergency moderation' as there's 
> nothing in the *non-existent* guidelines which say you are allowed to do so.

as said on irc, emergency moderation is the standard and expected tool
for ml admins to use to stomp out flame wars.

When this option is enabled, all list traffic is emergency moderated,
i.e. held for moderation. Turn this option on when your list is
experiencing a flamewar and you want a cooling off period.


emergency moderation is part of an ml admins job. it is not something i
thought up, invented, or wrote guidelines for. it is not something i
enjoy either.

having mails delayed ~2 minutes never hurt anyone.

-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] CoC enforcement activated

[Josh de Kock]

On Sun, 17 Dec 2017 17:12:24 -0500
Compn  wrote:

> On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock 
> wrote:
> 
> > On Sun, 17 Dec 2017 15:36:53 -0500
> > Compn  wrote:
> > 
> > > [...]
> > >
> > > emergency moderation has now been enabled.
> > > 
> > > why do i have to enforce the COC?
> > > 
> > > the ffmpeg-devel mailing list is for technical discussions of
> > > developing ffmpeg. personal insults will not be tolerated.
> > > 
> > 
> > Note that there is nothing on how the CoC should be 'enforced'. Also 
> > consider that the CoC in our case is more of guidelines than strict rules 
> > to be followed. There has also been no consensus on moderation being 
> > enabled under what circumstances. 
> 
> right, i brought this up in april.
> 
> http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/210519.html
> 

My point is: You should turn off this 'emergency moderation' as there's nothing 
in the *non-existent* guidelines which say you are allowed to do so.

-- 
Josh de Kock 
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] CoC enforcement activated

[Compn]

On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock 
wrote:

> On Sun, 17 Dec 2017 15:36:53 -0500
> Compn  wrote:
> 
> > [...]
> >
> > emergency moderation has now been enabled.
> > 
> > why do i have to enforce the COC?
> > 
> > the ffmpeg-devel mailing list is for technical discussions of
> > developing ffmpeg. personal insults will not be tolerated.
> > 
> 
> Note that there is nothing on how the CoC should be 'enforced'. Also consider 
> that the CoC in our case is more of guidelines than strict rules to be 
> followed. There has also been no consensus on moderation being enabled under 
> what circumstances. 

right, i brought this up in april.

http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/210519.html

-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] CoC enforcement activated

[Josh de Kock]

On Sun, 17 Dec 2017 15:36:53 -0500
Compn  wrote:

> [...]
>
> emergency moderation has now been enabled.
> 
> why do i have to enforce the COC?
> 
> the ffmpeg-devel mailing list is for technical discussions of
> developing ffmpeg. personal insults will not be tolerated.
> 

Note that there is nothing on how the CoC should be 'enforced'. Also consider 
that the CoC in our case is more of guidelines than strict rules to be 
followed. There has also been no consensus on moderation being enabled under 
what circumstances. 

-- 
Josh de Kock 
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] CoC enforcement activated

[Compn]

http://ffmpeg.org/developer.html#Code-of-conduct

5 Code of conduct

Be friendly and respectful towards others and third parties. Treat
others the way you yourself want to be treated. 

Be considerate. Not everyone shares the same viewpoint and priorities
as you do. Different opinions and interpretations help the project.
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. 

Stay friendly even if someone acts contrarily. Everyone has a bad day
once in a while. If you yourself have a bad day or are angry then try
to take a break and reply once you are calm and without anger if you
have to. 

Try to help other team members and cooperate if you can. 

The goal of software development is to create technical excellence, not
for any individual to be better and "win" against the others. Large
software projects are only possible and successful through teamwork. 

If someone struggles do not put them down. Give them a helping hand
instead and point them in the right direction. 

Finally, keep in mind the immortal words of Bill and Ted, "Be excellent
to each other."


-


enough fighting on the mailing list.

emergency moderation has now been enabled.

why do i have to enforce the COC?

the ffmpeg-devel mailing list is for technical discussions of
developing ffmpeg. personal insults will not be tolerated.

-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel