Re: Code of Conduct plan

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Jan Claeys <lists(at)janc(dot)be>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Code of Conduct plan
Date: 2018-06-06 00:15:53
Message-ID: 3402DB67-E0FC-4D70-B75C-D83B2AA220C3@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 17:07, Jan Claeys <lists(at)janc(dot)be> wrote:
>
> For example: having some people who have a background in something like
> psychology, sociology, education, law, human resources, marketing, etc.
> (in addition to the likely much easier to find developers, DBAs and IT
> managers) would be valuable too.

While it's good for the CoC committee to reach out for professional expertise if they need it, it should be on an engagement basis (if the CoC committee needs a lawyer, they find and retain a lawyer). The damage that someone smart who thinks they know another profession can do is substantial.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Tom Lane 2018-06-06 00:38:41 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-06-06 00:12:24 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Jonathan Marks 2018-06-06 00:36:00 Re: Segfault leading to crash, recovery mode, and TOAST corruption
Previous Message Adrian Klaver 2018-06-06 00:12:24 Re: Code of Conduct plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-06-06 00:38:41 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-06-06 00:12:24 Re: Code of Conduct plan

Browse pgsql-www by date

  From Date Subject
Next Message Tom Lane 2018-06-06 00:38:41 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-06-06 00:12:24 Re: Code of Conduct plan