Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90520 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88786 invoked from network); 11 Jan 2016 22:05:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2016 22:05:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=dz@heroku.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dz@heroku.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain heroku.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: dz@heroku.com X-Host-Fingerprint: 74.125.82.42 mail-wm0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:35782] helo=mail-wm0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/10-21941-54724965 for ; Mon, 11 Jan 2016 17:05:58 -0500 Received: by mail-wm0-f42.google.com with SMTP id f206so229642774wmf.0 for ; Mon, 11 Jan 2016 14:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heroku-com.20150623.gappssmtp.com; s=20150623; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vz40mu4gG2Hb+E3Efy7DCqJvTnHSsILDy4Lt5wZ/9XU=; b=znG1jhc9HChtWABxxxYWPGmjK25ciMa5AdTBdThO5ynmemIaVHJq94NmzFBjD8XEQF FuMKc1d97bn33yqJtTMVTJi0wKsWzX6zFucVMhkSjKCdBjmUHSrJ4OQcXo8lFHxoI5vj sXkvznheqIe5iuZnTrvW02uNjpK6fbnKFW91h1P6ZHQrDHNBxEJvbWQOX5OFT7xfxh7g 8rjpkD0c6+UgYiB9zfWziUpZVBetuUFxthvvmPR4KWqr/55quzlLbV99KJHaBB2WJkPW NlUkP51/tyreG1u0s3rO+Q+se4VLF1Ca2pEC5q/vPQQyu+V1EN8565fmMVvx/U/Xmf3G liLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=vz40mu4gG2Hb+E3Efy7DCqJvTnHSsILDy4Lt5wZ/9XU=; b=jeoUVaucHaKNF/tM3JTNsEsCCUULLR2U+nIx/zF13X4ECPUrPEObo3D8fpUzAF7Xeu kufU6t+CTLKgwCZfXOil6nrmstgaPQkDzGUnHKS90dVS7DeoeSj+IDp6pEl8n5D46sp8 bZZ5Oh1zR/i0fbU0vC8sSW9K2Tmzq3La3NIK6pXCYW2htTNP7vaR0JyYVXTQo7r7t/cd PC62iXwZa/jgBArVlT9yz1h/stwKhQn5rr4jCrD2k1YpwTxM2+mLAuNiLC0by0z/9OCt Km/E8PIsGjtuqdSZespmMmm/wMh2coeN0MfS9glvYNrtFHV7Sf7EPUk91ZevShsRCh6V Bbeg== X-Gm-Message-State: ALoCoQmZiOL47G+EYHgCe3xYzr8nKBkIh66SgXR/JzZo4ImdOYbUuoD+K90WcwLPIzif0p+Uc+f5fDBxX6kyh2iRzFDAql0zXQ== X-Received: by 10.194.205.5 with SMTP id lc5mr100191630wjc.163.1452549954789; Mon, 11 Jan 2016 14:05:54 -0800 (PST) Received: from [172.20.10.5] (ip-2-206-1-225.web.vodafone.de. [2.206.1.225]) by smtp.gmail.com with ESMTPSA id 67sm14708385wmp.20.2016.01.11.14.05.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 11 Jan 2016 14:05:53 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) In-Reply-To: Date: Mon, 11 Jan 2016 14:05:47 -0800 Cc: Stanislav Malyshev , Pierre Joye , Brandon Savage , Larry Garfield , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: 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> <56940D47.3060206@gmail.com> To: Anthony Ferrara X-Mailer: Apple Mail (2.2104) Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: dz@heroku.com (David Zuelke) On 11.01.2016, at 12:31, Anthony Ferrara wrote: > Actually, asking for proof and denying are the same thing. If they > weren't, then why would you be asking for proof unless you believed it > didn't happen? They are not the same thing. If you make a claim, then the onus of proof = is on you, and you cannot simply turn that reasonable request against = them by then implying they're denying. Otherwise, why have proof for = anything at all? To me, this begs the question: would you handle incidents covered by the = CoC in a similar way, with that same attitude? An accuser claims = something, and asking for proof will be interpreted as denial? By extension, will a third party asking for proof for an incident be = subject to kafkatrapping - "the fact that you're doubting X happened = means you're also guilty of X"? That one has happened to me before on = twitter. Didn't stick because of the ridiculousness, but maybe the = conjured mob was simply not large enough to spark sufficient outrage. I'm pretty uncomfortable that you as the person "in charge" of this RFC = hold such biased views. If you can't see that asking for proof and = denial are different things then that IMO disqualifies you for that = role. The same applies to your claims of threats of violence. It's fine if you = don't want to provide details, but then you can't bring those cases up. = It's legitimate for others here to ask you for evidence if you do bring = it up. I understand that we're all different personalities and you're = maybe more wired in that direction (mentioning something in passing), = but you need to understand that once a claim is out there, it's up to = you to back it up. If you then refuse to, it raises doubts, and = rightfully so. Otherwise, we "just have to take your word for it", and that's exactly = the thing many here are afraid of when it comes to this RFC - that in = the future, anyone can pull accusations out of their hats, and the = accusation is enough, because "why would you be making that accusation = if it didn't happen" (please compare that sentence to the quoted section = at the beginning of this message to understand why it is relevant. David