Re: Code of Conduct plan

What counts as foul language has changed a great deal in the last two decades. You could always tie it to what is printable in the New York Times, but that too is changing. I could live with something like “Be considerate, and if you can’t be nice, be at least civil”.

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
Date: Saturday, September 15, 2018 at 11:12 AM
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, James Keener <jim(at)jimkeener(dot)com>, Steve Litt <slitt(at)troubleshooters(dot)com>, "pgsql-generallists.postgresql.org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct plan

How about we just simplify the code of conduct to the following:
Any member in the various PostgreSQL lists is expected to maintain
respect to others and not use foul language. A variation from
the previous sentence shall be considered a violation of the CoC.

On Sat, Sep 15, 2018 at 11:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us<mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
Bruce Momjian <bruce(at)momjian(dot)us<mailto:bruce(at)momjian(dot)us>> writes:
> There is a risk that if we adopt a CoC, and nothing happens, and the
> committee does nothing, that they will feel like a failure, and get
> involved when it was best they did nothing. I think the CoC tries to
> address that, but nothing is perfect.

Yeah, a busybody CoC committee could do more harm than good.
The way the CoC tries to address that is that the committee can't
initiate action of its own accord: somebody has to bring it a complaint.

Of course, a member of the committee could go out and find a "problem"
and then file a complaint --- but then they'd have to recuse themselves
from dealing with that complaint, so there's an incentive not to.

regards, tom lane

--
Melvin Davidson
Maj. Database & Exploration Specialist
Universe Exploration Command – UXC
Employment by invitation only!