On Tue, Jan 5, 2016 at 11:08 AM, Mark Baker <m...@lange.demon.co.uk> wrote: > On 05/01/2016 15:59, François Laupretre wrote: >> >> >> Anyway, I don't say that it cannot happen, I just say that, AFAIK, we >> never got such concerns in the PHP community. So, maybe we should go the >> 'politically-correct' way but I'm afraid that's just a waste of time or, as >> Stas said, a solution for no problem. >> > How do you know that you haven't got problems already? It may well be that > people are put off from joining internals precisely because they have > nothing to tell them the environment won't be hostile toward them, and > there's been enough adverse publicity in the past about how "toxic" > internals is, and enough adverse publicity about other Open Source groups > that are abusive.... but you'd never know how many people wanted to > contribute but were put off... Having a public CoC is a way of telling > potential supporters/contributors who are thinking about getting involved > that they can do so without needing to worry about abuse. > > -- > Mark Baker > > _________ > |. \ \-3 > |_J_/ PHP | > || | __ | > || |m| |m| > > I LOVE PHP > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
Hi all, Even if there are no incidencts where a CoC is needed, after seeing today's Reddit thread, I'm convinced it's only a matter of time. https://www.reddit.com/r/PHP/comments/3zhapd/rfc_adopt_code_of_conduct Just my $0.02 Scott Arciszewski Chief Development Officer Paragon Initiative Enterprises -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
