From owner-freebsd-hackers@FreeBSD.ORG  Thu Jan 19 01:47:30 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 28B731065672
	for <freebsd-hackers@freebsd.org>; Thu, 19 Jan 2012 01:47:30 +0000 (UTC)
	(envelope-from dieterbsd@engineer.com)
Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67])
	by mx1.freebsd.org (Postfix) with SMTP id C83DB8FC18
	for <freebsd-hackers@freebsd.org>; Thu, 19 Jan 2012 01:47:29 +0000 (UTC)
Received: (qmail 11881 invoked by uid 0); 19 Jan 2012 00:57:37 -0000
Received: from 67.206.186.240 by rms-us005.v300.gmx.net with HTTP
Content-Type: text/plain; charset="utf-8"
Date: Wed, 18 Jan 2012 19:57:33 -0500
From: "Dieter BSD" <dieterbsd@engineer.com>
Message-ID: <20120119005735.218280@gmx.com>
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
X-Authenticated: #74169980
X-Flags: 0001
X-Mailer: GMX.com Web Mailer
x-registered: 0
Content-Transfer-Encoding: 8bit
X-GMX-UID: KA9lbyA03zOlNR3dAHAhws5+IGRvb4Dp
Subject: Getting PRs fixed (was: Re: ...focus, longevity, and lifecycle)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jan 2012 01:47:30 -0000

Andriy writes:
> And dealing with PRs is not always exciting.

Neither is brushing your teeth or cleaning the kitchen, but most of us
manage to do them at least occasionally. Part of being a grown up.

Instead of looking for a stick to hold over developers to get them
to fix PRs, let's look for carrots to make fixing PRs more appealing.

Idea 1: Fix 'n' PRs, get a tee-shirt, fridge magnet, plush daemon, ...

Idea 2: Give it status. Set up a web page with PR fixing stats

name/handle..total PRs fixed...fixed in last 12 months...average fixed/year
Sheldon......150...............90........................72
Leonard......131..............110........................67
Howard.......104...............20........................52
Raj...........80...............80........................80