Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90889 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42645 invoked from network); 24 Jan 2016 20:16:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jan 2016 20:16:07 -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.170 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.170 mail-pf0-f170.google.com Received: from [209.85.192.170] ([209.85.192.170:35614] helo=mail-pf0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/00-42451-50135A65 for ; Sun, 24 Jan 2016 15:16:06 -0500 Received: by mail-pf0-f170.google.com with SMTP id 65so70463076pff.2 for ; Sun, 24 Jan 2016 12:16:05 -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=Es2H1a3uXTROY3TRwr7D4OJGemppHldirZ6Duec93H8=; b=s8CCu6Yz619/SRGQhUk7QGV50TcdBR60SIa+tLmDMAZ2Wy2YzI0BZ8UxYn5F3HDOJw bwcwz4SZIA+iAHh9d7PUAmNeS8LKMNO3d48QVBeeUI9mf3A+nuxGzQBx5rTFNXBRAxnx d05T2ozF2WL4ePCgUNaCvaLzSZbzh3r8Ugtf98GGEyXz8kqItBQd18L9ht2RoNIGvsh/ d3NsUB1qq5GE3spmFqpYDYN7Ct1aGzcZqD96OidsGwK/TaAjEkc+Aygt8ofrG9HweDL+ ynvnRcXKqtwUJvXNC8fRWGiEc/rdPK5YKLYalkiQGSx9IzrvEnVJSN/0o2WC3gLsaDSe anew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Es2H1a3uXTROY3TRwr7D4OJGemppHldirZ6Duec93H8=; b=BokuKrS4cG6w8Bxm9V+2aKC4Lr6zp58Sv6P5UgQn2F/xHvMtDIEqv5vVcz8BqXKQrE dwZDHgfIPN/ShVMi5JnUvcp/r5q5ZfddGNJ9C5VVlpxBPoRVmWyzHoEmTuDVs9eW1mWc ihjILqbpNUuhICZyh9BvfzbbjIpq+Zqd+PQ8lqTt+hsB3IUNuR2VTJdlJQujMZZTCe8h g7IdegWnB4NSKlcHGi5IVD+z7CXY1okSiL2Yji1q2xmhZXoPyRs2Dy5FW/nnzXyH9soH VcixpyWMKt+YaXFFR6VEnpzcGO8Jw4SR8w1P5wxcT2edPt+ZGkO8313XxH/tVj/WnOAz luBg== X-Gm-Message-State: AG10YORmkiHnLCQAdX8yG2cLKmeCVTLDoo+0j4LJEU96wu1IZC3E7+fnERvlLK/WK1751w== X-Received: by 10.98.80.79 with SMTP id e76mr20575158pfb.126.1453666562790; Sun, 24 Jan 2016 12:16:02 -0800 (PST) Received: from Stas-Air.local ([2602:304:cdc2:e5f0:d507:643:d3c:eb3d]) by smtp.gmail.com with ESMTPSA id h87sm23377444pfd.33.2016.01.24.12.16.01 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 24 Jan 2016 12:16:01 -0800 (PST) To: Zeev Suraski References: <56A3F0FA.1050609@mprelu.de> <56A46649.8030802@gmail.com> Cc: "internals@lists.php.net" X-Enigmail-Draft-Status: N1110 Message-ID: <56A530FD.6030404@gmail.com> Date: Sun, 24 Jan 2016 12:15:57 -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] Re: [RFC] [Re-proposed] Adopt Code of Conduct From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > That's true, but I think that somewhat goes against the point of > having a 'penalizing CoC'. The list of violation is supposed to be > detailed and exhaustive. Well, this is part of the problem with "penal code". To create and maintain one, there are teams of very highly paid professionals working for years. That's how they reach "detailed and exhaustive", but even then they have to update it constantly and spend years arguing about it. We don't have any resources to do that, so I think we should not try the "penal code" approach. Instead, we should take "reasonable person" approach - if it is obvious something bad is going on, then something bad is going on. If there is a disagreement about it, moderation team comes in. > As far as I can see this is more or less based on what's in the US > law: http://www.eeoc.gov/laws/types/ Maybe. US law, however, is very much a product of both US history and current US political constellation, and taking this as the sacred text looks both imprudent and somewhat narrow-minded. US law also exists in a vast ecosystem of case law, legal practices, governmental regulations, etc. which complement it - none of which we have or need. So we should not borrow from it needlessly. > Again, here too, I think it is in fact supposed to be exhaustive, > with the exception of 'similar *personal* characteristic'. Would That's a contradiction :) You can not be both "exhaustive" and add an out clause of "also whatever we like to add in the future", but you have to. And that's the fundamental problem with the laundry list approach. That's why I do not like it. Because it grows too large and still is never complete. > control access be considered discrimination? Would someone not > willing to cooperate with a member or supporter of a US/EU designated > terrorist group (say ISIS) be considered discrimination? Good question. There's a potential for a lot of rule lawyering and controversy about such things, and I think the right way to handle it is not to try and write down every special case. -- Stas Malyshev smalyshev@gmail.com