Re: Code of Conduct plan

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Code of Conduct plan
Date: 2018-06-04 16:44:48
Message-ID: df9452cd-20ba-1214-8c47-cd16c0ed5b39@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

If there's been so much Bad Behavior that's so Weakened the Community, then
someone's done an excellent job of hiding that Bad Behavior.

On 06/04/2018 09:57 AM, Evan Macbeth wrote:
> I just want to chime in and thank all those who worked on this Code of
> Conduct. It's well thought out, and I'm personally very glad to see it. I
> think this just makes our community and its work stronger. I strongly
> support it being put into effect.
>
> Evan Macbeth
>
> On Sun, Jun 3, 2018 at 2:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
>
> Two years ago, there was considerable discussion about creating a
> Code of Conduct for the Postgres community, as a result of which
> the core team announced a plan to create an exploration committee
> to draft a CoC [1].  That process has taken far longer than expected,
> but the committee has not been idle.  They worked through many comments
> and many drafts to produce a version that seems acceptable in the view
> of the core team.  This final(?) draft can be found at
>
> https://wiki.postgresql.org/wiki/Code_of_Conduct
> <https://wiki.postgresql.org/wiki/Code_of_Conduct>
>
> We are now asking for a final round of community comments.
> Please send any public comments to the pgsql-general list (only).
> If you wish to make a private comment, you may send it to
> coc(at)postgresql(dot)org <mailto:coc(at)postgresql(dot)org>.
>
> The initial membership of the CoC committee will be announced separately,
> but shortly.
>
> Unless there are substantial objections, or nontrivial changes as a result
> of this round of comments, we anticipate making the CoC official as of
> July 1 2018.
>
>                         regards, tom lane
>
> [1]
> https://www.postgresql.org/message-id/56A8516B.8000105@agliodbs.com
> <https://www.postgresql.org/message-id/56A8516B.8000105@agliodbs.com>
>
>
>
>
> --
> Evan Macbeth - Director of Support - Crunchy Data
> +1 443-421-0343 - evan(dot)macbeth(at)crunchydata(dot)com
> <mailto:evan(dot)macbeth(at)crunchydata(dot)com>

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Joshua D. Drake 2018-06-04 16:52:09 Re: Code of Conduct plan
Previous Message Ron 2018-06-04 16:42:23 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2018-06-04 16:52:09 Re: Code of Conduct plan
Previous Message Ron 2018-06-04 16:42:23 Re: Code of Conduct plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2018-06-04 16:46:58 Recovery performance of DROP DATABASE with many tablespaces
Previous Message Ron 2018-06-04 16:42:23 Re: Code of Conduct plan

Browse pgsql-www by date

  From Date Subject
Next Message Joshua D. Drake 2018-06-04 16:52:09 Re: Code of Conduct plan
Previous Message Ron 2018-06-04 16:42:23 Re: Code of Conduct plan