The primary reason that would not work is because communication between the meetings would not be sufficient, for several reasons:
(1)Say there's a meeting in Portland and a meeting in Eugene. Portland meeting makes a major decision. Eugene meeting is working on other things entirely, and ends up with little to no say in resulting decision. End result: divided staff, and quite possibly people quitting outright.
(2)Certain staff needs to be in the same place as certain staff, i.e. all Ops staff needs to be together to meet properly. If half the staff is at the Portland meeting and half is at the Eugene meeting, even with an interim communications link (i.e., internet, phone call, etc.), one hand won't know what the other is doing.
(3)Even if you had, say, programming in Eugene and Ops in Portland, if a decision by Ops affects Prog, Prog may not get wind of it until they've planned right through said decision, which could undo a lot of work by either side.
Short version, communication is lacking too severely to make the "multiple sites at once" thing work for the monthly meetings. We discussed the possibility of having the majority of them in Salem, I think, and that really is a pretty decent medium for many people. When you get right down to it, though, it doesn't matter where the meeting is. There will always upon always be people complaining that they can't get there. It's a fact of life, and not really anyone's fault. Just something we have to work around.
PezCat
