From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5582F282 for ; Mon, 20 Jul 2015 07:08:31 +0000 (UTC) Received: from bedivere.hansenpartnership.com (bedivere.hansenpartnership.com [66.63.167.143]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id F0236F7 for ; Mon, 20 Jul 2015 07:08:30 +0000 (UTC) Message-ID: <1437376105.8968.14.camel@HansenPartnership.com> From: James Bottomley To: Jiri Kosina Date: Mon, 20 Jul 2015 08:08:25 +0100 In-Reply-To: References: <20150716094720.2bf9f5ac@gandalf.local.home> <55A7C7FE.6000604@sonymobile.com> <20150716094125.16cdda73@lwn.net> <1437063875.18768.59.camel@HansenPartnership.com> <20150717101151.5d5bc86d@lwn.net> <20150717133712.42c82add@gandalf.local.home> <20150717190223.GB1499@cloud> <20150717154326.6f129bc4@gandalf.local.home> <20150717202412.GA1856@cloud> <20150717163903.67747d86@gandalf.local.home> <20150717204856.GA2048@cloud> <20150717165501.62ed4e04@gandalf.local.home> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: "ksummit-discuss@lists.linuxfoundation.org" , Dan Carpenter , Jason Cooper Subject: Re: [Ksummit-discuss] [CORE TOPIC] Recruitment (Reviewers, Testers, Maintainers, Hobbyists) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2015-07-20 at 00:19 +0200, Jiri Kosina wrote: > On Fri, 17 Jul 2015, Steven Rostedt wrote: > > [ ... snip ... ] > > But that was an exception because the code submitted was really worth > > while > > This really made me wonder. Maybe we should really focus on why such > ocasions need to be pointed out as exceptions. > > Is it that Linux kernel development got hyped so much that everyone wants > to have that bullet in his CV, no matter how stupid the submitted patch > would be? > > If so, what should we do to change it? > > I.e. I might propose a a slightly controversial topic, going a bit the > other direction than the whole "motivating newcomers" discussion: how to > get rid of useless submissions that are slowing maintainers down? I second. I think we concentrate too much on contribution and not enough on useful contribution. > Should we stop publishing all the statistics? I believe there is no > question that those are one of the primary drivers of useless submissions. > Once maintainers get DoSed by submissions of wrong and/or useless patches > that eat non-negligible amount of their time, we're in trouble. I'm not sure it's just the stats. We also have to be careful about negative perceptions, so I don't think we want to go around highlighting bad patches. There are a couple of patch sets that are draining review talent from my point of view: the mechanical one file at a time fixing X. I think we need someone to be the gatekeeper and review and apply the script in one go. And perhaps we should call the other "small patches which don't fix bugs" ... I'm less sure what to do about these. At the other end of the scale, perhaps we should be doing more to recognise good contributions. Greg suggested prizes for first contributions, but what about in addition one more, say for best bug fix of the week (or month depending on who's running it and how much time it sucks)? We could have the maintainers nominate ones they think are good and whoever's running this picks the best. James