CoC does not help in benchmarks

Jeff Roberson jroberson at jroberson.net
Mon Jul 16 01:06:08 UTC 2018


On Mon, 16 Jul 2018, Adam wrote:

> 
> 
> On Mon, Jul 16, 2018 at 12:24 AM, Warner Losh <imp at bsdimp.com> wrote:
>       On Sun, Jul 15, 2018, 6:20 PM Andras Farkas
>       <deepbluemistake at gmail.com>
>       wrote:
>
>       > On Sun, Jul 15, 2018 at 7:31 PM Warner Losh <imp at bsdimp.com>
>       wrote:
>       > > Such overly-simply CoCs have proven unworkable in the past.
>       They were OK
>       > in
>       > > the 90's, but we live in a different internet world today.
>       These are good
>       > > guidelines and great advice, but make it hard to take action
>       when
>       > > necessary. I wish it were not so.
>       > > we live in a different internet world today
>       >
>       [Citation needed]
>
>       >
>       Direct personal experience on a conduct board, 10 years over the
>       last 20
>       serving on FreeBSD core team. Most of that time as core's
>       specialist in
>       interpersonal disputes. That qualifies me to have an informed,
>       expert
>       opinion.
>
>       So what are your credentials?
> 
> 
> I'm an expert because I say I am.? What kind of conduct is that?

Many past and present core members found that the existing document was 
insufficient in dealing with the conflict they were being asked to 
resolve.  This resulted in some relatively high profile incidents that 
harmed the project.  Having direct experience with the problem at hand, 
and having been voted into a position to deal with this, does in fact 
entitle Warner to speak with some authority on the subject.

Furthermore, we polled committers and found that there was near universal 
support for respectful communication and for removing people who were 
unable to conduct themselves well.  Core needs a document that provides 
guidelines so that this process is not capricious or surprising.

Jeff

> 
> --
> Adam
> 
>


More information about the freebsd-advocacy mailing list