Date: Sat, 16 Jun 2012 07:29:06 -0600
From: Jonathan Corbet <corbet@lwn.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Greg KH <greg@kroah.com>, 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: <20120616072906.7469ec24@tpl.lwn.net>
In-Reply-To: <alpine.LFD.2.02.1206161103320.3086@ionos>
References: <alpine.LFD.2.02.1206152313310.3086@ionos>
	<20120615233413.GB8894@kroah.com>
	<alpine.LFD.2.02.1206161103320.3086@ionos>
Organization: LWN.net
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1104
Lines: 26

On Sat, 16 Jun 2012 12:50:05 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:

> A good start would be if you could convert your kernel statistics into
> accounting the consolidation effects of contributions instead of
> fostering the idiocy that corporates have started to measure themself
> and the performance of their employees (I'm not kidding, it's the sad
> reality) with line and commit count statistics.

I would dearly love to come up with a way to measure "real work" in
some fashion; I've just not, yet, figured out how to do that.  I do
fear that the simple numbers we're able to generate end up creating the
wrong kinds of incentives.

Any thoughts on how to measure "consolidation effects"?  I toss out
numbers on code removal sometimes, but that turns out to not be a whole
lot more useful than anything else on its own.

Thanks,

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/