Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90519 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81362 invoked from network); 11 Jan 2016 20:31:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Jan 2016 20:31:29 -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.51 as permitted sender) X-PHP-List-Original-Sender: ircmaxell@gmail.com X-Host-Fingerprint: 74.125.82.51 mail-wm0-f51.google.com Received: from [74.125.82.51] ([74.125.82.51:34997] helo=mail-wm0-f51.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/67-40147-02114965 for ; Mon, 11 Jan 2016 15:31:29 -0500 Received: by mail-wm0-f51.google.com with SMTP id f206so226987267wmf.0 for ; Mon, 11 Jan 2016 12:31:28 -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=YhlkhNYP9T8Zehs0u+dlEbhFpcUFmrBSfnSIu7Ft4LM=; b=qFydFm3q9e/ot9Cxlz7E4DI8t8tWijPah8Hw5o/vdtj8yK56d2OiVfdA5aOe+u105e aawpuwwwo2AoNncQk+XPIj/wfH83PC4BOKw2Tl0uYb1h4dHa3GwlEf/0+BTfvM3w401S vLddfDEH7IFT8FFiABqFw5XuILQJj8U09ypige/y7UX2dmv9zHS9wIwCie2jLNbBcc6D x4lpD/DwhIuG1AJiNqslM2NsTLfZprHm07EZt5dTUStE3YtcEcoYTZfrUunQeLud6AWd lE/RmYW8DHWYPU4xS3jsAqZ6TRdnGKposBxdz0BfYvIKji1YSO1wteuT0MbsDDrr4/zS tpvg== MIME-Version: 1.0 X-Received: by 10.28.126.77 with SMTP id z74mr16475762wmc.3.1452544286328; Mon, 11 Jan 2016 12:31:26 -0800 (PST) Received: by 10.28.11.77 with HTTP; Mon, 11 Jan 2016 12:31:26 -0800 (PST) In-Reply-To: <56940D47.3060206@gmail.com> 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> Date: Mon, 11 Jan 2016 15:31:26 -0500 Message-ID: To: Stanislav Malyshev Cc: Pierre Joye , Brandon Savage , Larry Garfield , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: ircmaxell@gmail.com (Anthony Ferrara) Stas, On Mon, Jan 11, 2016 at 3:15 PM, Stanislav Malyshev wrote: > Hi! > >> I fail to understand how one can think that the CoC could be about >> censorship (which is basically what this comment says). > > I can explain you that very easily: there are known instances where CoCs > were used and even more instances where there were attempts to use CoCs > and CoC-like structures exactly for that. It's not a concern because > people think it *might* happen, it's a concern because it *already > happened* elsewhere and people think it also might happen *here*. Can you cite examples of where this has happened before? Perhaps studying those incidents will reveal insights we can use to prevent it. >> I also fail to understand how one can fail to accept that we already had >> and have issues, despite numerous people having experienced it. > > That's because nobody does that. Instead, the question is whether the > specific proposal is helpful to fix specific issues. The conversation > goes like this: > > A: here's solution X! > B: for what? > A: for problem Y > B: but do we have problem Y? Also, X does not seem to solve Y and also > introduces problem Z > A: we can solve Z easily! Also, here's proof problem Q exists. > B: but Q is not Y. And we didn't see Y exists so far. And your solution > to Z sounds iffy. > A: why you keep denying problem Q exists?! I don't think that's a fair characterization of this discussion. Some people have questioned what this is a solution to, but most haven't. Some have questioned if we have a problem, but most haven't. Most of the constructive discussion (meaning the discussion not using hyperbole or overloaded terms) has been not talking about if we need to do something, but if what is proposed is good or not. And the best parts have been help molding the proposal to be better overall. >> create a somehow useful CoC. If we do not see us having problems, there is >> no point to even discuss a document to solve non existant (for us) problems. > > As I note again, talking about abstract "having problems" as an argument > to do a specific thing is not very useful. > >> As a side but important note, it is very disturbing to read so many of us >> denying the very issues we have. Even if it is denied in a very diplomatic >> way. I am convinced that this is the first problem we must solve to get a >> CoC, to accept the very existence of these problems. > > First of all, asking for proof and denying is different thing (though > people often confuse the two, but these *are* different). Second, "very > issues we have" is, again, very unspecific thing, so it's not even > possible to deny it. Before I could even deny that "these problems > exist" - or before you claim I or anybody else does - I'd like to know > what exactly are "these problems" in specific terms. Because some of the > problems were almost unanimously recognized, some was not, so it's not > clear what parts we are talking about. 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? As far what exactly "these problems" are specifically, that's an entirely different discussion than the one we've been having here as part of the CoC. Because the vast majority of "these problems" aren't the goal of the CoC. The goal of the CoC to me is to help create a safe place. To create a mechanism and reinforcement that we should all behave appropriately. Other issues (such as over aggressiveness on the list, etc) are out of scope right now, so aren't worth discussing *in this thread*. Feel free to discuss it as much as you want in another thread, but I'd like to see this one get back to constructively discussing the proposal. Well, not really "get back to", but "start". Anthony