Page to collect info/ideas for future (BSDCan) devsummits
See DevSummitHowTo - make sure any unique notes from here are moved there
Rooms
- Flat rooms with movable furniture are best
- Comfortable chairs are very important -- the rooms in SITE and FTX were fairly similar, but the padded chairs in FTX made it much easier to stay there for an extended period of time.
- There's one room in the rez with a bunch of chairs, foldable tables, etc. that looks like it would be good
Equipment
- Too much time lost to laptops disagreeing with the projector -- collect slides/code/etc. beforehand and stick with one machine for the whole session
- Make sure internet access is working before the summit starts
Recording of talks
- Poor quality audio on the webcast/recording: find some way to get feed from wireless mic into encoding machine
- Bring a spindle of DVDs to dup the recordings during the conference
Slides
- Slide number / total (e.g. 7/12) on the slides is good to have, so everyone knows approximately how much material is left
Food
- For long talks, need afternoon snacks
Budget
- Collect a nominal fee for attendance, to cover lunches etc. - that way the budget scales with the number of attendees.
- Advise potential attendees to look to their employer or home institution as a first choice for funding, then look to the FreeBSD Foundation for travel grant funding. Doing so well in advance is a good idea so that the Foundation can budget for it, and if necessary, contact sponsors.
Schedule
12:57 <rwatson> also a good idea -- talks in the mornings, hacking in the afternoon, try to schedule talks that lead to hacking
Travel
Advise attendees to apply for visas well in advance, and make sure all passports have expiration dates at least six months past the expected departure date (after the conference). Some countries do not provide visas for passports with expiration dates less than six months in the future.