63
edits
Changes
→Food
# Keep Super Bowl Sunday free
# Avoid snow and bitter cold!
# no breakout reports - many feel they are unnecessary- as long as notes go on wiki or someplace# explicitly state that presentation with (most/least) votes will be on day 3, since so many people plan to leave early -- could affect their planning.# Breakout sessions could be proposed and voted on prior to conference -- ad hoc breakouts didn't provide much interest to some of us. ===Social Schedule===# Newcomer welcome on first night?# Beer party needs a big enough space# Have a reception in a museum or library, if possible# Maybe some evening groups for music, shows, etc.
==Food==
# Consider Vegetarians / Vegans
# Decent lunch menu - not taco or spaghetti :-)
## (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)
# Automated Testing
# Two words: Soft pretzels. # Beer party needs a big enough space. (Note: some attendees really like tacos and/or spaghetti, and think these are excellent lunch choices. YMMV.)
==Registration==
* Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated* Choose talks before registration
==T-shirts==
* more regional c4l (but drop the "regional" suffix)
* keep voting on programming!!!
* Name tags should have irc handle as well as name; code{4}lib can be smaller; IRC handle and Name and Institution should be readable at a glance.
* Announce scholarship winners the first day so that folks have a chance to meet them
* microphones for audience
* sign on podium "repeat the question"
* mc tells each presenter how to use the mic effectively
* Have one projection screen above or beside speaker so possible to view speaker and slides at the same time.
* attendee list handouts should have name, institution, irc handle ... (preferably a sorted mapping from irc handle -> names, a sort by firstname, and maybe a sort by last name)
[[Category: Code4Lib2013]]
