On Wed, Apr 7, 2010 at 8:17 AM, Paul W. Frields stickster@gmail.com wrote:
On Wed, Apr 07, 2010 at 11:11:20AM +0200, Yaakov Nemoy wrote:
2010/4/7 Robyn Bergeron robyn.bergeron@gmail.com:
Sorry for the cross-post - not sure which list is more appropriate :)
So - I'm looking into doing a bid for the ever-so-awesome city of Tempe, Arizona (ASU, baby!!).
Before I start calling around - I figured that there are probably a few pieces of information that might be useful to have. They aren't really called out on any of the fudcon bid / sop pages, so it might be helpful to answer them and then add the info to the wiki pages.
#1: How many days? From what I can see - it looks like 3 full days, at least in Toronto for a North America FUDCon. Is this flexible ("we'll throw in conference rooms if everyone stays an extra day,")? A guideline? Etc?
So far, every fudcon i've been to has been at least three days long.
We discussed the question of FUDCon length at the Events FAD. It was suggested that we make the next North American FUDCon four days long, with two days of sessions and two days of hacking. I do wonder a bit about how the burnout factor might increase -- but that factor could be *lower* for a four-day event, because we'll have more time available in general. It does, however, raise the overall cost of the event for an attendee (extra hotel room night, which might be a total of ~$50 per person at double occupancy).
Ok last year we broke how FUDcon worked I think because we had a ton of great ideas and not enough time to show them off. How about the following:
Halfday talks Halfday hacks.
or make it plainly obvious that people could do talks on the last days too (some people didn't think they could and others didn't want talks to intefere with the real reason they had come to the fudcon :)).
#2: Approximate number of people?
Check previous fudcons, but estimate around 200+
+1. An estimate of 200 should do.
It also depends on how much the local university system has towards Linux. The stronger that.. the more people to show up.