[dekhn]

Yes, but as we know, the best way to make a project that is late/slow/unreliable even later, slower, and more unreliable is to add inexperienced devs to the project. Which is (from the perspective of the university) what they are trying to avoid.

[mrmanner]

well except they allegedly asked said allegedly inexperienced developer to develop the thing for them, for free

[dekhn]

Yes, I think this post has established that whomever created the response to the original ToS violation (rather, just a plan to violate the ToS) wasn't being very thoughtful (assuming everything is being described correctly). I would assume that at this point, the discussion has been moved above the original employee who responded and is being dealt with at the dean level (with the goal to be avoiding UW appearing in a bad light in the press).

I've seen hundreds of "administration outrage" articles and I guess I've kind of learned that the backstory is usually more complicated, nuanced, and reasonable than the original poster implied. But the internet mobs proceed anyway.