Dan Sugalski writes:
> "General consensus" is best, but that can't be guaranteed. "Consensus of
> the ruling council" is more attainable, but there's that whole "ruling
> council" thing to contend with. "What Larry says" is best, but what happens
> if he doesn't, or gets hit by a bus at some point?
In terms of ongoing maintenance, I'd say that the teams will act as
the Ruling Council. When teams get pissed off with the release
manager, then the leader will have to go. When members of a team
can't work together, then the release manager works with them to
figure out where the problem is and fix it. This might be everything
from "play nice" to hiring a hitman :-)
We should begin the cloning process for Larry immediately. That way
it'd take an entire FLEET of busses to get him[1].
Nat
[1] I can just see the Python folks requesting a fleet of busses from
their corporate overlords :-)
