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

From Code4Lib
(Difference between pages)
Jump to: navigation, search
m (save the date)
 
m (→‎The Whatever Crew: link to me)
 
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].
+
== Community Support Volunteers ==
  
−
== '''Ninth Annual Code4Lib BC Unconference 2024''' ==
+
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.
  
−
'''Save the dates!'''
+
== Concierge/Local Guides ==
 +
Available after sessions to direct people to evening activities and local points of interest, etc.
  
−
* '''Thursday, 16 May and Friday, 17 May'''
+
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)
  
−
=== What's it all about? ===
+
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag
  
−
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.
+
== Conference Logistics & Registration ==
 +
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.
  
−
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. 
+
Onsite Volunteer Committee Coordinator: Hardy Pottinger
  
−
* '''What's included''': a room, coffee/tea, wifi, power
+
12 Noon - 1pm Monday, day one:
 +
* Hardy Pottinger
 +
* Heidi Burkhardt
  
−
* '''What to bring''': your ideas and enthusiasm.
+
8am - 9am Tuesday, day two:
 +
* ''Your Name Here''
 +
* ''Your Name Here''
  
−
* '''Mastodon Hashtag''': `#c4lbc`
+
== Social Events ==
  
−
* '''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.
+
Onsite Volunteer Committee Coordinator:
  
 +
Monday, Day One:
 +
* ''Your Name Here''
  
−
=== Schedule ===
+
Tuesday, Day Two:
 +
* ''Your Name Here''
  
−
'''''Please note that all times are PST (Vancouver, Canada).'''''
+
== Social Networking ==
  
−
==== Day 1 ====
+
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)
  
−
{| class="wikitable"
+
Onsite Volunteer Committee Coordinator:
−
| 8:30 || Venue opens
+
−
|-
+
−
| 9:00 || Welcome and announcements
+
−
|-
+
−
| 9:15 || Lightning talks
+
−
*
+
−
|-
+
−
| 10:30 || Break
+
−
|-
+
−
| 10:45 || Lightning talks (continued)
+
−
*
+
−
|-
+
−
| 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 ====
+
Monday, Day One:
−
{| class="wikitable"
+
* PM volunteer: ''Your Name Here''
−
| 8:30 || Venue opens
+
−
|-
+
−
| 9:00 || Welcome and announcements
+
−
|-
+
−
| 9:15 || Lightning talks
+
−
*  
+
−
|-
+
−
| 10:30 || Break
+
−
|-
+
−
| 10:45 || Lightning talks (continued)
+
−
*
+
−
|-
+
−
| 12:00 || Lunch
+
−
|-
+
−
| 1:00 || Breakout sessions
+
−
*
+
−
|-
+
−
| 2:30 || Break
+
−
|-
+
−
| 2:45 || Breakout sessions (continued)
+
−
*
+
−
|-
+
−
| 4:00 ||
+
−
|-
+
−
| 5:00 ||
+
−
|}
+
  
−
=== Sponsors ===
+
Tuesday, Day Two:
 +
*  AM volunteer: ''Your Name Here''
 +
*  PM volunteer: ''Your Name Here''
  
−
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].
+
Wednesday, Day Three:
 +
*  AM volunteer: ''Your Name Here''
 +
*  PM volunteer: ''Your Name Here''
  
−
=== 2024 Organizers ===
+
Thursday, Workshop Day:
 +
*  AM volunteer: ''Your Name Here''
 +
*  PM volunteer: ''Your Name Here''
  
−
* James Fournie
+
== Mic-minders ==
−
* Dan Sifton
+
−
* Eka Grguric
+
−
* Tamarack Hockin
+
−
* John Durno
+
−
* Scott Leslie
+
−
* Trevor Smith
+
−
* George Villavicencio
+
−
* Rebecca Dickson
+
  
−
= '''Past Events''' =
+
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
  
−
See our [[BC_Past_Events|past events]] page.
+
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]]

Revision as of 18:39, 19 March 2024

Code4Lib 2024 Conference Volunteers

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

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:

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
Retrieved from "https://wiki.code4lib.org/index.php?title=BC&oldid=48349"