Date: Wed, 18 Jan 2012 17:57:05 -0800 From: Devin Teske <devin.teske@fisglobal.com> To: "'Dieter BSD'" <dieterbsd@engineer.com>, <freebsd-hackers@freebsd.org> Subject: RE: Getting PRs fixed (was: Re: ...focus, longevity, and lifecycle) Message-ID: <04b001ccd64d$a58c4140$f0a4c3c0$@fisglobal.com> In-Reply-To: <20120119005735.218280@gmx.com> References: <20120119005735.218280@gmx.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Dieter BSD > Sent: Wednesday, January 18, 2012 4:58 PM > To: freebsd-hackers@freebsd.org > Subject: Getting PRs fixed (was: Re: ...focus, longevity, and lifecycle) >=20 > Andriy writes: > > And dealing with PRs is not always exciting. >=20 > Neither is brushing your teeth or cleaning the kitchen, but most of us ma= nage to > do them at least occasionally. Part of being a grown up. >=20 > 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. >=20 > Idea 1: Fix 'n' PRs, get a tee-shirt, fridge magnet, plush daemon, ... >=20 +1 (!) But careful not to incentivize those that raise PRs to split a single PR in= to multiples purely for metrics. We probably won't care that this might also incentivize committers to raise= PRs for the commits they would normally make without one (wait, does that = happen?) > Idea 2: Give it status. Set up a web page with PR fixing stats >=20 > name/handle..total PRs fixed...fixed in last 12 months...average fixed/ye= ar > Sheldon......150...............90........................72 > Leonard......131..............110........................67 > Howard.......104...............20........................52 > Raj...........80...............80........................80 +1 --=20 Devin _____________ The information contained in this message is proprietary and/or confidentia= l. If you are not the intended recipient, please: (i) delete the message an= d all copies; (ii) do not disclose, distribute or use the message in any ma= nner; and (iii) notify the sender immediately. In addition, please be aware= that any message addressed to our domain is subject to archiving and revie= w by persons other than the intended recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?04b001ccd64d$a58c4140$f0a4c3c0$>