Code4Lib - User contributions [en]

Conference Financial History At A Glance

2026-01-09T16:26:08Z

Phette23: add Philly '26

{| class="wikitable"
! style="text-align:left;"| Year
! Registration cost
! Hotel rate
! People
|-
|style="width: 30%; background-color: #f5fffa;"| 2026 Philadelphia, PA
|425 + 50/postcon
|$231/night
|TBD
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2025 Princeton, NJ
|250 + 40/postcon
|$269/$299/night (king vs. two doubles)
|225
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2024 Ann Arbor, MI
|225 (290 late deadline) + 40/postcon
|$167-$239/night (multiple)
|≈250 (???)
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2023 Princeton, NJ
|200 (260 late deadline) + 40/precon
|n/a
|192
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2022 Buffalo, NY
|195 (250 late deadline) + 40/precon
|108-179/night (+tax)
|150
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2021 Online
|49 (59 late deadline) + 19/postcon
|n/a
|620
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2020 Pittsburgh, PA
|375 (450 late deadline) + 50 precon
|159/night (+tax)
|289 [[#ref1|[1]]]
|-
|style="width: 30%; background-color: #f5fffa;"| 2019 San Jose, CA
|395 (450 late deadline) + 50 precon
|200/night (+tax)
|348
|-
|style="width: 30%; background-color: #f5fffa;"| 2018 Washington, DC
|350 + 60 precon
|182/night (+tax)
|476
|-
|style="width: 30%; background-color: #f5fffa;"| 2017 Los Angeles, CA
|275 + 60 precon
|175/night (+tax) to 229/night (no tax)
|430
|-
|style="width: 30%; background-color: #f5fffa;"| 2016 Philadelphia, PA
|200 + 15/30 precon
|169/night (+tax)
|440
|-
|style="width: 30%; background-color: #f5fffa;"| 2015 Portland, OR
|175 + 15/30 precon
|139/night (+tax)
|450
|-
|style="width: 30%; background-color: #f5fffa;"| 2014 Raleigh, NC
|165 + 10 preconf
|159/night
|350
|-
| style="width: 30%; background-color: #f5fffa;"| 2013 Chicago, IL
| 160
| 115/night
| 400
|-
|style="width: 30%; background-color: #f5fffa;"| 2012 Seattle, WA
| 150
| 159/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2011 Bloomington, IN
| 130 + 30 preconf
| 99-129/night
| 250
|-
|style="width: 30%; background-color: #f5fffa;"| 2010 Asheville, NC
| 120 + 25 preconf
| 119/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2009 Providence, RI
| 125
| 135/night
| 220
|-
|style="width: 30%; background-color: #f5fffa;"| 2008 Portland, OR
| 125
| 150/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2007 Athens, GA
| 100
|
| 140
|-
|style="width: 30%; background-color: #f5fffa;"| 2006 Corvallis, OR
| 125
| 84/night (+tax)
|
|}

== Notes ==

1. Attendance was affected by the [https://en.wikipedia.org/wiki/COVID-19_pandemic COVID-19 pandemic].

[[Category:Code4LibCon_Planning]]

Code4Lib 2026 Conference Committees

2025-08-07T21:01:48Z

Phette23: chair website committee

= Code4Lib Conference Committees =

Hosting a conference is 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 2026 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 Chair, Primary Contact

==Planning Committee==
Also known as the Local Planning Committee, although there is no requirement for the members to be local.

[[2026 Planning Committee Documents|2026 Planning Committee Documents]]

* Ann Marie Mesco - Primary Contact, Chair
* Ken Rose - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Erin Swift - Volunteer
* Joelen Pastva - Volunteer
* Lina Crowe - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2026 Website Working Group Documents|2026 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact, Chair
* Your Name Here - Trip Kirkpatrick, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[2026 Budget and Sponsorship Documents]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Your Name Here - Andromeda Yelton, Chair ''if someone else really wants to chair hit me up; I've done this a few times and I'm happy to do it again but I'm also happy to share the opportunity''
* Your Name Here - Maccabee Levine, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Workshop Committee (Pre / Post-Conference)==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2026 Pre-conference Documents|2026 Pre-conference Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2026 Program Documents|2026 Program Documents]]

* Your Name Here - Primary Contact, Chair
* Dre - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Scholarship 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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2026 T-Shirt Documents|2026 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2026 Conference Volunteers]]'''

[[2026 Online Volunteer Documents|2026 Online Volunteer Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2026 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Code4Lib 2027 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2026 Host Voting Documents|2026 Host Voting Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2026 Accessibility Documents|2026 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2026 Whatever Documents|2026 Whatever Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category: Code4Lib2026]]
[[Category:Conference Committees]]

How To Plan A Code4LibCon

2025-03-03T19:32:21Z

Phette23:

== General Process ==

While this is the general chronology of running the conference, it never hurts to plan ahead. Before hosting proposals for the next year are solicited, you can prepare some components of your proposal. Before your proposal is accepted, you can recruit volunteers to serve on committees. In particular, it helps to have at least a few initial people who will form the nucleus of your Local Planning Committee (LPC).

* When the call for next year's host goes out, '''prepare a proposal'''
** See [[Successful Code4Lib Conference Proposals]] from prior years
** '''Identify venues''' for both the conference and the hotel (if different).
** '''Prepare cost estimates'''. The primary factors are:
*** Lodging (hotels) - see if hotels offer discounted room block quotes
*** Venues (conference, workshop, reception, other activities)
*** Catering
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you look at a hotel or other venue, make sure you talk to them about bandwidth and costs.
*** Do you have organizational relationships which might ensure extra sponsorships? If so, factor in that this might reduce the registration cost. For instance, when we were at the Library of Congress in 2018, they were also [https://2018.code4lib.org/sponsors/ our largest sponsor].
*** You can reference data from previous years to estimate minimums and maximums.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask them questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel room block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if so, they can also be very helpful and will know more about campus spaces and costs (e.g. if there are free rooms to use for pre-conferences).
* Get approved by the community and start planning
** Receive access to the Code4Lib Conference Drive folders with information from prior years
** Construct a planning timeline (see templates in Drive)
** Find a hotel, negotiate and sign a contract with them. CONCENTRA does this but this [[Sample RFI]] is still a useful reference; '''note the WiFi requirements'''
** Put out a call for committee volunteers (on the listserv, in Slack)
* '''Put on an amazing conference!''' If you get this far, you have survived the worst part.
* The final duties of LPC are putting out the call for next year's proposals and writing up reflections.

== Location ==

Code4Lib has been hosted on university campuses and also located purely in hotels. Campus facilities tend to be more affordable, but housing can be scattered and challenging. Hotels are more expensive but cohesive.

If your campus or town has a conference center, that is a logical starting point. Large hotels are also an option. In recent years, the conference has been smaller (a little over 200 attendees). If you are unsure how many attendees to plan for, look at [[Conference_Financial_History_At_A_Glance|historical attendance]] figures or ask in the code4libcon channel in Slack. In general, 200-400 attendees is a good range.

A couple of isolated rooms for the conference but away from the main space are important for both the Community Support Squad to hold private discussions and to private a place of quiet respite for weary conference-goers.

=== Workshops ===

Workshops have been held before and after the conference. They are referred to as "pre-conferences" or "post-conferences" in planning and publicity materials. There should be space to facilitate 10-20 workshops. It is helpful if they can be located in the same building but not necessary.

These can be class or meeting rooms but should have a projector and ideally a whiteboard. Electricity for attendees is also important.

=== Reception ===

A nice reception venue can be appealing to many attendees. In the past, we have gone to museums, libraries, and more fun venues. If Philadelphia, we went to The Mütter Museum. In D.C., we went to the Library of Congress. In Michigan, we went to "fowling" (football bowling).

A nice reception at a separate location is not strictly necessary. It might be possible to do catering at the conference venue in the evening, for instance.

=== Transportation ===

Consider how folks coming into town will get to their lodging. Is the airport far? Are there free shuttles? Is it possible to get there via a major railway?

If lodging and the venue are separate, how will attendees get to the conference venue? Are there shuttles? If we need to purchase a bus, how much will it cost?

Most years, we pay for a bus to the reception venue, as it tends to be in a different location.

=== Local Appeal ===

Successful proposals in the past included local spots that attendees will be interested in: cultural institutions, tourist attractions, book stores, libraries, restaurants, and nightlife. The Social Activities committee plans around these venues. It is nice to have a nighttime location where Game Night can be held (which can be a workshop room).

There is nothing wrong with doing a conference in a location we've been to before, or in a location that is close to last year's location. In the past, Code4Lib tended to bounce between the East Coast, West Coast, and Midwest, but that is not a requirement and should not dissuade any location from submitting a proposal.

== Committee List ==

Each year we copy the prior year's list of committees (see [[:Category:Conference Committees]]) to a new wiki page. If you are looking for information on a committee or new volunteers, prior years can provide some names, but know that not all committees keep their membership on the wiki up to date.

Brief descriptions of the primary committees:

* Planning (LPC) - primary committee, should have delegates on most others, makes major decisions
* Website - creates and updates the website using a template and data provided by other committees
* Sponsorship - acquires sponsorships to reduce costs
* Keynote - solicits suggestions from community and communicates with keynote candidates
* Pre-conference - plans workshops
* Program - plans posters and conference talks
* Scholarship - solicits diversity scholarship applications and selects candidates
* Community Support Squad (CSS) - enforces the [https://github.com/code4lib/code-of-conduct Code of Conduct]
* T-Shirt - solicits T-Shirt designs
* Social Activities - plans social events at the conference such as Game Night
* Streaming - runs the livestream
* Host Voting - solicits proposals for next year
* Accessibility - consults on physical and digital accessibility, e.g. of venues and the conference websites

You will also need on-site volunteers during the conference for tasks like MCing the conference, timing talks, and running microphones for audience questions.

Code4Lib is democratic; most committees faced with multiple options (keynote, pre-conference, program, t-shirt, host voting) host community votes to determine some or all of their choices.

Some committees are small, even a single person. Some years may have some unique committees not present in the list above. For more information on any particular committee, look in their Drive folder or on the wiki.

== Planning ==

=== Budgeting ===

* [[Conference_Financial_History_At_A_Glance]]

=== Wireless ===

Historically, Code4Lib has had trouble with wifi bandwidth at venues. Hotels will lie about their wifi. Try to receive assurance that every attendee will be able to simultaneously have 1-2 devices connected to the network. It's best if you are able to visit the venue to verify its network characteristics.

It is good if the venue allows VPN traffic as many folks use a work VPN. It's also nice if commonly used ports, like 22 for ssh/git, are usable.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

== At the Conference ==

=== Code of Conduct ===

LPC may be consulted by the CSS if a Code of Conduct violation occurs. These have sometimes necessitated someone being removed from the conference or an announcement being made from the stage.

=== Keynotes ===

* Speaker gifts
* Small honorarium
* Offer to make dinner plans

=== Lightning Talks ===

* Sign up ahead of time on papers in the venue
* Load slides onto the podium in the break before
* Everybody lines during the time slot (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

=== Conference ===

* Power - everyone would like to plug in their laptop (and possibly their phone)

=== Photography ===

Code4Lib uses different colored lanyards to articulate personal photography preferences.

* Green = it's ok to take my picture
* Yellow = please ask before taking my picture
* Red = don't take my picture

=== Podium ===

# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide a stand (apple box?) for presenters who would like to use one

=== Video ===

# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Calls for Hosting ===

'''To do''': This has not been kept up to date. We should use examples from recent years and remove older ones.

See [[:Category:Conference Hosting Proposals]].

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Further Readings ==

The most recent year's Lessons Learned (in Drive) are more likely to be relevant. Some of these links are quite old but may still contain valuable insight on problems that have happened over the years.

* [[Code4Lib Conference Lessons Learned]] (from 2014)
* [[2017_Lessons_Learned]]
* [https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

[[Category: Code4LibCon Planning]]

Conference Financial History At A Glance

2025-02-06T21:51:43Z

Phette23:

{| class="wikitable"
! style="text-align:left;"| Year
! Registration cost
! Hotel rate
! People
|-
|style="width: 30%; background-color: #f5fffa;"| 2025 Princeton, NJ
|250 + 40/postcon
|???
|TBD
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2024 Ann Arbor, MI
|225 (290 late deadline) + 40/postcon
|$167-$239/night (multiple)
|≈250 (???)
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2023 Princeton, NJ
|200 (260 late deadline) + 40/precon
|???
|192
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2022 Buffalo, NY
|195 (250 late deadline) + 40/precon
|108-179/night (+tax)
|150
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2021 Online
|49 (59 late deadline) + 19/postcon
|n/a
|620
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2020 Pittsburgh, PA
|375 (450 late deadline) + 50 precon
|159/night (+tax)
|289 [[#ref1|[1]]]
|-
|style="width: 30%; background-color: #f5fffa;"| 2019 San Jose, CA
|395 (450 late deadline) + 50 precon
|200/night (+tax)
|348
|-
|style="width: 30%; background-color: #f5fffa;"| 2018 Washington, DC
|350 + 60 precon
|182/night (+tax)
|476
|-
|style="width: 30%; background-color: #f5fffa;"| 2017 Los Angeles, CA
|275 + 60 precon
|175/night (+tax) to 229/night (no tax)
|430
|-
|style="width: 30%; background-color: #f5fffa;"| 2016 Philadelphia, PA
|200 + 15/30 precon
|169/night (+tax)
|440
|-
|style="width: 30%; background-color: #f5fffa;"| 2015 Portland, OR
|175 + 15/30 precon
|139/night (+tax)
|450
|-
|style="width: 30%; background-color: #f5fffa;"| 2014 Raleigh, NC
|165 + 10 preconf
|159/night
|350
|-
| style="width: 30%; background-color: #f5fffa;"| 2013 Chicago, IL
| 160
| 115/night
| 400
|-
|style="width: 30%; background-color: #f5fffa;"| 2012 Seattle, WA
| 150
| 159/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2011 Bloomington, IN
| 130 + 30 preconf
| 99-129/night
| 250
|-
|style="width: 30%; background-color: #f5fffa;"| 2010 Asheville, NC
| 120 + 25 preconf
| 119/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2009 Providence, RI
| 125
| 135/night
| 220
|-
|style="width: 30%; background-color: #f5fffa;"| 2008 Portland, OR
| 125
| 150/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2007 Athens, GA
| 100
|
| 140
|-
|style="width: 30%; background-color: #f5fffa;"| 2006 Corvallis, OR
| 125
| 84/night (+tax)
|
|}

== Notes ==

1. Attendance was affected by the [https://en.wikipedia.org/wiki/COVID-19_pandemic COVID-19 pandemic].

[[Category:Code4LibCon_Planning]]

Conference Financial History At A Glance

2025-02-06T21:51:22Z

Phette23: link footnote

{| class="wikitable"
! style="text-align:left;"| Year
! Registration cost
! Hotel rate
! People
|-
|style="width: 30%; background-color: #f5fffa;"| 2025 Princeton, NJ
|250 + 40/postcon
|???
|TBD
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2024 Ann Arbor, MI
|225 (290 late deadline) + 40/postcon
|$167-$239/night (multiple)
|≈250 (???)
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2023 Princeton, NJ
|200 (260 late deadline) + 40/precon
|???
|192
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2022 Buffalo, NY
|195 (250 late deadline) + 40/precon
|108-179/night (+tax)
|150
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2021 Online
|49 (59 late deadline) + 19/postcon
|n/a
|620
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2020 Pittsburgh, PA
|375 (450 late deadline) + 50 precon
|159/night (+tax)
|289 [[#ref1|[1]]]
|-
|style="width: 30%; background-color: #f5fffa;"| 2019 San Jose, CA
|395 (450 late deadline) + 50 precon
|200/night (+tax)
|348
|-
|style="width: 30%; background-color: #f5fffa;"| 2018 Washington, DC
|350 + 60 precon
|182/night (+tax)
|476
|-
|style="width: 30%; background-color: #f5fffa;"| 2017 Los Angeles, CA
|275 + 60 precon
|175/night (+tax) to 229/night (no tax)
|430
|-
|style="width: 30%; background-color: #f5fffa;"| 2016 Philadelphia, PA
|200 + 15/30 precon
|169/night (+tax)
|440
|-
|style="width: 30%; background-color: #f5fffa;"| 2015 Portland, OR
|175 + 15/30 precon
|139/night (+tax)
|450
|-
|style="width: 30%; background-color: #f5fffa;"| 2014 Raleigh, NC
|165 + 10 preconf
|159/night
|350
|-
| style="width: 30%; background-color: #f5fffa;"| 2013 Chicago, IL
| 160
| 115/night
| 400
|-
|style="width: 30%; background-color: #f5fffa;"| 2012 Seattle, WA
| 150
| 159/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2011 Bloomington, IN
| 130 + 30 preconf
| 99-129/night
| 250
|-
|style="width: 30%; background-color: #f5fffa;"| 2010 Asheville, NC
| 120 + 25 preconf
| 119/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2009 Providence, RI
| 125
| 135/night
| 220
|-
|style="width: 30%; background-color: #f5fffa;"| 2008 Portland, OR
| 125
| 150/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2007 Athens, GA
| 100
|
| 140
|-
|style="width: 30%; background-color: #f5fffa;"| 2006 Corvallis, OR
| 125
| 84/night (+tax)
|
|}

== Notes ==

1. Attendance was affected by the [https://en.wikipedia.org/wiki/COVID-19_pandemic 2019-20 coronavirus pandemic].

[[Category:Code4LibCon_Planning]]

How To Plan A Code4LibCon

2025-02-06T21:44:36Z

Phette23:

== General Process ==

While this is the general chronology of running the conference, it never hurts to plan ahead. Before hosting proposals for the next year are solicited, you can prepare some components of your proposal. Before your proposal is accepted, you can recruit volunteers to serve on committees. In particular, it helps to have at least a few initial people who will form the nucleus of your Local Planning Committee (LPC).

* When the call for next year's host goes out, '''prepare a proposal'''
** See [[Successful Code4Lib Conference Proposals]] from prior years
** '''Identify venues''' for both the conference and the hotel (if different).
** '''Prepare cost estimates'''. The primary factors are:
*** Lodging (hotels) - see if hotels offer discounted room block quotes
*** Venues (conference, workshop, reception, other activities)
*** Catering
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you look at a hotel or other venue, make sure you talk to them about bandwidth and costs.
*** Do you have organizational relationships which might ensure extra sponsorships? If so, factor in that this might reduce the registration cost. For instance, when we were at the Library of Congress in 2018, they were also [https://2018.code4lib.org/sponsors/ our largest sponsor].
*** You can reference data from previous years to estimate minimums and maximums.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask them questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel room block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if so, they can also be very helpful and will know more about campus spaces and costs (e.g. if there are free rooms to use for pre-conferences).
* Get approved by the community and start planning
** Receive access to the Code4Lib Conference Drive folders with information from prior years
** Construct a planning timeline (see templates in Drive)
** Find a hotel, negotiate and sign a contract with them. CONCENTRA does this but this [[Sample RFI]] is still a useful reference; '''note the WiFi requirements'''
** Put out a call for committee volunteers (on the listserv, in Slack)
* '''Put on an amazing conference!''' If you get this far, you have survived the worst part.
* The final duties of LPC are putting out the call for next year's proposals and writing up reflections.

== Location ==

Code4Lib has been hosted on university campuses and also located purely in hotels. Campus facilities tend to be more affordable, but housing can be scattered and challenging. Hotels are more expensive but cohesive.

If your campus or town has a conference center, that is a logical starting point. Large hotels are also an option. In recent years, the conference has been smaller (a little over 200 attendees). If you are unsure how many attendees to plan for, look at [[Conference_Financial_History_At_A_Glance|historical attendance]] figures or ask in the code4libcon channel in Slack. In general, 200-400 attendees is a good range.

A couple of isolated rooms for the conference but away from the main space are important for both the Community Support Squad to hold private discussions and to private a place of quiet respite for weary conference-goers.

=== Workshops ===

Workshops have been held before and after the conference. They are referred to as "pre-conferences" or "post-conferences" in planning and publicity materials. There should be space to facilitate 10-20 workshops. It is helpful if they can be located in the same building but not necessary.

These can be class or meeting rooms but should have a projector and ideally a whiteboard. Electricity for attendees is also important.

=== Reception ===

A nice reception venue can be appealing to many attendees. In the past, we have gone to museums, libraries, and more fun venues. If Philadelphia, we went to The Mütter Museum. In D.C., we went to the Library of Congress. In Michigan, we went to "fowling" (football bowling).

A nice reception at a separate location is not strictly necessary. It might be possible to do catering at the conference venue in the evening, for instance.

=== Transportation ===

Consider how folks coming into town will get to their lodging. Is the airport far? Are there free shuttles? Is it possible to get there via a major railway?

If lodging and the venue are separate, how will attendees get to the conference venue? Are there shuttles? If we need to purchase a bus, how much will it cost?

Most years, we pay for a bus to the reception venue, as it tends to be in a different location.

=== Local Appeal ===

Successful proposals in the past included local spots that attendees will be interested in: cultural institutions, tourist attractions, book stores, libraries, restaurants, and nightlife. The Social Activities committee plans around these venues. It is nice to have a nighttime location where Game Night can be held (which can be a workshop room).

There is nothing wrong with doing a conference in a location we've been to before, or in a location that is close to last year's location. In the past, Code4Lib tended to bounce between the East Coast, West Coast, and Midwest, but that is not a requirement and should not dissuade any location from submitting a proposal.

== Committee List ==

Each year we copy the prior year's list of committees (see [[:Category:Conference Committees]]) to a new wiki page. If you are looking for information on a committee or new volunteers, prior years can provide some names, but know that not all committees keep their membership on the wiki up to date.

Brief descriptions of the primary committees:

* Planning (LPC) - primary committee, should have delegates on most others, makes major decisions
* Website - creates and updates the website using a template and data provided by other committees
* Sponsorship - acquires sponsorships to reduce costs
* Keynote - solicits suggestions from community and communicates with keynote candidates
* Pre-conference - plans workshops
* Program - plans posters and conference talks
* Scholarship - solicits diversity scholarship applications and selects candidates
* Community Support Squad (CSS) - enforces the [https://github.com/code4lib/code-of-conduct Code of Conduct]
* T-Shirt - solicits T-Shirt designs
* Social Activities - plans social events at the conference such as Game Night
* Streaming - runs the livestream
* Host Voting - solicits proposals for next year
* Accessibility - consults on physical and digital accessibility, e.g. of venues and the conference websites

You will also need on-site volunteers during the conference for tasks like MCing the conference, timing talks, and running microphones for audience questions.

Code4Lib is democratic; most committees faced with multiple options (keynote, pre-conference, program, t-shirt, host voting) host community votes to determine some or all of their choices.

Some committees are small, even a single person. Some years may have some unique committees not present in the list above. For more information on any particular committee, look in their Drive folder or on the wiki.

== Planning ==

=== Budgeting ===

* [[Conference_Financial_History_At_A_Glance]]

=== Wireless ===

historically, Code4Lib has had trouble with wifi bandwidth at venues. Hotels will lie about their wifi. Try to receive assurance that every attendee will be able to simultaneously have 1-2 devices connected to the network. It's best if you are able to visit the venue to verify its network characteristics.

It is good if the venue allows VPN traffic as many folks use a work VPN. It's also nice if commonly used ports, like 22 for ssh/git, are usable.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

== At the Conference ==

=== Code of Conduct ===

LPC may be consulted by the CSS if a Code of Conduct violation occurs. These have sometimes necessitated someone being removed from the conference or an announcement being made from the stage.

=== Keynotes ===

* Speaker gifts
* Small honorarium
* Dinner plans

=== Lightning Talks ===

* Sign up ahead of time on papers in the venue
* Load slides onto the podium in the break before
* Everybody lines during the time slot (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

=== Conference ===

* Power - everyone would like to plug in their laptop (and possibly their phone)

=== Photography ===

Code4Lib uses different colored lanyards to articulate personal photography preferences.

* Green = it's ok to take my picture
* Yellow = please ask before taking my picture
* Red = don't take my picture

=== Podium ===

# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide a stand (apple box?) for presenters who would like to use one

=== Video ===

# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Calls for Hosting ===

See [[:Category:Conference Hosting Proposals]].

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Further Readings ==

The most recent year's Lessons Learned (in Drive) are more likely to be relevant. Some of these links are quite old but may still contain valuable insight on problems that have happened over the years.

* [[Code4Lib Conference Lessons Learned]] (from 2014)
* [[2017_Lessons_Learned]]
* [https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

=== Additional Links ===

* [[C4L2010planning|2010 planning]]
* [[C4L2011planning|2011 planning]]
* [[Useful information from 2012]]

[[Category: Code4LibCon Planning]]

How To Plan A Code4LibCon

2025-02-06T21:12:19Z

Phette23: link to prior successful proposals

== General Process ==

While this is the general chronology of running the conference, it never hurts to plan ahead. Before hosting proposals for the next year are solicited, you can prepare some components of your proposal. Before your proposal is accepted, you can recruit volunteers to serve on committees. In particular, it helps to have at least a few initial people who will form the nucleus of your Local Planning Committee (LPC).

* When the call for next year's host goes out, '''prepare a proposal'''
** See [[Successful Code4Lib Conference Proposals]] from prior years
** '''Identify venues''' for both the conference and the hotel (if different).
** '''Prepare cost estimates'''. The primary factors are:
*** Lodging (hotels) - see if hotels offer discounted room block quotes
*** Venues (conference, workshop, reception, other activities)
*** Catering
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you look at a hotel or other venue, make sure you talk to them about bandwidth and costs.
*** Do you have organizational relationships which might ensure extra sponsorships? If so, factor in that this might reduce the registration cost. For instance, when we were at the Library of Congress in 2018, they were also [https://2018.code4lib.org/sponsors/ our largest sponsor].
*** You can reference data from previous years to estimate minimums and maximums.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask them questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel room block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if so, they can also be very helpful and will know more about campus spaces and costs (e.g. if there are free rooms to use for pre-conferences).
* Get approved by the community and start planning
** Receive access to the Code4Lib Conference Drive folders with information from prior years
** Construct a planning timeline (see templates in Drive)
** Find a hotel, negotiate and sign a contract with them. CONCENTRA does this but this [[Sample RFI]] is still a useful reference; '''note the WiFi requirements'''
** Put out a call for committee volunteers (on the listserv, in Slack)
* '''Put on an amazing conference!''' If you get this far, you have survived the worst part.
* The final duties of LPC are putting out the call for next year's proposals and writing up reflections.

== Location ==

Code4Lib has been hosted on university campuses and also located purely in hotels. Campus facilities tend to be more affordable, but housing can be scattered and challenging. Hotels are more expensive but cohesive.

If your campus or town has a conference center, that is a logical starting point. Large hotels are also an option. In recent years, the conference has been smaller (a little over 200 attendees). If you are unsure how many attendees to plan for, look at [Conference_Financial_History_At_A_Glance] figures or ask in the code4libcon channel in Slack. In general, 200-400 attendees is a good range.

A couple of isolated rooms for the conference but away from the main space are important for both the Community Support Squad to hold private discussions and to private a place of quiet respite for weary conference goers.

=== Workshops ===

Workshops have been held before and after the conference. They are often referred to as "pre-conferences" or "post-conferences" in planning and publicity materials. There should be space to facilitate 10-20 workshops. It is helpful if they can be located in the same building but not necessary.

These can be class or meeting rooms but should have a projector and ideally a whiteboard. Electricity for every attendee is also important.

=== Reception ===

A nice reception venue can be appealing to many attendees. In the past, we have gone to museums, libraries, and more fun venues. If Philadelphia, we went to The Mütter Museum. In D.C., we went to the Library of Congress. In Michigan, we went to a "fowling" (football bowling) place.

A nice reception at a separate location is not stricly necessary. It might be possible to do catering at the conference venue in the evening, for instance.

=== Transportation ===

Consider how folks coming into town will get to their lodging. Is the airport far? Are there free shuttles? Is it possible to get there via a major railway?

If lodging and the venue are separate, how will attendees get to the conference venue? Are there shuttles? If we need to purchase a bus, how much will it cost?

Most years, we need to pay for a bus to the reception venue, as it tends to be in a different location.

=== Local Appeal ===

Successful proposals in the past tend to include local spots that folks will be interested in: cultural institutions, tourist attractions, book stores, libraries, restaurants, and night life. The Social Activities committee plans around these venues. It is nice to have a nighttime location where Game Night can be held (which might be one of the workshop rooms).

There is nothing wrong with doing a conference in a location we've been to before, or in a location that is close to last year's location. In the past, Code4Lib tended to bounce between the East coast, West coast, and Midwest but that is not a requirement and should not dissuade any location from submitting a proposal.

== Committee List ==

Each year we copy the prior year's list of committees (see [[:Category:Conference Committees]]) to a new wiki page. If you are looking for information on a committee or new volunteers, looking at prior years can sometimes give you some names, but know that not all committees keep their membership on the wiki up to date.

Here are brief descriptions of some of the primary committees:

* Planning (LPC) - primary committee, should have delegates on most others, makes major decisions
* Website - creates and updates the website using a template and data provided by other committees
* Sponsorship - acquires sponsorships to reduce costs
* Keynote - solicits suggestions from community and communicates with keynote candidates
* Pre-conference - plans workshops
* Program - plans posters and conference talks
* Scholarship - solicits diversity scholarship applications and selects candidates
* Community Support Squad (CSS) - enforces the Community [https://github.com/code4lib/code-of-conduct Code of Conduct]
* T-Shirt - solicit T-Shirt designs
* Social Activities - plans social events at the conference such as Board Game Night
* Streaming - runs the livestream
* Host Voting - solicit proposals for next year
* Accessibility - consult on physical and digital accessibility, e.g. of venues and the conference websites

You will also need on-site volunteers during the conference for tasks like MCing the conference, timing talks, and running microphones for audience questions.

Code4Lib is democratic; most committees faced with multiple options (keynote, pre-conference, program, t-shirt, host voting) host community votes to determine some or all of their choices.

Some committees are quite small, even a single person. Each year may have some unique committees not present in the list above. For more information on any particular committee, look in their Drive folder or on the wiki.

== Planning ==

=== Budgeting ===

* [[Conference_Financial_History_At_A_Glance]]

=== Wireless ===

historically, Code4Lib has had trouble with wifi bandwidth at venues. Hotels will lie about their wifi. Try to receive assurance that every attendee will be able to simultaneously have 1-2 devices connected to the network. It's best if you are able to visit the venue to verify its network characteristics.

It is good if the venue allows VPN traffic as many folks use a work VPN. It's also nice if commonly used ports, like 22 for ssh/git, are usable.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

== At the Conference ==

=== Code of Conduct ===

LPC may be consulted by the CSS if a Code of Conduct violation occurs. These have sometimes necessitated someone being removed from the conference or an announcement being made from the stage.

=== Keynotes ===

# Speaker gifts
# Dinner plans

=== Lightning Talks ===

* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

=== Conference ===

# Power - everyone would like to plug in their laptop (and possibly their phone)
# IRC Monitor for podium during speaker changes?

=== Photography ===

Code4Lib uses different colored lanyards to articulate personal photography preferences.

* Green = it's ok to take my picture
* Yellow = please ask before taking my picture
* Red = don't take my picture

=== Podium ===

# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide an apple box for presenters who would like to use one.

=== Video ===

# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Calls for Hosting ===

See [[:Category:Conference Hosting Proposals]].

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Further Readings ==

The most recent year's Lessons Learned (in Drive) are more likely to be relevant. Some of these links are quite old but may still contain valuable insight on problems that have happened over the years.

* [[Code4Lib Conference Lessons Learned]] (from 2014)
* [[2017_Lessons_Learned]]
* [https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

=== Additional Links ===

* [[C4L2010planning|2010 planning]]
* [[C4L2011planning|2011 planning]]
* [[Useful information from 2012]]

[[Category: Code4LibCon Planning]]

Successful Code4Lib Conference Proposals

2025-02-06T21:11:40Z

Phette23: create page

This page lists successful proposals for prior Code4Lib conferences. The list is not exhaustive. Use these as a guide for future proposals.

See also: [[:Category:Conference Hosting Proposals]].

== Successful Proposals ==

* 2024 [https://umich-code4lib-proposal.netlify.app/ Ann Arbor, Michigan] ([https://web.archive.org/web/20230913040638/umich-code4lib-proposal.netlify.app/ archive])
* 2019 [https://phette23.github.io/c4l19-norcal-proposal/ San Jose, California] ([https://web.archive.org/web/20201029164034/phette23.github.io/c4l19-norcal-proposal/ archive])
* 2018 [[2018 Hosting Proposals|Washington, District of Columbia]]
* 2016 [https://c4l-phl.github.io/ Philadelphia, Pennsylvania] ([https://web.archive.org/web/20161024174902/http://c4l-phl.github.io/ archive])
* 2015 [https://osulp.github.io/code4lib-pdx/ Portland, Oregon] ([https://web.archive.org/web/20150111223851/osulp.github.io/code4lib-pdx/ archive])
* 2012 [https://web.archive.org/web/20120115030208/sites.google.com/site/code4lib2012seattle/ Seattle, Washington]
* 2011 [https://web.archive.org/web/20120103125715/wiki.dlib.indiana.edu/display/EVENTS/Code4Lib+2011+Proposal Bloomington, Indiana]

Prefer Internet Archive links where available. These proposals have a tendency to be deleted after the conference passes.

2018 Hosting Proposals

2025-02-06T21:06:02Z

Phette23: /* Washington DC 2018 Code4Lib Proposal */

'''Schedule (second round)'''

* Proposal period opens: February 28th, 2017

* Proposal period ends: March 17th 2017

* Voting opens: March 20th, 2017

* Voting closes: March 31st, 2017

'''Please list your proposal below.'''

==Washington DC 2018 Code4Lib Proposal==

===Welcome to Washington D.C!===

Most people know the District of Columbia as the home of our nation's capital, but we're also proud of being the capital of FREE. Explore museums and galleries like the newly opened National Museum of African American History and Culture, see a performance at our National Kennedy Center, or connect with nature at our Botanical Garden, Arboretum, or National Zoo. Our food scene is also making waves. We were rated '2016 restaurant city of the year,' and in 2017, we joined New York, San Francisco and Chicago with a Michelin Guidebook. Voted the #1 transit-friendliest city and #2 most walkable city in the United States, D.C. makes getting around between all of these amenities painless and safe. Furthermore, with three airports (DCA, IAD, BWI) and Amtrak, D.C. is a destination that is easy and relatively inexpensive to get to. It's a great time to come to Washington D.C.!

===The Conference===

We're currently investigating venues for a February 2018 conference that can accommodate roughly 400(~450) attendees and meet Code4Lib's technical requirements.

Pre-conference workshops would take place in several of our metro-accessible DC Public Library neighborhood branches, and we're looking at throwing the opening reception at the Library of Congress.

===The Cost===

DC is a bit pricey, so we're investigating a range of alternative housing options to hotels. AirBnBs average around $80 per night in February, and there are several hostels near Capitol Hill including Washington DC House and Capital View Hostel.

===Fiscal Sponsor===
This proposal has been made possible by the generous cooperation of DLF and CLIR, who have agreed to be our fiscal host for the 2018 Code4Lib Conference in D.C. Thank you Bethany and the CLIR/DLF team <3

===Organizational Committee===

* Jaime Mears - Library of Congress (Chair)
* Bohyun Kim - University of Maryland, Baltimore, Health Sciences and Human Services Library
* Nick Kerelchuck - DC Public Libraries
* Joel Richard - Smithsonian Libraries
* Ben Wallberg- University of Maryland Libraries
* Kate Dohe - University of Maryland Libraries

[[Category:Code4Lib2018]]
[[Category:Conference Hosting Proposals]]

Code4Lib 2014 Conference Planning Volunteers

2025-02-06T20:57:39Z

Phette23:

= Code4Lib 2014 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and 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. 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 hope to include at least one local person on each committee.

A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.

The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).

== Book Give-Away Committee ==

This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.

Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.

* Kevin S. Clarke (Manning) and general wrangling (nominated as lead) - no luck with books from Manning
* Michael B. Klein (Pragmatic) and winner-picker app
* Sarah Shealy (Packt) and general wrangling if/when needed - no luck with books from Packt
* Shaun Ellis (Rosenfeld Media and O'Reilly eBooks)

Current Status:
* O'Reilly is also offering a free ebook to all attendees. This is in the form of a printed voucher that should be bundled with the t-shirt and other swag. Shaun Ellis is responsible for the printing of the vouchers.
* Rosenfeld Media is shipping a number of giveaway titles directly to Tim McGeary a couple weeks before the conference.
* Pragmatic responds: "Thank you for thinking of us and contacting us again about providing give-away items. We are actually in the Raleigh area, and would be happy to coordinate a drop off of books for use as door prizes at the time of the conference." I will follow up with them closer to the conference date to coordinate a drop-off.

Shaun also mentioned that we have a prospectus this year that would be great to send along with our requests to the publishers. You can find it at: http://code4lib.org/files/Code4LibProspectus.pdf

== Keynote Speakers Committee ==

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

Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013 
Keynote speaker voting - September 9, 2013 - September 20, 2013 
Have speakers finalized by November 15, 2013

* Jason Casden (NCSU) -- lead
* Tom Johnson (Johnson.tom@gmail.com)
* Bret Davidson (NCSU)
* Jeff Campbell (UNC)
* Joyce Chapman (State Library of NC)
* Dre (NCSU)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)

== Onsite Volunteer Committee ==

This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.

* Kevin S. Clarke
* Kevin Beswick (NCSU)
* Yan Wang (NCCU)
* Kelly Leong (Duke)
* Dre (NCSU)
* Jason Raitz (NCSU)

== Pre-conference Committee ==

This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

Call for pre-conf proposals -- October 14, 2013 
Deadline for pre-conf proposals -- December 6, 2013 
Finalize pre-confs before registration opens -- January 3, 2014 
Send rosters to pre-conf organizers -- by February 21, 2014

* Adam Constabaris (NCSU) -- nominated as lead
* Tim Shearer (UNC)
* Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.

Call for talk proposals -- October 14 - November 8, 2013 
First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013 
Voting on talks -- November 18, 203 - December 6, 2013 
Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013 
Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!) 
Post final program schedule with talks - January 13, 2014

* Tom Johnson (Johnson.tom@gmail.com) -- lead
* Kevin Beswick (NCSU)
* Ranti Junus (ranti.junus@gmail.com)
* Roy Tennant (OCLC)
* Trevor Thornton (hellotrevorthornton@gmail.com)
* Lucas Mak (makw@mail.lib.msu.edu)
* [[User:DataGazetteer|Peter Murray]] (LYRASIS)
* Tod Olson (tod at uchicago dot edu)

== 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.

Call for applicants -- November 18, 2013 - December 13, 2013 
Determine winners -- December 14, 2014 - January 5, 2014 
Notify winners -- January 6, 2014 (must be before registration)

* Jason Ronallo (NCSU) -- lead
* Cory Lown (NCSU)
* Bohyun Kim (FIU)
* Santi Thompson (University of Houston) sathompson3@uh.edu
* Sarah Shealy (sarah.shealy@outlook.com)

== Social Activities Committee ==

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

* Jason Raitz
* Rosalyn Metz
* Dre
* Becky Yoose
* Bohyun Kim

== Sponsorships Committee ==

This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). 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.

* Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)
* Roy Tennant (OCLC)
* Shaun Ellis (shaune@princeton.edu)
* Robert H. McDonald (Indiana)
* Sean Chen (Duke)
* Thomas Dowling (Wake Forest)
* Will Sexton (Duke)
* Jeff Campbell (UNC)
* Brett Bonfield (Collingswood Public)

== Streaming Video Committee ==
As of 12-18-2013 this committee has been combined with the Wifi/Electrical/IRC committee

== T-Shirt Committee ==

This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

Call for T-shirt designs - December 2, 2014 - January 3, 2014 
Voting on T-shirt designs - January 13, 2014 - January 24, 2014 
Get bids based on sizes and design - January 27, 2014 - February 14, 2014 
Order t-shirts by February 17, 2014

*Charlie Morris (NCSU) -- lead
*Josh Wilson, State Library of NC (joshwilsonnc at gmail)

== 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.

*Adam Constabaris (NCSU)

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* Francis Kayiwa
* Kevin S. Clarke
* Dre
* Ranti Junus

== Wifi / Electrical / IRC / Streaming Video Committee==

This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur, in addition the committee is responsible to work with the local hosts to figure out the requirements for video / streaming video and work to get final A/V estimates by late November 2013 to use for the final budget

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org
* [[User:RileyChilds|Riley Childs]], Riley@TFSGEO.com
* Francis Kayiwa
* Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)
* Jeff Campbell - UNC - CH

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2014]]
[[Category:Conference Committees]]

2013 committees sign-up page

2025-02-06T20:54:49Z

Phette23:

= Code4Lib 2013 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2013 conference, create an account on this wiki and 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.

'''[[2013 During the Conference Volunteers | During the Conference Volunteers]]''' - If you're going to be at the conference, sign up to help out!

== Book Give-Away Committee ==

* Michael North (m-north@northwestern.edu)

== 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.

* Margaret Heller mheller@dom.edu
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* Kyle Banerjee banerjek@uoregon.edu
* Bohyun Kim kimb et fiu dot edu
* [http://roytennant.com/ Roy Tennant], roytennant@gmail.com
* [http://twitter.com/TheRealArty Cynthia Ng]
* [[User:highermath|Cary Gordon]], cgordon@chillco.com

== 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.

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Anjanette Young
*Kevin Reiss kr2 @ princeton . edu
*Jim Rible rible@sou.edu

== Program Committee ==

This committee plans the structure of the program, arranges the voting on presentations, etc. These folks will also announce speakers, etc.
* [[User:DataGazetteer|Peter Murray]], peter.murray@lyrasis.org
* [http://twitter.com/ranti Ranti Junus], ranti.junus@gmail.com
* Ray Schwartz, schwartzr2@wpunj.edu
* [http://twitter.com/TheRealArty Cynthia Ng], cynthia.s.ng at gmail
* Tom Johnson, thomas.johnson@oregonstate.edu
* Tod Olson, tod at uchicago dot edu

== 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.
* [http://jodischneider.com/jodi.html Jodi Schneider]
* [http://ecorrado.us/ Edward M. Corrado]
* Santi Thompson, sathompson3@uh.edu
* Christina Salazar (christina.salazar AT csuci DOT edu)

== T-Shirt Committee ==

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

* akorphan (akorphan AT ncsu DOT edu)
* [[User:Pberry|Pberry]] Patrick Berry (pberry@csuchico.edu)
* Shaun Ellis (shaune@princeton.edu)

== Social Activities Committee ==

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

*Francis Kayiwa kayiwa@ YOU EYE SEE DOT edu
*Ray Schwartz, schwartzr2@wpunj.edu
*Bohyun Kim kimb et fiu dot edu
*Shane Beers, sbeers depaul edu
*[[User:JonGorman|Jon Gorman]], jtgorman @ illinois dot edu
*Becky Yoose, b.yoose cinnamon roll gmail speck com
* [http://twitter.com/danwho Dan "lampshade" Suchy], dansuchy at gmail
*Margaret Heller, mheller@dom.edu

== 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.
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail

== Whatever Committee ==

This committee does whatever the organizers can't talk anyone else into doing.

* [[User:highermath|Cary Gordon]], cgordon@chillco.com
* [http://twitter.com/jlefager Jim LeFager], jameslefager at gmail
* [[User:Wolf29|Wolf Halton]], wolf.halton@lyrasis.org./dev/null
* [[User:crowesn|Sean Crowe]], sean.crowe@ uc dot edu
* [[User:shawnc12|Shawn Carraway]], carraways@ midlandstech dot edu
* [[User:mackeral|Michael Lindsey]], mackeral at gmail
* [[User:Mnorth|Michael North]], m-north AT northwestern DOT edu
* [[User:Tracy.seneca|Tracy Seneca]], tjseneca at uic dot edu

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2013]]
[[Category:Conference Committees]]

2012 committees sign-up page

2025-02-06T20:51:16Z

Phette23:

= Code4Lib 2012 Committees =

If you are interested in helping out with a particular part of the Code4Lib 2012 conference, create an account on this wiki and 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.

[[During the Conference Volunteers]]

== Book Give-Away Committee ==

* Kevin S. Clarke (ksclarke@gmail.com) -- McHenry Library, UC Santa Cruz -- Asking O'Reilly
* Chandos Publishing. Yes.
* No Starch. Yes.
* [http://www.seattletechnicalbooks.com Ada's Technical Books]. Woohoo.
* Andrew Nagy -- oXygen XML Editor (5 Licenses to give away)
* [[BookRaffle|Suggestions for Book Raffle.]]

== 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
* Anjanette Young -- University of Washington
* Mike Giarlo -- Penn State
* [[User:DataGazetteer|Peter Murray]] -- LYRASIS (likely sponsor)
* Andrew Nagy -- Serials Solutions
* Roy Tennant -- OCLC

== 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
* Ranti Junus (ranti.junus at gmail) - Michigan State University
* John Fink (john.fink at gmail) - McMaster University
* Tom Johnson (thomas dot johnson at oregonstate dot edu) - Oregon State University
* [[User:DataGazetteer|Peter Murray]] - LYRASIS

== 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
* Jodi Schneider - DERI, NUI Galway
* Becky Yoose [yoosebec] at grinnell dot edu - Grinnell College
* Ed Corrado - Binghamton University
* Terry Reese - Oregon State University
* Ranti Junus - Michigan State University

== 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
* Angie Beiriger (beiriger at reed dot edu) Reed college

== Social Activities Committee ==

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

* Jennifer Ward (jlward1 at uw dot edu) -- University of Washington
* Jeff Sherwood (jeffs3 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.

= Documentation =
To help with documention, no need to sign up, just start editing.
* [[How To Plan A Code4LibCon]]

== Documentation Interest Group ==
Promote ongoing documentation efforts.

[[Category: Code4Lib2012]]
[[Category:Conference Committees]]

How To Plan A Code4LibCon

2025-02-06T20:42:45Z

Phette23:

== General Process ==

While this is the general chronology of running the conference, it never hurts to plan ahead. Before hosting proposals for the next year are solicited, you can prepare some components of your proposal. Before your proposal is accepted, you can recruit volunteers to serve on committees. In particular, it helps to have at least a few initial people who will form the nucleus of your Local Planning Committee (LPC).

* When the call for next year's host goes out, '''prepare a proposal'''
** '''TODO see successful proposals from prior years'''
** '''Identify venues''' for both the conference and the hotel (if different).
** '''Prepare cost estimates'''. The primary factors are:
*** Lodging (hotels) - see if hotels offer discounted room block quotes
*** Venues (conference, workshop, reception, other activities)
*** Catering
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you look at a hotel or other venue, make sure you talk to them about bandwidth and costs.
*** Do you have organizational relationships which might ensure extra sponsorships? If so, factor in that this might reduce the registration cost. For instance, when we were at the Library of Congress in 2018, they were also [https://2018.code4lib.org/sponsors/ our largest sponsor].
*** You can reference data from previous years to estimate minimums and maximums.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask them questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel room block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if so, they can also be very helpful and will know more about campus spaces and costs (e.g. if there are free rooms to use for pre-conferences).
* Get approved by the community and start planning
** Receive access to the Code4Lib Conference Drive folders with information from prior years
** Construct a planning timeline (see templates in Drive)
** Find a hotel, negotiate and sign a contract with them. CONCENTRA does this but this [[Sample RFI]] is still a useful reference; '''note the WiFi requirements'''
** Put out a call for committee volunteers (on the listserv, in Slack)
* '''Put on an amazing conference!''' If you get this far, you have survived the worst part.
* The final duties of LPC are putting out the call for next year's proposals and writing up reflections.

== Location ==

Code4Lib has been hosted on university campuses and also located purely in hotels. Campus facilities tend to be more affordable, but housing can be scattered and challenging. Hotels are more expensive but cohesive.

If your campus or town has a conference center, that is a logical starting point. Large hotels are also an option. In recent years, the conference has been smaller (a little over 200 attendees). If you are unsure how many attendees to plan for, look at [Conference_Financial_History_At_A_Glance] figures or ask in the code4libcon channel in Slack. In general, 200-400 attendees is a good range.

A couple of isolated rooms for the conference but away from the main space are important for both the Community Support Squad to hold private discussions and to private a place of quiet respite for weary conference goers.

=== Workshops ===

Workshops have been held before and after the conference. They are often referred to as "pre-conferences" or "post-conferences" in planning and publicity materials. There should be space to facilitate 10-20 workshops. It is helpful if they can be located in the same building but not necessary.

These can be class or meeting rooms but should have a projector and ideally a whiteboard. Electricity for every attendee is also important.

=== Reception ===

A nice reception venue can be appealing to many attendees. In the past, we have gone to museums, libraries, and more fun venues. If Philadelphia, we went to The Mütter Museum. In D.C., we went to the Library of Congress. In Michigan, we went to a "fowling" (football bowling) place.

A nice reception at a separate location is not stricly necessary. It might be possible to do catering at the conference venue in the evening, for instance.

=== Transportation ===

Consider how folks coming into town will get to their lodging. Is the airport far? Are there free shuttles? Is it possible to get there via a major railway?

If lodging and the venue are separate, how will attendees get to the conference venue? Are there shuttles? If we need to purchase a bus, how much will it cost?

Most years, we need to pay for a bus to the reception venue, as it tends to be in a different location.

=== Local Appeal ===

Successful proposals in the past tend to include local spots that folks will be interested in: cultural institutions, tourist attractions, book stores, libraries, restaurants, and night life. The Social Activities committee plans around these venues. It is nice to have a nighttime location where Game Night can be held (which might be one of the workshop rooms).

There is nothing wrong with doing a conference in a location we've been to before, or in a location that is close to last year's location. In the past, Code4Lib tended to bounce between the East coast, West coast, and Midwest but that is not a requirement and should not dissuade any location from submitting a proposal.

== Committee List ==

Each year we copy the prior year's list of committees (see [[:Category:Conference Committees]]) to a new wiki page. If you are looking for information on a committee or new volunteers, looking at prior years can sometimes give you some names, but know that not all committees keep their membership on the wiki up to date.

Here are brief descriptions of some of the primary committees:

* Planning (LPC) - primary committee, should have delegates on most others, makes major decisions
* Website - creates and updates the website using a template and data provided by other committees
* Sponsorship - acquires sponsorships to reduce costs
* Keynote - solicits suggestions from community and communicates with keynote candidates
* Pre-conference - plans workshops
* Program - plans posters and conference talks
* Scholarship - solicits diversity scholarship applications and selects candidates
* Community Support Squad (CSS) - enforces the Community [https://github.com/code4lib/code-of-conduct Code of Conduct]
* T-Shirt - solicit T-Shirt designs
* Social Activities - plans social events at the conference such as Board Game Night
* Streaming - runs the livestream
* Host Voting - solicit proposals for next year
* Accessibility - consult on physical and digital accessibility, e.g. of venues and the conference websites

You will also need on-site volunteers during the conference for tasks like MCing the conference, timing talks, and running microphones for audience questions.

Code4Lib is democratic; most committees faced with multiple options (keynote, pre-conference, program, t-shirt, host voting) host community votes to determine some or all of their choices.

Some committees are quite small, even a single person. Each year may have some unique committees not present in the list above. For more information on any particular committee, look in their Drive folder or on the wiki.

== Planning ==

=== Budgeting ===

* [[Conference_Financial_History_At_A_Glance]]

=== Wireless ===

historically, Code4Lib has had trouble with wifi bandwidth at venues. Hotels will lie about their wifi. Try to receive assurance that every attendee will be able to simultaneously have 1-2 devices connected to the network. It's best if you are able to visit the venue to verify its network characteristics.

It is good if the venue allows VPN traffic as many folks use a work VPN. It's also nice if commonly used ports, like 22 for ssh/git, are usable.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

== At the Conference ==

=== Code of Conduct ===

LPC may be consulted by the CSS if a Code of Conduct violation occurs. These have sometimes necessitated someone being removed from the conference or an announcement being made from the stage.

=== Keynotes ===

# Speaker gifts
# Dinner plans

=== Lightning Talks ===

* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

=== Conference ===

# Power - everyone would like to plug in their laptop (and possibly their phone)
# IRC Monitor for podium during speaker changes?

=== Photography ===

Code4Lib uses different colored lanyards to articulate personal photography preferences.

* Green = it's ok to take my picture
* Yellow = please ask before taking my picture
* Red = don't take my picture

=== Podium ===

# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide an apple box for presenters who would like to use one.

=== Video ===

# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Calls for Hosting ===

See [[:Category:Conference Hosting Proposals]].

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Further Readings ==

The most recent year's Lessons Learned (in Drive) are more likely to be relevant. Some of these links are quite old but may still contain valuable insight on problems that have happened over the years.

* [[Code4Lib Conference Lessons Learned]] (from 2014)
* [[2017_Lessons_Learned]]
* [https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

=== Additional Links ===

* [[C4L2010planning|2010 planning]]
* [[C4L2011planning|2011 planning]]
* [[Useful information from 2012]]

[[Category: Code4LibCon Planning]]

C4L2012 Call For Host

2025-02-06T20:32:04Z

Phette23:

The Code4Lib Conference Planning Group is putting out a call for
proposals to host the 2012 Code4Lib Conference. Information on the
kind of venue we seek and the delineation of responsibilities between
the host organization and the Planning Group can be found at the
conference hosting web page [1] and on the Code4Lib Wiki [2].

The deadline for proposals is Sunday January 23, 2011. The
decision will be made over the course of the following weeks by a
popular vote. Voting will begin on or around Wednesday January 25,
2011 and will continue through the first three days of Code4Lib 2011 until
11:59PM Eastern on Wednesday, February 9th. The results of the vote will be
announced on Thursday, February 10th, the final day of Code4Lib 2011.
You can apply by making your pitch to the Code4Lib Conference Planning
list [3]; attention to the criteria listed on the conference hosting
page is appreciated. May the best site win!

Feel free to take a look at past hosting proposals from 2011 for
ideas:

*https://wiki.dlib.indiana.edu/display/EVENTS/Code4Lib+2011+Proposal

*http://www.library.yale.edu/~dlovins/c4l/code4lib2011.html

*http://sites.google.com/site/code4libvancouver2011

1. http://code4lib.org/conference/hosting

2. http://wiki.code4lib.org/index.php/How_To_Plan_A_Code4LibCon

3. code4libcon@googlegroups.com

[[Category:Code4Lib2012]]
[[Category:Conference Hosting Proposals]]

How To Plan A Code4LibCon

2025-02-06T20:29:15Z

Phette23: large update

== General Process ==

While this is the general chronology of running the conference, it never hurts to plan ahead. Before hosting proposals for the next year are solicited, you can prepare some components of your proposal. Before your proposal is accepted, you can recruit volunteers to serve on committees. In particular, it helps to have at least a few initial people who will form the nucleus of your Local Planning Committee (LPC).

* When the call for next year's host goes out, '''prepare a proposal'''
** '''TODO see successful proposals from prior years'''
** '''Identify venues''' for both the conference and the hotel (if different).
** '''Prepare cost estimates'''. The primary factors are:
*** Lodging (hotels) - see if hotels offer discounted room block quotes
*** Venues (conference, workshop, reception, other activities)
*** Catering
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you look at a hotel or other venue, make sure you talk to them about bandwidth and costs.
*** Do you have organizational relationships which might ensure extra sponsorships? If so, factor in that this might reduce the registration cost. For instance, when we were at the Library of Congress in 2018, they were also [https://2018.code4lib.org/sponsors/ our largest sponsor].
*** You can reference data from previous years to estimate minimums and maximums.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask them questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel room block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if so, they can also be very helpful and will know more about campus spaces and costs (e.g. if there are free rooms to use for pre-conferences).
* Get approved by the community and start planning
** Receive access to the Code4Lib Conference Drive folders with information from prior years
** Construct a planning timeline (see templates in Drive)
** Find a hotel, negotiate and sign a contract with them. CONCENTRA does this but this [[Sample RFI]] is still a useful reference; '''note the WiFi requirements'''
** Put out a call for committee volunteers (on the listserv, in Slack)
* '''Put on an amazing conference!''' If you get this far, you have survived the worst part.
* The final duties of LPC are putting out the call for next year's proposals and writing up reflections.

== Location ==

Code4Lib has been hosted on university campuses and also located purely in hotels. Campus facilities tend to be more affordable, but housing can be scattered and challenging. Hotels are more expensive but cohesive.

If your campus or town has a conference center, that is a logical starting point. Large hotels are also an option. In recent years, the conference has been smaller (a little over 200 attendees). If you are unsure how many attendees to plan for, look at [Conference_Financial_History_At_A_Glance] figures or ask in the code4libcon channel in Slack. In general, 200-400 attendees is a good range.

A couple of isolated rooms for the conference but away from the main space are important for both the Community Support Squad to hold private discussions and to private a place of quiet respite for weary conference goers.

=== Workshops ===

Workshops have been held before and after the conference. They are often referred to as "pre-conferences" or "post-conferences" in planning and publicity materials. There should be space to facilitate 10-20 workshops. It is helpful if they can be located in the same building but not necessary.

These can be class or meeting rooms but should have a projector and ideally a whiteboard. Electricity for every attendee is also important.

=== Reception ===

A nice reception venue can be appealing to many attendees. In the past, we have gone to museums, libraries, and more fun venues. If Philadelphia, we went to The Mütter Museum. In D.C., we went to the Library of Congress. In Michigan, we went to a "fowling" (football bowling) place.

A nice reception at a separate location is not stricly necessary. It might be possible to do catering at the conference venue in the evening, for instance.

=== Transportation ===

Consider how folks coming into town will get to their lodging. Is the airport far? Are there free shuttles? Is it possible to get there via a major railway?

If lodging and the venue are separate, how will attendees get to the conference venue? Are there shuttles? If we need to purchase a bus, how much will it cost?

Most years, we need to pay for a bus to the reception venue, as it tends to be in a different location.

=== Local Appeal ===

Successful proposals in the past tend to include local spots that folks will be interested in: cultural institutions, tourist attractions, book stores, libraries, restaurants, and night life. The Social Activities committee plans around these venues. It is nice to have a nighttime location where Game Night can be held (which might be one of the workshop rooms).

There is nothing wrong with doing a conference in a location we've been to before, or in a location that is close to last year's location. In the past, Code4Lib tended to bounce between the East coast, West coast, and Midwest but that is not a requirement and should not dissuade any location from submitting a proposal.

== Committee List ==

Each year we copy the prior year's list of committees (see [[Category:Conference Committees]]) to a new wiki page. If you are looking for information on a committee or new volunteers, looking at prior years can sometimes give you some names, but know that not all committees keep their membership on the wiki up to date.

Here are brief descriptions of some of the primary committees:

* Planning (LPC) - primary committee, should have delegates on most others, makes major decisions
* Website - creates and updates the website using a template and data provided by other committees
* Sponsorship - acquires sponsorships to reduce costs
* Keynote - solicits suggestions from community and communicates with keynote candidates
* Pre-conference - plans workshops
* Program - plans posters and conference talks
* Scholarship - solicits diversity scholarship applications and selects candidates
* Community Support Squad (CSS) - enforces the Community [https://github.com/code4lib/code-of-conduct Code of Conduct]
* T-Shirt - solicit T-Shirt designs
* Social Activities - plans social events at the conference such as Board Game Night
* Streaming - runs the livestream
* Host Voting - solicit proposals for next year
* Accessibility - consult on physical and digital accessibility, e.g. of venues and the conference websites

You will also need on-site volunteers during the conference for tasks like MCing the conference, timing talks, and running microphones for audience questions.

Code4Lib is democratic; most committees faced with multiple options (keynote, pre-conference, program, t-shirt, host voting) host community votes to determine some or all of their choices.

Some committees are quite small, even a single person. Each year may have some unique committees not present in the list above. For more information on any particular committee, look in their Drive folder or on the wiki.

== Planning ==

=== Budgeting ===

* [[Conference_Financial_History_At_A_Glance]]

=== Wireless ===

historically, Code4Lib has had trouble with wifi bandwidth at venues. Hotels will lie about their wifi. Try to receive assurance that every attendee will be able to simultaneously have 1-2 devices connected to the network. It's best if you are able to visit the venue to verify its network characteristics.

It is good if the venue allows VPN traffic as many folks use a work VPN. It's also nice if commonly used ports, like 22 for ssh/git, are usable.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

== At the Conference ==

=== Code of Conduct ===

LPC may be consulted by the CSS if a Code of Conduct violation occurs. These have sometimes necessitated someone being removed from the conference or an announcement being made from the stage.

=== Keynotes ===

# Speaker gifts
# Dinner plans

=== Lightning Talks ===

* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

=== Conference ===

# Power - everyone would like to plug in their laptop (and possibly their phone)
# IRC Monitor for podium during speaker changes?

=== Photography ===

Code4Lib uses different colored lanyards to articulate personal photography preferences.

* Green = it's ok to take my picture
* Yellow = please ask before taking my picture
* Red = don't take my picture

=== Podium ===

# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide an apple box for presenters who would like to use one.

=== Video ===

# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

== Suggested Timeline ==

TODO there are more current timelines available or this section is just not needed.

* See [[C4L2010planning]] for an example
* Ideal to have program set before registration, including pre-conf
** also allows clarity for how many spots are avail for non-presenters

===Calls for Hosting===

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Some Suggested Readings ==

*[[Code4Lib Conference Lessons Learned]] (from 2014)
*[[Useful information from 2012]]
*[https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

[[Category: Code4LibCon Planning]]

Category:Conference Committees

2025-02-06T19:42:19Z

Phette23: add all prior pages

Lists each year's committees.

== Annual Lists of Committees ==

* [[2015 Conference Committees]]
* [[2016 Conference Committees]]
* [[2017 Conference Committees]]
* [[Code4Lib 2018 Conference Committees]]
* [[Code4Lib 2019 Conference Committees]]
* [[Code4Lib 2020 Conference Committees]]
* [[Code4Lib 2021 Conference Committees]]
* [[Code4Lib 2022 Conference Committees]]
* [[Code4Lib 2023 Conference Committees]]
* [[Code4Lib 2024 Conference Committees]]
* [[Code4Lib 2025 Conference Committees]]
* [[Code4Lib 2026 Conference Committees]]

Code4Lib 2026 Conference Committees

2025-02-06T19:37:10Z

Phette23:

= Code4Lib Conference Committees =

Hosting a conference is 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 2026 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 Chair, Primary Contact

==Planning Committee==
Also known as the Local Planning Committee, although there is no requirement for the members to be local.

[[2026 Planning Committee Documents|2026 Planning Committee Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2026 Website Working Group Documents|2026 Website Working Group Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[2026 Budget and Sponsorship Documents]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2026 Pre-conference Documents|2026 Pre-conference Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2026 Program Documents|2026 Program Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Scholarship 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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2026 T-Shirt Documents|2026 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2026 Conference Volunteers]]'''

[[2026 Online Volunteer Documents|2026 Online Volunteer Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2026 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Code4Lib 2026 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2026 Host Voting Documents|2026 Host Voting Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2026 Accessibility Documents|2026 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2026 Whatever Documents|2026 Whatever Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category: Code4Lib2026]]
[[Category:Conference Committees]]

Code4Lib 2024 Conference Committees

2025-02-06T19:36:21Z

Phette23:

= Code4Lib 2024 Conference Committees =

Hosting a conference is 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 2024 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 Chair, Primary Contact

==Planning Committee==
Also known as the Local Planning Committee, although there is no requirement for the members to be local.

[[2024 Planning Committee Documents|2024 Planning Committee Documents]]

* [[User:NatashaAllen|Natasha Allen]] (U-M) - Primary Contact, Chair
* Jesse Johnston (U Michigan) - Secondary Contact, Co-chair, documentarian
* Jennifer Cummings (Concentra) - Tertiary Contact
* Kathy Azevedo (Concentra) - Volunteer
* [[User:varnum|Ken Varnum]] (U-M) - Volunteer
* [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2024 Website Working Group Documents|2024 Website Working Group Documents]]

* Esmé Cowles - Primary Contact, Chair
* [[User:Phette23|Eric Phetteplace]] phette23@gmail.com - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Andy Pederson (apederson@unl.edu) - Accessibility Committee Contact
* Trip Kirkpatrick trip.kirkpatrick@yale.edu - Volunteer
* Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* Christine Salek (cmsalek@wisc.edu) - Volunteer
* [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - LPC liaison

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2024 Budget and Sponsorship Documents]

* Jesse Johnston (UMich) - Primary Contact, Chair, and liaison to LPC
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Bohyun Kim - Volunteer
* Mary Jinglewski - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start work in late September. The work will wrap up in January, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Andromeda Yelton - Primary Contact, Chair
* Mike Taylor (mike.taylor@nau.edu) - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Lillian Hogendoorn (lillian.hogendoorn@utoronto.ca) - Volunteer
* Maccabee Levine (@maccabeelevine on slack) - Volunteer
* [[User:NatashaAllen|Natasha Allen]] - LPC Liaison

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2024 Pre-conference Documents|2024 Pre-conference Documents]]

* Ann Marie Mesco - Primary Contact, CoChair
* Ken Rose - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:SheriseKimura|Sherise Kimura]] - Volunteer
* Jason Glenn - Volunteer
* [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2024 Program Documents|2024 Program Documents]]

* Your Name Here - Primary Contact, Chair
* [[User:MegoFranks|Mego Franks]] - Secondary Contact, CoChair - megofranks@gmail.com
* [[User:BrandonPatterson|Brandon Patterson]] - Documentarian
* Matt Sherman - Volunteer
* Dre - Volunteer
* [[User:varnum|Ken Varnum]] - LPC liaison
* [[User:highermath|Cary Gordon]] - Volunteer
* [[User:MoniqueRio|Monique Rio]] - Volunteer

== Scholarship 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.

[[2024 Scholarship Documents|Scholarship Committee Documents]]

Work will start in early October

* Chad Nelson - chad.nelson at ucop.edu, @bibliotechy on Slack - Primary Contact, Chair
* Michelle Speed - Secondary Contact, CoChair
* Andrew Battelini - abattel@emory.edu, Documentarian
* [[User:MaxEckard|Max Eckard]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2024.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

'''Currently seeking a co-coordinator.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Soojeong Herring on Slack or via email (soojeong_herring@brown.edu).

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2024 T-Shirt Documents|2024 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''

[[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Coral Sheldon-Hess - Volunteer, virtual-only
* [[User:Hardyoyo|Hardy Pottinger]] - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Brandon Patterson - Primary Contact, Chair
* [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:Hardyoyo|Hardy Pottinger]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

* [[User:DataGazetteer|Peter Murray]] - Primary Contact, Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - LPC Volunteer
* Your Name Here - Volunteer

== Code4Lib 2025 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2025 Host Voting Documents|2025 Host Voting Documents]]

*[[User:NatashaAllen|Natasha Allen]] (University of Michigan) - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* [[User:DavidFulmer|David Fulmer]] - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2024 Accessibility Documents|2024 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Christine Salek (cmsalek@wisc.edu) - Volunteer
* Zhaneille Green (zbg@duke.edu) - Volunteer
* Andy Pederson (apederson@unl.edu) - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2024 Whatever Documents|2024 Whatever Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* [[User:SamHansen|Sam Hansen]] - Volunteer
* [[User:coral|Coral Sheldon-Hess]] - Remote Volunteer

[[Category: Code4Lib2024]]
[[Category:Conference Committees]]

Code4Lib 2021 Conference Committees

2025-02-06T19:36:05Z

Phette23:

= Code4Lib 2021 Conference Committees =

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 2021 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 (LPC) to each committee.

== Location and Dates ==

* Location: Virtual
* Dates: Monday, March 22, 2021 to Friday, March 26, 2021
** Main meeting: Monday, March 22, 2021 to Thursday, March 25, 2021
** Post-conferences: Friday, March 26, 2021

== Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Blake Carver - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Secondary Contact AKA CoChair
* [mailto:jester@dltj.org Peter Murray] - Tertiary Contact AKA CoChair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Documentarian
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer
* [mailto:abattel@emory.edu Andrew Battelini] - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2021 Website Working Group Documents|2021 Website Working Group Documents]]

* [https://wiki.code4lib.org/User:Derekz Derek Zoladz] - Primary Contact AKA Chair
* [mailto:jcaffreyhill@towson.edu Julia Caffrey-Hill] - Secondary Contact AKA CoChair
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Planning Committee Contact
* [mailto:jerry.yarnetsky@miamioh.edu Jerry Yarnetsky] - Documentarian
* [mailto:ranti.junus@gmail.com Ranti Junus] - Volunteer
* Andy Hickner (alh4014@med.cornell.edu) - Volunteer
* [mailto:qum@miamioh.edu Meng Qu]- Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the VPC to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2021 Budget and Sponsorship Documents|2021 Budget and Sponsorship Documents]]

* Mary Jinglewski - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Janna Avon - Documentarian
* [[User:BrianMaass|Brian Maass]] (brian.maass@unmc.edu) - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2021 Keynote Documents|2021 Keynote Documents]]

[[2021 Keynote Speakers Nominations|2021 Keynote Speakers Nominations]]

* [mailto:clara.turp@mcgill.ca Clara Turp] - Primary Contact AKA Chair
* [mailto:dana.reijerkerk@stonybrook.edu Dana Reijerkerk] - Secondary Contact AKA CoChair
* [mailto:abattel@emory.edu Andrew Battelini] - Planning Committee Contact
* [mailto:bobbi@bobbifox.net Bobbi Fox] - Documentarian
* [[User:Khaley|Kathleen Haley]] - Volunteer
* Your Name Here - Volunteer

== Post-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2021 Post-conference Documents|2021 Post-conference Documents]]

* [mailto:casden@gmail.com Jason Casden] - Primary Contact AKA Chair
* [mailto:tod@uchicago.edu Tod Olson] - Secondary Contact AKA CoChair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Documentarian/Planning Committee Contact
* [mailto:brighidmgonzales@gmail.com Brighid Gonzales] - Volunteer
* [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Volunteer
* [mailto:kr2e@andrew.cmu.edu Ken Rose] - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2021 Program Documents|2021 Program Documents]]

* [mailto:aaron.collier@stanford.edu Aaron Collier] - Primary Contact AKA Chair
* [mailto:akorphan@ncsu.edu Andreas Orphanides] - Secondary Contact AKA CoChair
* [mailto:mike.taylor@nau.edu Mike Taylor] - Planning Committee Contact
* [mailto:jtremc@gmail.com Julien Tremblay McLellan] - Documentarian
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* Jessica McMillen (new) - Volunteer
* David Schober - Volunteer
* [[User:EmilyBoss|Emily Boss]] - Volunteer

== Scholarship 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.

[[2021 Scholarship Documents|2021 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers are being vetted now! Fill out [https://forms.gle/1mvdbF8aaGidQZfD8 this form] to view the list & provide feedback.'''

[https://drive.google.com/drive/folders/1Dr2hJlnuo8vQdsyEOYC67TOrmQmIGqzG?usp=sharing 2021 CSS Documents]

* [[User:Phette23|Eric Phetteplace]] phette23[at]gmail.com - Co-Coordinator
* '''Your Name Here''' - Co-Coordinator. Please help Eric run the Squad! Contact him with questions.

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2021 T-Shirt Documents|2021 T-Shirt Documents]]

* [[User:Khaley|Kathleen Haley]] - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* [[User:ChristyKarpinski|Christy Karpinski]] - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2021 Conference Volunteers]]'''

[[2021 Online Volunteer Documents|2021 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes virtual social activities.

2021 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder

Conference attendees - Social Activities information will be posted in the Community section of Whova.

* [[User:Yoosebj|Becky Yoose]]- Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* [[User:ChristyKarpinski|Christy Karpinski]] - Documentarian
* A.M. Serrano - Volunteer
* Mike Paulmeno - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2021 Streaming Video Documents|2021 Streaming Video Documents]]
This will likely be part of the general conference planning.v

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:RichardHiggins|Richard Higgins]] - Volunteer
* Your Name Here - Volunteer

== Code4Lib 2022 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2022 Host Voting Documents|2022 Host Voting Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:NicoleLawrence|Nicole Lawrence]] - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2021 Book Giveaway Documents|2021 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2021 IRC and Slack Documents|2021 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees (virtual only, this year).

[[2021 Accessibility Documents|2021 Accessibility Documents]]

* [mailto:dkrahmer@colgate.edu Debbie Krahmer] - Primary Contact aka Chair
* [mailto:schulera@caryinstitute.org Amy Schuler] - Documentarian
* Your Name Here - Planning Committee Contact
* [mailto:kelly@trln.org Kelly Farrell] - Volunteer
* [mailto:kira.lillard@kc.frb.org Kira Lillard] - Volunteer
* [mailto:grey.maixner@gmail.com Gary Maixner] - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2021 Whatever Documents|2021 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* [[User:LoriStethers|Lori Stethers]] - Volunteer
* [mailto:heather@samvera.org Heather Greer Klein] - Volunteer

[[Category:Code4Lib2021]]
[[Category:Conference Committees]]

Code4Lib 2020 Conference Committees

2025-02-06T19:35:58Z

Phette23:

= Code4Lib 2020 Conference Committees =

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 2020 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 (LPC) to each committee.

== Location and Dates ==

* Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA
* Dates: March 08 (pre-con) - 22, 2020
** Pre-conferences: March 08, 2020
** Main meeting: March 09-11, 2020
** Post conference activities: Coming Soon

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2020 Website Working Group Documents|2020 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* Julia Caffrey (newbie) - Volunteer
* [[User:Ranti|Ranti Junus]] (v) - Volunteer
* [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer
* [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer
* [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)

== Sponsorship Committee ==
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* Mary Jinglewski - Primary Contact aka Chair
* Scott Carlson - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Janna Avon - Documentarian
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer
* [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2020 Keynote Documents|2020 Keynote Documents]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact
* [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer
* [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2020 Pre-conference Documents|2020 Pre-conference Documents]]

* [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian
* [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer
* [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer
* [mailto:jamen.mcgranahan@vanderbilt.edu Jamen McGranahan] (new) - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2020 Program Documents|2020 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer
* [mailto:akorphan@ncsu.edu Dre] - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* [mailto:bomanc@oclc.org Craig Boman] - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [[User:RichardHiggins|Richard Higgins]], Indiana University - Volunteer

== Scholarship 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.

[[2020 Scholarship Documents|2020 Scholarship Documents]]

* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer
* Your Name Here - (Volunteer)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2020 T-Shirt Documents|2020 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''

[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]

* [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer
* [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2020 Streaming Video Documents|2020 Streaming Video Documents]]

* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

== Code4Lib 2021 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2021 Host Voting Documents|2021 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]

* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:Hardyoyo|Hardy Pottinger]] - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).

[[2020 Accessibility Documents|2020 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Local Planning Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2020 Whatever Documents|2020 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* [mailto:ldobin@courthouselibrary.ca Lesley Dobin] (newbie) - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2020]]
[[Category:Conference Committees]]

Code4Lib 2019 Conference Committees

2025-02-06T19:35:49Z

Phette23:

= Code4Lib 2019 Conference Committees =

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 2019 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 (LPC) to each committee.

== Location and Dates ==

* Location: '''[http://doubletree3.hilton.com/en/hotels/california/doubletree-by-hilton-hotel-san-jose-JOSE-DT/index.html DoubleTree by Hilton]''' near the Airport, San José, CA
* Dates: February 19 (pre-con) - 22, 2019
** Pre-conferences: February 19, 2019
** Main meeting: February 20-22, 2019
** Post conference activities: Coming Soon

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - Chair, Primary Contact
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact

== 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).

[[2019 Website Working Group Documents|2019 Website Working Group Documents]]

* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair
* [[User:WhitniWatkins|Whitni Watkins]], Analog Devices, Inc. - Secondary Contact aka Co-Chair (if you want to volunteer and you've not served on any Code4Lib committees before, let me know, I'll step aside)
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact
* [http://mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Documentarian
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer
* Cody Whitby, Virginia Commonwealth University - Volunteer
* Laura Chuang - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* Mark Matienzo - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)

== Sponsorship Committee ==
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol], Long Beach City College - Secondary Contact aka Co-Chair
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact
* [mailto:dicossio@crimson.ua.edu Diana Cossio]- Documentarian
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer
* [mailto:cmathieu@jpl.nasa.gov Camille Mathieu], JPL Library - Volunteer
* [mailto:subrama@purdue.edu Annapurni Subramaniam], Purdue - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2019 Keynote Documents|2019 Keynote Documents]]

* [mailto:axm1195@case.edu Andrew Mancuso] - Primary Contact aka Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Secondary Contact aka Co-Chair
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact
* [mailto:lconrad@cca.edu Lisa Conrad] - Documentarian
* [mailto:ehenry124@gmail.com Elizabeth Henry] - Volunteer
* [mailto:clara.turp@mcgill.ca Clara Turp] - Volunteer
* [mailto:crh92@case.edu Charlie Harper] - Volunteer

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2019 Pre-conference Documents|2019 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:roytennant@gmail.com Roy Tennant] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:lydiaz@ualberta.ca Lydia Zvyagintseva] - Volunteer
* [mailto:tod@uchicago.edu Tod Olson] - Volunteer
* [mailto:KHaley@mwa.org Kathleen Haley] - Volunteer
* [[User:Kimpham54|Kim Pham]] - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2019 Program Documents|2019 Program Documents]]

* [[User:highermath|Cary Gordon]], Cherry Hill Company - Primary Contact aka Chair
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* [[User:DanielDraper|Dan Draper]] - Volunteer
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - Volunteer

== Scholarship 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.

[[2019 Scholarship Documents|2019 Scholarship Documents]]

* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (Volunteer)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2019 T-Shirt Documents|2019 T-Shirt Documents]]

* [mailto:ewahl@folger.edu Emily Wahl] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:matienzo@stanford.edu Mark Matienzo] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2019 Conference Volunteers]]'''

[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]

* [mailto:Kim.Pham60@du.edu Kim Pham] U Denver - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:hpottinger@library.ucla.edu Hardy Pottinger] UCLA Library - Volunteer
* [mailto:Tammy.Allgood@asu.edu Tammy Wolf] Arizona St. - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is at [[2019 Social Activities]]

* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair
* [http://wiki.code4lib.org/User:NatashaAllen Natasha Allen] - Secondary Contact aka Co-Chair
* [mailto:amcollie@stanford.edu Aaron Collier] - Local Planning Contact
* Meredith Broadway - Documentarian
* Ann S. - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2019 Streaming Video Documents|2019 Streaming Video Documents]]

* Your Name Here - Chair
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

== Code4Lib 2020 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2020 Host Voting Documents|2020 Host Voting Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Roy Tennant - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:lillyho@gmail.com Lilly HS HO] - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2019 Book Giveaway Documents|2019 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:Anarchivist|Mark A. Matienzo]] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:JieChen|Jie Chen]], Univ. of WI-Milwaukee Libraries - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).

[[2019 Accessibility Documents|2019 Accessibility Documents]]

* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2019 Whatever Documents|2019 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2019]]
[[Category:Conference Committees]]

Code4Lib 2018 Conference Committees

2025-02-06T19:35:42Z

Phette23:

= Code4Lib 2018 Conference Committees =

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 2018 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 (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

* All committees and committee members abides by [https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md the Code4Lib Code of Conduct].
== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

== 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).

[https://drive.google.com/drive/folders/0By3fUWhy9lUCeFN5SzVpVFB2N0U Website Working Group Documents (G Drive)]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University Libraries - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* [[User:ranti|Ranti Junus]] - Volunteer
* [[User:Kimpham54|Kim Pham]] - Volunteer
* [mailto:meag.sullivan@gmail.com Meaghan Sullivan] - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* [Your name here] - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* [[User:Dkerchner|Dan Kerchner]], George Washington University Libraries - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:morganem2015@gmail.com Morgan McKeehan] - Volunteer
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2018 Keynote Documents|2018 Keynote Documents]]

* [mailto:charles.harper@case.edu Charlie Harper], Case Western Reserve University - Primary Contact aka Chair
* [mailto:cleak@gmu.edu Carl Leak], George Mason University - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:maurini.strub@louisville.edu Maurini Strub], University of Louisville - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman], Miami University Libraries - Volunteer

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* [mailto:rdean@msu.edu Robin Dean], Michigan State University - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:johnna.percell@dc.gov Johnna Percell], DC Public Libraries - Volunteer
* [mailto:zhangj@cua.edu Jane Zhang], Catholic University of America - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [[User:Kimpham54|Kim Pham]] - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2018 Program Documents|2018 Program Documents]]

* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - Volunteer


== Scholarship 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.

[[2018 Scholarship Documents]]

* [[User:AmyWickner|Amy Wickner]] - Primary Contact aka Chair
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:aisha.connerg@gmail.com Aisha Conner-Gaten] - Documentarian
* Brooke Johnson - Volunteer
* [[User:ToddStoffer | Todd Stoffer]], NCSU Libraries - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [mailto:elvia.arroyo@gmail.com Elvia Arroyo-Ramirez], Princeton University - Volunteer
* [mailto:anastasia.chiu@stonybrook.edu Anastasia Chiu] - Volunteer
* [[User:RuthKitchinTillman|Ruth Kitchin Tillman]] - Volunteer
* Marco Seiferle-Valencia - Volunteer
* Chad Nelson - Volunteer

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Joslyn Jones, Prince William County Library System, Chair
* [mailto:ccox@ubalt.edu Carolyn Cox], University of Baltimore - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:ssmith35@gmu.edu Stephanie Smith], George Mason University Libraries - Volunteer
* [mailto:ewahl@folger.edu Emily Wahl], Folger Shakespeare Library - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* [mailto:kere@loc.gov Kelly Revak] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:LibbyM@si.edu Monique Libby], Smithsonian Libraries - Volunteer
* [mailto:durden@umd.edu David Durden], University of Maryland Libraries - Volunteer
* [mailto:jkoivist@umd.edu Joseph Koivisto], University of Maryland Libraries - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).



Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Code4Lib 2019 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer

== Wifi and Electrical ==
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:djiao@jhu.edu Dazhi Jiao], Johns Hopkins University - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* [mailto:nan.lov2010@gmail.com Nancy Lovas], Library of Congress - Primary Contact aka Chair
* [mailto:crh92@case.edu Charlie Harper] - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:cheever@cua.edu Erin Cheever] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* [[User:Anarchivist|Mark Matienzo]] - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* [mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Co-Chair
* [mailto:katherly@upenn.edu Katherine Lynch], University of Pennsylvania Libraries - Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:elandav@lib.msu.edu Elisa Landaverde], MSU Libraries - Volunteer
* [mailto:wmann@gmu.edu Wendy Mann], George Mason University Libraries - Volunteer
* [mailto:mpolchow@gmu.edu Michelle Polchow], George Mason University Libraries - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer

[[Category:Code4Lib2018]]
[[Category:Conference Committees]]

2017 Conference Committees

2025-02-06T19:35:33Z

Phette23:

= Code4Lib 2017 Conference Committees =

Call for Volunteers coming soon.

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 2017 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 (LPC) to each committee.

== Location and Dates ==

* Location: Luskin Conference Center at UCLA http://luskinconferencecenter.ucla.edu/
* Dates: March 6, 2017 - March 9, 2017
** Pre-conferences: Coming Soon
** Main meeting: Coming Soon
** Post conference activities: Coming Soon

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* [mailto:glt@library.ucla.edu Gary Thompson], UCLA - Primary Contact
* [mailto:JGomez@getty.edu Joshua Gomez], The Getty - Secondary Contact
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Tertiary Contact
* [mailto:christina.salazar@csuci.edu Christina Salazar], California State University Channel Islands - Tertiary Contact
* [mailto:brian-rogers@utc.edu Brian Rogers], University of Tennessee at Chattanooga - Documentarian
* [mailto:acollier@calstate.edu Aaron Collier], California State University
* [mailto:jsabol@marymountcalifornia.edu Jeffrey Sabol], Marymount California University
* [mailto:gmcharlt@gmail.com Galen Charlton], Equinox Open Library Initiative
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski], Equinox Open Library Initiative
* [mailto:andrea-schurr@utc.edu Andrea Schurr], University of Tennessee at Chattanooga
* [mailto:robin.m.fay@gmail.com Robin Fay], Independent Metadata Contractor
* [mailto:wendy.hagenmaier Wendy Hagenmaier], Georgia Tech

== 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).

[[2017 Website Working Group Documents|2017 Website Working Group Documents]]

* [mailto:JGomez@getty.edu Joshua Gomez] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:robin.m.fay@gmail.com Robin Fay] - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* [mailto:steven-shelton@utc.edu Steven Shelton] - Volunteer
* [mailto:shaune@princeton.edu Shaun Ellis] - Volunteer or Documentarian (will figure it out after initial call)
* [mailto:phette23@gmail.com Eric Phetteplace] - Volunteer
* [mailto:lukeaeschleman@gmail.com Luke Aeschleman] - Volunteer
* [mailto:sgritz@lmu.edu Stephanie Gritz] - Volunteer
* [mailto:jcoyne@justincoyne.com Justin Coyne] - Volunteer

== Budget and Sponsorship Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2017 Budget and Sponsorship Documents|2017 Budget and Sponsorship Documents]]

* [mailto:glt@library.ucla.edu Gary Thompson] - Primary Contact aka Chair
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] Twitter: @mjingle - Secondary Contact aka Co-Chair
* [mailto:jsabol@marymountcalifornia.edu Jeffrey Sabol] - Local Planning Contact (Southern California)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian
* [mailto:liblna@emory.edu Laura Akerman] - Volunteer
* [[User:Highermath|Cary Gordon]] - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2017 Keynote Documents|2017 Keynote Documents]]

* [mailto:norma.palomino@gmail.com Norma Palomino] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jgomez@getty.edu Joshua Gomez] - Local Planning Contact (Southern California)
* [mailto:brian-rogers@utc.edu Brian Rogers] - Local Planning Contact (Chattanooga)
* [mailto:selenachau@gmail.com Selena Chau] - Documentarian
* [mailto:msandford@colgate.edu Mark Sandford] - Volunteer

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2017 Pre-conference Documents|2017 Pre-conference Documents]]

* [mailto:kim.pham@utoronto.ca Kim Pham] (University of Toronto) - Primary Contact aka Chair
* [mailto:MCritchlow@ucsd.edu Matt Critchlow] (UC San Diego) - Local Planning Contact (Southern California)
* [mailto:andrea-schurr@utc.edu Andrea Schurr] (UT Chattanooga) - Local Planning Contact (Chattanooga)
* [mailto:akallaher@ncf.edu Amelia Kallaher] (New College of Florida) - Documentarian
* [mailto:cmharlow@gmail.com Christina Harlow] (Cornell) - Volunteer
* [mailto:elandav@mail.lib.msu.edu Elisa Landaverde] (Michigan State University) - Volunteer
* [mailto:makw@mail.lib.msu.edu Lucas Mak] (Michigan State University) - Volunteer
* [mailto:tod@uchicago.edu Tod Olson] (University of Chicago) - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2017 Program Documents|2017 Program Documents]]

* [mailto:whitni.watkins@gmail.com Whitni Watkins] - Primary Contact aka Chair (Analog Devices, Boston-ish) -- Twitter: @_whitni
* [mailto:acollier@calstate.edu Aaron Collier] - Local Planning Contact/Secondary Contact aka Co-Chair (Southern California) -- Twitter: @aaronisbrewing
* [mailto:wendy.hagenmaier@gmail.com Wendy Hagenmaier] - Local Planning Contact (Chattanooga)
* [mailto:katherly@upenn.edu Katherine Lynch] - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer
* [mailto:ranti.junus@gmail.com Ranti Junus] - Volunteer (Michigan State University)
* [mailto:akorphan@ncsu.edu Andreas Orphanides] - Volunteer
* [mailto:gpark@siue.edu Sarah Park] - Volunteer
* [mailto:gloria@zepheira.com Gloria Gonzalez] - Volunteer
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.

== Scholarship 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.

[[2017 Scholarship Documents|2017 Scholarship Documents]]

* [mailto:linda.ballinger@gmail.com Linda Ballinger] - Primary Contact aka Chair (PSU Libraries)
* [mailto:jsabol@marymountcalifornia.edu Jeffrey Sabol] - Secondary Contact aka Co-Chair/Local Planning Contact (Southern California)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Local Planning Contact (Chattanooga)
* [mailto:hsherid2@illinois.edu Helenmary Sheridan] - Documentarian (UIUC)
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer (IUPUI)
* [mailto:jronallo@gmail.com Jason Ronallo] - Volunteer (NCSU Libraries)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2017 T-Shirt Documents|2017 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Shira Peltzman - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Victoria (Tori) Maches - Documentarian
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> people to volunteer for the following duties:

[[2017 Onsite Volunteer Documents|2017 Onsite Volunteer Documents]]

* [mailto:ambittel@schoolofmusic.ucla.edu Aaron Bittel] - Primary Contact aka (Co-)Chair
* [mailto:mhughes@library.ucla.edu Maggie Hughes] - Secondary Contact aka Co-Chair
* Gary Thompson - Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* [mailto:syhwang@shsu.edu Soo-yeon Hwang] - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

[[2017 Social Activities Documents|2017 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2017 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [mailto:b.bohyun.kim.ois@gmail.com Bohyun Kim] - Secondary Contact aka Co-Chair
* Joshua Gomez - Local Planning Contact(Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2017 Streaming Video Documents|2017 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:highermath|Cary Gordon]]- Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* [mailto:jsabol@marymountcalifornia.edu Jeffrey Sabol] - Volunteer

== Code4Lib 2018 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2018 Host Voting Documents|2018 Host Voting Documents]]

* Galen Charlton - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Wifi and Electrical ==
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.

[[2017 Wifi and Electrical Documents|2017 Wifi and Electrical Documents]]

* [[User:highermath|Cary Gordon]] - Primary Contact/Local Planning Contact (Southern California)
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2017 Book Giveaway Documents|2017 Book Giveaway Documents]]

* Elizabeth Peele Mumpower - Primary Contact aka Chair
* Raymond Schwartz - Secondary Contact aka Co-Chair
* Joshua Gomez - Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2017 IRC and Slack Documents|2017 IRC and Slack Documents]]

* [mailto:mark.matienzo@gmail.com Mark A. Matienzo] - Primary Contact aka Chair
* [[User:highermath|Cary Gordon]] - Local Planning Contact/Secondary Contact aka Co-Chair (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).

[[2017 Accessibility Documents|2017 Accessibility Documents]]

* [mailto:katherly@upenn.edu Katherine Lynch] - Primary Contact aka Chair
* Your Name Here - Local Planning Contact (Southern California)
* [mailto:brian-rogers@utc.edu Brian Rogers] - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Kate Deibel - Volunteer
* Brett Bonfield - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2017 Whatever Documents|2017 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact (Southern California)
* Your Name Here - Local Planning Contact (Chattanooga)
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2017]]
[[Category:Conference Committees]]

2016 Conference Committees

2025-02-06T19:35:25Z

Phette23:

= 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 (LPC) to each committee.

== Location and Dates ==

* Location: Old City District of Philadelphia, PA
* Dates: March 7-10, 2016
** Pre-conferences -
** Main meeting -
** Post conference activities?

== Local Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* David Lacy (Villanova) - Primary Contact (v)
* Chad Nelson - Secondary Contact (v)
* Anna Headley (Chemical Heritage Foundation) - Documentarian (v)
* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* Katherine Lynch (U Penn) (v)
* Stephen Ng (Temple)
* Brett Bonfield (Collingswood Public)
* Lauren Gala (UPenn)
* David Uspal (Villanova) (v)
* Chris Clement (Drexel)

== 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).

[[Website Working Group Documents|Website Working Group Documents]]

* Shaun Ellis (Princeton) - Primary Contact
* [[User:LukeAeschleman| Luke Aeschleman]] (UNC - Chapel Hill | Health Sciences Library) - Secondary Contact
* [[User:jtidal|Junior Tidal]] (New York City College of Technology)
* [[User:BillMcMillin|Bill McMillin]] (Pratt Institute) - Documentarian
* [[User:Sdellis|Shaun Ellis]] (Princeton) - LPC Contact (v)
* [[User:Phette23|Eric Phetteplace]] (Cal College of the Arts)
* [[User:Sarahshealy| Sarah Shealy]] (Greenville (SC) County Public Library)
* [[User:JennC| Jennifer Colt]] (Cornell University Library)
* [[User:LaurenAjamie| Lauren Ajamie]] (University of Notre Dame Library)
* [[User:MichaelSchofield| Michael Schofield]] ( @schoeyfield )
* [[User:Wickr|Ryan Wick]]
* [[User:cbeer|Chris Beer]]
* [[User:Cdmo|Charlie Morris]] (Penn State)

== Sponsorship Committee ==
This group will focus on making sure all who want to support the conference have the opportunity to do so. Sponsorship Committee work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

The Sponsorship committee meets every other Tuesday at 2pm EST (11am PST) via [https://plus.google.com/hangouts/_/gwibrfqhzxe23uto4me3tktbnia Google hangout].

* [[User:Sdellis|Shaun Ellis]] (Princeton) (v)
* David Uspal (Villanova) - LPC Contact (v)
* Chad Nelson
* Morgan McKeehan
* Ray Schwartz
* Sharon Whitfield (Rowan University)
* Brett Bonfield (Collingswood Public) (v)
* Rachel Trent (George Washington University)

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

* Brett Bonfield (Collingswood Public)
* John Mignault (ESDN/METRO)
* Emily Morton-Owens
* [[User:Phette23|Eric Phetteplace]]
* Whitni Watkins (Analog Devices, Inc.)
* Beatrice Pulliam (Providence Public)

== Pre-conference Committee ==
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.
* Anna Headley - Chemical Heritage Foundation (Local Contact)
* [[User:ChristinaHarlow|Christina Harlow]] - convener
* Eric Lease Morgan - Librarian-At-Large
* Andrea Schurr - Univ. of TN at Chattanooga
* [[User:AndyWeidner|Andy Weidner]] - Univ. of Houston

[[Preconference2016Workspace]]

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.
* David Lacy - Villanova (Local Contact)
* Kevin Beswick - NCSU
* Peter Murray - Cherry HIll Company
* Chris Beer - Stanford University Libraries
* Matt Sherman - University of Bridgeport
* Whitni Watkins - Analog Devices, Inc.
* Ben Armintor - Columbia University
* Ranti Junus - Michigan State University
* Katherine Lynch - U Penn
* Tod Olson - University of Chicago

== Scholarship 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.
* Chad Nelson (Local Contact)
* [[User:jtidal|Junior Tidal]] (New York City College of Technology)
* Linda Ballinger (Penn State)
* Mairelys Lemus-Rojas (University of Miami Libraries)
* Spencer Lamm (Drexel University)
* Lauren Gala (U Penn)
* Bohyun Kim (U Maryland, Baltimore)
* [[User:dkerchner|Dan Kerchner]] (George Washington University)
* Jason Ronallo (NCSU Libraries)

== Childcare Committee ==
This group assess the need for childcare at the conference, organizes childcare options, determines cost, and liaises with parents and chilcare providers
* Chad Nelson (Local Contact)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.
* Lauren Gala (Local Contact)
* [[User:ChristinaHarlow|Christina Harlow]]
* Katherine Lynch (U Penn)

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> people to volunteer for the following duties:
** MC
** Registration
** Session Timers
** Etc.

* David Uspal (Villanova) - LPC Contact
* [[User:Khaley|Kathleen Haley]] (American Antiquarian Society) (Chair /Acting Documentarian)
* (Documentarian)

== Social Activities ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

Conference goers - The page you are looking for is at [[2016 Social Activities]]

* Becky Yoose (The Seattle Public Library; benevolent dictator for life)
* Chad Nelson (Temple University, Local Planning Committee contact)
* (Documentarian)
* [[User:LisaShiota|Lisa Shiota]]
* Katherine Lynch (U Penn)
* (Chair)
* Nabil Kashyap (Swarthmore College)

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

* [[User:StevenNg|Steven Ng]] (Local Contact)
* Ashley Blewer
* (Documentarian)
* [[User:DataGazetteer|Peter Murray]] (Chair)
*

== Code4Lib 2017 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

* Anna Headley (Local Contact)
* (Documentarian)
* (Chair)

== Wifi/Electrical ==
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference.

* (Local Contact)
* (Documentarian)
* (Chair)

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

* Katherine Lynch (Local Contact)
* (Chair)
* (Documentarian)

== IRC Committee ==
Coordinate with freenode to ensure that the #code4lib IRC channel can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

* (Local Contact)
* (Documentarian)
* Mx A. Matienzo (anarchivist on IRC, Slack, Twitter, etc.) (Chair)

== Accessibility Committee ==
A new committee for 2016 - document and address major points of the conference that are not accessible for conference attendees (physical and virtual).

* Katherine Lynch (Local Contact / Chair)
* (Documentarian)
* [[User:Coral|Coral Sheldon-Hess]] ([https://twitter.com/web_librarian @web_librarian] or coral on IRC/Slack)

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

* Alison Hitchens ([https://twitter.com/ahitchens @ahitchens])
* ...
* ...

== Additional Committees... Coming Soon! ==
* Reception?

[[Category:Code4Lib2016]]
[[Category:Conference Committees]]

Category:Conference Committees

2025-02-06T19:34:13Z

Phette23: Created page with "Lists each year's committees."

Lists each year's committees.

Code4Lib 2023 Conference Committees

2025-02-06T19:33:50Z

Phette23: add category

= Code4Lib 2023 Conference Committees =

Hosting a conference is 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 2023 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 (LPC) to each committee.

== Location and Dates ==

* Location: Princeton University
* Pre-conferences: March 14, 2023 (Rabinowitz Building)
* Main conference: March 15-17, 2023 (Frist Campus Center)

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact
* Hillel Arnold - (harnold@rockarch.org) - Volunteer
* Chulin Meng - (chm213@lehigh.edu) - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* Yinlin Chen - (ylchen@vt.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* John DeLooper - (john.delooper@lehman.cuny.edu) - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* Jenn Cummings & Kathy Azevedo - (code4lib@concentra-cms.com) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[https://drive.google.com/drive/u/1/folders/1BvNAQ0J_a9COYrrkLrofsz6qBkf_3JeH Keynote Documents] -- this is a Google Drive folder which has templates for all the communications you need to send, READMEs, an overview of our timeline, etc. It should cover what you need to run the process; just add committee members and stir. It's access-restricted; you can get sharing permissions from Andromeda Yelton (2023 keynote documentarian) or Jenn Cummings or Kathy Azevedo at Concentra.

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* [[User:Khaley|Kathleen Haley]] - Primary Contact, Chair
* Kathryn Michaelis - (kmicha3@emory.edu) - Secondary Contact, CoChair
* [[User:Thatandromeda|Andromeda Yelton]] - Documentarian
* Ranti Junus - Volunteer
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey
* Tod Olson <tod@uchicago.edu> - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* Andrew Battelini - (abattel@emory.edu)- Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Emily Boss (eboss-at-unr-edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Scholarship 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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* Yongming Wang - (wangyo@tcnj.edu) - Primary Contact, Chair
* - Secondary Contact, CoChair
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian
* Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2022_national_conference_annual_report.md.

'''Currently seeking one or two coordinators.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Anne Slaughter on Slack or via email (anne dot slaughter at railslibraries dot info).

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* Kate Lynch - (katelynch@princeton.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Margaret Heller - (mheller1@luc.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Hardy Pottinger - hardy.pottinger@ucop.edu - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Kate Lynch - (katelynch@princeton.edu) - LPC Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* Caitlin Bakker - (caitlin.bakker@uregina.ca) - Secondary Contact, CoChair
* Ed Hill - (edhill@duck.com) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]
[[Category:Conference Committees]]

Code4Lib 2022 Conference Committees

2025-02-06T19:33:40Z

Phette23: add category

= Code4Lib 2022 Conference Committees =

Hosting a conference is 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 2022 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 (LPC) to each committee.

== Location and Dates ==

* Your Name Here -conferences:

== Planning Committee ==
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Francis Kayiwa - (kayiwa at princeton dot edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* [[User:derekz| Derek Zoladz]] - (derekz@ohionet.org) - Primary Contact AKA Chair
* [[User:Phette23|Eric Phetteplace]] - (phette23@gmail.com) - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Jenn Colt - (jrc88@cornell.edu) - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Jerry Yarnetsky (Miami University of Ohio) - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Dave Erlandson - (de12@rice.edu) - Documentarian
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer
* Jenn Bielewski - (jennifer.bielewski@lyrasis.org) - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Margaret Heller - (mheller1 at luc dot edu) - Primary Contact AKA Chair
* Chad Nelson (chadbnelson at gmail dot com) - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa at princeton dot edu) - Planning Committee Contact
* Ken Irwin (irwinkr at miamioh.edu) - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Anne Slaughter (anne dot slaughter at railslibraries dot info) - Volunteer

== Pre-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Tod Olson - (tod at uchicago dot edu) - Primary Contact AKA Chair
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Documentarian
* Megan Kudzia - (kudzia at msu dot edu ) - Volunteer
* Sharon Clapp - (sclapp@ccsu.edu) Volunteer
* Your Name Here - Volunteer

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2022 Program Documents|2022 Program Documents]]

* Daricus Larry - (dlarry@arizona.edu) - Primary Contact AKA Chair
* Matt Sherman - (matt.r.sherman@gmail.com) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Heather Greer Klein - (heather@samvera.org) - Documentarian
* Dre - (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu - (jingjing.wu@ttu.edu) - Volunteer
* Jessica McMillen - (jessica.mcmillen@mail.wvu.edu) - Volunteer
* Emily Boss - (eboss@unr.edu) - Volunteer
* Jenn Bielewski - (Jennifer.Bielewski@lyrasis.org) - Volunteer

== Scholarship 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Jessica Benner - (jbenner@andrew.cmu.edu) - Primary Contact AKA Chair
* Yongming Wang - (wangyo@tcnj.edu) - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Andy Hickner - previous scholarship recipient, volunteer
* Tiffany Henry - previous scholarship recipient, volunteer
* Esther Jackson - previous scholarship recipient, volunteer
* Claire Payne - previous scholarship recipient, volunteer
* Ashley Evans Bandy - previous scholarship recipient, volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator: Anne Slaughter - (anne.m.slaughter@gmail.com)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Molly Maloney - (mkm9@buffalo.edu) - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Omar Brown - (omarbrow@buffalo.edu) - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2022 Conference Volunteers]]'''

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

2022 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:ThomasGuignard|Thomas Guignard]] (tom@timtom.ca) - Volunteer
* Molly Maloney - (mkm9@buffalo.edu) - Volunteer

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* [[User:highermath|Cary Gordon]] - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Code4Lib 2023 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Kate Deibel (katherine.deibel@gmail.com) - Primary Contact aka Chair
* Ashlea Green - (greenam7@appstate.edu) - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer
* Christine McClure (camcclure@gmail.com) - Volunteer
* Kelly Stathis (kelly.stathis@engagedri.ca) - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Rebekah Burke - Volunteer
* [[User:ThomasGuignard|Thomas Guignard]] (tom@timtom.ca) - Volunteer

[[Category:Code4Lib2022]]
[[Category:Conference Committees]]

Category:Conference Hosting Proposals

2025-02-06T19:32:09Z

Phette23:

All of the conference hosting proposals from prior years. Please add this category to future years' hosting proposals. If a year does not appear here, it's possible the proposals were not listed on the wiki or there was no formal proposal process that year.

== Other Proposals ==

For some reason, these years are not appearing below even though they are in this category.

* [[2019 Hosting Proposals]]
* [[2020 Hosting Proposals]]
* [[2024 Hosting Proposals]]

2025 Hosting Proposals

2025-01-30T17:59:14Z

Phette23: /* Previous Hosting Proposals */ fix links, use archive

==Code4Lib 2025 Hosting Information==

T/B/D

==Code4Lib 2025 Hosting Guidelines==
===Schedule (tentative)===
* Proposal period opens: 5/17/2024
* Proposal period ends: 6/14/2024
* Voting opens: TBD
* Voting closes: TBD

===2025 Host Voting Committee===
* Esmé Cowles
*
* '''Your name here!'''

==2025 Hosting Proposals==
'''Please list your proposal below.'''
*

==Previous Hosting Proposals==
* [[2024 Hosting Proposals]]
* [[2020 Hosting Proposals]]
* [[2019 Hosting Proposals]]
* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [https://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://web.archive.org/web/20210128100039/docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [https://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://web.archive.org/web/20220623095927/sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

==Code4Lib 2025 Location Proposals Proposed Template==

===Welcome to ...!===

Place details such as notable landmarks, activities, transit information.

===The Conference===

Venue needs: first half of 2025 conference that can accommodate roughly 200-300 attendees and meet Code4Lib's technical requirements.

===The Cost===

Approximate costs to attendees such as venue, lodging, and travel.

===Sponsoring Organizations===

CLIR/DLF will be the fiscal host regardless of location but we welcome institutional support for the conference.

===Organizational Committee===

Who are you!

[[Category:Code4Lib2025]]
[[Category:Conference Hosting Proposals]]

2026 Hosting Proposals

2025-01-30T17:58:26Z

Phette23:

==Code4Lib 2026 Hosting Information==

T/B/D

==Code4Lib 2026 Hosting Guidelines==
===Schedule (tentative)===
* Proposal period opens: TBD
* Proposal period ends: TBD
* Voting opens: TBD
* Voting closes: TBD

===2026 Host Voting Committee===
* '''Your name here!'''
* '''Your name here!'''
* '''Your name here!'''

==2026 Hosting Proposals==
'''Please list your proposal below.'''
*

==Previous Hosting Proposals==
* [[2025 Hosting Proposals]]
* [[2024 Hosting Proposals]]
* [[2020 Hosting Proposals]]
* [[2019 Hosting Proposals]]
* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

==Code4Lib 2026 Location Proposals Proposed Template==

===Welcome to ...!===

Place details such as notable landmarks, activities, transit information.

===The Conference===

Venue needs: first half of 2026 conference that can accommodate roughly 200-300 attendees and meet Code4Lib's technical requirements.

===The Cost===

Approximate costs to attendees such as venue, lodging, and travel.

===Sponsoring Organizations===

CLIR/DLF will be the fiscal host regardless of location but we welcome institutional support for the conference.

===Organizational Committee===

Who are you!

[[Category:Code4Lib2026]]
[[Category:Conference Hosting Proposals]]

2025 Hosting Proposals

2025-01-30T17:52:48Z

Phette23:

==Code4Lib 2025 Hosting Information==

T/B/D

==Code4Lib 2025 Hosting Guidelines==
===Schedule (tentative)===
* Proposal period opens: 5/17/2024
* Proposal period ends: 6/14/2024
* Voting opens: TBD
* Voting closes: TBD

===2025 Host Voting Committee===
* Esmé Cowles
*
* '''Your name here!'''

==2025 Hosting Proposals==
'''Please list your proposal below.'''
*

==Previous Hosting Proposals==
* [[2024 Hosting Proposals]]
* [[2020 Hosting Proposals]]
* [[2019 Hosting Proposals]]
* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

==Code4Lib 2025 Location Proposals Proposed Template==

===Welcome to ...!===

Place details such as notable landmarks, activities, transit information.

===The Conference===

Venue needs: first half of 2025 conference that can accommodate roughly 200-300 attendees and meet Code4Lib's technical requirements.

===The Cost===

Approximate costs to attendees such as venue, lodging, and travel.

===Sponsoring Organizations===

CLIR/DLF will be the fiscal host regardless of location but we welcome institutional support for the conference.

===Organizational Committee===

Who are you!

[[Category:Code4Lib2025]]
[[Category:Conference Hosting Proposals]]

2024 Hosting Proposals

2025-01-30T17:52:41Z

Phette23:

==Code4Lib 2024 Hosting Information==

Voting is closed.

==Code4Lib 2024 Hosting Guidelines==
===Schedule (tentative)===
* Proposal period opens: 3/27/2023
* Proposal period ends: 5/12/2023
* Voting opens: 5/15/2023
* Voting closes: 5/22/2023

===2024 Host Voting Committee===
* Esmé Cowles
*
* '''Your name here!'''

==2024 Hosting Proposals==
'''Please list your proposal below.'''
* [https://umich-code4lib-proposal.netlify.app/ University of Michigan, Ann Arbor, MI]
* [https://umnlibraries.github.io/c4l-2024 University of Minnesota, Minneapolis, MN]
* [https://u.mcmaster.ca/code4lib-hamilton2024 McMaster University, Hamilton, ON]

==Previous Hosting Proposals==
* [[2020 Hosting Proposals]]
* [[2019 Hosting Proposals]]
* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

==Code4Lib 2024 Location Proposals Proposed Template==

===Welcome to ...!===

Place details such as notable landmarks, activities, transit information.

===The Conference===

Venue needs: first half of 2024 conference that can accommodate roughly 200-300 attendees and meet Code4Lib's technical requirements.

===The Cost===

Approximate costs to attendees such as venue, lodging, and travel.

===Sponsoring Organizations===

CLIR/DLF will be the fiscal host regardless of location but we welcome institutional support for the conference.

===Organizational Committee===

Who are you!

[[Category:Code4Lib2024]]
[[Category:Conference Hosting Proposals]]

2020 Hosting Proposals

2025-01-30T17:52:26Z

Phette23:

==Code4Lib 2019 Breakout Session==

The 2020 Host Voting Committee, along with members of the 2019 Local Planning Committee, will host an informational breakout session on host proposals during the 2019 conference in San José. Attendance isn't required for those submitting host proposals but we can help work on your proposal, provide feedback, and answer questions about the process and our experience from this year.

==Code4Lib 2020 Hosting Guidelines==

'''Schedule (First round)'''

* Proposal period opens: February 18th

* Proposal period ends: March 15th

* Voting opens: March 18th

* Voting closes: March 25th

'''2020 Host Voting Committee'''

* [[User:Phette23|Eric Phetteplace]]
* Roy Tennant
* Lilly Ho
* '''Your name here!''' We're still accepting volunteers. No prior experience necessary.

See previous host proposals for examples:

* [[2019 Hosting Proposals]]
* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

'''Please list your proposal below.'''

* [https://dulibrarytech.github.io/c4l2020denver/ Denver, CO]
* [https://code4lib2020.library.cmu.edu/ Pittsburgh, PA]

==Code4Lib 2020 Location Proposals Proposed Template==

===Welcome to ...!===

Place details such as notable landmarks, activities, transit information.

===The Conference===

Venue needs: first half of 2020 conference that can accommodate roughly 400(~450) attendees and meet Code4Lib's technical requirements.

===The Cost===

Approximate costs to attendees such as venue, lodging, and travel.

===Sponsoring Organizations===

CLIR/DLF will be the fiscal host regardless of location but we welcome institutional support for the conference.

===Organizational Committee===

Who are you!

[[Category:Code4Lib2020]]
[[Category:Conference Hosting Proposals]]

2019 Hosting Proposals

2025-01-30T17:52:15Z

Phette23:

'''Schedule (First round)'''

* Proposal period opens: November 14th, 2017

* Proposal period ends: March 12th, 2018

* Voting opens: TBD

* Voting closes: TBD

'''2019 Host Voting Committee'''

* Peggy Griesinger, George Mason University
* Craig Boman, Discovery Services Librarian, Miami University
* Benjamin Florin

'''Please list your proposal below.'''

* [https://phette23.github.io/c4l19-norcal-proposal/ San Francisco Bay Area 2019 Hosting Proposal]

See previous host proposals for examples:

* [[2018 Hosting Proposals]]
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]

==Code4Lib 2019 Location Proposals==

===Welcome to ...!===

===The Conference===

Venue needs: February/March 2019 conference that can accommodate roughly 400(~450) attendees and meet Code4Lib's technical requirements.

===The Cost===

===Fiscal Sponsor===

===Organizational Committee===

[[Category:Code4Lib2019]]
[[Category:Conference Hosting Proposals]]

2018 Hosting Proposals

2025-01-30T17:51:45Z

Phette23:

'''Schedule (second round)'''

* Proposal period opens: February 28th, 2017

* Proposal period ends: March 17th 2017

* Voting opens: March 20th, 2017

* Voting closes: March 31st, 2017

'''Please list your proposal below.'''

==Washington DC 2018 Code4Lib Proposal==

http://freestock.ca/acrylic_waves_of_washington_dc_sjpg4982.jpg

[Image by Nicolas Ramyond, 'Acrylic Waves of Washington DC'; Creative Commons License Attribution 3.0 Unported]

===Welcome to Washington D.C!===

Most people know the District of Columbia as the home of our nation's capital, but we're also proud of being the capital of FREE. Explore museums and galleries like the newly opened National Museum of African American History and Culture, see a performance at our National Kennedy Center, or connect with nature at our Botanical Garden, Arboretum, or National Zoo. Our food scene is also making waves. We were rated '2016 restaurant city of the year,' and in 2017, we joined New York, San Francisco and Chicago with a Michelin Guidebook. Voted the #1 transit-friendliest city and #2 most walkable city in the United States, D.C. makes getting around between all of these amenities painless and safe. Furthermore, with three airports (DCA, IAD, BWI) and Amtrak, D.C. is a destination that is easy and relatively inexpensive to get to. It's a great time to come to Washington D.C.!

===The Conference===

We're currently investigating venues for a February 2018 conference that can accommodate roughly 400(~450) attendees and meet Code4Lib's technical requirements.

Pre-conference workshops would take place in several of our metro-accessible DC Public Library neighborhood branches, and we're looking at throwing the opening reception at the Library of Congress.

===The Cost===

DC is a bit pricey, so we're investigating a range of alternative housing options to hotels. AirBnBs average around $80 per night in February, and there are several hostels near Capitol Hill including Washington DC House and Capital View Hostel.

===Fiscal Sponsor===
This proposal has been made possible by the generous cooperation of DLF and CLIR, who have agreed to be our fiscal host for the 2018 Code4Lib Conference in D.C. Thank you Bethany and the CLIR/DLF team <3

===Organizational Committee===

* Jaime Mears - Library of Congress (Chair)
* Bohyun Kim - University of Maryland, Baltimore, Health Sciences and Human Services Library
* Nick Kerelchuck - DC Public Libraries
* Joel Richard - Smithsonian Libraries
* Ben Wallberg- University of Maryland Libraries
* Kate Dohe - University of Maryland Libraries

[[Category:Code4Lib2018]]
[[Category:Conference Hosting Proposals]]

2017 Host Proposals

2025-01-30T17:51:27Z

Phette23:

== Links to Second Round Proposals go Here ==
* YOUR PROPOSAL LINK HERE

==Links to Proposals Go Here==
This round of submissions is now closed
* [http://lab.lib.utc.edu/c4l-cha Chattanooga]

==Schedule==

Proposal period opens: January 19th 2016

Proposal period ends: March 1st 2016

Voting opens: March 3rd, 2016

Voting closes: March 15th, 2016

==Text of CFP==
Host Code4Lib 2017 in your city!

The deadline for proposals is midnight PT Tuesday 1 March 2016.

To apply please email the Code4Lib Conference Planning list [0] and link to your proposal on the 2017 Host Proposals wiki page [1]

The decision will be made by popular vote. Voting will begin on or around Thursday March 3rd, 2016 and will continue until midnight PT March 15th, 2016. The results of the vote will be announced Friday March 16th via listserv.

Prior to submitting a proposal we recommend reviewing the conference hosting web page [2] and How To Plan a Code4LibCon on the wiki [3] to learn more about the kind of venue the community seeks and the responsibilities involved with hosting the conference.

Here's a sample of past successful proposals:

2016: http://c4l-phl.github.io/

2015: http://osulp.github.io/code4lib-pdx/

2014: https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit

2013: http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html

2012: https://sites.google.com/site/code4lib2012seattle/

Thank you and good luck!!

Anna Headley

On behalf of the 2016 Planning Committee

[0] code4libcon@googlegroups.com

[1] http://wiki.code4lib.org/2017_Host_Proposals

[2] http://code4lib.org/conference/hosting

[3] http://wiki.code4lib.org/index.php/How_To_Plan_A_Code4LibCon

[[Category:Code4Lib2017]]
[[Category:Conference Hosting Proposals]]

2016 Hosting Proposals

2025-01-30T17:50:57Z

Phette23: add category

'''Schedule'''

Proposal period opens: January 9th 2015

Proposal period ends: February 20th 2015

Voting opens: February 23rd, 2015

Voting closes: March 6th, 2015

Please list your proposal below:

'''Los Angeles''' ([https://docs.google.com/document/d/1-VWVwN0-0LFXhWW1kfQxmCkkjQoK7oor5RZhMwP3zuc/edit?usp=sharing proposal document])

Organizing Committee:
* Joshua Gomez, Getty Research Institute
* Cary Gordon, Cherry Hill Company
* Christina Salazar, CSU-Channel Islands
* Gary Thompson, UCLA

''' Philadelphia ''' ([http://c4l-phl.github.io/ Proposal Website])

Proposal Committee
* Shaun Ellis - Princeton University
* Anna Headley - Chemical Heritage Foundation
* David Lacy - Villanova University
* Katherine Lynch - Temple University
* Chad Nelson - Lyrasis
* David Uspal - Villanova University

[[Category:Code4Lib2016]]
[[Category:Conference Hosting Proposals]]

Category:Conference Hosting Proposals

2025-01-30T17:50:43Z

Phette23: add description

2015 Hosting Proposals

2025-01-30T17:49:02Z

Phette23: add category

==Schedule==
Proposal period opens: Wednesday January 29th, 2014

Proposal period closes: Wednesday March 12th, 2014 - '''Extention to Tuesday, March 18th, 2014'''

Voting opens: '''Tentative Wednesday March 19th, 2014'''

Voting closes: Wednesday March 26th, 2014

Please list your proposal below;

==[http://osulp.github.io/code4lib-pdx/ Portland, OR]==
Oregon State University hosted the first Code4Lib conference in Corvallis, Oregon in 2005. In the spirit of celebrating the conference's 10th year, OSU wants to bring Code4Lib back to Oregon! See http://osulp.github.io/code4lib-pdx/ for details.

[[Category:Code4Lib2015]]
[[Category:Conference Hosting Proposals]]

How To Plan A Code4LibCon

2025-01-16T16:58:26Z

Phette23: We use CONCENTRA every year now

== General Process ==
* Apply to be a host; see also the page on [http://code4lib.org/conference/hosting Conference Hosting] at [http://code4lib.org code4lib.org]
** '''Identify venues''' for both the conference and the hotel (if different). Get some cost estimates from each. Make sure the hotel will give you a room block.
*** 2006/Corvallis: the campus provided the conference space at a low cost, and this made running the conference much more affordable.
*** 2016/Portland: we held everything in a single hotel and we had to acquire 2x the amount of sponsorship than what appears to be normal.
** '''Prepare a sample / generalized budget'''
*** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.
*** Get data from previous years to estimate minimums and maximums, and fill in as much as you can ahead of time.
*** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.
*** Also, when you get cost estimates, don't forget to include food costs.
*** Wireless: If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs.
** '''Use our conference planner (CONCENTRA)'''
*** Since 2014 in NC, Code4lib has contracted with [https://www.concentra-cms.com CONCENTRA] to help manage and plan the conference. Their expertise is invaluable. You can ask questions while preparing your proposal. CONCENTRA knows Code4Lib and our unique structure and well as how to plan various aspects of conferences (hotel block, catering, bus to reception, etc.). Look for Jennifer Cummings in Slack or use their site's contact link.
*** See if your institution has a conference planning services group or something similar - if it does, they can also be very helpful. They'll handle registration, budgeting, contracts, etc, and really make life easy.
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]
* Invite the community to join committees
* Have a timeline
*[[Useful information from 2012]]

== Important Public Resources ==
* Past calls for host sites: [http://code4lib.org/node/275 2010] -
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]
* Sponsorship info (public)
* [http://code4lib.org/logo/ Logos]
* [http://code4lib.org/content/template-code4lib-20xx Template for the conference page on the main Code4Lib website] - This page is only visible to those who have a code4lib.org account. Once a host has been selected, please copy the template to a new page for that conference year.
* [[Code4Lib Conference Lessons Learned]]

== Important Private Resources ==
* Code4LibCon-hostsite listserv
* Budgets from previous years
* Sponsorship info (private)

== Committee List ==
* Local Planning Committee
* Accessibility Committee
* [[BookGiveawayCommittee|Book Giveaway Committee]]
* Childcare
* Documentation
* Keynote
* Onsite Volunteer
* Pre-conference
* [[ProgramCommittee|Program Committee]]
* [[ScholarshipCommittee|Gender Diversity & Minority Scholarship Committee]]
* Slack/IRC
* Social Activities
* [[SponsorshipCommittee|Sponsorship Committee]]
* Streaming Video
* [[T-ShirtCommittee|T-Shirt Committee]]
* [[Voting|Voting]]
* Whatever
* Wifi/Electrical
* Duty Officers

== Planning ==

=== Budgeting ===
* [[Conference_Financial_History_At_A_Glance]]
* private conlist has budget info

=== Hotels ===
* You will likely have to convince the conference hotel of the conference size and past room uptake as part of negotiating your contract. They may want to contact past conference hotels to get more info about actual uptake.
* 2014 -- Raleigh Downtown Sheraton
* IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.
* Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.
* prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012

TODO: get actual room uptake numbers into a chart here. (NB totals are only useful in the context of how many attendees there were.)

=== Wireless ===
* make sure VPN is allowed

TODO: put actual concurrent connections and bandwidth usage data numbers in a chart here. Note when problems were occurring to give context on whether these numbers were sufficient of insufficient.

Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].

=== Policies ===
A record of [[Conference_Policies]] of all kinds!

== Shortly before the Conference ==

=== Keynotes ===
# Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc

=== Email Boilerplates / templates ===
* [[ConferenceOrientationEmail|Quick orientation email for newer folks]] - Send out at least a week in advance before conference...
* [[FreenodeIrcConnection|Freenode IRC connection]]
** Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.
** Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are "private" IP ranges used for connection sharing.)
** Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:
** I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)
** Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.

== At the Conference ==

===Keynotes===
# Speaker gifts
# Dinner plans

=== Timers ===
* Sit in the front of the room
* Have several people
* You may want to use an extra machine
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/

=== Lightning Talks ===
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )

===PreConf===
# make sure projector avail for each session
# whiteboards or reasonable facsimile thereof
# everyone wants a power outlet

=== Conference ===
# power - everyone would like to plug in their laptop (and possibly their phone)
# IRC Monitor for podium during speaker changes?

===Photography===

* Consider different colored lanyards to articulate personal photography preferences.
** Portland/2015 had color-coded lanyards:
*** Green = it's ok to take my picture
*** Yellow = please ask before taking my picture
*** Red = don't take my picture

=== Podium ===
# Water at the podium
# Provide height adjustable podium, if available. Otherwise:
# Provide an apple box for presenters who would like to use one.

=== Video ===
# Videos are streamed at https://youtube.com/code4lib
# Presenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.
# Presenters must not use unlicensed music in their presentation. Likewise, unlicensed music must not be used between presentations.
# Video must be able to work with the house A/V crew and set up the day before the main con begins.
# Lighting must be provided for the speakers.

=== Live Blogging ===
Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.

=== Ask Anything===
* Add to volunteer page to have a moderator or do a general call out
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )

===Book Raffle===
See details here: https://wiki.code4lib.org/BookRaffle

* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table

=== Flipcharts ===
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/

=== Hospitality Suite ===
# having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening
# making sure the mess left for cleaning staff is an appropriate mess
# making sure the noise made near other hotel guests is an appropriate noise
# having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite

== Suggested Timeline ==
* See [[C4L2010planning]] for an example
* See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit Code4Lib 2014 planning schedule] planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.
* Ideal to have program set before registration, including pre-conf
** also allows clarity for how many spots are avail for non-presenters

===Calls for Hosting===
No one has claimed responsibility for putting out the call and setting the deadline. Consider having this task as the host committee, the voting committee, or perhaps the whatever committee.

{| class="wikitable"
! Year of proposal
! Text of call
! Call issued
! Deadline for submission
! Weeks to submit
! Voting start
! Voting end
! Weeks to vote
! Announcement
|-
|2010
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]
|5 Feb
|5 Mar
|4 weeks
|
|
|
|
|-
|2011
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]
|10 Dec, 2010
|23 Jan (Sun)
|6 weeks + 3 days
|25 Jan (Tue)
|9 Feb (3rd day of conf)
|2 weeks + 2 days
|10 Feb (last day of conf)
|-
|2012
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]
|1 Dec, 2011
|22 Jan (Sun)
|7 weeks + 4 days
|25 Jan (Wed)
|8 Feb (3rd day of conf)
|2 weeks + 1 day
|9 Feb (last day of conf)
|-
|2013
|
|
|
|
|
|
|
|15 April?
|-
|2014
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]
|29 Jan
|12 Mar (Wed)
|6 weeks + 1 day
|14 Mar (Fri)
|26 Mar
|1 week + 6 days
|27 Mar (Thursday; last day of conf)
|-
|2015
|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]
|8 Jan
|20 Feb (Fri)
|6 weeks + 2 days
|23 Feb (Mon)
|6 Mar
|1 week + 5 days
|9 Mar (Mon)
|-
|2016
|
|19 Jan (Tue)
|1 Mar (Tue)
|6 weeks
|3 Mar (Thu)
|15 Mar (Tue)
|1 week + 5 days (note conf is Mar 7-10)
|16 Mar (Fri)
|}

== Some Suggested Readings ==
[https://medium.com/@louisrosenfeld/how-to-organize-a-conference-567fb50ccdbd How To Organize a Conference] - Some excellent thoughts on conferences in general.

[[Category: Code4Lib2010]]
[[Category: Code4Lib2011]]
[[Category: Code4Lib2012]]
[[Category: Code4Lib2013]]
[[Category: Code4LibCon Planning]]

User:Phette23

2025-01-16T16:47:31Z

Phette23:

Systems Librarian at [http://libraries.cca.edu California College of the Arts]. Code4Lib 2019 Bay Area local planning co-chair. Recurring member of the conference website committee and community support squad. I love the command line, python, node, and Android: Netrunner.

'''Sites''': [http://phette.net phette.net] |[https://digipres.club/@phette23 @phette23@digipres.club] | [https://github.com/phette23 GitHub]

Conference Financial History At A Glance

2025-01-16T16:31:43Z

Phette23: add in 2025 year registration cost

{| class="wikitable"
! style="text-align:left;"| Year
! Registration cost
! Hotel rate
! People
|-
|style="width: 30%; background-color: #f5fffa;"| 2025 Princeton, NJ
|250 + 40/postcon
|???
|TBD
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2024 Ann Arbor, MI
|225 (290 late deadline) + 40/postcon
|$167-$239/night (multiple)
|≈250 (???)
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2023 Princeton, NJ
|200 (260 late deadline) + 40/precon
|???
|192
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2022 Buffalo, NY
|195 (250 late deadline) + 40/precon
|108-179/night (+tax)
|150
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2021 Online
|49 (59 late deadline) + 19/postcon
|n/a
|620
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2020 Pittsburgh, PA
|375 (450 late deadline) + 50 precon
|159/night (+tax)
|289 [1]
|-
|style="width: 30%; background-color: #f5fffa;"| 2019 San Jose, CA
|395 (450 late deadline) + 50 precon
|200/night (+tax)
|348
|-
|style="width: 30%; background-color: #f5fffa;"| 2018 Washington, DC
|350 + 60 precon
|182/night (+tax)
|476
|-
|style="width: 30%; background-color: #f5fffa;"| 2017 Los Angeles, CA
|275 + 60 precon
|175/night (+tax) to 229/night (no tax)
|430
|-
|style="width: 30%; background-color: #f5fffa;"| 2016 Philadelphia, PA
|200 + 15/30 precon
|169/night (+tax)
|440
|-
|style="width: 30%; background-color: #f5fffa;"| 2015 Portland, OR
|175 + 15/30 precon
|139/night (+tax)
|450
|-
|style="width: 30%; background-color: #f5fffa;"| 2014 Raleigh, NC
|165 + 10 preconf
|159/night
|350
|-
| style="width: 30%; background-color: #f5fffa;"| 2013 Chicago, IL
| 160
| 115/night
| 400
|-
|style="width: 30%; background-color: #f5fffa;"| 2012 Seattle, WA
| 150
| 159/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2011 Bloomington, IN
| 130 + 30 preconf
| 99-129/night
| 250
|-
|style="width: 30%; background-color: #f5fffa;"| 2010 Asheville, NC
| 120 + 25 preconf
| 119/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2009 Providence, RI
| 125
| 135/night
| 220
|-
|style="width: 30%; background-color: #f5fffa;"| 2008 Portland, OR
| 125
| 150/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2007 Athens, GA
| 100
|
| 140
|-
|style="width: 30%; background-color: #f5fffa;"| 2006 Corvallis, OR
| 125
| 84/night (+tax)
|
|}

1. Attendance was affected by the [https://en.wikipedia.org/wiki/2019%E2%80%9320_coronavirus_pandemic 2019-20 coronavirus pandemic].

[[Category:Code4LibCon_Planning]]

Conference Financial History At A Glance

2024-05-14T21:17:46Z

Phette23: add 2024 con

{| class="wikitable"
! style="text-align:left;"| Year
! Registration cost
! Hotel rate
! People
|-
|style="width: 30%; background-color: #f5fffa;"| 2024 Ann Arbor, MI
|225 (290 late deadline) + 40/postcon
|$167-$239/night (multiple)
|≈250 (???)
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2023 Princeton, NJ
|200 (260 late deadline) + 40/precon
|???
|192
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2022 Buffalo, NY
|195 (250 late deadline) + 40/precon
|108-179/night (+tax)
|150
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2021 Online
|49 (59 late deadline) + 19/postcon
|n/a
|620
|-
|-
|style="width: 30%; background-color: #f5fffa;"| 2020 Pittsburgh, PA
|375 (450 late deadline) + 50 precon
|159/night (+tax)
|289 [1]
|-
|style="width: 30%; background-color: #f5fffa;"| 2019 San Jose, CA
|395 (450 late deadline) + 50 precon
|200/night (+tax)
|348
|-
|style="width: 30%; background-color: #f5fffa;"| 2018 Washington, DC
|350 + 60 precon
|182/night (+tax)
|476
|-
|style="width: 30%; background-color: #f5fffa;"| 2017 Los Angeles, CA
|275 + 60 precon
|175/night (+tax) to 229/night (no tax)
|430
|-
|style="width: 30%; background-color: #f5fffa;"| 2016 Philadelphia, PA
|200 + 15/30 precon
|169/night (+tax)
|440
|-
|style="width: 30%; background-color: #f5fffa;"| 2015 Portland, OR
|175 + 15/30 precon
|139/night (+tax)
|450
|-
|style="width: 30%; background-color: #f5fffa;"| 2014 Raleigh, NC
|165 + 10 preconf
|159/night
|350
|-
| style="width: 30%; background-color: #f5fffa;"| 2013 Chicago, IL
| 160
| 115/night
| 400
|-
|style="width: 30%; background-color: #f5fffa;"| 2012 Seattle, WA
| 150
| 159/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2011 Bloomington, IN
| 130 + 30 preconf
| 99-129/night
| 250
|-
|style="width: 30%; background-color: #f5fffa;"| 2010 Asheville, NC
| 120 + 25 preconf
| 119/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2009 Providence, RI
| 125
| 135/night
| 220
|-
|style="width: 30%; background-color: #f5fffa;"| 2008 Portland, OR
| 125
| 150/night
|
|-
|style="width: 30%; background-color: #f5fffa;"| 2007 Athens, GA
| 100
|
| 140
|-
|style="width: 30%; background-color: #f5fffa;"| 2006 Corvallis, OR
| 125
| 84/night (+tax)
|
|}

1. Attendance was affected by the [https://en.wikipedia.org/wiki/2019%E2%80%9320_coronavirus_pandemic 2019-20 coronavirus pandemic].

[[Category:Code4LibCon_Planning]]

2024 Conference Volunteers

2024-04-30T21:18:26Z

Phette23: /* Mic-minders */ rm myself, conflict with CSV schedules

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* Heidi Burkhardt
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: Michelle Navarro
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: Michelle Navarro
* PM volunteer: Michelle Navarro

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: Cary Gordon
* PM Volunteer: Barbara Cormack

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-04-17T17:49:51Z

Phette23: /* Mic-minders */ take another shift

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* ''Your Name Here''
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-04-17T17:47:04Z

Phette23: /* Mic-minders */ ad me to Tuesday PM

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* ''Your Name Here''
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-03-19T18:39:02Z

Phette23: /* The Whatever Crew */ link to me

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* ''Your Name Here''
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-03-19T18:38:32Z

Phette23: /* The Whatever Crew */ add me

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* ''Your Name Here''
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* Eric Phetteplace — I will be able to volunteer for specific tasks once I know my Community Support schedule
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

Category:Code4Lib2024

2023-09-29T22:04:44Z

Phette23:

{{Conference
|URL=https://2024.code4lib.org
|Start Date=May 13, 2024
|End Date=May 16, 2024
|Location=University of Michigan, Michigan League Ballroom
|Contact= Natasha Allen
}}

* [[Code4Lib_2024_Conference_Committees | 2024 Conference Committees]]
* [[2024 Hosting Proposals]]

[[Category: Conferences]]

User:Phette23

2023-09-29T22:03:30Z

Phette23:

Systems Librarian at [http://libraries.cca.edu California College of the Arts]. Code4Lib 2019 Bay Area local planning co-chair. Recurring member of the conference website committee and community support squad. I love the command line, node, Android: Netrunner, and communism.

'''Sites''': [http://phette.net phette.net] |[https://digipres.club/@phette23 @phette23@digipres.club] | [https://github.com/phette23 GitHub]