Revision as of 14:51, 24 February 2010

Code4Lib 2011 ideas

See also C4L2010planning: wishlist

Preconferences

1. Ask people to download in advance
2. Remind preconference leaders 2 weeks before the conference to send an email to registrants. (Email registrants 1 week in advance b/c time before travel is hectic, may be offline)

Ideas

1. Codesprint
2. Hackathon

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?)

Power

Providence, power supplies on top of the table, worked well

Presentations

1. Make people use a single conference PC (but Mac, Linux, Win?)
2. Ask for slides (investigate option for sharing ad-hoc)

Bandwidth

1. Expect higher bandwidth issues on pre-conferences if held in same venue. ???
2. Find out exactly which ethernet ports in the venue are on the protected bandwidth dedication and be sure speakers are hooked to them.
3. Make sure wireless access points are not plugged into ports that have protected bandwidth dedication.
4. For preconferences, do downloads before coming - minimizes problems with bandwidth, and saves time at the preconference to work with the app
5. Bandwidth usage, for planning

• Monday
• Tuesday

Name Tags

1. Include institution, please.
2. Leave space on name tags for first-timer self-identification
3. Leave space on name tags for doodling one's interests

Packet Handed Out

1. list of attendees - name, institution, email ... projects/topic of interest? (free text field on form?)
2. map of meeting rooms
3. brief schedule (titles only)
4. full schedule (abstracts)
5. list of restaurants is great!

Hospitality Suite

• Projector is awesome - do this

Add your category here...

T Shirts non-black much appreciated at 2010