Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90846
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.48 as permitted sender)
MIME-Version: 1.0
Sender: kobrasrealm@gmail.com
Date: Sat, 23 Jan 2016 00:41:16 -0500
Message-ID: <CAPKwhwuSjAcmGpkkH_Lmaf2dNJ9ANFVNT4WWsqMFLi20qfTiuw@mail.gmail.com>
To: "inter >> PHP internals" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11441f64d96f9f0529f9c879
Subject: A Modest Code of Conduct Proposal that Almost Everyone Can Agree On
From: scott@arciszewski.me (Scott Arciszewski)

--001a11441f64d96f9f0529f9c879
Content-Type: text/plain; charset=UTF-8

Let's start with a rhetorical question: When you are adding unit tests to a
legacy code base, where do you start?

...

Typically, you start at the extremes and work your way to the core of the
application, refactoring as you need to go.

I think many people agree that a Code of Conduct, in the abstract (not a
particular one!), would be a good thing to have. So why don't we apply the
same methodology with the CoC initiative?

I propose we start with the most extreme elements of the PHP community and
field test a CoC proposal there. If we can improve the quality of
communication and contributions there, then we know it will have a positive
impact on the core.

And my most extreme, I am of course talking about OpenCart[1], arguably the
most toxic open source software project on the Internet.

----

Please, fellow PHP community members, join me in proposing a Code of
Conduct (i.e. the Contributors' Covenant) to the OpenCart team, explicitly
stating that it applies to Daniel Kerr and James Allsup too.

[1] http://www.openwall.com/lists/oss-security/2016/01/19/16
[2] https://github.com/opencart/opencart/issues

--001a11441f64d96f9f0529f9c879--