Re: Code of Conduct plan
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Chris Travers <chris.travers@gmail.com>, James Keener <jim@jimkeener.com>,
Steve Litt <slitt@troubleshooters.com>,
"pgsql-generallists.postgresql.org"
<pgsql-general@lists.postgresql.org>
Date: 2018-09-15T15:50:45Z
Lists: pgsql-hackers, pgsql-general
Bruce Momjian <bruce@momjian.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