| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Benjamin Scherrey <scherrey(at)proteus-tech(dot)com> |
| Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(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-05 19:12:08 |
| Message-ID: | 77D201D9-F009-47AE-81C4-9271114A9E87@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-general pgsql-hackers pgsql-www |
> On Jun 5, 2018, at 12:06, Benjamin Scherrey <scherrey(at)proteus-tech(dot)com> wrote:
> Doesn't that 20 years of results pretty clearly demonstrate that this community does not gain an advantage for adopting a CoC?
Not at all. The need for a CoC is not theoretical. Real people, recently, have left the community due to harassment, and there was no system within the community to report and deal with that harassment.
What we do have is 20 years of people demonstrating reasonable good judgment, which we can conclude will apply to a CoC committee as well.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-05 19:16:07 | Re: Code of Conduct plan |
| Previous Message | Benjamin Scherrey | 2018-06-05 19:06:24 | Re: Code of Conduct plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-05 19:16:07 | Re: Code of Conduct plan |
| Previous Message | Benjamin Scherrey | 2018-06-05 19:06:24 | Re: Code of Conduct plan |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-05 19:16:07 | Re: Code of Conduct plan |
| Previous Message | Peter Eisentraut | 2018-06-05 19:08:33 | Re: Variable-length FunctionCallInfoData |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-05 19:16:07 | Re: Code of Conduct plan |
| Previous Message | Benjamin Scherrey | 2018-06-05 19:06:24 | Re: Code of Conduct plan |