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

From Bruce Momjian
Subject Re: Code of Conduct plan
Date
Msg-id 20181011224838.GJ7807@momjian.us
Whole thread Raw
In response to Re: Code of Conduct plan  (Chris Travers <chris.travers@gmail.com>)
List pgsql-general
On Thu, Sep 20, 2018 at 07:12:22AM +0200, Chris Travers wrote:
>     If we have a committer who loudly and proudly goes to neo-nazi rallies or
>     pickup artist / pro-rape meetups, then actually yes, I have a problem with
>     that. That impacts my ability to work in the community, impacts everyone's
>     ability to recruit people to work on Postgres, potentially makes people
>     reluctant to engage with the community, etc.
> 
> There's a problem here though. Generally in Europe, one would not be able to
> fire a person or even discriminate against him for such activity.  So if you
> kick someone out of the PostgreSQL community for doing such things in, say,
> Germany but their employer cannot fire them for the same, then you have a real
> problem if improving PostgreSQL is the basis of their employment.    EU
> antidiscrimination law includes political views and other opinions so
> internationally that line is actually very hard to push in an international
> project.  So I think you'd have a problem where such enforcement might actually
> lead to legal action by the employer, or the individual kicked out, or both.

Yes, I had the same reaction.  Activity not involving other Postgres
members seems like it would not be covered by the CoC, except for
"behavior that may bring the PostgreSQL project into disrepute", which
seems like a stretch.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +


pgsql-general by date:

Previous
From: legrand legrand
Date:
Subject: no queryId in post_parse_analyze hook when row is locked
Next
From: magodo
Date:
Subject: Re: how to identify the timeline of specified recovery_target_timewhen do multiple PITR