From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751129Ab3GQBWA (ORCPT ); Tue, 16 Jul 2013 21:22:00 -0400 Received: from mail-yh0-f52.google.com ([209.85.213.52]:53956 "EHLO mail-yh0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750866Ab3GQBV6 (ORCPT ); Tue, 16 Jul 2013 21:21:58 -0400 Message-ID: <51E5F1AF.2020408@gmail.com> Date: Tue, 16 Jul 2013 21:21:51 -0400 From: Ric Wheeler User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: "Myklebust, Trond" CC: Sarah Sharp , David Lang , "ksummit-2013-discuss@lists.linuxfoundation.org" , Greg Kroah-Hartman , Darren Hart , Ingo Molnar , Olivier Galibert , Linux Kernel Mailing List , stable , Linus Torvalds , Willy Tarreau Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML References: <20130715204135.GH15531@xanatos> <1373926109.17876.221.camel@gandalf.local.home> <20130715223615.GI15531@xanatos> <20130716211235.GG4994@xanatos> <20130716212704.GB9371@thunk.org> <20130716224357.GK4994@xanatos> <1374015299.6458.76.camel@gandalf.local.home> <20130716231217.GL4994@xanatos> <51E5D7C8.5000306@gmail.com> <1374018809.2249.29.camel@leira.trondhjem.org> In-Reply-To: <1374018809.2249.29.camel@leira.trondhjem.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/16/2013 07:53 PM, Myklebust, Trond wrote: > On Tue, 2013-07-16 at 19:31 -0400, Ric Wheeler wrote: >> On 07/16/2013 07:12 PM, Sarah Sharp wrote: >>> On Tue, Jul 16, 2013 at 06:54:59PM -0400, Steven Rostedt wrote: >>>> On Tue, 2013-07-16 at 15:43 -0700, Sarah Sharp wrote: >>>> >>>>> Yes, that's true. Some kernel developers are better at moderating their >>>>> comments and tone towards individuals who are "sensitive". Others >>>>> simply don't give a shit. So we need to figure out how to meet >>>>> somewhere in the middle, in order to establish a baseline of civility. >>>> I have to ask this because I'm thick, and don't really understand, >>>> but ... >>>> >>>> What problem exactly are we trying to solve here? >>> Personal attacks are not cool Steve. Some people simply don't care if a >>> verbal tirade is directed at them. Others do not want anyone to attack >>> them personally, but they're fine with people attacking their code. >>> >>> Bystanders that don't understand the kernel community structure are >>> discouraged from contributing because they don't want to be verbally >>> abused, and they really don't want to see either personal attacks or >>> intense belittling, demeaning comments about code. >>> >>> In order to make our community better, we need to figure out where the >>> baseline of "good" behavior is. We need to define what behavior we want >>> from both maintainers and patch submitters. E.g. "No regressions" and >>> "don't break userspace" and "no personal attacks". That needs to be >>> written down somewhere, and it isn't. If it's documented somewhere, >>> point me to the file in Documentation. Hint: it's not there. >>> >>> That is the problem. >>> >>> Sarah Sharp >> The problem you are pointing out - and it is a problem - makes us less effective >> as a community. > Not really. Most of the people who already work as part of this > community are completely used to it. We've created the environment, and > have no problems with it. You should never judge success by being popular with those people who are already contributing and put up with things. If you did that in business, you would never reach new customers. > > Where it could possibly be a problem is when it comes to recruiting > _new_ members to our community. Particularly so given that some > journalists take a special pleasure in reporting particularly juicy > comments and antics. That would tend to scare off a lot of gun-shy > newbies. That is my point - recruiting new members is made harder. As some one who manages *a lot* of upstream kernel developers, I will add that it is not just new comers that find this occasionally offensive and off putting. > On the other hand, it might tend to bias our recruitment toward people > of a more "special" disposition. Perhaps we finally need the services of > a social scientist to help us find out... > To be fair, we usually do very well at this, especially with new comers to our community. I think that most of the problems come up between people who know each other quite well and are friendly with each other in person. The problem is that when you use language that you would use with good friends over drinks to tell them they are being stupid and do that on a public list, you set a tone that reaches far beyond your intended target. All of those new comers also read this list and do not see it as funny or friendly. I really don't think that we have to be politically correct or overly kind to make things better. As a very low bar, we could start by trying to avoid using language that would get you fired when you send off an email to someone that you have power over (either manage directly or indirectly control their career). Ric From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <51E5F1AF.2020408@gmail.com> Date: Tue, 16 Jul 2013 21:21:51 -0400 From: Ric Wheeler MIME-Version: 1.0 To: "Myklebust, Trond" CC: Sarah Sharp , David Lang , "ksummit-2013-discuss@lists.linuxfoundation.org" , Greg Kroah-Hartman , Darren Hart , Ingo Molnar , Olivier Galibert , Linux Kernel Mailing List , stable , Linus Torvalds , Willy Tarreau Subject: Re: [Ksummit-2013-discuss] [ATTEND] How to act on LKML References: <20130715204135.GH15531@xanatos> <1373926109.17876.221.camel@gandalf.local.home> <20130715223615.GI15531@xanatos> <20130716211235.GG4994@xanatos> <20130716212704.GB9371@thunk.org> <20130716224357.GK4994@xanatos> <1374015299.6458.76.camel@gandalf.local.home> <20130716231217.GL4994@xanatos> <51E5D7C8.5000306@gmail.com> <1374018809.2249.29.camel@leira.trondhjem.org> In-Reply-To: <1374018809.2249.29.camel@leira.trondhjem.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 07/16/2013 07:53 PM, Myklebust, Trond wrote: > On Tue, 2013-07-16 at 19:31 -0400, Ric Wheeler wrote: >> On 07/16/2013 07:12 PM, Sarah Sharp wrote: >>> On Tue, Jul 16, 2013 at 06:54:59PM -0400, Steven Rostedt wrote: >>>> On Tue, 2013-07-16 at 15:43 -0700, Sarah Sharp wrote: >>>> >>>>> Yes, that's true. Some kernel developers are better at moderating their >>>>> comments and tone towards individuals who are "sensitive". Others >>>>> simply don't give a shit. So we need to figure out how to meet >>>>> somewhere in the middle, in order to establish a baseline of civility. >>>> I have to ask this because I'm thick, and don't really understand, >>>> but ... >>>> >>>> What problem exactly are we trying to solve here? >>> Personal attacks are not cool Steve. Some people simply don't care if a >>> verbal tirade is directed at them. Others do not want anyone to attack >>> them personally, but they're fine with people attacking their code. >>> >>> Bystanders that don't understand the kernel community structure are >>> discouraged from contributing because they don't want to be verbally >>> abused, and they really don't want to see either personal attacks or >>> intense belittling, demeaning comments about code. >>> >>> In order to make our community better, we need to figure out where the >>> baseline of "good" behavior is. We need to define what behavior we want >>> from both maintainers and patch submitters. E.g. "No regressions" and >>> "don't break userspace" and "no personal attacks". That needs to be >>> written down somewhere, and it isn't. If it's documented somewhere, >>> point me to the file in Documentation. Hint: it's not there. >>> >>> That is the problem. >>> >>> Sarah Sharp >> The problem you are pointing out - and it is a problem - makes us less effective >> as a community. > Not really. Most of the people who already work as part of this > community are completely used to it. We've created the environment, and > have no problems with it. You should never judge success by being popular with those people who are already contributing and put up with things. If you did that in business, you would never reach new customers. > > Where it could possibly be a problem is when it comes to recruiting > _new_ members to our community. Particularly so given that some > journalists take a special pleasure in reporting particularly juicy > comments and antics. That would tend to scare off a lot of gun-shy > newbies. That is my point - recruiting new members is made harder. As some one who manages *a lot* of upstream kernel developers, I will add that it is not just new comers that find this occasionally offensive and off putting. > On the other hand, it might tend to bias our recruitment toward people > of a more "special" disposition. Perhaps we finally need the services of > a social scientist to help us find out... > To be fair, we usually do very well at this, especially with new comers to our community. I think that most of the problems come up between people who know each other quite well and are friendly with each other in person. The problem is that when you use language that you would use with good friends over drinks to tell them they are being stupid and do that on a public list, you set a tone that reaches far beyond your intended target. All of those new comers also read this list and do not see it as funny or friendly. I really don't think that we have to be politically correct or overly kind to make things better. As a very low bar, we could start by trying to avoid using language that would get you fired when you send off an email to someone that you have power over (either manage directly or indirectly control their career). Ric