Re: Code of Conduct plan - Mailing list pgsql-general

From Robert Eckhardt
Subject Re: Code of Conduct plan
Date
Msg-id CAAtBm9XYoHKEqq9+9c2KoxY_rhVQWrmeyKuENFZ3TSwK-wT=Qw@mail.gmail.com
Whole thread Raw
In response to Re: Code of Conduct plan  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: Code of Conduct plan  (James Keener <jim@jimkeener.com>)
Re: Code of Conduct plan  (James Keener <jim@jimkeener.com>)
Re: Code of Conduct plan  (James Keener <jim@jimkeener.com>)
Re: Code of Conduct plan  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Code of Conduct plan  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Code of Conduct plan  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Code of Conduct plan  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Code of Conduct plan  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Code of Conduct plan  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Code of Conduct plan  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
On Fri, Sep 14, 2018 at 9:41 AM, Adrian Klaver
<adrian.klaver@aklaver.com> wrote:
> On 9/14/18 1:31 AM, Chris Travers wrote:
>>
>>
>>
>> On Wed, Sep 12, 2018 at 10:53 PM Tom Lane <tgl@sss.pgh.pa.us
>> <mailto:tgl@sss.pgh.pa.us>> wrote:
>>
>>     I wrote:
>>      > Stephen Frost <sfrost@snowman.net <mailto:sfrost@snowman.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
>>
>>     (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)."
>
>
> I second that objection. It is not in PGDG's remit to cure the world, for
> whatever form of cure you ascribe to. This is especially true as 'community
> member' has no strict definition.

I understand the concern, however, if you look at how attacks happen
it is frequently through other sites. Specifically under/poorly
moderated sites. For specific examples, people who have issues with
people on Quora will frequently go after them on Facebook and Twitter.

these aren't a solution looking for a problem. If we just want to look
at the clusterfuck that is happening in the reddis community right now
we can see conversations spilling onto twitter and into ad hominem
vitriol.

My $0.02
-- Rob Eckhardt

>
>
>>
>> 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
>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>


pgsql-general by date:

Previous
From: Juan Manuel Cuello
Date:
Subject: Re: Slow shutdowns sometimes on RDS Postgres
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Code of Conduct plan