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

On Mon, 17 Sep 2018 08:27:48 -0700
"Joshua D. Drake" <jd@commandprompt.com> wrote:

> On 09/17/2018 08:11 AM, Dmitri Maziuk wrote:
> > On Sun, 16 Sep 2018 12:52:34 +0000
> > Martin Mueller <martinmueller@northwestern.edu> wrote:
> >
> >> ... The overreach is dubious on both practical and theoretical
> >> grounds. "Stick to your knitting " or the KISS principle seem good
> >> advice in this context.
> > Moderated mailing lists ain't been broken all these years,
> > therefore they need fixing. Obviously.
>
> Folks,
>
> At this point it is important to accept that the CoC is happening. We
> aren't going to stop that. The goal now is to insure a CoC that is
> equitable for all community members and that has appropriate
> accountability. At hand it appears that major concern is the CoC
> trying to be authoritative outside of community channels. As well as
> wording that is a bit far reaching. Specifically I think people's
> main concern is these two sentences:
>
> "To that end, we have established this Code of Conduct for community
> interaction and participation in the project’s work and the community
> at large. 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)."
>
> If we can constructively provide feedback about those two sentences,
> great (or constructive feedback on other areas of the CoC). If we
> can't then this thread needs to stop. It has become unproductive.
>
> My feedback is that those two sentences provide an overarching
> authority that .Org does not have the right to enforce and that it is
> also largely redundant because we allow that the idea that if another
> CoC exists, then ours doesn't apply. Well every single major
> collaboration channel we would be concerned with (including something
> like Blogger) has its own CoC within its Terms of use. That
> effectively neuters the PostgreSQL CoC within places like Slack,
> Facebook, Twitter etc...

The perfect is the enemy of the good. Whatever CoC is decided upon, it
will be updated later. If it's easier, for now, to pass it with
enforcement WITHIN the Postgres community, why not do that? If, later
on, we get instances of people retaliating, in other venues, for
positions taken in Postgres, that can be handled when it comes up.

SteveT

Steve Litt
September 2018 featured book: Quit Joblessness: Start Your Own Business
http://www.troubleshooters.com/startbiz