Ideas for 2013

From Code4Lib
Revision as of 00:16, 8 February 2012 by Ndushay (Talk | contribs) (Code4Lib 2013 ideas)

Jump to: navigation, search

Code4Lib 2013 ideas

Schedule

  1. Keep Super Bowl Sunday free
  2. Avoid snow and bitter cold!
  3. no breakout reports - many feel they are unnecessary

Food

  1. 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?)
  2. Is it possible to get a hot breakfast with/instead of continental?
  3. Consider Vegetarians
  4. Decent lunch menu - not taco or spaghetti :-)
  5. Automated Testing
  6. Two words: Soft pretzels.
  7. 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


T-shirts

  • Men's and ladies sizes -- can it be done?
  • 100% cotton is worth it.
  • How about blind submissions to tee shirt vote? I.e., submitter name not associated with submissions during voting.

Suggestions from dchuds talk

  • less complacency from overall committee--less burden on local org committee
  • Advisory committee - made up of representatives from past hosts
  • Programming committee - don't have voting on talks
  • do work in the open
  • build on experience from past conferences
  • code4lib multicore
  • multi-track conference
  • support 500 people
  • make it more like PyCon

Other ideas

  • more regional c4l (but drop the "regional" suffix)
  • keep voting on programming!!!