Thanks for everyone who replied to the previous postings. Unfortunately the amount of the feedback is, let’s say, not statistically significant enough to base further planning on it.
In addition to this we settled for the 4. and 5. November. Unfortunately, we then learned that this clashes with the RubyConf in Charlotte, North Carolina. Is that a problem for anyone (i.e. would you attend both conferences if they wouldn’t clash)? If so, please raise your
exception voice. If we don’t know about it, we can’t fix it – so please tell us (well, tell me). Even though it’s still close to RubyConf, we could for example settle with the 10. and 11. November. What do you think/prefer?
Anyway, there’s the first lesson learned: For next year we’ll have to start planning earlier to avoid the date conflicts.
As the precise location isn’t fixed yet, we’re still open to adjust the location to the expected number of attendees – in only we’d know what to expect. Given year’s increase of interest in Ruby and Rail, it’s very hard to estimate this number. And a good estimation would help us a lot, since we wouldn’t like to prevent people from attending, just because there’s way to few places available.