Re: Code of Conduct plan

From: Dave Page <dpage(at)pgadmin(dot)org>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Chris Travers <chris(dot)travers(at)gmail(dot)com>, 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 14:14:26
Message-ID: CA+OCxoxwK9_PF1dSYTtC-GPXqVbchPvB8+phSP++BF7p+i3-uQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

On Fri, Sep 14, 2018 at 3:08 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:

> On 09/14/2018 01:31 AM, Chris Travers wrote:
>
>
> 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 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 this is a complicated issue. On the one hand, postgresql.org has
> no business telling people how to act outside of postgresql.org. Full
> stop.
>

I'm going to regret jumping in here, but...

I disagree. If a community member decides to join forums for other software
and then strongly promotes PostgreSQL to the point that they become abusive
or offensive to people making other software choices, then they are clearly
bringing the project into disrepute and we should have every right to
sanction them by preventing them participating in our project in whatever
ways are deemed appropriate.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Stephen Frost 2018-09-14 14:15:33 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-09-14 14:13:38 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2018-09-14 14:15:33 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-09-14 14:13:38 Re: Code of Conduct plan

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-09-14 14:15:33 Re: Code of Conduct plan
Previous Message Tomas Vondra 2018-09-14 14:13:46 Re: logical decoding bug when mapped relation with toast contents is rewritten repeatedly

Browse pgsql-www by date

  From Date Subject
Next Message Stephen Frost 2018-09-14 14:15:33 Re: Code of Conduct plan
Previous Message Adrian Klaver 2018-09-14 14:13:38 Re: Code of Conduct plan