Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90366 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62072 invoked from network); 8 Jan 2016 16:53:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 8 Jan 2016 16:53:53 -0000 Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.41 as permitted sender) X-PHP-List-Original-Sender: ircmaxell@gmail.com X-Host-Fingerprint: 74.125.82.41 mail-wm0-f41.google.com Received: from [74.125.82.41] ([74.125.82.41:34715] helo=mail-wm0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 13/C0-55593-0A9EF865 for ; Fri, 08 Jan 2016 11:53:52 -0500 Received: by mail-wm0-f41.google.com with SMTP id u188so144180799wmu.1 for ; Fri, 08 Jan 2016 08:53:52 -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=d8uuuCHC+uj4Q+tgeNN5traLsx1xKM7zkbsbjGHj9sg=; b=KnesdOpYxLtCxSVboS3wjgYmyFVWGdUoddbLomV7DNP5iARD0R7d6KDZ5MH6zDxJfX e+9a9QPmpU71DljYlI/ZSwPRkwcHEHNf87WP6XqI1ch7etowCbE67fw0bJ8CZ0Zh7+7a zXB/v+AHQrnMLdUH7OB2jmZVhA2nDBwgpSW7156E7kkhrwRWzO0vIsBkmmqe7vnP8zS3 T6qgVUJbNHvpS99Pp1Eux6pjmxglBvxUfSmjUZ5QLRoFba5Y6XtbkLo5UVnF59M01KSR BcubkHv0ug+VGlc6nlRr7brIk9ByJPcuOqg1N7PsCpq3M4gis4BgmGRIBsGuzDGH1i0m TsEw== MIME-Version: 1.0 X-Received: by 10.28.225.132 with SMTP id y126mr24636530wmg.98.1452272028155; Fri, 08 Jan 2016 08:53:48 -0800 (PST) Received: by 10.28.11.77 with HTTP; Fri, 8 Jan 2016 08:53:47 -0800 (PST) In-Reply-To: <568FE61E.4010902@caseysoftware.com> 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> <8D90A4F6-4E3E-4283-B8E3-152E4707EF4E@moonspot.net> <568F4E81.1020205@garfieldtech.com> <568FE61E.4010902@caseysoftware.com> Date: Fri, 8 Jan 2016 11:53:47 -0500 Message-ID: To: D Keith Casey Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: ircmaxell@gmail.com (Anthony Ferrara) Keith, On Fri, Jan 8, 2016 at 11:38 AM, D Keith Casey wrote: > On 1/7/16 11:52 PM, Larry Garfield wrote: >> >> On 01/07/2016 10:08 PM, Brian Moon wrote: >>>> >>>> Why not? The harassment has been nullified. >>> >>> I agree with your position on most of this, Paul. However, free email, >>> and thus, Twitter and other social media accounts are nearly >>> unlimited. It becomes an arms race to try and block someone. >>> >>> Brian. >> >> >> Simply cutting off contact (either by the receiver of harassment or >> otherwise) isn't the entire goal. There are least 2 others: >> >> 1) Harassment does not need to be direct. If I were to start tweeting >> up a hostile, insulting storm about someone else on this list, by name >> and talking about PHP Internals business, but not tweeting @ that >> person, them blocking me isn't going to accomplish anything. The harm >> isn't that they are seeing the message necessarily, it's that everyone >> else I know is seeing it, many of whom that person may not even know. >> That's still an attack on a person's reputation, and damaging to the >> person. > > > Good scenario but we don't have to be hypothetical. Let's apply it to the > real world of this week: > > > Throughout this discussion, Paul Jones has been active and - despite vocally > attacking the proposal - I have yet to see him attack anyone in general. > > And then Phil Sturgeon else used a sexualized term to insult Paul to his > ~16k followers but didn't name him: https://archive.is/oeekT > > While Phil claims this is not sexualized, Urban Dictionary disagrees but > then he follows it up with a claim that he doesn't represent the project > anyway: https://archive.is/TA2YP > > According to the definition including attending conferences that use the PHP > logo and active in PHP channels, he does. > > And then Phil follows it up with another more potentially damaging attack - > again, without naming Paul - https://archive.is/Z3zNy > > And finally, it turns out it's all Phil is blocking Paul anyway - > https://archive.is/6iZQY - so Paul wouldn't even have see the attacks to > defend himself or report to the PHP Code of Conduct group. > > So my questions: > - In his day to day interactions, would Phil be considered a representative > of the PHP team? In normal day-to-day interactions? No, I don't think so. In this case, considering he's directly discussing the project at the time, I think that it would be fair to say he is representing the project in context. > - If not, why not? > - If so, do his personal attacks using sexualized terms constitute a breach > of the Code of Conduct? I think a strong argument could be made for that. Either way, I don't think it's the level of comment or discussion we want to encourage, so whether or not it's a "violation", it's definitely something that's bad. > - If not, why not? > - If so, what would the consequences be for Phil? Depends on the precise version we adopt. I think having someone step in and say "Phil, cut it out" would be enough. Though if he continues to do it, then we may want to escalate further. In general, I think the fact that we tolerate that sort of behavior is insane. The fact that many in this thread are suggesting that "it didn't happen on list, so we shouldn't care" is extremely narrow. We should hold ourselves to a higher standard. We should commit ourselves to treating each other fairly and with respect, even if we disagree with that person. I know I have crossed that line before. I've also apologized each time, and am honestly working hard to not do that again. None of us are perfect in this regard. What we're talking about isn't a "if you're not perfect, get out". It's a "we know you won't be perfect, but that doesn't mean we should tolerate bad behavior either". Anthony