This is a page where we can work through the "FUDCon 2.0" track of the Events FAD 2010.
- FUDCon page and things it links to
- FUDCon/Organization - our current howto plan a FUDCon doc
- 1 FUDCon per quarter
- $20k of budget from Red Hat per quarter, for FUDcons and FADs
- Hard minimum of at least 4 months advance planning for a FUDCon - 6 months recommended
- Time investment for planners: 3 months ahead at 10-15 hours per week, 1 month ahead at 25 hours per week.
- Not Europe for EMEA FUDcon?
- India on its own (split out from APAC)
- Rest of APAC
- Keep budget spread out.
- Do all FUDCons cost the same?
- Fill in the gaps with FADs
- Vacation time (contributors who have to take it)
- Proximity to other major events
- Fix spacing over time
Data from the FUDCon survey
See Marketing_research#FUDCon_Toronto_2009_Survey for data.
Discussion notes below:
- May very well need four days for next FUDCon. Need two days for technical sessions alone, fewer rooms at once.
- Welcome packet *at hotel*
- Conference software - ConMan
- Accessibility for remote attendees - workable FUDCon Live directions
- Find people who know what it means to make the event "family friendly"
Figuring out action items
- Look at the problems brainstorm at the start of the day, and...
- For each action item/deliverable, see what problems it potentially solves.
- If it definitely solves a problem, it's a "must do."
- If it might solve a problem, consider it as an experiment, and mark any regional concerns.
Potential things to work on Saturday
- General calendar for FUDcons
- 2010 instance of said calendar
- Bid process
- "things we should keep" list
- Bug list
- "howto run a fudcon" doc
- make FUDCon 4 days
- Welcome packet at hotel
- Conference software (conman)
- Improved FUDCon Live
- Make event "family friendly"
- Have a clear process for attendee sponsorship
The ideal process for Toronto
Roll back the clock: it's summer 2009 and we've just decided that Toronto's going to be the place for the NA FUDCon at the start of December. What, ideally, goes down? (We're constrained to tools and people we had at the time.)
|External resources |
|Bid process end
|2 days||Print nametags, signs, and the hotel handout. Give hotel handout to hotel. Sleep a lot, and be contactable only by the (remote) remainder of the event team whenever possible to avoid becoming overwhelmed.||Continue to buffer last-minute requests on the attendees list and try to make sure local planners don't get overloaded. Start being (literally) on-call - begin to have someone contactable by phone and someone contactable by IRC at all times, in shifts.||Make sure stuff is delivered and paid-for.|
|1 day||Post signs, setup wifi and power. Sleep.||Arrive at the location city (if remote). Start FUDCon live; migrate on-callness to FUDCon live. Test hotel handout (if coming from out of town).||Make sure stuff is delivered and paid-for.|
|Morning-of||Show non-local planners to location early. Try to rest.||Make barcamp grid. Ensure FUDCon live is still up and running and ready for the load. Be on-call for the day. Open feedback surveys as needed.||Make sure stuff is delivered and paid for.|
|Right afterwards||Local thank-yous. Make sure location is cleaned up. Post-mortem meeting.||Wrap-up documentation (FUDCon Live). Publicize FUDCon live doc results. Thank everyone. Open/publicize feedback surveys as needed. Revise planning docs for the next round.||File receipts and close the books.|