Re: Code of Conduct plan
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Dave Page <dpage@pgadmin.org>, James Keener <jim@jimkeener.com>,
"Joshua D. Drake" <jd@commandprompt.com>,
Robert Eckhardt <reckhardt@pivotal.io>,
Adrian Klaver <adrian.klaver@aklaver.com>,
Chris Travers <chris.travers@gmail.com>,
Stephen Frost <sfrost@snowman.net>,
"pgsql-generallists.postgresql.org"
<pgsql-general@lists.postgresql.org>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
pgsql-advocacy@lists.postgresql.org
Date: 2018-09-14T20:17:39Z
Lists: pgsql-hackers, 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