Date: Thu, 19 Jan 2012 06:23:00 +0000 From: Pegasus Mc Cleaft <ken@mthelicon.com> To: freebsd-hackers@freebsd.org Subject: Re: Getting PRs fixed (was: Re: ...focus, longevity, and lifecycle) Message-ID: <201201190623.00241.ken@mthelicon.com> In-Reply-To: <20120119031908.GB95131@DataIX.net> References: <20120119005735.218280@gmx.com> <4F177914.5090706@missouri.edu> <20120119031908.GB95131@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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 > > > > You should get extra points for difficult PR's. One way to measure this > > would be to give more points for fixing older PR's than newer PR's. > > Number of points = number of days or weeks that a PR has been in the system > before triage ? > > I would think this would put some emphasis on either triaging old PRs > before new ones or actually postponing and assigning a status that cannot > accumulate a higher amount of points. But then what? What to do with the points after they accumulate? Wouldn't it be cool if there was some funding or backing where you could trade your points in for a pint or a cup of coffee? Call it "Coffee for Coders" or the CC fund 8-) You know.. That might be a funny way of assigning points for a PR. How many cups of coffee you expect to be drunk during the fixing of a PR. All meant tongue to cheek, of course 8-) Peg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201190623.00241.ken>