Hi Steven:
A finer-grained set of responsibility designations sounds reasonable to me. 
I could be wrong, but I suspect that the main purpose of the weekly IRC meetings that are creating the scheduling bottleneck is to force multiple eyes/editors to skim the articles that are going through the system for potential problems (licensing problems, technical taboos like disabling selinux, using unsupported or out-of-date software, etc.).
The IRC meeting system was established well before Taiga was introduced into the workflow. I’ve noticed that the Taiga columns parallel the IRC meeting stages. If we want to eliminate the bottleneck of the weekly meeting, it might be possible to do asynchronously with Taiga what is currently being done synchronously at the IRC meetings. Maybe we could require multiple “looks good to me” approvals on cards in the “review” column from editors and, once the card has enough +1’s, any editor could move the card to the “to edit” column at any time and complete the process as normal.
Just an idea.
Also, thanks Steven, for picking up the slack on these tasks that some of us have been leaving 