Re: CoC [Final v2]

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
Cc: "FarjadFarid(ChkNet)" <farjad(dot)farid(at)checknetworks(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: CoC [Final v2]
Date: 2016-01-24 17:48:32
Message-ID: 56A50E70.1090708@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 01/24/2016 09:39 AM, Geoff Winkless wrote:
> On 24 January 2016 at 17:30, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> Sarcasm is not productive.
>
> Actually I wasn't being sarcastic. OK, I was being sarcastic in the
> first paragraph, but not the second :p
>
> The most significant problem I see with the Contributor Covenant
> (other than my personal feeling that Postgres shouldn't have anything
> to do members' lives outside the community, but that's just my
> opinion) is the potential for legal wranglings that would ensue. Just
> being in a position to say "we know what legal problems there are",
> let alone being able to say "we know that we are covered against any
> potential legal issues" would be prohibitively expensive.

This thread is not about the Contributor Covenant. This thread is about
working the CoC that this community is already progressing through. It
is already clear that primary contributors in this community do not want
something as politically charged as the Contributor Covenant.

At its core, PostgreSQL is a practical community, not a political one.
That is why the CoC we are working on is practical, succinct and to the
point.

Sincerely,

Joshua D. Drake

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2016-01-24 17:50:46 Re: CoC [Final v2]
Previous Message Geoff Winkless 2016-01-24 17:44:00 Re: CoC [Final v2]