From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Benjamin Scherrey <scherrey(at)proteus-tech(dot)com>, Christophe Pettus <xof(at)thebuild(dot)com>, Chris Travers <chris(dot)travers(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Code of Conduct plan |
Date: | 2018-06-06 15:34:23 |
Message-ID: | 2360e055-718a-7f57-991e-547de99fd3d5@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-general pgsql-hackers pgsql-www |
On 06/05/2018 08:55 PM, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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. *****
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Schneider | 2018-06-06 17:39:36 | Re: Code of Conduct plan |
Previous Message | Chris Travers | 2018-06-06 05:27:40 | Re: Code of Conduct plan |
From | Date | Subject | |
---|---|---|---|
Next Message | David Gauthier | 2018-06-06 15:36:08 | Doing a \set through perl DBI ? |
Previous Message | Tom Lane | 2018-06-06 14:32:27 | Re: Using distinct in an aggregate prevents parallel execution? |
From | Date | Subject | |
---|---|---|---|
Next Message | Nico Williams | 2018-06-06 15:34:32 | Re: [HACKERS] [PATCH] WIP Add ALWAYS DEFERRED option for constraints |
Previous Message | Tom Lane | 2018-06-06 15:17:33 | Re: Why is fncollation in FunctionCallInfoData rather than fmgr_info? |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Schneider | 2018-06-06 17:39:36 | Re: Code of Conduct plan |
Previous Message | Jonathan S. Katz | 2018-06-06 14:35:37 | Re: Add PostgreSQL 11 to feature matrix page? |