Josh, If we do write a CoC, can we give it a different acronym. I'm going to say something very sensitive here, so don't think I am joking. When I was 5 I was raped by a next door neighbor. Everytime I here people talk about Cocs and how silencing they are I think about that. Thanks, Regina -----Original Message----- From: Joshua D. Drake [mailto:jd@xxxxxxxxxxxxxxxxx] Sent: Monday, January 11, 2016 2:00 PM To: Regina Obe <lr@xxxxxxxx>; 'Brian Dunavant' <brian@xxxxxxxxxx> Cc: 'Scott Mead' <scottm@xxxxxxxxxxx>; 'Adrian Klaver' <adrian.klaver@xxxxxxxxxxx>; 'Gavin Flower' <GavinFlower@xxxxxxxxxxxxxxxxx>; 'PostgreSQL General' <pgsql-general@xxxxxxxxxxxxxx> Subject: Re: Code of Conduct: Is it time? Hello, A lot of good discussion has happened on this thread and as a whole I think it has been determined that if done correctly, a CoC would not be a bad idea. Of course we need to write one. A CoC is about providing a safe, respectful, productive, and collaborative place for any person who is willing to contribute in a safe, respectful, productive and collaborative way. A CoC is not about being offended. The act of being offended is purely a recipients response and usually because the recipient is more interested in being a victim than moving forward. JD -- Command Prompt, Inc. - http://the.postgres.company/ 503-667-4564 PostgreSQL Centered full stack support, consulting and development. If your social views are from the Silicon Valley or The Bay, please leave them there. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
