Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90897
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain allanmacgregor.com from 209.85.223.172 cause and error)
Message-ID: <56A573C2.4070202@allanmacgregor.com>
Date: Sun, 24 Jan 2016 20:00:50 -0500
Reply-To: amacgregor@allanmacgregor.com
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Sharon Levy <slevy1@pipeline.com>
CC: ajf@ajf.me, PHP internals <internals@lists.php.net>
References: <023119E29B154072B09D82ED35C29C36@sharonc67d61d6>
In-Reply-To: <023119E29B154072B09D82ED35C29C36@sharonc67d61d6>
Content-Type: multipart/mixed;
 boundary="------------040003070704010600020700"
Subject: Re: [PHP-DEV] Re: [RFC] [Re-proposed] Adopt Code of Conduct
From: amacgregor@allanmacgregor.com (Allan MacGregor)

--------------040003070704010600020700
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Everyone,

I been following the discussion over the weekend, albeit I been hesitant 
to post again I decided to write a blog post with everything in my mind 
regarding the subject. Feel free to read it at 
http://coderoncode.com/community/2016/01/24/on-codes-on-conduct.html

Now, back to the issue at hand I think the current discussion is 
starting to derail from a meaningful conversation and productive output.

It's clear that our opinions vary drastically when it comes down to the 
currently proposed CoC; from what scope should it cover, to what 
restrictions, to what if any kind of punitive actions should be taken.

I believe that is time to take a step back, and start with a smaller 
goal; let's establish the PHP Community values first, set those up as a 
detached document from the CoC.

What does the PHP Community stand for:

- Openness
- Communication
- Stuffed Elephants

Let's start small and move from there, once that's in place we can have 
a more productive conversation about a code of conduct that actually 
matches this community values.

Now, if we are still adamant on coming up with a CoC first I would like 
to put forward the following 3 documents as alternatives for the 
Contributor Covenant:


[A contribution policy for open source that 
works](https://medium.com/@jmaynard/a-contribution-policy-for-open-source-that-works-bfc4600c9d83#.d53666v7u)

[The Code of 
Merit](https://github.com/rosarior/Code-of-Merit/blob/master/CODE_OF_MERIT.md)

[The Pragmatists Code of 
Conduct](https://github.com/amacgregor/Pragmatists-Code-of-Conduct/blob/master/Prag-Code-of-Conduct.md)


Cheers!

Sharon Levy wrote:
> Or, is the purpose of the CoC really a device to control perceptions,
> i.e. protect the image of the PHP project and its citizens?
>
>>> Well, that would also be a benefit. I don't think these are exclusive
>>> goals. If PHP isn't inviting, people won't want to contribute.
>
>
>
> What I fear is that if the citizenry of Userland and PHPland do not feel
> at liberty to publicly and freely express their criticism of the PHP
> project, then important feedback will not be forthcoming, feedback that
> could aid in advancing PHP.
>
>
>
> Also, if taking personal responsibility for one's communication style
> seems like an unworthy value to subscribe to, then it seems that a BDFL
> might be in order.
>
>
>
> My own unsolicited 0.02 is that their should be a brief lexicon of
> expressions that are deemed inappropriate for discussion along with
> *suggested* substitutions.
>
>
>
> Those who feel only comfortable with rigid rules underestimate the power
> that freedom affords to the creative process.
>
>
>
> So, is this CoC really about attracting new thoughts or is it about
> making the status quo an even more comfortable place for those who count
> as part of the meritocracy?
>
>
>
> ^Z
>
>
>
>
>
>

-- 
Allan MacGregor
coderoncode.com <http://coderoncode.com>


--------------040003070704010600020700--