This was sent last week, without knowing that our mail server was not
fully functional. The situation below still stands, and I hope to get
feedback on whether we'll still get good attendance if we do it on a
Wednesday or Thursday next week, or if we should simply wait for our
April meeting slot.

Thanks all!

Thanks,
Mac


---------- Forwarded message ----------
From: Mac Newbold <[email protected]>
Date: Thu, Mar 15, 2012 at 6:16 PM
Subject: Meeting Postponed!
To: UPHPU List <[email protected]>


Hi all,

I'm extremely sorry for the late notice, but I wanted to get word to
people who weren't in IRC. Sorry for the confusion about the meeting,
it's my fault. I was trying to finalize and announce the decision last
week and didn't do so.

By the information I was able to gather, our meeting attendance would
be better (and our speaker and attendees happier) if we postponed the
meeting, due largely to the Republican Caucus meetings tonight. So
there will be no formal meeting tonight.

We wanted to postpone one week, but the room we use at C7 is already
booked (I believe by Utah Python). Our options are as follows:
1. Hold the meeting in 2 weeks on a Thursday (March 29th)
2. Hold the meeting on a different evening, like Wednesday March 21st
(I haven't confirmed this is even possible for our speaker)
3. Hold the meeting at a different location on Thursday March 22nd -
I'm open to this, but don't have another location to offer at this
point
4. Cancel this month's meeting, postponing Clint Berry's talk on Phing
(deployment tool) until April, and pushing back our April presenter to
May
5. None of the above - I'm open to suggestions...

Let me know your preference. If we don't get much response, #1 will
probably be the default, as long as that works for the speaker.

Thanks,
Mac

--
Mac Newbold
[email protected]
801-694-6334


-- 
Mac Newbold
[email protected]
801-694-6334

_______________________________________________

UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net

Reply via email to