This page is currently under development

If you are interested in helping out with a particular part of the Code4Lib 2012 conference, sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.

Book Give-Away Committee

• Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz

Sponsorships Committee

This committee organizes the sponsorship activities. Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.

Kyle Banerjee (banerjek@uoregon.edu) -- Orbis Cascade Alliance

Keynote Speakers Committee

This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community) and work with the speakers to arrange their travel and arrangements.

Ann Lally (alally at uw dot edu) University of Washington

Dre (akorphan at ncsu dot edu) North Carolina State University

Program Committee

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.

Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona

Scholarships Committee

This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

Jeremy Frumkin (frumkinj at u dot library dot arizona dot edu) - University of Arizona

T-Shirt Committee

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes.

Ann Lally (alally at uw dot edu) University of Washington

Social Activities Committee

The committee plans, proposes, and organizes the evening activities.

Jennifer Ward (jlward1 at uw dot edu) -- University of Washington

Voting Activities Committee

This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.

Hospitality Suite Committee

This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want

Welcome Wagon Committee

Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.

Social Networking

Responsible for non-IRC social networking presence.

IRC Evangelists

Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

IRC Access

Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.

Registration Desk Volunteers

The Registration Desk has a group from IU to register C4L attendees, but we need an additional 1-2 volunteers to hang out for 2-hour shifts and be there to help out. Also on Monday and Tuesday, an additional volunteer with IU Wireless access knowledge would be helpful on the Registration Desk to answer tech questions.

Microphone Runners

Run wireless handheld microphones to audience members asking questions.

Session Timer Volunteers

People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).

Ann Gleason - (amwhit24 at uw dot edu) - University of Washington

Schedule for Session Timers

Raffles

(calling awardees)
(backup)
(program)

To help with documention, no need to sign up, just start editing.

• How To Plan A Code4LibCon

Documentation Interest Group

Promote ongoing documentation efforts.