MV> The question was to "Andrew and all running". You are running, you are MV> part of "them". So now I am asking you.
Ok, but you should ask them as well, not just me.
MV>>> So... Suppose an invited guest brings a personal issue into the MV>>> members only FTSC echo and refuses your request to drop it. How MV>>> would you deal with that interuption of the smooth operation of the MV>>> FTSC?
I have dealt with similar over the decades. The frst was Cott Lang (original Regade author) then many tothers, including some very intersting ones when election coodinator for FN_SYSOP and some not well behaved people.
I never cut access then dissed them after leaving them no rebuttal. In fact, I never cut access. I was always handle to handle such with actually talking to the person. We are different. You see black and white and I see shades of grey. I work within that to create cooperation.
MV> Suppose an invited guest brings a personal issue into the members only MV> FTSC echo and refuses your request to drop it. How would you deal with
Best I can see is you accused Ward of being something like an infamous African dictator and he objected. I would have taken that offline and worked it out.
CS>> It turns out later you failed due dilligence to notify the new Z1C CS>> that they had guest access
MV> Just FYI: Technically, he was invited. The door of my areamanger was MV> unlocked. All he had to do was open it and enter.
There is no 'mandate' to tell them. That document has not been looked at for revision since it happened just as you assumed office, so, didnt happen. This is an FTSC member failure and i am equally guilty as I didn't see it until we found a new ZC was not told. Did you bother to notify the Z4C? They changed too since you came in.
