Difference between pages "BC" and "2024 Conference Volunteers"

From Code4Lib
(Difference between pages)
Jump to: navigation, search
m (program update)
 
(Livestream QA (Remote): add Michael Andrec and Umar Faruk Yunus as backup volunteers for all days)
 
Line 1: Line 1:
Welcome to Code4Lib BC! Begun in Summer 2013, this chapter aims to create connections and professional development opportunities for folks from British Columbia and surrounding areas.
+
= Code4Lib 2024 Conference Volunteers =
  
You can find the public discussion channel on the Code4lib Slack in #c4lbc.
+
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].
  
If you're interested in hosting, please [https://docs.google.com/document/d/1mh8haGBziQHiBkG_0byNgIEPxWIsBjKAXOss0cE9fJs/edit?usp=sharing take a read over our Planner's Guide].
+
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.
  
== '''Ninth Annual Code4Lib BC Unconference 2024''' ==
+
== Community Support Volunteers ==
  
'''Save the dates!'''
+
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.
  
* Thursday, 16 May and Friday, 17 May
+
== Concierge/Local Guides ==
* [https://www.eventbrite.ca/e/872117846957/?aff=oddtdtcreator Registration is now open]
+
Available after sessions to direct people to evening activities and local points of interest, etc.
  
This year's C4LBC will be held in Vancouver, BC, and hosted by VCC at the [https://www.vcc.ca/about/college-information/contact-us/downtown-campus/ Downtown Campus].
+
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.
  
=== What's it all about? ===
+
* [[User:NatashaAllen|Natasha Allen]] (U-M)
  
It's a 2-day unconference - a participant-driven meeting bringing together a diverse and open community of library developers and non-developers engaging in effective, collaborative problem-solving through technology regardless of their department or background.
+
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag
  
This year’s event will feature lightning talks and breakout sessions. Lightning talks are brief, 10-minute presentations on topics related to library technologies. Breakout sessions are an opportunity to bring participants together in an ad hoc fashion for a short, yet sustained period of problem solving, software development and fun.
+
== Conference Logistics & Registration ==
 +
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.
  
* '''What's included''': a room, coffee/tea, wifi, power
+
Onsite Volunteer Committee Coordinator: Hardy Pottinger
  
* '''What to bring''': your ideas and enthusiasm.
+
12 Noon - 1pm Monday, day one:
 +
* Hardy Pottinger
 +
* Heidi Burkhardt
  
* '''Mastodon Hashtag''': `#c4lbc`
+
8am - 9am Tuesday, day two:
 +
* Heidi Burkhardt
 +
* Elena Colon-Marrero
  
* '''Code of Conduct''': As a Code4Lib event, we adhere to the [http://bit.ly/coc4lib Code4Lib Code of Conduct], which seeks to provide a welcoming, harassment-free environment.
+
== Social Events ==
  
 +
Onsite Volunteer Committee Coordinator: ''Your Name Here''
  
===Lightning Talk and Breakout Session Ideas===
+
Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):
 +
* ''Your Name Here''
  
 +
Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):
 +
* [[User:MichelleJanowiecki|Michelle Janowiecki]] (morning run)
 +
* ''Your Name Here'' (reception)
  
If there’s a neat project you've been working on, a cool new tool you want to show off, or an interesting development in the world of library technology that you want to discuss, Code4Lib BC is a great opportunity to share that with the community.
+
Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):
 +
* [[User:Hardyoyo|Hardy Pottinger]]
  
[https://forms.gle/FH6DxDJgq18jPM5A6 Submit a lightning talk or breakout session idea]
+
== Social Networking ==
  
=== Schedule ===
+
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)
  
'''''Please note that all times are PST (Vancouver, Canada).'''''
+
Onsite Volunteer Committee Coordinator:
  
==== Day 1 : Thursday, May 16 ====
+
Monday, Day One:
 +
*  PM volunteer: ''Your Name Here''
  
{| class="wikitable"
+
Tuesday, Day Two:
| 8:30 || Venue opens
+
* AM volunteer: ''Your Name Here''
|-
+
* PM volunteer: ''Your Name Here''
| 9:00 || Welcome and announcements
+
|-
+
| 9:15 || Lightning talks
+
* Giving back to the profession through transparency and a public handbook - Cynthia "Arty" Ng
+
* Twitter Archiving, Post-Twitter - Dan Sifton
+
|-
+
| 10:30 || Break
+
|-
+
| 10:45 || Lightning talks (continued)
+
* FindaSpace - Andy Peterson
+
* Implementing Time of Flight People Counting at UVic Libraries - John Durno
+
* Improving online user experience through collaboration with public service staff - Janis McKenzie
+
|-
+
| 12:00 || Lunch
+
|-
+
| 1:00 || Breakout sessions
+
*  
+
|-
+
| 2:30 || Break
+
|-
+
| 2:45 || Breakout sessions (continued)
+
*
+
|-
+
| 4:00 || Breakout reports
+
|-
+
| 5:00 || Social event
+
|}
+
  
==== Day 2 : Friday, May 17 ====
+
Wednesday, Day Three:
{| class="wikitable"
+
* AM volunteer: ''Your Name Here''
| 8:30 || Venue opens
+
* PM volunteer: ''Your Name Here''
|-
+
| 9:00 || Welcome and announcements
+
|-
+
| 9:15 || Lightning talks
+
* CatalogerGPT: an AI powered cataloguing assistant as agentic collaboration - Glen Greenly
+
* Moving to the Cloud: Better late than never? - Scott Leslie
+
* Moving our library to the Folio LSP - Olga Kalachinskaya
+
  
|-
+
Thursday, Workshop Day:
| 10:30 || Break
+
AM volunteer: ''Your Name Here''
|-
+
* PM volunteer: ''Your Name Here''
| 10:45 || Lightning talks (continued)
+
* OpenAthens Authentication vs IP EZProxy - Ryan Regier
+
|-
+
| 12:00 || Lunch
+
|-
+
| 1:00 || Breakout sessions
+
*  
+
|-
+
| 2:30 || Break
+
|-
+
| 2:45 || Breakout sessions (continued)
+
*
+
|-
+
| 4:00 ||
+
|-
+
| 5:00 ||
+
|}
+
  
=== Sponsors ===
+
== Mic-minders ==
  
While Code4Lib BC no longer solicits sponsorship, we want to acknowledge the continued administrative and fiscal support from the [https://bc.libraries.coop/ BC Libraries Cooperative].
+
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
  
=== 2024 Organizers ===
+
Onsite Volunteer Committee Coordinator: ''Your Name Here''
  
* James Fournie
+
Monday, Day One:
* Dan Sifton
+
* PM volunteer: Ange Zaytsev
* Eka Grguric
+
* PM volunteer: ''Your Name Here''
* Tamarack Hockin
+
* John Durno
+
* Scott Leslie
+
* Trevor Smith
+
* George Villavicencio
+
* Rebecca Dickson
+
* Cynthia Ng
+
  
= '''Past Events''' =
+
Tuesday, Day Two:
 +
*  AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]
 +
*  AM volunteer: ''Your Name Here''
 +
*  PM volunteer: Ange Zaytsev
 +
*  PM volunteer: ''Your Name Here''
  
See our [[BC_Past_Events|past events]] page.
+
Wednesday, Day Three:
 +
*  AM volunteer: ''Your Name Here''
 +
*  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: ''[http://mailto:liblna@emory.edu Laura Akerman]''
 +
* Backup volunteer (all day): Michael Andrec (East Coast)
 +
* Backup volunteer (all day): Umar Faruk Yunus (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)
 +
 
 +
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)
 +
 
 +
== 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
 +
* Elena Colon-Marrero
 +
* ''Your Name Here''
 +
 
 +
 
 +
future potential volunteers:
 +
 
 +
* ''Your Name Here''
 +
 
 +
podium tech help:
 +
 
 +
* ''Your Name Here''
 +
 
 +
 
 +
[[Category: Code4Lib2024]]

Revision as of 16:05, 10 May 2024

Code4Lib 2024 Conference Volunteers

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.

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):

Wednesday, Day Three (Game Night):

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: Your Name Here
  • 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)

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)

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)

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