First of all, Jerry, thanks for the tremendous amount of hard work you expend on
behalf of this organization - PLEASE don't stop doing things just because you might
sometimes do something that some folks criticize, just keep trying to do what you
think is best in the immediate situation and we'll all try to learn from it and
support you on it.
As one of those who must drive a great distance, I would rather get the email than get
surprised after a long fruitless drive.
If nobody transmits the information, it's not my fault, but shame on them. If I don't
receive it, that's not their fault, it's my problem. Other people might get it, and
benefit from it (as I did this time, despite my sympathies for Ben and others who
might not have).
In the interest of making a positive suggestion for something less labor-intensive
than a phone tree, I'd think a good protocol in the future would be to send out an
urgent email advising of the schedule change, but still hold a meeting (even if it's
nothing more than a eat/drink/be-merry bull session) for those who don't get the
message or want to come anyway. This at least lets those of us who normally read
email frequently the chance to make an informed decision about the relative priorities
of an unstructured evening at Martha's vs. spousal commitments...
btw, I'm worried about any of our members who are so stressed that finding themselves
stranded in a brewpub with nothing to do leaves them annoyed!
I can understand having conflicting priorities that would have made that situation
undesireable, but learn to cope - liberal consumption of yeast piss might help :-)
just my .02 worth.
--Bruce McCulley
jkubeck wrote:
> To Ben and any others who missed the cancellation email. My sincerest apologies. I
> take full responsibility for the lateness in the email, however, I did do so in
> the best interest of the group as a whole. I did get feedback from a couple of
> people that said they felt it was best for the people driving long distances.
>
> If I had of had a few more hours to send out emails and in the supposition that
> people would have seen them to vote for holding it anyway, then I guess I made a
> poor judgement, but I am the one that had to make the decision and I made it.
>
> We (I) can strive to do a better job in the future. This was simply a case of two
> people making different dates in calendars, and then both being gone and out of
> touch for several days.
>
> We have a new system in place to avoid these things from happening in the future,
> however, all the people that could have done the follow up were also gone. No
> excuses, just reality.
>
> Ben, as to the volunteering for the phone tag duty, how can you do that and not
> check email? No sarrcasm here, just an honest question. I sent a personal email to
> everyone that rsvp'd me as well as the GNHLUG announcement.
>
> Jerry
>
> Benjamin Scott wrote:
>
> > On Wed, 30 Aug 2000, Jerry Kubeck wrote:
> > > I am sorry to say, I have to CANCEL tonights meeting.
> >
> > And I am sorry to say that some of us work for a living, don't have the
> > opportunity to check our email for cancelations all day long, and wasted a
> > considerable amount of time waiting for a meeting that didn't happen. And no,
> > I wasn't the only one. And yes, I'm in a bad mood.
> >
> > Personally, I think if something goes south the *same day* of the meeting,
> > the meeting should happen anyway, and we'll find *something* to talk about,
> > even if it is only a presentation on how to use the 'logout' command.
> >
> > Since I don't want to be *entirely* unproductive in this message... how
> > about a volentary register of people's phone number(s), maintained on an
> > opt-in basis, so that organizers can provide active notification in the event
> > that a similar screw^H^H^H^H^H occurance happens again? I would be happy to
> > maintain such a list and play phone tag for everyone, if for no other reason
> > then it would at least ensure I get notified in the future.
> >
> > --
> > Ben Scott <[EMAIL PROTECTED]>
> > | Brooks's Law: "Adding manpower to a late software project makes it later." |
> >
> > **********************************************************
> > To unsubscribe from this list, send mail to
> > [EMAIL PROTECTED] with the following text in the
> > *body* (*not* the subject line) of the letter:
> > unsubscribe gnhlug
> > **********************************************************
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
