Re: Code of Conduct plan
Joshua D. Drake <jd@commandprompt.com>
From: "Joshua D. Drake" <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Adrian Klaver <adrian.klaver@aklaver.com>
Cc: Benjamin Scherrey <scherrey@proteus-tech.com>,
Christophe Pettus <xof@thebuild.com>, Chris Travers
<chris.travers@gmail.com>,
"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2018-06-06T15:34:23Z
Lists: pgsql-hackers, pgsql-general
On 06/05/2018 08:55 PM, Tom Lane wrote: > Adrian Klaver <adrian.klaver@aklaver.com> writes: >> On 06/05/2018 04:41 PM, Tom Lane wrote: >>> I'm getting a little tired of people raising hypothetical harms and >>> ignoring the real harms that we're hoping to fix. Yes, this is an >>> experiment and it may not work, but we can't find out without trying. >>> If it turns out to be a net loss, we'll modify it or abandon it. > >> Good to hear this is considered an experiment. > >> To that end will there be quarterly/yearly reports, suitably anonymized, >> that spell out the activity that took place with reference to the CoC? > > That seems like a good idea from here. I don't know exactly how much > can be reported without risking privacy issues, but surely we could at > least provide the number of incidents and how they were resolved. Yeah I like it too. We don't have to give out any confidential information but it adds to the transparency and allows the community as a whole to see that. > > regards, tom lane > -- Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc *** A fault and talent of mine is to tell it exactly how it is. *** PostgreSQL centered full stack support, consulting and development. Advocate: @amplifypostgres || Learn: https://postgresconf.org ***** Unless otherwise stated, opinions are my own. *****