Re: [RFC] [Draft] Adopt Code of Conduct

From: Date: Wed, 06 Jan 2016 01:03:57 +0000
Subject: Re: [RFC] [Draft] Adopt Code of Conduct
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-90178@lists.php.net to get a copy of this message
Hi, On 6 January 2016 at 09:20, Paul M. Jones <pmjones88@gmail.com> wrote: > > > On Jan 5, 2016, at 17:09, Terry Cullen <terry@terah.com.au> wrote: > > > > Hi, > > > > > > > > On 5 January 2016 at 07:06, Anthony Ferrara <ircmaxell@gmail.com> wrote: > > > >> Hey all, > >> > >> I have created a new RFC for the PHP Project to adopt the Contributor > >> Covenant as the official Code of Conduct for the project > >> > >> https://wiki.php.net/rfc/adopt-code-of-conduct > >> > >> Let me know what you think or if there are any concerns > >> > >> Thanks > >> > >> Anthony > >> > >> -- > >> PHP Internals - PHP Runtime Development Mailing List > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > ​Here is a timely blog post of a FreeBSD community member's account of > > bullying within a large OS project. I thought it might add to the > > conversation... > > > > > > http://blog.randi.io/2015/12/31/the-developer-formerly-known-as-freebsdgirl/ > > And here's a timely reference from the other side of that argument. > > > L“¾ÙÙ > åsۀ¥QŽ8Òhttps://lists.freebsd.org/pipermail/freebsd-questions/2015-June/266479.html > > If one presents only the one side, that of the accuser, that might be > problematic. It's even more problematic when speech is being policed by a > COC. > > > ​Yes... Enforcing a COC can be a ​very complicated undertaking. > > -- > Paul M. Jones > pmjones88@gmail.com > http://paul-m-jones.com > > Modernizing Legacy Applications in PHP > https://leanpub.com/mlaphp > > Solving the N+1 Problem in PHP > https://leanpub.com/sn1php > > > ​Terry​

« previous php.internals (#90178) next »