Alright, let's not attempt to mix new contributors and code review, then. Thank you for your good arguments.
On Friday, April 4, 2014, Tim Landscheidt tim@tim-landscheidt.de wrote:
if the issue at hand is to review the ~ 2500 "code re- views waiting for reviewer", if every one of the ~ 100 WMF employees reviews one (additional) changeset per workday, the task will be done by the end of this month.
As far as I can see, there are not 100 WMF employees capable of reviewing changesets, even less of merging them. Not only this, expertise and +2 rights must be seen from the point of view of repositories, because not every reviewer can review every patch. Once we solve "Bug 63533 - Gerrit metrics about open changesets should ignore -1s", we will be able to see what kind of problem we have, and that will help us decide what needs to be done.
There is already https://gerrit.wikimedia.org, "git review -l" and Jon's (brilliant) tool (cf. https://raw.github.com/jdlrobson/GerritCommandLine/master/gerrit.py) to pick a change to review;
Brilliant indeed! Whatever we do, it is going to be useful (friendlier URL: https://github.com/jdlrobson/GerritCommandLine )
and the nice thing about reviewing all of them in a foreseeable time period is that you don't have to prioritize! Just pick any!
I reckon your strategy is sexy. More when we have reliable numbers.
Just in case it got lost in transmission: Pick any!
+1