Introducing Event Monger

Well, the votes are in and it appears that my “By the Community, For the Community” project is to build an ASP.NET-based event management site – I have decided to call it Event Monger. My objective is to ship this application out on or before the 4th of August which means that I had better get cracking. I’m going to use my blog to document the process of designing and building the application.

What is Event Monger – really?

Event Monger is something that I have wanted to have for a long time as an co-organiser of a technical event like Code Camp Oz. The problem is that all the tools out there to date are really good at content management, but not that great at automating the workflow of an event, including things like:

• Accepting session submissions
• Ranking session submissions
• Scheduling accepted sessions
• Accepting attendee registrations
• Sending attendee and speaker notifications
• Presenting venue information
• Posting of during-event notices
• Accepting speaker uploads

In my next post on Event Monger I am going to list out the specific end-user scenarios that are going to be supported and where they sit in the overal workflow of managing an event. I’ll use the scenarios to drive the development forward and keep track of how things are progressing.

My name is Mitch Denny and CSS is my Kryptonite!

Looks like someone was listening to the check-ins to our internal Team Foundation Server installation. Of course, when I posted that comment I expected it to be a closely guarded corporate secret, and not have it blurted out across the Internet. We may as well just create an RSS feed and throw it out there!

 Now – I have to be honest, I am really bad at CSS, I could handle CSS1, but CSS2 is just so much more expressive. The problem of course is that one plus one does not always equal two, so even though the CSS I write renders OK inside of Outlook 2007, it might not render correctly inside of OWA or Outlook 2003 – and it would just scare me to think what it would render like in Firefox or Opera (good thing I don’t really care about either of those two for this project – how backwards thinking of me!).