Difference between revisions of "2023 Conference Volunteers"
(remove DRAFT stamp, this is as real as it gets) |
HectorCorrea (Talk | contribs) (→Mic-minders) |
||
| Line 70: | Line 70: | ||
* AM volunteer: ''Your Name Here'' | * AM volunteer: ''Your Name Here'' | ||
* AM volunteer: ''Your Name Here'' | * AM volunteer: ''Your Name Here'' | ||
| − | * PM volunteer: | + | * PM volunteer: Hector Correa |
* PM volunteer: ''Your Name Here'' | * PM volunteer: ''Your Name Here'' | ||
Revision as of 14:45, 7 March 2023
Code4Lib 2023 Conference Volunteers
Call for volunteers during the actual conference, as opposed to the conference planning committees.
Community Support Volunteers
See https://2023.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.
- Your Name Here
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: Your Name Here
8am - 9am Wednesday, day one:
- Hardy Pottinger
- Your Name Here
8am - 9am Thursday, day two:
- Hardy Pottinger
- Your Name Here
Social Events
Onsite Volunteer Committee Coordinator:
Wednesday, Day One:
- Your Name Here
Thursday, Day Two:
- 11pm Game Night Cleanup: Your Name Here
- 11pm Game Night Cleanup: Your Name Here
Social Networking
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)
Onsite Volunteer Committee Coordinator:
Tuesday, Preconference Day:
- AM volunteer: Your Name Here
- PM volunteer: Your Name Here
Wednesday, Day One:
- AM volunteer: Your Name Here
- PM volunteer: Your Name Here
Thursday, Day Two:
- AM volunteer: Your Name Here
- PM volunteer: Your Name Here
Friday, Day Three:
- AM 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
Wednesday, Day One:
- AM volunteer: Your Name Here
- AM volunteer: Your Name Here
- PM volunteer: Hector Correa
- PM volunteer: Your Name Here
Thursday, Day Two:
- AM volunteer: Your Name Here
- AM volunteer: Your Name Here
- PM volunteer: Your Name Here
- PM volunteer: Your Name Here
Friday, Day Three:
- AM volunteer: Your Name Here
- AM volunteer: Your Name Here
Livestream Assistants (Onsite)
Livestream assistants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!
Onsite Volunteer Committee Coordinator: Your Name Here
Wednesday, Day One:
- AM Volunteer: Your Name Here
- AM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
Thursday, Day Two:
- AM Volunteer: Your Name Here
- AM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
Friday, Day Three:
- AM Volunteer: Your Name Here
- AM 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
Wednesday, Day One:
- AM Volunteer: Your Name Here
- PM volunteer: Your Name Here
Thursday, Day Two:
- AM Volunteer: Your Name Here
- PM volunteer: Your Name Here
Friday, Day Three:
- AM 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
Wednesday, Day One:
- AM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
Thursday, Day Two:
- AM Volunteer: Your Name Here
- PM Volunteer: Hardy Pottinger
Friday, Day Three:
- AM 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
Wednesday, Day One:
- AM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
Thursday, Day Two:
- AM Volunteer: Your Name Here
- PM Volunteer: Your Name Here
Friday, Day Three:
- AM Volunteer: Your Name Here
The Whatever Crew
Volunteers who are willing to help with various tasks as needed during the conference.
- Your Name Here
- Your Name Here
- Your Name Here
future potential volunteers:
- Your Name Here
podium tech help:
- Your Name Here
