Re: Code of Conduct plan

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, PostgreSQL Advocacy <pgsql-advocacy(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct plan
Date: 2018-06-05 22:20:15
Message-ID: CAH2-Wzn9jYmnt7h+rCMv9prVufnNcv78NKe1XXOVEiYS9Lp0nQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

On Tue, Jun 5, 2018 at 2:06 PM, Sven R. Kunze <srkunze(at)mail(dot)de> wrote:
> 1) CoC might result in developers leaving projects
> http://lists.llvm.org/pipermail/llvm-dev/2018-May/122922.html

This guy left LLVM for several reasons. The pertinent reason for us
was that he had to agree to a code of conduct in order to attend
conferences, which he found to be unacceptable. He did not have to
agree that the idea of a code of conduct was a good one, though. It
would have been perfectly possible for him to be opposed in principle
to the idea of a CoC, while also formally agreeing to it and attending
those conferences. I gather that his objections were around questions
of unintended consequences, the role of a certain authority to assess
violations of the CoC, and so on (I surmise that he was not actually
opposed to or constrained by any of the specific rules around content
in technical presentations and so on).

I for one accept that these may have been reasonable concerns, even
though I don't really agree, since the LLVM CoC seems quite
reasonable. Anybody that participates in an open source community soon
learns that their opinion on almost any matter may not be the one that
prevails. There are often differences of opinion on -hackers that seem
to fundamentally be down to a difference in values. We still manage to
make it work, somehow.

> 2) CoC might result in not so equal peers and friends, might result in a
> committee which feels above their peers, and might promote conceit and
> denunciation.

I think that having a code of conduct is better than not having one,
and I think that the one that we came up with is appropriate and
proportionate. We could speculate all day about specific unintended
consequences that may or may not follow. That doesn't seem very
constructive, though. Besides, the time for that has passed.

> In related discussions, people recurringly ask not to establish a secondary
> judicial system but to use the already existing ones.

I don't follow. Practically any organized group has rules around
conduct, with varying degrees of formality, means of enforcement, etc.
Naturally, the rules across disparate groups vary widely for all kinds
of reasons. Formalizing and being more transparent about how this
works seems like the opposite of paternalism to me.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Christophe Pettus 2018-06-05 22:26:34 Re: Code of Conduct plan
Previous Message Ozz Nixon 2018-06-05 21:34:39 RE: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Christophe Pettus 2018-06-05 22:26:34 Re: Code of Conduct plan
Previous Message Jerry Sievers 2018-06-05 21:53:31 Which backend using which pg_temp_N schema?

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2018-06-05 22:26:34 Re: Code of Conduct plan
Previous Message Teodor Sigaev 2018-06-05 21:53:47 Re: \d t: ERROR: XX000: cache lookup failed for relation

Browse pgsql-www by date

  From Date Subject
Next Message Christophe Pettus 2018-06-05 22:26:34 Re: Code of Conduct plan
Previous Message Ozz Nixon 2018-06-05 21:34:39 RE: Code of Conduct plan