I don't think we can do anything about a situation like this, it really is up to Rosetta.  Even if Oni was kicked from the team (which I'm not advocating at this point) they would still have all the tasks and none would be freed up.

The issue in part is Team Biblepay is accounting for roughly 25% of the work of Rosetta@Home, and this happened basically overnight.  So if you're the Rosetta managers, having to increase your work units by that much could be a bit problematic on the short term.  We were on track to be 1/3rd the work done, which is a massive increase on what is typically a pretty consistent project.

I do think it becomes a higher priority to see if the project can handle our work load or if other plans (backup projects) should be made.  Even though it doesn't mesh well with the timeline, making sure PoDC works consistently, becomes more important in my book than new features.