Re: Code of Conduct

From: Fred Pratt <fpratt(at)microtechnologies(dot)com>
To: ERR ORR <rd0002(at)gmail(dot)com>
Cc: James Keener <jim(at)jimkeener(dot)com>, Dave Page <dpage(at)postgresql(dot)org>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, pgsql-generallists(dot)postgresql(dot)org <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct
Date: 2018-09-19 15:27:23
Message-ID: CBB0649D-607F-4760-9CEE-53D45A87887A@microtechnologies.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Keep pg open and free. This smells of PC police. This community can police itself

Sent from my mobile device. Please pardon my brevity and typos. I am not responsible for changes made by this device’s autocorrect feature.

Fred Pratt
AmerisourceBergen
Manager – IT Infrastructure
Micro Technologies

8701 CenterPort Blvd<x-apple-data-detectors://8>
Amarillo, TX 79108<x-apple-data-detectors://8>

Work: 806.372.2369 (Ext. 8364)<tel:806.372.2369;8364>
Fax: 855.849.0680<tel:855.849.0680>
Mobile: 806.679.1742<tel:806.679.1742>

microtechnologies.com<http://microtechnologies.com/>

On Sep 19, 2018, at 9:32 AM, ERR ORR <rd0002(at)gmail(dot)com<mailto:rd0002(at)gmail(dot)com>> wrote:

I was never consulted.
I was only Told that there was a CoC "to be". Not when, not how.
A CoC will inevitably lead to the project taken over by leftists, political and technical decisions will be made by others.
Most important from my PoV, the projects quality will decrease until its made unviable.
As others have said, this was rammed down our throats.
Before you ppl become unemployed, read "SJWs always lie". You'll know what awaits you.
As for myself, I'll be on the lookout for another DB. One that's not infiltrated by leftist nuts.

And Dave, you can tell the core team a big "FUCK YOU" for this.

James Keener <jim(at)jimkeener(dot)com<mailto:jim(at)jimkeener(dot)com>> schrieb am Di., 18. Sep. 2018, 13:48:
> following a long consultation process

It's not a consultation if any dissenting voice is simply ignored. Don't sugar-coat or politicize it like this -- it was rammed down everyone's throats. That is core's right, but don't act as everyone's opinions and concerns were taken into consideration. There are a good number of folks who are concerned that this CoC is overreaching and is ripe for abuse. Those concerns were always simply, plainly, and purposely ignored.

> Please take time to read and understand the CoC, which is intended to ensure that PostgreSQL remains an open and enjoyable project for anyone to join and participate in.

I sincerely hope so, and that it doesn't become a tool to enforce social ideology like in other groups I've been part of. Especially since this is the main place to come to get help for PostgreSQL and not a social club.

Jim

On September 18, 2018 6:27:56 AM EDT, Dave Page <dpage(at)postgresql(dot)org<mailto:dpage(at)postgresql(dot)org>> wrote:
The PostgreSQL Core team are pleased to announce that following a long consultation process, the project’s Code of Conduct (CoC) has now been finalised and published at https://www.postgresql.org/about/policies/coc/.

Please take time to read and understand the CoC, which is intended to ensure that PostgreSQL remains an open and enjoyable project for anyone to join and participate in.

A Code of Conduct Committee has been formed to handle any complaints. This consists of the following volunteers:

- Stacey Haysler (Chair)
- Lætitia Avrot
- Vik Fearing
- Jonathan Katz
- Ilya Kosmodemiansky

We would like to extend our thanks and gratitude to Stacey Haysler for her patience and expertise in helping develop the Code of Conduct, forming the committee and guiding the work to completion.

--
Dave Page
PostgreSQL Core Team
http://www.postgresql.org/
<http://www.postgresql.org/>

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alban Hertroys 2018-09-19 15:37:43 Re: Regrading brin_index on required column of the table
Previous Message Andreas Kretschmer 2018-09-19 14:56:56 Re: *Regarding brin_index on required column of the table

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2018-09-19 15:33:24 Re: doc - add missing documentation for "acldefault"
Previous Message Joe Conway 2018-09-19 15:18:58 Re: doc - add missing documentation for "acldefault"