Re: Code of Conduct plan - Mailing list pgsql-general

From Tom Lane
Subject Re: Code of Conduct plan
Date
Msg-id 6841.1536956259@sss.pgh.pa.us
Whole thread Raw
In response to Re: Code of Conduct plan  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Code of Conduct plan  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Re: Code of Conduct plan  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Re: Code of Conduct plan  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Re: Code of Conduct plan  (Robert Haas <robertmhaas@gmail.com>)
Re: Code of Conduct plan  (Robert Haas <robertmhaas@gmail.com>)
Re: Code of Conduct plan  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-general
Robert Haas <robertmhaas@gmail.com> writes:
> It's not clear to me that there IS a general consensus here.  It looks
> to me like the unelected core team got together and decided to impose
> a vaguely-worded code of conduct on a vaguely-defined group of people
> covering not only their work on PostgreSQL but also their entire life.

There's been quite a lot of input, from quite a lot of people, dating
back at least as far as a well-attended session at PGCon 2016.  I find
it quite upsetting to hear accusations that core is imposing this out
of nowhere.  From my perspective, we're responding to a real need
voiced by other people, not so much by us.

> However, I also don't think it matters very much.

Yeah, this.  The PG community is mostly nice people, AFAICT.  I'll be
astonished (and worried) if the CoC committee finds much to do.  We're
implementing this mostly to make newcomers to the project feel that
it's a safe space.

It's also worth reminding people that this is v1.0 of the CoC document.
We plan to revisit it in a year or so, and thereafter as needed, to
improve anything that's causing problems or not working well.

            regards, tom lane


pgsql-general by date:

Previous
From: Peter Kleiner
Date:
Subject: Re: Convert interval to hours
Next
From: Arup Rakshit
Date:
Subject: Bitmap Heap Scan and Bitmap Index Scan