Difference between revisions of "Ideas for 2013"
From Code4Lib
Line 16: | Line 16: | ||
==Registration== | ==Registration== | ||
− | Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated | + | Use EventBrite--it's worth the admin money for the ease of use, and the reports that can be generated |
==Suggestions from dchuds talk== | ==Suggestions from dchuds talk== | ||
− | * less | + | * less complacency from overall committee--less burden on local org committee |
* Advisory committee | * Advisory committee | ||
* Programming committee | * Programming committee | ||
− | do work in | + | * do work in the open |
[[Category: Code4Lib2013]] | [[Category: Code4Lib2013]] |
Revision as of 17:50, 7 February 2012
Contents
Code4Lib 2013 ideas
Schedule
- Keep Super Bowl Sunday free
- Avoid snow and bitter cold!
Food
- If you do the preconferences in the main conference space (vs. in spread-out off-site spots), many people will expect breakfast or at least regular coffee/tea/soft-drink breaks throughout the day (so have them?)
- Is it possible to get a hot breakfast with/instead of continental?
- Consider Vegetarians
- Decent lunch menu - not taco or spaghetti :-)
- Automated Testing
(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
Suggestions from dchuds talk
- less complacency from overall committee--less burden on local org committee
- Advisory committee
- Programming committee
- do work in the open