On Wed, Jan 18, 2012 at 07:59:48PM -0600, Stephen Montgomery-Smith wrote: > On 01/18/2012 06:57 PM, Dieter BSD wrote: > > 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 > > 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. -- ;s =;
pgpKAvBuxOSKG.pgp
Description: PGP signature
