If I see one more "kitchen" where everything is either fried, made of corn, or both....
But some people have decided -- for a number of understandable reasons -- that Tor is actually a good thing to help with.
Everyone's got different ideas of worthwhile uses of their time. Some people love contributing to something; others won't spend 5 minutes on it. It has to do with desire, goals, values, and passion, rather than strictly mathematical aptitude, as you suggested.
It's the manager's job to make sure there is slack in production; that there are resources available for emergency situations, and that there is enough redundancy built into the production team that if somebody gets sick or somehow can't work a normal workload, somebody else can pick it up. If a crunch situation is unavoidable, as a manager, I would be deeply apologetic and appreciative of my employees' sacrifice, while frantically searching for a solution to ease the burden. If I can't bring in help, I need to adjust the scope or push back on the deadline. Plain and simple.
No, no, no, a thousand times no. Software isn't an assembly line. It's not piece work. Adding more people to a late project only makes it later, as the existing dev team has to work to bring the new hires (even if they're experienced developers, they're still new to the project) up to speed. Adding more resources to a late project, without accounting for a period of reduced productivity is the absolute worst thing management can do. I have literally seen projects go from, "Well, it's borderline, but we can deliver if we work weekends," to, "There is no way we can do this by the delivery date," because management decided to add two new developers to the team.
The worst thing is, Fred Brooks published a book talking about this phenomenon in the '70s: The Mythical Man Month. And somehow, the lesson still hasn't sunk in.
A year is a long time to wait in startup time.