Call for volunteers during the actual conference, as opposed to the 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.

• 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
• Elena Colon-Marrero

Social Events

Onsite Volunteer Committee Coordinator: Your Name Here

Monday, Day One (Tours):

• Your Name Here

Tuesday, Day Two (Morning Run, Reception):

• Michelle Janowiecki (morning run)
• Your Name Here (reception)

Wednesday, Day Three (Game Night):

• Hardy Pottinger

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: Trip Kirkpatrick
• AM volunteer: Your Name Here
• PM volunteer: Ange Zaytsev
• PM volunteer: Your Name Here

Wednesday, Day Three:

• AM volunteer: Trip Kirkpatrick
• AM volunteer: Your Name Here
• PM volunteer: Ange Zaytsev
• 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: Laura Akerman
• Backup volunteer (all day): Michael Andrec (East Coast)
• Backup volunteer (all day): Umar Faruk Yunus (West Africa)
• Backup volunteer (all day): Merit Ibekeme (West Africa)

Tuesday, Day Two:

• AM Volunteer: Michelle Navarro
• PM volunteer: Your Name Here
• Backup volunteer (all day): Michael Andrec (East Coast)
• Backup volunteer (all day): Umar Faruk Yunus (West Africa)
• Backup volunteer (all day): Merit Ibekeme (West Africa)

Wednesday, Day Three:

• AM Volunteer: Michelle Navarro
• PM volunteer: Michelle Navarro
• Backup volunteer (all day): Michael Andrec (East Coast)
• Backup volunteer (all day): Umar Faruk Yunus (West Africa)
• Backup volunteer (all day): Merit Ibekeme (West Africa)

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
• Eric Phetteplace — I will be able to volunteer for specific tasks once I know my Community Support schedule
• Ange Zaytsev
• Elena Colon-Marrero
• Your Name Here

future potential volunteers:

• Your Name Here

podium tech help:

• Your Name Here