Re: WIP: CoC V6 - Mailing list pgsql-general

From Steve Petrie, P.Eng.
Subject Re: WIP: CoC V6
Date
Msg-id FE40750DAD85456C8E6521F406F6E032@Dell
Whole thread Raw
In response to WIP: CoC  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-general
Please see my two suggestions below.

Steve

----- Original Message -----
From: "Joshua D. Drake" <jd@commandprompt.com>
To: "Neil" <neil@fairwindsoft.com>; "Psql_General (E-mail)"
<pgsql-general@postgresql.org>
Sent: Thursday, January 14, 2016 4:48 PM
Subject: Re: [GENERAL] WIP: CoC V6


> Hello,
>
> I posted this earlier but ended up breaking my own silly rev scheme.
> So, I am going back to my silly rev scheme. Rev 6 it is:
>
> tl;dr;
>
>  * added being tolerant of opposing views
>  * Removed excess wording from Grittner's version
>  * Removed non-.org controlled spaces in first paragraph
>
> == PostgreSQL Community Code of Conduct (CoC) ==
>
> This document is intended to provide community guidelines for
> creating and enforcing a safe, respectful, productive, and
> collaborative place for any person who is willing to contribute in
> a safe, respectful, productive and collaborative way.  It applies
> to all "collaborative space", which is defined as community
> communications channels (such as mailing lists, IRC, submitted
> patches, commit comments, etc.).
>

It seems to me that the above paragraph is too long, especially
considering that the following points are crisp short single sentences.

Also, why repeat the phrase "safe, respectful, productive, and
collaborative"?

My suggestion -- make two paragraphs:

This document provides community guidelines for
creating and enforcing a safe, respectful, productive, and
collaborative place. Every contributor is expected to support these
goals.

The guidelines apply to all "collaborative space", which is defined as
community
communications channels (such as mailing lists, IRC, submitted
patches, commit comments, etc.).

> * We are tolerant of people’s right to have opposing views.
>

I recall someone earlier mentioning the benefit of keeping discussions
on topic.

And it seems to me that that only views actually expressed are of
concern.

So I would offer the following revision:

* We are tolerant of people’s right to express opposing views relevant
to the success of the project.

> * Participants must ensure that their language and actions are free
> of personal attacks and disparaging personal remarks.
>
> * When interpreting the words and actions of others, participants
> should always assume good intentions.
>
> * Participants must avoid sustained disruption of the collaborative
> space, or any pattern of behavior which could reasonably be
> considered harassment.
>
>
> --
> Command Prompt, Inc.                  http://the.postgres.company/
>                      +1-503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general



pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: Why PG uses nested-loop join when no indexes are available?
Next
From: Sylvain MARECHAL
Date:
Subject: Re: [BDR] Best practice to automatically abort a DDL operation when one node is down