Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 82BA61800F for ; Fri, 3 Jul 2015 21:27:15 +0000 (UTC) Received: (qmail 25269 invoked by uid 500); 3 Jul 2015 21:27:12 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 25151 invoked by uid 500); 3 Jul 2015 21:27:12 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 25130 invoked by uid 99); 3 Jul 2015 21:27:12 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jul 2015 21:27:12 +0000 Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id AF1941A0254; Fri, 3 Jul 2015 21:27:11 +0000 (UTC) Received: by obbop1 with SMTP id op1so75578635obb.2; Fri, 03 Jul 2015 14:27:11 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.52.138 with SMTP id b132mr35136607oia.125.1435958831034; Fri, 03 Jul 2015 14:27:11 -0700 (PDT) Received: by 10.202.83.20 with HTTP; Fri, 3 Jul 2015 14:27:10 -0700 (PDT) In-Reply-To: References: <75F348B6-53F4-4626-AC39-D24A629FBE70@gmail.com> <509381228.65871.1435720089079.JavaMail.yahoo@mail.yahoo.com> Date: Fri, 3 Jul 2015 14:27:10 -0700 Message-ID: Subject: Re: [DISCUSS] correcting abusive behavior on mailing lists was (Re: [DISCUSS] Multi-Cluster HBase Client) From: Andrew Purtell To: "dev@hbase.apache.org" , "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a113d3e02093ceb0519ff382d --001a113d3e02093ceb0519ff382d Content-Type: text/plain; charset=UTF-8 It looks like the discussion is settling down and we have a consensus on the course of action of a three month temporary ban from the project mailing lists. If you feel that is not correct please say so, otherwise on Monday the PMC will begin that process. Going forward I think we should have a documented policy. We've never needed this before but now that has changed. Below is a strawman for your kind consideration. I will file a JIRA with a site update proposal next week if someone doesn't beat me to it. >>> We expect participants in discussions on the HBase project mailing lists, IRC channels, and JIRA issues to abide by the Apache Software Foundation's Code of Conduct (http://apache.org/foundation/policies/conduct.html). If you feel there had been a violation of this code, please point out your concerns publicly in a friendly and matter of fact manner. Nonverbal communication is prone to misinterpretation and misunderstanding. Everyone has bad days and sometimes says things they regret later. Someone else's communication style may clash with yours, but the difference can be amicably resolved. After pointing out your concerns please be generous upon receiving an apology. Should there be repeated instances of code of conduct violations, or if there is an obvious and severe violation, the HBase PMC may become involved. When this happens the PMC will openly discuss the matter, most likely on the dev@hbase mailing list, and will consider taking the following actions, in order, if there is a continuing problem with an individual: 1. A friendly off-list warning; 2. A friendly public warning, if the communication at issue was on list, otherwise another off-list warning; 3. A three month suspension from the public mailing lists and possible operator action in the IRC channels. 4. A permanent ban from the public mailing lists, IRC channels, and project JIRA. For flagrant violations requiring a firm response the PMC may opt to skip early steps. No action will be taken before public discussion leading to consensus or a successful majority vote. <<< On Wednesday, July 1, 2015, Sean Busbey wrote: > Due to an off list request, let me clarify my previous email. Apologies if > this is overly detailed, but I'm presuming folks on user@ don't often deal > with ASF mechanics. > > For those on user@hbase, Andrew asked on a sub-thread that mistakenly went > only to dev@hbase if those advocating for moderating Michael S's email > would we would vote against a 3 month ban if Andrew called a vote. My > response copied user@hbase back in and that's why you may have a gap in > messages. > > In ASF terminology, votes are one of > > * <0 against or a veto depending on what kind of vote has been called, > usually "-1" > * 0 either neutral or too conflicted to state a for/against preference, > usually has some concerns attached > * >0 in favor, usually "+1" > > I precisely said "I would not vote -1" because I would not take a stance > that might cause the vote to fail, but I would not vote in favor. I very > likely would vote "-0 I think moderating his messages will suffice, but > acknowledge the community does not want that." > > > On Wed, Jul 1, 2015 at 12:23 PM, Sean Busbey > wrote: > > > I would not vote -1 on a 3 month ban. It doesn't look like we have > > consensus around moderating messages. > > > > On Wed, Jul 1, 2015 at 11:42 AM, Andrew Purtell > > > wrote: > > > >> For those who are advocating moderation, would you be opposed if I > propose > >> a 3 month ban for a vote? If you are not opposed, then we should be able > >> to > >> achieve consensus here without needing a vote to take place. > >> > >> > > -- > Sean > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White) --001a113d3e02093ceb0519ff382d--