273
edits
Changes
m
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.2024 Conference Volunteers =
You can find Call for volunteers during the public discussion channel on actual conference, as opposed to the Code4lib Slack in #c4lbc[[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 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.
* If you'''Thursdayre local to the area (or know it very well), 16 May and Fridayyou can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, 17 May'''restaurant recommendations, etc.
=== WhatOnsite Volunteer Committee Coordinator: 's it all about? ==='Your Name Here'' and anyone else with a "LOCAL" tag
It's a 2-day unconference - a participant-driven meeting bringing together a diverse == Conference Logistics & Registration ==Sets up registration table, signage and open community of library developers and non-developers engaging in effectivewelcome packets, ensures proper power availability to conference attendees, collaborative problem-solving through technology regardless of their department or backgroundetc.
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
* '''Mastodon Hashtag''': `#c4lbc`== Social Events ==
* '''Code of Conduct'''Onsite Volunteer Committee Coordinator: 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.
=== 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"| 8Onsite Volunteer Committee Coordinator: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|}
==== Monday, Day 2 ===={| class="wikitable"| 8One:30 || Venue opens|-| 9:00 || Welcome and announcements|-| 9:15 || Lightning talks* |-| 10 PM volunteer: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 || |}''Your Name Here''
=== Sponsors ===Tuesday, Day Two:* AM volunteer: ''Your Name Here''* PM volunteer: ''Your Name Here''
While Code4Lib BC no longer solicits sponsorshipWednesday, we want to acknowledge the continued administrative and fiscal support from the [httpsDay Three://bc.libraries.coop/ BC Libraries Cooperative].* 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* Dan Sifton* Eka Grguric* Tamarack Hockin* John Durno* Scott Leslie* Trevor Smith* George Villavicencio * Rebecca Dickson== Mic-minders ==
= '''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 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* [BC_Past_Events[User:Phette23|past eventsEric 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]] page.
→The Whatever Crew: link to me
* [[User:NatashaAllen|Natasha Allen]] (U-M)
12 Noon - 1pm Monday, day one:* '''What's included''': a room, coffee/tea, wifi, powerHardy Pottinger* Heidi Burkhardt
8am - 9am Tuesday, day two:* ''Your Name Here'What to bring'* ''Your Name Here'': your ideas and enthusiasm.
Monday, Day One:
* ''Your Name Here''
