Timing and time for planning

[Dave Klein]

As some have already seen the potential difficulty in planning an event like
this by committee (distributed committee no less) and considering that there
*is* going to be a Groovy / Grails (and hopefully Griffon) conference in the
fall, might it make sense to plan on a early Spring conference? That would
allow more time to find speakers, sponsors and attendees.

In the words of the prophets Simon and Garfunkle:

"Slow down, you move too fast, you've got to make the morning last
Just kickin' down the cobble-stones, lookin' for fun and feelin' groovy!"

Dave

[Shaun Jurgemeyer]

The only concern I have about that is losing the momentum we have. If
the conference is nearly a year in the future it is much more tempting
to sit back wait. We have quite a few people excited and
participating and that is a great thing.

That said, when people initially started talking about August, my
first thought was "August 2010 is a long time from now". Even the
September/October timeframes we're talking about are coming up
quickly.

I think even with our design by committee approach we can get venues
etc lined up by Sep, but our bigger problems may be getting speakers
and attendees at relatively short notice. I'd like to see how many of
the folks on Hamlet's list are able to make it during the time frame
we're talking about.

[Bill Turner]

If we run it in the Spring, we run the risk of competing with GR8. For
the same reason people do not want to run the conference here too late
in the fall, we cannot run it too early in Spring. Granted, GR8 is in
Europe, so not much competition, but there will be some. And, if there
is speaker cross-over, then we'll likely end up with a number of
duplicate presentations.