From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1756850Ab2GFKMD (ORCPT <rfc822;w@1wt.eu>);
	Fri, 6 Jul 2012 06:12:03 -0400
Received: from mail-bk0-f46.google.com ([209.85.214.46]:36610 "EHLO
	mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750802Ab2GFKL7 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 6 Jul 2012 06:11:59 -0400
Date: Fri, 6 Jul 2012 12:11:49 +0200
From: Richard Cochran <richardcochran@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Glauber Costa <glommer@parallels.com>,
        "J. Bruce Fields" <bfields@fieldses.org>,
        Jonathan Corbet <corbet@lwn.net>,
        ksummit-2012-discuss@lists.linux-foundation.org,
        LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2012-discuss] [ATTEND or not ATTEND] That's the
 question!
Message-ID: <20120706101149.GA26028@localhost.localdomain>
References: <alpine.LFD.2.02.1206152313310.3086@ionos>
 <20120615233413.GB8894@kroah.com>
 <alpine.LFD.2.02.1206161103320.3086@ionos>
 <20120616072906.7469ec24@tpl.lwn.net>
 <20120620195121.GA1719@fieldses.org>
 <4FF6B32A.7070006@parallels.com>
 <20120706095450.GB7728@somewhere.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120706095450.GB7728@somewhere.redhat.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Fri, Jul 06, 2012 at 11:54:52AM +0200, Frederic Weisbecker wrote:
> On Fri, Jul 06, 2012 at 01:43:06PM +0400, Glauber Costa wrote:
> > The same way we have checkpatch, we can have something automated that
> > will attempt to rule out some trivial patches in the counting process.
> > We can scan a patch, and easily determine if each part of it is:
> > 
> > * pure whitespace
> > * pure Documentation change
> > * comment fix
> > 
> > And if a patch is 100 % comprised by those, we simply don't count it.
> > People that just want to increase their numbers - they will always
> > exist, will tend to stop doing that. Simply because doing it will not
> > help them at all.
> 
> OTOH, documentation changes or comment fixes, and even sometimes pure whitespace
> fixes, can be very valuable contributions. This can be a useful and ungrateful
> work and that deserve credit.
> 
> We just can't find an automated and right way to evaluate a contribution.

Well what about submitters and maintainers labeling patches below the
SOB with tags like the following?

   Signed-off-by: Richard Cochran <richardcochran@gmail.com>
   Tags: docu whitespace trivial

Part of the review would be making sure the labels fit.

Thanks,
Richard