Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90124 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52579 invoked from network); 5 Jan 2016 18:27:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2016 18:27:27 -0000 Authentication-Results: pb1.pair.com header.from=kevin@gohearsay.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=kevin@gohearsay.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gohearsay.com designates 50.116.30.253 as permitted sender) X-PHP-List-Original-Sender: kevin@gohearsay.com X-Host-Fingerprint: 50.116.30.253 li495-253.members.linode.com Received: from [50.116.30.253] ([50.116.30.253:41504] helo=frodo.gohearsay.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id ED/AD-12097-E0B0C865 for ; Tue, 05 Jan 2016 13:27:27 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gohearsay.com; s=default; h=In-Reply-To:To:References:Date:Subject: Mime-Version:Message-Id:Content-Type:From; bh=OwgFcsDYDo9xte5M93JScpVnzlhWHdgb95w99+l6yNk=; b=XLsTDmTtMBwkrxKWmFAYCxfs5q 9df+boQ38qb2swcpcyda+dWiF3nUcgsxEX1tZ4PE31qpnaE2R9XseFFRLHbOoq3bsE6lIm4QxYM6G NVU8EL2GeAk4D68DPQm6VkIAc86nWOjWy/BaMf4vaLBsi52b/LZO6Wr/SyYa6svdfMZg=; Received: from c-68-52-158-4.hsd1.tn.comcast.net ([68.52.158.4]:36641 helo=[10.0.1.6]) by frodo.gohearsay.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.86) (envelope-from ) id 1aGWKK-0004W8-GL for internals@lists.php.net; Tue, 05 Jan 2016 12:27:24 -0600 Content-Type: multipart/alternative; boundary="Apple-Mail=_82ED44BE-58C2-411A-B5E8-DC63E5729653" Message-ID: <7995F3E4-D9BC-499C-9D62-EE804D3292EF@gohearsay.com> Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Date: Tue, 5 Jan 2016 12:27:22 -0600 References: <568AE803.1080209@gmail.com> <568B0C8E.3080206@eliw.com> <568B1041.1060601@gmail.com> <568B1DA8.3060908@gmail.com> <568BD0CA.7040909@php.net> <568BE845.2090102@php.net> <568BFF63.3080403@garfieldtech.com> To: PHP Internals In-Reply-To: X-Mailer: Apple Mail (2.3112) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - frodo.gohearsay.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gohearsay.com X-Get-Message-Sender-Via: frodo.gohearsay.com: authenticated_id: kevin@gohearsay.com X-Authenticated-Sender: frodo.gohearsay.com: kevin@gohearsay.com Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: kevin@gohearsay.com (Kevin Smith) --Apple-Mail=_82ED44BE-58C2-411A-B5E8-DC63E5729653 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Much of the argument in favor of a code of conduct seems to be centered = around the desire to send a message to the wider developer world that = we=E2=80=99re a welcoming community that doesn=E2=80=99t look kindly on = poor treatment of others. If that=E2=80=99s the goal, rather than the = goal being to punish or censor people who violate our own values, why do = we need a response team with the power to ban? If a person's treatment of others truly warrants banishment, then as = Zeev noted the RFC process is already perfectly suited for that. As far = as I=E2=80=99m concerned, the absolute greatest power the response team = should be given is the power to issue a censure. If sending a message is = the goal, that=E2=80=99ll do it. Kevin Smith http://gohearsay.com= --Apple-Mail=_82ED44BE-58C2-411A-B5E8-DC63E5729653--