Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90315 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21191 invoked from network); 7 Jan 2016 20:35:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2016 20:35:03 -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.218.48 as permitted sender) X-PHP-List-Original-Sender: chasepeeler@gmail.com X-Host-Fingerprint: 209.85.218.48 mail-oi0-f48.google.com Received: from [209.85.218.48] ([209.85.218.48:36007] helo=mail-oi0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/54-21405-6FBCE865 for ; Thu, 07 Jan 2016 15:35:02 -0500 Received: by mail-oi0-f48.google.com with SMTP id o62so315823293oif.3 for ; Thu, 07 Jan 2016 12:35:02 -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=5AgYkVUbb1nsEPo3K/cNHlFsosmoTtvv9i2f4VereMg=; b=XpRGDJuElMQ41cp9aX9GRWagTLgXJl06DBZ6d0S5ElcgtWXYrUR620Y20oFX0tV79c 7EyJtriRenHD6tR8USFfsjfrN+yPWn2sg9p5rH4KUKEYxrVNUWDlJCbthVXI9HLZStwU 6W1dBZBXYZhkePq3hLp/iPPT4T6PEYO8Nr7XzAIhCafNaho2GiDErPH9v6j0h4btxFOh /niFTQElOCtiMmVQeSPo0WL1ubeqEHkKGpvGVZTbTLMAuqWhbSvGi/LcGtZN4Eb8bA1Z /h/3etyo8CjICiRF2Q26GqXt2OTm+1HLGPsscsXL1b8rLhWv3P6gAGp2w/2U5I9sZO5W bksg== X-Received: by 10.202.71.147 with SMTP id u141mr55767004oia.45.1452198899347; Thu, 07 Jan 2016 12:34:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.144.65 with HTTP; Thu, 7 Jan 2016 12:34:39 -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:34:39 -0500 Message-ID: To: Pierre Joye Cc: "Paul M. Jones" , Anthony Ferrara , PHP internals Content-Type: multipart/alternative; boundary=001a113e576889f8a20528c46735 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: chasepeeler@gmail.com (Chase Peeler) --001a113e576889f8a20528c46735 Content-Type: text/plain; charset=UTF-8 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. -- Chase Peeler chasepeeler@gmail.com --001a113e576889f8a20528c46735--