Joshua,
I have to agree that a COC is in order. But to add to that, I would like to
see basic requirements when submitting a problem.
IE: 1. Version of PostgreSQL
2.. O/S
3. Enough info to duplicate the problem EG: minimal schema & data
On Tue, Jan 5, 2016 at 11:47 AM, Joshua D. Drake <j...@commandprompt.com>
wrote:
> Hello,
>
> I had a hard time writing this email. I think Code of Conducts are
> non-essential, a waste of respectful people's time and frankly if you are
> going to be a jerk, our community will call you out on it. Unfortunately a
> lot of people don't agree with that. I have over the course of the last
> year seen more and more potential users very explicitly say, "I will not
> contribute to a project or attend a conference that does not have a CoC".
>
> Some of us may be saying, "Well we don't want those people". I can't argue
> with some facts though. Ubuntu has had a CoC[1] since the beginning of the
> project and they grew exceedingly quick. Having walls in the hallway of
> interaction isn't always a bad thing.
>
> In reflection, the only thing a CoC does is put in writing what behaviour
> we as a project already require, so why not document it and use it as a
> tool to encourage more contribution to our project?
>
> Sincerely,
>
> JD
>
>
> 1. http://www.ubuntu.com/about/about-ubuntu/conduct
> --
> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
> Announcing "I'm offended" is basically telling the world you can't
> control your own emotions, so everyone else should do it for you.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
