Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90317 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24227 invoked from network); 7 Jan 2016 20:39:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2016 20:39:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=chasepeeler@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=chasepeeler@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.169 as permitted sender) X-PHP-List-Original-Sender: chasepeeler@gmail.com X-Host-Fingerprint: 209.85.214.169 mail-ob0-f169.google.com Received: from [209.85.214.169] ([209.85.214.169:34634] helo=mail-ob0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7A/05-21405-30DCE865 for ; Thu, 07 Jan 2016 15:39:31 -0500 Received: by mail-ob0-f169.google.com with SMTP id wp13so201660795obc.1 for ; Thu, 07 Jan 2016 12:39:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=tkI7wyVWiTi8X8NOcooEVClx+/hNQxI6BS80XZz5qgQ=; b=jZUeqJtaT0Y2LAOFSWql4z8+TyRzYpSDXT82IRviW39q23ykdWv5lNbKFrd2/WcQSW 1FNs+BHumkixf0qj8WD+Cb17tXaTkPoiJdBc4Xv3TPvgLXiKldF8UT8XVNdA4CfVsswN Gs/TbWy9ECMQFCD4qJrcS1QSEcwb1CxEhbWDBz0b1gzUDSKWk2MuzRlnNydtEX990UWQ 8jUaOle7LYEMxwQCvsE5pigNSwhHJyCt1SP2vutG7+A8qFV5Zk49MG2Uf29yWzDvBT1Z knfkXpgtbFpRgXdfU4FsyPX/LuewYEJNS37ge85jt8Hku1oRJEJdkwLJjaLfOxpVyGbL q3PQ== X-Received: by 10.60.220.230 with SMTP id pz6mr10398803oec.49.1452199168865; Thu, 07 Jan 2016 12:39:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.144.65 with HTTP; Thu, 7 Jan 2016 12:39:09 -0800 (PST) In-Reply-To: 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> <0AFAA09D-0933-4C8D-91A4-307F9916D3AD@gmail.com> <2328961D-4B28-4EE7-8DDD-AD1F1A0A3617@gmail.com> <87E54FB2-7294-4CED-B969-46B086903E18@gmail.com> Date: Thu, 7 Jan 2016 15:39:09 -0500 Message-ID: To: Pierre Joye Cc: Anthony Ferrara , "Paul M. Jones" , PHP internals Content-Type: multipart/alternative; boundary=001a11367c2e9a7f820528c477a6 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: chasepeeler@gmail.com (Chase Peeler) --001a11367c2e9a7f820528c477a6 Content-Type: text/plain; charset=UTF-8 On Thu, Jan 7, 2016 at 3:37 PM, Pierre Joye wrote: > > On Jan 8, 2016 3:34 AM, "Chase Peeler" wrote: > > > > > > > > On Thu, Jan 7, 2016 at 3:21 PM, Pierre Joye > wrote: > >> > >> > >> On Jan 8, 2016 3:14 AM, "Chase Peeler" wrote: > >> > >> > > >> > And none of those caveats exist in the definition you provided. > >> > >> Hmmm. Which one did you read? > >> > >> "the act of systematic and/or continued unwanted and annoying actions > of one party or a group, including threats and demands. The purposes may > vary, including racial prejudice, personal malice, an attempt to force > someone to ..." > >> > >> If I asked him to stop and he continues, aggressively, then it matches > the "unwanted", "annoying" and "to force". > >> > >> > That is a prime example of one of the main concerns we all have - the > ability for anyone to reshape definitions as they please. Even if you > assume they will do so in a way they believe is in everyone's best > interest, we all know that won't always happen > >> > > >> > -- > >> > Chase Peeler > >> > chasepeeler@gmail.com > > > > > > Where is the requirement in the definition that you have to ask him to > stop? I don't see the word "aggressive" in there either. As far as the "to > force" part, that's part of the phrase preceded by "The purposes may vary, > including..." which means that it is not a requirement to meet the > definition. > > > > Again, you might call this nitpicking, but I'm trying to show how a > simple definition for a term that we all think we know the meaning of can > be twisted and reinterpreted. All it takes is one person in a position of > power to abuse that. > > Let make it crystal clear: > > "Stop message me privately, no matter the channel" > > The person continues. It starts here. Got it? > Got it. As long as I annoy you and continue my unwanted behavior publicly, that's OK and not harassment. Definitely crystal clear. -- Chase Peeler chasepeeler@gmail.com --001a11367c2e9a7f820528c477a6--