Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:90271 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41955 invoked from network); 7 Jan 2016 16:47:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Jan 2016 16:47:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@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: pierre.php@gmail.com X-Host-Fingerprint: 209.85.218.48 mail-oi0-f48.google.com Received: from [209.85.218.48] ([209.85.218.48:33269] helo=mail-oi0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 17/54-21405-B969E865 for ; Thu, 07 Jan 2016 11:47:23 -0500 Received: by mail-oi0-f48.google.com with SMTP id y66so317373064oig.0 for ; Thu, 07 Jan 2016 08:47:23 -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=VaXaTmLlHd/FfUqCSZH+VSGMhJ7hAop9Bo6Bsqc5u+A=; b=MSj4G6UFmWpfGoc2a4YIphQ9cmU2YAdvcnHOFDehHvy66uy8j/MEAS1iK6icbzThW0 8T3WBv9rtGFFesE9V8gxn4uf8PcSlEyoooI85iTMkGvdrbnzdf+TnwusbcId4McUZ2Vg QgfUxmooAZKr0xHY7R7Jve3bs66G7G5Fs49Cez49gz1x9zTMdh6AE3fKyTxlqU/CtRZe EViVEKeOWUIdhPG/myfG/gN8Kd94NffN8i41mvqS7MwpGOGFkpFw36EmK38NzC2CbGzz SbW0EhongQO2KCVZqz5Da+y6o7zYLVLfrfwDzEQze8dKdhkPjvcDK+E7JIl3OUbUmUAr NJAw== MIME-Version: 1.0 X-Received: by 10.202.72.137 with SMTP id v131mr73564019oia.90.1452185240841; Thu, 07 Jan 2016 08:47:20 -0800 (PST) Received: by 10.202.64.136 with HTTP; Thu, 7 Jan 2016 08:47:20 -0800 (PST) Received: by 10.202.64.136 with HTTP; Thu, 7 Jan 2016 08:47:20 -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> Date: Thu, 7 Jan 2016 23:47:20 +0700 Message-ID: To: "Paul M. Jones" Cc: Anthony Ferrara , PHP internals Content-Type: multipart/alternative; boundary=001a113e55a66db5e10528c139b8 Subject: Re: [PHP-DEV] [RFC] [Draft] Adopt Code of Conduct From: pierre.php@gmail.com (Pierre Joye) --001a113e55a66db5e10528c139b8 Content-Type: text/plain; charset=UTF-8 On Jan 7, 2016 11:38 PM, "Paul M. Jones" wrote: > > > > On Jan 7, 2016, at 10:37, Pierre Joye wrote: > > > > On Thu, Jan 7, 2016 at 11:28 PM, Paul M. Jones wrote: > >> > >>> On Jan 7, 2016, at 10:17, Pierre Joye wrote: > >>> > >>> If someone starts to put bad pressure on another person (harassment, > >>> insults, personal attacks, etc) trying to make this person either > >>> abandon an idea, RFC or even to force this person to leave the > >>> project, the attacker will most likely use non php.net's channel. > >> > >> In which case there are existing means at their disposal: blocking, muting, junk-foldering, reporting to the channel owner for abuse, etc. > > > > Indeed. And it is also obvious that we cannot take actions to block > > the harasser on non php.net's channels. However this was not my point. > > > >> If the harasser cannot actually reach their target, does that not have the same effect? > > > > No, it does not have the same effect. > > Why not? The harassment has been nullified. Are you saying that a person has his place in php.net after being proven gulty of harassment or other similar events? To me, definitely no. And this is why I think we should consider all channels, and name a few examples to make that point clear. --001a113e55a66db5e10528c139b8--