Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90757 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53800 invoked from network); 20 Jan 2016 23:42:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jan 2016 23:42:44 -0000 Authentication-Results: pb1.pair.com header.from=padraic.brady@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=padraic.brady@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.43 as permitted sender) X-PHP-List-Original-Sender: padraic.brady@gmail.com X-Host-Fingerprint: 74.125.82.43 mail-wm0-f43.google.com Received: from [74.125.82.43] ([74.125.82.43:34231] helo=mail-wm0-f43.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 6F/CA-22511-37B10A65 for ; Wed, 20 Jan 2016 18:42:43 -0500 Received: by mail-wm0-f43.google.com with SMTP id u188so205183234wmu.1 for ; Wed, 20 Jan 2016 15:42:43 -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:content-transfer-encoding; bh=lpZ8isOpiA5jLPY/rvSQtd4ziaFpWV1ZfjkqFBZLsG4=; b=aaPhaVYTAp9yHN4ss+CApTTYXqPo5zP9YF7aQTaopQsJpqGhfKPisMHwZhBkYQLGXM S8sfC12l+7xm/WH6xTeMwPxhHdhuvQir0WjBfjgc3FLuwEEz6A4MrpgeAOVsjSA1llhc RdhDfB8gP9Oj4bjiy7VePcMDUGvogScSxGl3QBdDu5u4NpNV9tc9HqopYup0Dw3T98rQ rpVeoUoaaXOkW9TfjpArinbROxKN8h9U19mnd7i/N5v7pLxJi7OrwVzVRgRGOqYNxT8S jC/35lL30owpdp74jD7X4ZE/6q822kX/9Yocc3dzvpmzzwmsGuX2OBI6jVNQSe8MlhOQ J4FQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lpZ8isOpiA5jLPY/rvSQtd4ziaFpWV1ZfjkqFBZLsG4=; b=LlbS6uqKr/Llt1gDVSaLxQN5eqxwLv39qJ1r5kgRwV5m4vWAdt6bOGxRvlsxlFGuFP VMlxel4xx2bH1XrXFbSqsYg65tq1wNyXOgL+0v4wwKd61pJFXAeUFf+Ruuxj5T3iNoxH ayj4esVvc07mn9AiGPgH4ZqCRI12amS4Ov3w2a8JTgwrfOlPUds/LZJcqlre/Pl3aNYC aAYM+hVGQYVWJdelJE+fHQw5G/IuKY3CVkUBJvOBWZmcacbskiGmpO2+8v9ZlMC+nYU2 hcJGbOQbsbevwS/kBUd1j65SFOC7toAM2pAnWdvVfXmhuqRa0P0kfF6kB1ISJB9wTSwH HhLg== X-Gm-Message-State: AG10YOSKhv9Efa11Tw6SAngc2rBfqcaFABwSea0Jy5MPQDlV0uc9Q+atT0M0mFIzOjs81rbacnQWrGMgjV+/kw== MIME-Version: 1.0 X-Received: by 10.28.221.85 with SMTP id u82mr7007907wmg.95.1453333360075; Wed, 20 Jan 2016 15:42:40 -0800 (PST) Received: by 10.28.152.212 with HTTP; Wed, 20 Jan 2016 15:42:39 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Jan 2016 23:42:39 +0000 Message-ID: To: Zeev Suraski Cc: Derick Rethans , PHP Developers Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] [Re-proposed] Adopt Code of Conduct From: padraic.brady@gmail.com (=?UTF-8?Q?P=C3=A1draic_Brady?=) Hi, Up front, I agree the objective of the COC needs to be clearly stated. There is confusion, whether it's here or externally by observers, as to whether this is intended to fix mailing list toxicity (I assume, for now, not) or intended to state the projects intentions should there be a complaint concerning conduct as specifically listed in the COC text per the RFC. It serves neither side when this confusion gets muddled into argument for, against or in-between. On 20 January 2016 at 22:14, Zeev Suraski wrote: > I'm not going to repeat arguments I've made half a dozen times as to why = having a judicial system must be avoided, and why we must deal exclusively = with desired behaviors and not the 'exception handling' of bad behaviors. = I made my case in the best possible way I can and people who are interested= in it can read it in my previous replies on the topic. Equally important = - many others expressed similar views. Thus far, the only response is a la= conic 'without penalties it's useless', even though we've brought numerous = supporting arguments as why this is simply not true. > > I will repeat that I'm very much in favor of a CoC that includes our posi= tive core values, and that includes a mediation team in case people are fee= ling offended and that can intervene also w/o complaint - but that does not= have any sort of special powers - but is instead exclusively based on good= will of all parties. Even if certain people don't think that's good enoug= h, I don't believe that anybody would argue that it's BAD - the way many th= ink the current CoC proposal is. This is precisely why this is the right p= lace to start. > > Thanks, > > Zeev At a basic level, what exactly is a code of conduct where the only consequence is mediation, where both parties are assumed to have good will, and where the outcome is ??????????. That's the a problem from my perspective. What is the outcome? Does mediation continue indefinitely without results? While the mediation is ongoing for the long haul, will be there be any remediation set to protect a theoretical victim? What is Plan B? Part of the COC is to explicitly limit ad-hoc reactions should things go completely down the gutter by defining something upfront. By extension, any uncertainty of what would happen should Person A complain may act as a deterrent to making such a complaint. It could be anticipated that long drawn out procedures with an unknown ending are in and of themselves stressful (and to both parties to boot). Sincere apologies if this is covered elsewhere. Paddy