Re: Code of Conduct plan

From: James Keener <jim(at)jimkeener(dot)com>
To: Steve Litt <slitt(at)troubleshooters(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Code of Conduct plan
Date: 2018-09-15 02:47:04
Message-ID: CAG8g3tzARO7-LoBE-rGhFd+NPbQ=btbj+ABQjiDf-iesTR=ZSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general pgsql-hackers pgsql-www

The preceding's pretty simple. An attacker goes after an individual,
> presumably without provocation and/or asymetrically. The attacked
> person is on this mailing list. IMHO this attacker must choose between
> continuing his attacks, and belonging to the Postgres community.
>
> What's tougher is the person who attacks groups of people.
>
>
The preceding's pretty simple. An "attacker" voices their political opinions
or other unorthodoxy or unpopular stance, but in no way directs it at the
postgres user base or on a postgres list. The "attacked"
person is on this mailing list. IMHO this "attacker" must choose between
continuing to voice their opinion, and belonging to the Postgres community.

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Chris Travers 2018-09-15 06:44:10 Re: Code of Conduct plan
Previous Message Steve Litt 2018-09-15 02:04:48 Re: Code of Conduct plan

Browse pgsql-general by date

  From Date Subject
Next Message Schneider, Jeremy 2018-09-15 05:06:49 Re: Slow shutdowns sometimes on RDS Postgres
Previous Message Jerry Sievers 2018-09-15 02:29:44 Re: Vacuum not deleting tuples when lockless

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Travers 2018-09-15 06:44:10 Re: Code of Conduct plan
Previous Message Tom Lane 2018-09-15 02:20:31 Re: move PartitionDispatchData definition to execPartition.c

Browse pgsql-www by date

  From Date Subject
Next Message Chris Travers 2018-09-15 06:44:10 Re: Code of Conduct plan
Previous Message Steve Litt 2018-09-15 02:04:48 Re: Code of Conduct plan