Revision as of 16:43, 10 April 2015

Code4Lib 2016 Committees

Many hands make for light work.

Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2016 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

We will assign a local contact to each committee.

Location and Dates

• Location: TBD, Philadelphia, PA
• Dates: TBD
  • Pre-conferences -
  • Main meeting -
  • Post conference activities?

Website Working Group

This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

• Someone - Primary Contact
• Someone else - Secondary Contact
• Yet another - Documentarian
• Shaun Ellis (Princeton) - LPC Contact (v)
• Charlie Morris (Penn State)
• Axa Liau (Princeton)
• Chris Beer (Stanford)
• Ryan Wick (OSU)

Additional Committees... Coming Soon!