Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90332 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52864 invoked from network); 7 Jan 2016 22:58:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2016 22:58:14 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.180 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.180 mail-pf0-f180.google.com Received: from [209.85.192.180] ([209.85.192.180:34437] helo=mail-pf0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DA/7A-21405-58DEE865 for ; Thu, 07 Jan 2016 17:58:13 -0500 Received: by mail-pf0-f180.google.com with SMTP id q63so194998pfb.1 for ; Thu, 07 Jan 2016 14:58:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=fx1DaXJvWyxjgqgKcAFavW3rOoxQ/kVCpuradzPV5ms=; b=vWpUjzgu/2fi+Yd9/G8AaMhbP4xJcDZJ5BX+6qq/yN/iVDHl6mo/OfkyeJXVSKdSE9 +1Ux9q3rxCg7DV8a5k7L9NMV1ONJ/wMzBAM3kAKvk/fBtDbCTxHDdZR5OONAHGps6Kwt dplOkRYvJZ4+cwjXRevrNZ2su16QD5V8d5lQ5KvpVsdz5MUyGQ0ZUMXKdVplWllhk8ec P1c9IoKi0ZFoIJCNLG6UjB7mpKBDJA2UHnmvD9i3A8EUsJlUHb4YqvGNbwxcTkGYa9C3 Tql1YkGlRPxlc5z7JttIvgCe7in9YJDcdgBGFW7OCsMQT1Oqzumsc3Sm5abCn/c2eed5 GJKA== X-Received: by 10.98.66.139 with SMTP id h11mr103086pfd.121.1452207489944; Thu, 07 Jan 2016 14:58:09 -0800 (PST) Received: from Stas-Air.local ([12.97.215.254]) by smtp.gmail.com with ESMTPSA id fc6sm162563908pac.44.2016.01.07.14.58.07 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jan 2016 14:58:08 -0800 (PST) To: Pierre Joye References: <66E04ACF-7363-4E47-BFFD-E380E5B1EA23@gmail.com> <6D.39.21755.3576D865@pb1.pair.com> <1AD1B991-A3E5-4D6C-A532-5F0FCCC2ED61@gmail.com> <568D7C5D.9020405@php.net> <1e6a13607a3a1c8b20a4649f8a5ef767@mail.gmail.com> <3AB5AA82-4F17-40C3-B8B5-33697A8DBEC2@gmail.com> <568E9D01.1020808@gmail.com> <568EA4F1.9070802@gmail.com> Cc: PHP internals X-Enigmail-Draft-Status: N1110 Message-ID: <568EED7D.2090207@gmail.com> Date: Thu, 7 Jan 2016 14:58:05 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > It is not what I am referring to but harassment, insults, attacks or > similar events. I do not think we need to discuss endlessly that we Proposed CoC says "insulting/derogatory comments" and "[o]ther unethical or unprofessional conduct". And that can be (and in some cases has been) treated very broadly - from "how can an ethical person support that fraud of a politician X" to "your statement in support of policy Y is offensive to group Z and therefore is insulting and derogatory". I want to avoid that as much as possible upfront. > It is not about taking actions now blindly but to create a structure > that allows to create action when necessary, after investigations, > discussions and decisions, with common sense in mind during all these > processes. Is it not obvious? I feel like you keep come back to What I am trying to say is that supporting doing something with argument "we don't know if this is needed or if it would help, but since we can't conclusively prove it would not we must do it" - is a very bad argument. > extreme cases where common sense should apply. I agree that we have > seen cases where it happened. So let try to prevent them here. But not > at the price of creating a CoC with no power to actually ban someone > if necessary (even if I am sure it will happen extremely rarely). We already have power to ban someone, that doesn't need to be created. The question is how this power is to be applied. -- Stas Malyshev smalyshev@gmail.com