Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90504 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45274 invoked from network); 11 Jan 2016 16:00:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2016 16:00:41 -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.173 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.173 mail-pf0-f173.google.com Received: from [209.85.192.173] ([209.85.192.173:34281] helo=mail-pf0-f173.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/01-40147-9A1D3965 for ; Mon, 11 Jan 2016 11:00:41 -0500 Received: by mail-pf0-f173.google.com with SMTP id q63so48006037pfb.1 for ; Mon, 11 Jan 2016 08:00:41 -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=JHBcS6eX5ht2aGloLethc+AKiteDO5ZYk4Jr4ThhHb0=; b=XbsCC+8CbFZz274GetCQRold6NP8Is4/TqUVulVe79PAtZnLGvBottftx3ShbongKE qK9PGt4+gtDWqw+R+XceUAFqABxxpZm+aNXrehqOFAq2wObSONPGW24QLXBwzac5LXAd q8MeTirpqoLaAZpxiAK8BkTjo8rh4gauwl31LM23kcbX49gcNZKltH/jgQk6lbyZhDqm w3Co6zbTbrXDaIq5ZVFTlPnC5FqmrLlCN/m2H5ERub8IRLkFyIeIeK6txa2T2P2UkLiv e8TA2kKCpy+PxRDg+UFzFo5WKzEvax2SgsxQmVHQJ0tJkm6kuuHlW5y7KJY39BY3Pc6M NzRQ== X-Received: by 10.98.14.81 with SMTP id w78mr27292323pfi.26.1452528038796; Mon, 11 Jan 2016 08:00:38 -0800 (PST) Received: from stas-air.router ([166.170.39.245]) by smtp.gmail.com with ESMTPSA id dg12sm145737970pac.47.2016.01.11.08.00.37 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 11 Jan 2016 08:00:38 -0800 (PST) To: Anthony Ferrara References: <910b145571b2c3e98338d54c0dd6a981@mail.gmail.com> <0E9E4C89-1800-4000-BD5A-BC81F43BE2FE@gohearsay.com> <44142A2C-0E7C-4525-880F-7759CD8A502A@heroku.com> <5691D820.4080309@gmail.com> <56934116.70002@garfieldtech.com> Cc: PHP internals X-Enigmail-Draft-Status: N1110 Message-ID: <5693D1A4.2050208@gmail.com> Date: Mon, 11 Jan 2016 08:00:36 -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! > least hold ourselves to a level of mutual respect. Going out and > calling someone a moron in public is not constructive nor respectful, > and IMHO we as a project shouldn't sit back and blindly say "whatever" > if it happens. OK, so what should we do instead? So far my calls to apply some TDD were not heard, maybe this time? Let's consider an example of twitter user drupliconissad. It may be genuine individual or a troll, it doesn't matter either way. If you read the feed, you can find much more than "moron". Now, had we had CoC, what would we do? We don't know who that is, so private moderation is out of the question, even if we did - it's not look like a personal conflict that can be amicably reconciled. Should we issue a proclamation saying "we think some anonymous account on twitter is being bad"? Should we ban that person (or group of persons - we have no idea either way), which we have no idea who that is, from our list? Any other ideas? -- Stas Malyshev smalyshev@gmail.com