Re: Code of Conduct plan

From: Damir Colak <dcolak(at)gmail(dot)com>
To: Chris Travers <chris(dot)travers(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org, pgsql-advocacy(at)lists(dot)postgresql(dot)org
Subject: Re: Code of Conduct plan
Date: 2018-09-14 11:21:33
Message-ID: B368DFD4-4467-4C48-BD1C-62F24C98FFB2@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

Please take me off this list.

> On Sep 14, 2018, at 05:31, Chris Travers <chris(dot)travers(at)gmail(dot)com> wrote:
>
>
>
> On Wed, Sep 12, 2018 at 10:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
> I wrote:
> > Stephen Frost <sfrost(at)snowman(dot)net <mailto:sfrost(at)snowman(dot)net>> writes:
> >> We seem to be a bit past that timeline... Do we have any update on when
> >> this will be moving forward?
> >> Or did I miss something?
>
> > Nope, you didn't. Folks have been on holiday which made it hard to keep
> > forward progress going, particularly with respect to selecting the initial
> > committee members. Now that Magnus is back on shore, I hope we can
> > wrap it up quickly --- say by the end of August.
>
> I apologize for the glacial slowness with which this has all been moving.
> The core team has now agreed to some revisions to the draft CoC based on
> the comments in this thread; see
>
> https://wiki.postgresql.org/wiki/Code_of_Conduct <https://wiki.postgresql.org/wiki/Code_of_Conduct>
>
> (That's the updated text, but you can use the diff tool on the page
> history tab to see the changes from the previous draft.)
>
> I really have to object to this addition:
> "This Code is meant to cover all interaction between community members, whether or not it takes place within postgresql.org <http://postgresql.org/> infrastructure, so long as there is not another Code of Conduct that takes precedence (such as a conference's Code of Conduct)."
>
> That covers things like public twitter messages over live political controversies which might not be personally directed. At least if one is going to go that route, one ought to *also* include a safe harbor for non-personally-directed discussions of philosophy, social issues, and politics. Otherwise, I think this is asking for trouble. See, for example, what happened with Opalgate and how this could be seen to encourage use of this to silence political controversies unrelated to PostgreSQL.
>
> I think we are about ready to announce the initial membership of the
> CoC committee, as well, but that should be a separate post.
>
> regards, tom lane
>
>
>
> --
> Best Wishes,
> Chris Travers
>
> Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.
> http://www.efficito.com/learn_more <http://www.efficito.com/learn_more>

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message James Keener 2018-09-14 12:50:34 Re: Code of Conduct plan
Previous Message Chris Travers 2018-09-14 10:10:47 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message James Keener 2018-09-14 12:50:34 Re: Code of Conduct plan
Previous Message Arup Rakshit 2018-09-14 10:13:03 Re: Can I add Index to make a query faster which involves joins on unnest ?

Browse pgsql-hackers by date

  From Date Subject
Next Message Brad DeJong 2018-09-14 11:27:09 Re: Re[3]: doc - improve description of default privileges
Previous Message Amit Khandekar 2018-09-14 11:18:24 Re: Query is over 2x slower with jit=on

Browse pgsql-www by date

  From Date Subject
Next Message James Keener 2018-09-14 12:50:34 Re: Code of Conduct plan
Previous Message Chris Travers 2018-09-14 10:10:47 Re: Code of Conduct plan