Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90164 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30703 invoked from network); 5 Jan 2016 22:49:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 22:49:17 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.50 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 74.125.82.50 mail-wm0-f50.google.com Received: from [74.125.82.50] ([74.125.82.50:34867] helo=mail-wm0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 85/A1-21755-C684C865 for ; Tue, 05 Jan 2016 17:49:17 -0500 Received: by mail-wm0-f50.google.com with SMTP id f206so40448065wmf.0 for ; Tue, 05 Jan 2016 14:49:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dK34cpM3W7TvwBxiM5oxvxiOU7ymzd21GP4QkE67yG4=; b=GN4rjoUV5ZgFVutVPfXDTdedYA6Ez/zsz+qOg6JbKPyiiSwB/fqGHF0vLQCLUy/7Ya /v2c21iFaDlkOx8FbuVtscxkFpzo4MfaAnoiOlsYJYd6J/N2T8cDIeJGY5N0XA0e4Wyc f5j2RwSdgUfAdmOmcRqwXHrVyhWhX8T3YOml8ibSs8G1uzhPtoWFlH3ajIHucmvcgtfq V/sFfOnNQqwJOrfTNnFeoNHii37Wzj2NR9WIwP39ulUNMgMiKHyrffDoR0fzbk5ywB8m zVJPX/rzJq4PxfM2EfNdUNRvkEh6i9UKXhIO/5G47CvR0TK8L7F24m+Vyl4SDsdHkFWJ Hflw== MIME-Version: 1.0 X-Received: by 10.195.12.163 with SMTP id er3mr104855187wjd.135.1452034153487; Tue, 05 Jan 2016 14:49:13 -0800 (PST) Received: by 10.27.86.202 with HTTP; Tue, 5 Jan 2016 14:49:13 -0800 (PST) In-Reply-To: <568C400E.6090404@gmail.com> References: <568C400E.6090404@gmail.com> Date: Tue, 5 Jan 2016 23:49:13 +0100 Message-ID: To: Stanislav Malyshev Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7bf0d966ebc8a205289e0b75 Subject: Re: [PHP-DEV] Re: [RFC] [Draft] Adopt Code of Conduct From: tyra3l@gmail.com (Ferenc Kovacs) --047d7bf0d966ebc8a205289e0b75 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 5, 2016 at 11:13 PM, Stanislav Malyshev wrote: > Hi! > > >> True, but as Larry said, either side is problematic. Too loose of a > >> CoC with no enforcement and nothing really was changed from today > >> considering we already have the post that Rasmus made 6-7 years ago. > > That implies we do *need* change from situation today. But so far I > didn't see anybody claiming situation today is problematic (not in terms > "not having CoC makes us look uncool and we want to be cool" but in > terms of "something bad is happening right now and we need to take > action to stop it".). Now, I have nothing against looking cool, and if > we can make the community look cooler/safer/warmer/welcomer/more > unicorns and hellokitties with no downsides - sure, why not? The part > that is worrysome for me is the one with downsides, namely "enforcement". > > having a CoC is not just a cool shiny thing, it is like having an emergency plan, it doesn't matter much until you need one, and some people are more comfortable knowing that there is one ready. everybody start without one, and usually it is better to prepare it beforehand than after the first real need for it, and coming up with one while going through the emergency is asking for trouble. currently we also have no way of knowing how many people are actually uncomfortable/leaving because we don't have one. > > Perhaps there's a path to compromise here though. A CoC plus a > > Response Team *without* authority for any punitive action would be a > > step forward. We don't have to solve every problem right up front, we > > can start with: > > that something which resonates with what Sara said and similar in nature what we do with security@, point of contact, with trustworthy people experienced on the topic and without any additional privileges apart of being able to seeing the reports and being able to discuss the reported problem and escalate if necessary. > I think if we would talk about moderation/mediation team that would try > to resolve a conflict and in a complicated cases - like irresolvable > conflict which makes collaboration impossible - prepare an impartial > summary of the issue and let the community take an action, and maybe be > able to alert necessary people (or even have such people as members) in > case urgent action - like emergency block to stop publishing sensitive > information, etc. - is needed, I would have no problem with that. > that could be a good compromise, I suppose we could cover most of the stuff which could have immediate actions with having somebody with web/* karma, somebody with php-src(preferable also including Zend/*) and somebody from the systems@ team. > I had numerous instances in the past where skillful third-party > mediation allowed resolving differences and pave way for cooperation. So > having people that can do that and are publicly known address for doing > this is a good thing to me. If we lose the punitive focus and have more > "what we want to do and what should happen" and less "what should not > happen and how badly we'll punish you", it would be much better. agree, and this was also mentioned previously my others, so I can't add much to it. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --047d7bf0d966ebc8a205289e0b75--