This is one area I'm willing to attribute more to ignorance -- solid unshakeable ignorance -- rather than requiring an assumption of malice.
Note well, I'm not at all an expert on queing theory or operations research. I took a course from an instructor with some practical experience in the area. I highly respected his knowledge and experience -- and I learned very quickly that even the most trivial systems (two-queue, three-state) exhibited altogether non-intuitive behavior. But people who've never experienced being hit by that kind of clue stick (and most people haven't) really can't grasp how totally clueless they are.
And ... the ODP includes 600,000 queues, an arbitrarily large number of states, millions of undocumented constraints, ... and we get several people a week thinking all our problems would be solved by a single FIFO queue.
"Right, we've got 10,000 editors just staring at their computer screen because the next submittal in the queue is in some obscure Khoi-San dialect, and our one editor who speaks it is on vacation. Shut the servers down, folks, we have gridlock. Check back on or around September 1, and oh, the 300,000 edits that you might have done in the meantime, fagetaboutit."
Alright, now that I've said that, it's blindingly obvious. And what do people respond? Do they say "If my brilliant conception breaks on something so simple as that, maybe, just maybe, I don't know as much about the subject as I thought I did. I'll tell you what, I'll go get a degree in Operations Research so I can tell when I'm talking through my hat. And I'll also sign on to edit my hometown Society category, to gain an experential knowledge of what the queues are really like. Then I might be able to know enough of the facts to contribute constructively"?
Sigh. No, they don't. They come up with some equally simplistic idea that handles the Khoi-San case, but fails utterly if the website uses Flash....
You missed the last go-round on this subject. If you have a very sick mind, that thread would make entertaining reading. It just made me sick. The guy just flat didn't know what an "average" was, or how to calculate it, or what it signified, but he was bound and determined that he was going to pry an "average time to review" out of us with a sharpened crowbar.
Then he thoughtfully explained that if we were having such a hard time calculating the average, we could switch to FIFO submittal processing, "which would make the average easier to calculate." (Ignoring the fact that nobody at the ODP WANTED an average, and nobody ANYWHERE could do anything useful with one if they had it, all of which had been explained to him) But the kicker is: in reality, the order in which submittals are processed DOESN'T AFFECT THE ARITHMETIC MEAN AT ALL! And any bright high-school algebra student could prove that. (Gauss proved it when he was 7 years old, IIRC.)
Sigh. I have a degree in math, not operations research. All I really know is that for anything more complex than single-stage queues with perfect preclassification, FIFO starts doing things you don't want to see. And ... whatever the ODP is, it is not that simple.
And, speaking from mathematical experience again, if a problem becomes sufficiently complex, the ONLY efficient solutions involve nondeterminism (that is, randomness.) So, if you see the ODP appear random, there is a chance that we may be doing the best job theoretically possible. If the ODP DOESN'T appear completely random, then please let us know about it, so that we can work on fixing the problem!