https://wiki.code4lib.org/api.php?action=feedcontributions&user=Hardyoyo&feedformat=atomCode4Lib - User contributions [en]2024-03-28T22:33:14ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483402024 Conference Volunteers2024-03-05T00:14:56Z<p>Hardyoyo: Hardy volunteers for the Whatever Crew</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
12 Noon - 1pm Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Workshop Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: Dre<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: Eric Hellman<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483242024 Conference Volunteers2024-02-02T14:47:03Z<p>Hardyoyo: /* Session Timers */</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
12 Noon - 1pm Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Workshop Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483232024 Conference Volunteers2024-02-02T00:26:22Z<p>Hardyoyo: modernizing the social media names and hashtags</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
12 Noon - 1pm Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Workshop Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483222024 Conference Volunteers2024-02-01T19:56:41Z<p>Hardyoyo: Add MC slot to Wed PM</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
12 Noon - 1pm Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Workshop Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483212024 Conference Volunteers2024-02-01T19:44:36Z<p>Hardyoyo: revised to match the 2024 schedule (starting on an afternoon, and a full last day)</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
12 Noon - 1pm Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Workshop Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=483202024 Conference Volunteers2024-02-01T18:53:49Z<p>Hardyoyo: first draft of 2024 Conference Volunteers page</p>
<hr />
<div>= Code4Lib 2024 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
8am - 9am Monday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Tuesday, day two:<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2024]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480872023 Conference Volunteers2023-03-10T15:31:00Z<p>Hardyoyo: /* Mic-minders */ added Michael Andrec to Thursday AM mic minder slot as per request via Jennifer Cummings</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* Bobbi Fox<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* Hector Correa<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 7am Run/Walk organizer: Eric Hellman<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: Benjamin Riesenberg<br />
* PM volunteer: Hector Correa<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: Michael Andrec<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Heather Greer Klein<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: Vickie Karasic<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: Eric Hellman<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: Trey Pendragon<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: Heather Greer Klein<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* Craig Rosenbeck<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480812023 Conference Volunteers2023-03-08T23:18:45Z<p>Hardyoyo: /* Livestream Assistants (Onsite) */ removing section, livestream assistance not required this year</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* Hector Correa<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 7am Run/Walk organizer: Eric Hellman<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Hector Correa<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Heather Greer Klein<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: Eric Hellman<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: Trey Pendragon<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* Craig Rosenbeck<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480742023 Conference Volunteers2023-03-07T17:41:08Z<p>Hardyoyo: volunteer to be the onsite volunteer committee coordinator for registration</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Hector Correa<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: Maccabee Levine<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480712023 Conference Volunteers2023-03-07T14:37:56Z<p>Hardyoyo: remove DRAFT stamp, this is as real as it gets</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480632023 Conference Volunteers2023-02-07T17:49:21Z<p>Hardyoyo: add link to the conference planning committees page</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480622023 Conference Volunteers2023-02-07T17:43:55Z<p>Hardyoyo: Update days</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480612023 Conference Volunteers2023-02-07T17:42:33Z<p>Hardyoyo: /* Livestream Assistants (Onsite) */ update days</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480602023 Conference Volunteers2023-02-07T17:41:59Z<p>Hardyoyo: /* Livestream QA (Remote) */</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480592023 Conference Volunteers2023-02-07T17:41:28Z<p>Hardyoyo: /* Session Timers */ update days</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480582023 Conference Volunteers2023-02-07T17:40:49Z<p>Hardyoyo: /* MCs */ fix days for MC slots, and volunteered for one of 'em, whee!</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Hardy Pottinger<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480572023 Conference Volunteers2023-02-06T22:38:40Z<p>Hardyoyo: /* Conference Logistics & Registration */Fixed registration dates</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Thursday, day two:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480562023 Conference Volunteers2023-02-06T22:26:50Z<p>Hardyoyo: /* Conference Logistics & Registration */ volunteer for registration</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Tuesday, preconference day:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* Hardy Pottinger<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480552023 Conference Volunteers2023-02-06T22:23:26Z<p>Hardyoyo: add times for registration</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
8am - 9am Tuesday, preconference day:<br />
* ''Your Name Here''<br />
<br />
8am - 9am Wednesday, day one:<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480522023 Conference Volunteers2023-02-03T20:53:13Z<p>Hardyoyo: hashtag for social stuff</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480512023 Conference Volunteers2023-02-03T20:38:07Z<p>Hardyoyo: proper bolding of DRAFT label</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
'''DRAFT/Work in Progress'''<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon, IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=480502023 Conference Volunteers2023-02-03T20:36:33Z<p>Hardyoyo: copy-pasta with light edits, from 2020 to 2023</p>
<hr />
<div>= Code4Lib 2023 Conference Volunteers =<br />
<br />
** DRAFT/Work in Progress **<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
* ''Your Name Here''<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
* 11pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Mastodon, IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
* Before the conference: ''Your Name Here''<br />
* During the conference: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: ''Your Name Here''<br />
<br />
Monday, Day One:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Tuesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
<br />
future potential volunteers:<br />
<br />
* ''Your Name Here''<br />
<br />
podium tech help:<br />
<br />
* ''Your Name Here''<br />
<br />
<br />
[[Category: Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=48041Code4Lib 2023 Conference Committees2023-01-10T23:37:20Z<p>Hardyoyo: Volunteering for the Social Activities Committee</p>
<hr />
<div>= Code4Lib 2023 Conference Committees =<br />
<br />
Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Princeton University<br />
* Pre-conferences: March 14, 2023 (Rabinowitz Building)<br />
* Main conference: March 15-17, 2023 (Frist Campus Center)<br />
<br />
== Local Planning Committee ==<br />
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br />
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact<br />
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br />
* Hillel Arnold - (harnold@rockarch.org) - Volunteer<br />
* Chulin Meng - (chm213@lehigh.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br />
<br />
* Yinlin Chen - (ylchen@vt.edu) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact<br />
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br />
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br />
* John DeLooper - (john.delooper@lehman.cuny.edu) - Volunteer<br />
<br />
== Budget and Sponsorship Committee ==<br />
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br />
<br />
* Jenn Cummings & Kathy Azevedo - (code4lib@concentra-cms.com) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2023 Keynote Documents|2023 Keynote Documents]]<br />
<br />
[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br />
<br />
* [[User:Khaley|Kathleen Haley]] - Primary Contact, Chair<br />
* Kathryn Michaelis - (kmicha3@emory.edu) - Secondary Contact, CoChair<br />
* [[User:Thatandromeda|Andromeda Yelton]] - Documentarian<br />
* Ranti Junus - Volunteer<br />
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br />
<br />
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br />
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br />
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br />
* Eric Morgan <emorgan@nd.edu> - Volunteer, grip, and all-around lackey <br />
* Tod Olson <tod@uchicago.edu> - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2023 Program Documents|2023 Program Documents]]<br />
<br />
* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br />
* Dre (akorphan) - Secondary Contact, CoChair<br />
* Andrew Battelini - (abattel@emory.edu)- Documentarian<br />
* Ranti Junus (junus-at-msu-edu) - Volunteer<br />
* Emily Boss (eboss-at-unr-edu) - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2023 Scholarship Documents|2023 Scholarship Documents]]<br />
<br />
* Yongming Wang - (wangyo@tcnj.edu) - Primary Contact, Chair<br />
* - Secondary Contact, CoChair<br />
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br />
* Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Community Support Squad (CSS) ==<br />
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2022_national_conference_annual_report.md.<br />
<br />
'''Currently seeking one or two coordinators.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Anne Slaughter on Slack or via email (anne dot slaughter at railslibraries dot info).<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br />
<br />
* Kate Lynch - (katelynch@princeton.edu) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Margaret Heller - (mheller1@luc.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Online Volunteer Committee ==<br />
<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br />
<br />
[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Social Activities Committee ==<br />
<br />
This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences. <br />
<br />
2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Hardy Pottinger - hardy.pottinger@ucop.edu - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.<br />
<br />
[[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Kate Lynch - (katelynch@princeton.edu) - LPC Volunteer<br />
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Code4Lib 2023 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2023 Host Voting Documents|2023 Host Voting Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
This committee will assist attendees with IRC and Slack.<br />
<br />
[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees.<br />
<br />
[[2023 Accessibility Documents|2023 Accessibility Documents]]<br />
<br />
* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br />
* Caitlin Bakker - (caitlin.bakker@uregina.ca) - Secondary Contact, CoChair<br />
* Ed Hill - (edhill@duck.com) - Documentarian<br />
* Hilary Shiue (hilaryszuyinshiue@nypl.org) - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2023 Whatever Documents|2023 Whatever Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=47909Code4Lib 2023 Conference Committees2022-10-19T20:06:11Z<p>Hardyoyo: add "pre or post" to preconference day, to keep our options open</p>
<hr />
<div>= Code4Lib 2023 Conference Committees =<br />
<br />
Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Princeton University<br />
* Dates: March 14-17, 2023<br />
<br />
== Local Planning Committee ==<br />
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br />
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact<br />
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br />
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br />
* Your Name Here - Volunteer<br />
<br />
== Budget and Sponsorship Committee ==<br />
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2023 Keynote Documents|2023 Keynote Documents]]<br />
<br />
[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Ranti Junus - Volunteer<br />
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br />
<br />
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br />
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br />
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2023 Program Documents|2023 Program Documents]]<br />
<br />
* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br />
* Dre (akorphan) - Secondary Contact, CoChair<br />
* Andrew Battelini - (abattel@emory.edu)- Documentarian<br />
* Ranti Junus (junus-at-msu-edu) - Volunteer<br />
* Emily Boss (eboss-at-unr-edu) - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2023 Scholarship Documents|2023 Scholarship Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair<br />
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br />
* Yongming Wang - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Community Support Squad (CSS) ==<br />
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers<br />
<br />
* Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Online Volunteer Committee ==<br />
<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br />
<br />
[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Social Activities Committee ==<br />
<br />
This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences. <br />
<br />
2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.<br />
<br />
[[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Code4Lib 2023 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2023 Host Voting Documents|2023 Host Voting Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
This committee will assist attendees with IRC and Slack.<br />
<br />
[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees.<br />
<br />
[[2023 Accessibility Documents|2023 Accessibility Documents]]<br />
<br />
* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2023 Whatever Documents|2023 Whatever Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=47908Code4Lib 2023 Conference Committees2022-10-19T20:03:52Z<p>Hardyoyo: volunteering for the Pre-conference Documentarian position</p>
<hr />
<div>= Code4Lib 2023 Conference Committees =<br />
<br />
Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Princeton University<br />
* Dates: March 14-17, 2023<br />
<br />
== Local Planning Committee ==<br />
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br />
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact<br />
* Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br />
* Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br />
* Your Name Here - Volunteer<br />
<br />
== Budget and Sponsorship Committee ==<br />
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2023 Keynote Documents|2023 Keynote Documents]]<br />
<br />
[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Ranti Junus - Volunteer<br />
* Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br />
<br />
* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br />
* Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br />
* Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2023 Program Documents|2023 Program Documents]]<br />
<br />
* Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br />
* Dre (akorphan) - Secondary Contact, CoChair<br />
* Andrew Battelini - (abattel@emory.edu)- Documentarian<br />
* Ranti Junus (junus-at-msu-edu) - Volunteer<br />
* Emily Boss (eboss-at-unr-edu) - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2023 Scholarship Documents|2023 Scholarship Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair<br />
* Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br />
* Yongming Wang - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Community Support Squad (CSS) ==<br />
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers<br />
<br />
* Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Online Volunteer Committee ==<br />
<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br />
<br />
[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Social Activities Committee ==<br />
<br />
This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences. <br />
<br />
2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and possibly running the camera during the conference.<br />
<br />
[[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br />
* [[User:highermath|Cary Gordon]] - Volunteer<br />
<br />
== Code4Lib 2023 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2023 Host Voting Documents|2023 Host Voting Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
This committee will assist attendees with IRC and Slack.<br />
<br />
[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees.<br />
<br />
[[2023 Accessibility Documents|2023 Accessibility Documents]]<br />
<br />
* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2023 Whatever Documents|2023 Whatever Documents]]<br />
<br />
* NAME - (EMAIL) - Primary Contact, Chair<br />
* NAME - (EMAIL) - Secondary Contact, CoChair<br />
* NAME - (EMAIL) - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2023]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&diff=47260Code4Lib 2020 Conference Committees2019-11-25T15:48:59Z<p>Hardyoyo: /* Book Giveaway Committee */</p>
<hr />
<div>= Code4Lib 2020 Conference Committees =<br />
<br />
Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2020 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA<br />
* Dates: March 08 (pre-con) - 22, 2020<br />
** Pre-conferences: March 08, 2020<br />
** Main meeting: March 09-11, 2020<br />
** Post conference activities: Coming Soon<br />
<br />
== Local Planning Committee ==<br />
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact<br />
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact<br />
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact<br />
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact<br />
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact<br />
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact<br />
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer<br />
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Volunteer<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2020 Website Working Group Documents|2020 Website Working Group Documents]]<br />
<br />
* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair<br />
* [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Julia Caffrey (newbie) - Volunteer <br />
* [[User:Ranti|Ranti Junus]] (v) - Volunteer<br />
* [[User:Tomkeays|Tom Keays]] - Volunteer<br />
* [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer<br />
* [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer <br />
* [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact <br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)<br />
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)<br />
<br />
== Sponsorship Committee ==<br />
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br />
<br />
* Mary Jinglewski - Primary Contact aka Chair<br />
* Scott Carlson - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Janna Avon - Documentarian <br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer<br />
* [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2020 Keynote Documents|2020 Keynote Documents]]<br />
<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair<br />
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)<br />
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact <br />
* [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer<br />
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2020 Pre-conference Documents|2020 Pre-conference Documents]]<br />
<br />
* [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact <br />
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian<br />
* [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer<br />
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2020 Program Documents|2020 Program Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact <br />
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer<br />
* [mailto:akorphan@ncsu.edu Dre] - Volunteer<br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [mailto:bomanc@oclc.org Craig Boman] - Volunteer<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
* [[User:RichardHiggins|Richard Higgins]], Indiana University - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2020 Scholarship Documents|2020 Scholarship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Co-Chair<br />
* Your Name Here - Primary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian <br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer<br />
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer<br />
* Your Name Here - (Volunteer)<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2020 T-Shirt Documents|2020 T-Shirt Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair<br />
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
'''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''<br />
<br />
[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]<br />
<br />
* [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer<br />
* [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer<br />
<br />
== Social Activities Committee ==<br />
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between). <br />
<br />
[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]<br />
<br />
Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]<br />
<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair<br />
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian<br />
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br />
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.<br />
<br />
[[2020 Streaming Video Documents|2020 Streaming Video Documents]]<br />
<br />
* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)<br />
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer<br />
<br />
== Code4Lib 2021 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2021 Host Voting Documents|2021 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]<br />
<br />
* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* [[User:Hardyoyo|Hardy Pottinger]] - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).<br />
<br />
[[2020 Accessibility Documents|2020 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2020 Whatever Documents|2020 Whatever Documents]]<br />
<br />
* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2020]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&diff=47259Code4Lib 2020 Conference Committees2019-11-25T15:48:18Z<p>Hardyoyo: officially volunteering for the book giveaway committee</p>
<hr />
<div>= Code4Lib 2020 Conference Committees =<br />
<br />
Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2020 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA<br />
* Dates: March 08 (pre-con) - 22, 2020<br />
** Pre-conferences: March 08, 2020<br />
** Main meeting: March 09-11, 2020<br />
** Post conference activities: Coming Soon<br />
<br />
== Local Planning Committee ==<br />
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact<br />
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact<br />
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact<br />
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact<br />
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact<br />
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact<br />
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact<br />
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer<br />
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Volunteer<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2020 Website Working Group Documents|2020 Website Working Group Documents]]<br />
<br />
* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair<br />
* [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Julia Caffrey (newbie) - Volunteer <br />
* [[User:Ranti|Ranti Junus]] (v) - Volunteer<br />
* [[User:Tomkeays|Tom Keays]] - Volunteer<br />
* [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer<br />
* [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer <br />
* [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact <br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)<br />
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)<br />
<br />
== Sponsorship Committee ==<br />
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br />
<br />
* Mary Jinglewski - Primary Contact aka Chair<br />
* Scott Carlson - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Janna Avon - Documentarian <br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer<br />
* [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2020 Keynote Documents|2020 Keynote Documents]]<br />
<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair<br />
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)<br />
* [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact <br />
* [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer<br />
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2020 Pre-conference Documents|2020 Pre-conference Documents]]<br />
<br />
* [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair<br />
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact <br />
* [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian<br />
* [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer<br />
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2020 Program Documents|2020 Program Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact <br />
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer<br />
* [mailto:akorphan@ncsu.edu Dre] - Volunteer<br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [mailto:bomanc@oclc.org Craig Boman] - Volunteer<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
* [[User:RichardHiggins|Richard Higgins]], Indiana University - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2020 Scholarship Documents|2020 Scholarship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Co-Chair<br />
* Your Name Here - Primary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian <br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer<br />
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer<br />
* Your Name Here - (Volunteer)<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2020 T-Shirt Documents|2020 T-Shirt Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair<br />
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer<br />
<br />
== Onsite Volunteer Committee ==<br />
<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
'''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''<br />
<br />
[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]<br />
<br />
* [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer<br />
* [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer<br />
<br />
== Social Activities Committee ==<br />
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between). <br />
<br />
[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]<br />
<br />
Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]<br />
<br />
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair<br />
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian<br />
* [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br />
* [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.<br />
<br />
[[2020 Streaming Video Documents|2020 Streaming Video Documents]]<br />
<br />
* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)<br />
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer<br />
<br />
== Code4Lib 2021 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2021 Host Voting Documents|2021 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]<br />
<br />
* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* [[User:Hardyoyo]] Hardy Pottinger - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).<br />
<br />
[[2020 Accessibility Documents|2020 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2020 Whatever Documents|2020 Whatever Documents]]<br />
<br />
* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2020]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=One_recommended_tool/resource_for_n00bs&diff=46848One recommended tool/resource for n00bs2019-03-30T17:22:25Z<p>Hardyoyo: added link to Jenn Riley's Seeing Standards site</p>
<hr />
<div>===One recommended tool/resource for n00bs===<br />
<br />
These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive]. <br />
<br />
Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!<br />
<br />
====Tools/Resources====<br />
<br />
=====Books or Things to read=====<br />
* O'Reilly Head first series<br />
* Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245<br />
* [https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]<br />
* [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas. A book that teaches beginners how think like a programmer, and reminds experts of good practices.<br />
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/<br />
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.<br />
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie.<br />
* [http://www.worldcat.org/title/agile-web-development-with-rails-4/oclc/852808602&referer=brief_results Agile Web Development with Rails 4] is a well-paced introduction to Rails and Ruby. Covers a lot of core concepts (MVC, agile development, testing, AJAX).<br />
** To dive further into Ruby, there's [http://www.worldcat.org/title/programming-ruby-19-20-the-pragmatic-programmers-guide/oclc/855706057&referer=brief_results Programming Ruby] (aka The PickAxe Book)<br />
* http://www.w3.org/International<br />
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed<br />
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series<br />
<br />
=====Software=====<br />
<br />
* Vi- because it keeps me (you?) focused.<br />
* [http://www.activestate.com/komodo-edit Komodo Edit]<br />
* [http://notepad-plus-plus.org/ Notepad++ IMO best open source lightweight editor on Windows]<br />
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.<br />
*A @rdio subscription. :) And a text editor with syntax highlighting.<br />
* Git (Version Control)<br />
* Github, Bitbucket and Other Remote Git Services<br />
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets. <br />
* [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]<br />
* LESS http://lesscss.org/ <br />
* Compass http://compass-style.org/ - extends SASS with reusable patterns<br />
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]<br />
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.<br />
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.<br />
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]<br />
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.<br />
<br />
=====Websites=====<br />
* Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)<br />
* Google is more useful than any reference book to find answers to programming problems.<br />
* [http://stackexchange.com/ StackExchange] (by extension, [http://stackoverflow.com StackOverflow]) is a great site for questions.<br />
* [http://lynda.com lynda.com]<br />
* [http://www.pluralsight.com/ PluralSight.com]<br />
* JS Fiddle http://jsfiddle.net/<br />
* CodePen http://codepen.io/<br />
* [http://css-tricks.com CSS Tricks ]<br />
* [http://openhatch.org/ Open Hatch] - to learn tools you need to participate in open source development and find friendly projects to be a part of<br />
* [http://drupalladder.org/ Drupal Ladder], which teaches you what you need to know to participate in developing Drupal<br />
* [http://rubykoans.com/ Ruby Koans] - learn Ruby by fixing failing tests<br />
* [https://librarycarpentry.org/ Library Carpentry] - Free, open-source lessons for non-techy librarians on coding, data analysis, and related topics. They also give in-person workshops upon request.<br />
* [http://jennriley.com/metadatamap/ Seeing Standards] - Let's be frank, there is a giant pile of metadata standards awaiting any newbie to this field. Jenn Riley's map of these standards, and the accompanying glossary, is an invaluable resource. It may be tempting to try to print the PDF of this visualization, just be aware that it is absolutely gigantic. You will need access to a poster printer to do it justice. Don't let that frighten you, feel free to explore it on your computer, save it, keep it as a reference. This poster will help you, you need it.<br />
<br />
=====Meetups and User Groups=====<br />
<br />
* Perl Mongers http://www.pm.org/groups/<br />
* Python Local User Groups http://wiki.python.org/moin/LocalUserGroups<br />
** Look for user groups running an incarnation of the [http://bostonpythonworkshop.com/ Boston Python Workshop], a women-and-their-friends day-and-a-half introduction to Python which assumes no prior knowledge.<br />
* R Users Group Meetups http://r-users-group.meetup.com/<br />
* Drupal Groups http://groups.drupal.org/<br />
* Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/<br />
** Look for groups running an incarnation of [http://workshops.railsbridge.org/ RailsBridge] (like Boston Python Workshop except it came first, and covers Ruby)<br />
* Haskell User Groups http://www.haskell.org/haskellwiki/User_groups<br />
* ColdFusion Meetups http://coldfusion.meetup.com/<br />
<br />
=====Other=====<br />
<br />
* Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]<br />
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]<br />
* [http://foss4lib.org/ FOSS4lib]<br />
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)<br />
* Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).<br />
* It's still useful to learn a little something about configuring a webserver / database / etc.<br />
* The [http://connect.ala.org/node/167971 Library Code Year Interest Group], an ALA group (joint between LITA and ALCTS) for librarians who want to learn and apply code<br />
<br />
=====Advice on what to do=====<br />
*Building things that help people matters, and for that you need empathy.<br />
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.<br />
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.<br />
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.<br />
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46840Code4Lib2019 Lightning Talks2019-03-21T18:45:59Z<p>Hardyoyo: </p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# [https://osf.io/fby9s/ Islandora for All: ISLE + LASIR + Community Engagement] - David Keiser-Clark<br />
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery<br />
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre<br />
# [https://github.com/hardyoyo/code4lib19-serverspec-talk Wait, what? Getting your bearings with ServerSpec] - Hardy Pottinger<br />
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates<br />
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee<br />
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.<br />
# SCOPE: a born digital access interface - Stefana Breitwieser, Canadian Centre for Architecture - [[https://github.com/CCA-Public/dip-access-interface github]] [[https://journal.code4lib.org/articles/14283 more info]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)<br />
# The Patron Data Firehose - David Lacy<br />
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]<br />
# The Real World of Technology - Ashley Blewer<br />
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]<br />
# Profiles Core - Karen Coyle<br />
# [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 22, 2019 ==<br />
# [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis<br />
# [https://osf.io/x75bk/ What is Audio Description] - Carli Spina<br />
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark<br />
# Web-based AR. Simple! - Dan Lou<br />
# We Are Family - Code4Lib Local Chapters - Thomas Guignard<br />
# Making a staff calendar: an intro to automation - Zach Pell<br />
# Speed mentoring/skill share<br />
#</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46839Code4Lib2019 Lightning Talks2019-03-21T18:45:02Z<p>Hardyoyo: added link to my lightning talk slides</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# [https://osf.io/fby9s/ Islandora for All: ISLE + LASIR + Community Engagement] - David Keiser-Clark<br />
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery<br />
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre<br />
# [https://github.com/hardyoyo/code4lib19-serverspec-talk Wait, what? Getting your bearings with server spec] - Hardy Pottinger<br />
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates<br />
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee<br />
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.<br />
# SCOPE: a born digital access interface - Stefana Breitwieser, Canadian Centre for Architecture - [[https://github.com/CCA-Public/dip-access-interface github]] [[https://journal.code4lib.org/articles/14283 more info]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)<br />
# The Patron Data Firehose - David Lacy<br />
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]<br />
# The Real World of Technology - Ashley Blewer<br />
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]<br />
# Profiles Core - Karen Coyle<br />
# [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 22, 2019 ==<br />
# [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis<br />
# [https://osf.io/x75bk/ What is Audio Description] - Carli Spina<br />
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark<br />
# Web-based AR. Simple! - Dan Lou<br />
# We Are Family - Code4Lib Local Chapters - Thomas Guignard<br />
# Making a staff calendar: an intro to automation - Zach Pell<br />
# Speed mentoring/skill share<br />
#</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466942019 Conference Volunteers2019-02-15T18:17:52Z<p>Hardyoyo: add slack channel info to the Livestream QA (Remote) volunteer info</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: [[User:Anarchivist|Mark Matienzo]]<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: [[User:tallgood|Tammy Allgood Wolf]] (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* https://www.thetech.org/floor-maps Floor Map. Lower Level<br />
<br />
<br />
<br />
Thursday, Day Two:<br />
* 9:30-10pm Game Night Cleanup: [[User:Phette23|Eric Phetteplace]]<br />
* 9:30-10pm Game Night Cleanup: [[User:hardyoyo|Hardy Pottinger]]<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter (#c4l19), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
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<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: [[User:Kimpham54|Kim Pham]]<br />
* AM volunteer: Thomas Guignard<br />
* PM volunteer: Lydia Zvyagintseva<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Whitni''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: [[User:ChrisDay|Chris Day]]<br />
* PM volunteer: Lydia Zvyagintseva<br />
<br />
Friday, Day Four:<br />
* AM volunteer: [[User:ChrisDay|Chris Day]]<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); Kevin Clair (West)<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]] & [[User:Anarchivist|Mark Matienzo]]<br />
* During the conference: [[User:Anarchivist|Mark Matienzo]] & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:tallgood|Tammy Allgood Wolf]]<br />
<br />
Wednesday, Day One:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: Whitni<br />
<br />
Thursday, Day Two:<br />
* AM Volunteer: [http://mailto:phette23@gmail.com Eric Phetteplace]<br />
* PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]<br />
<br />
Friday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: Whitni<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Whitni<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466732019 Conference Volunteers2019-02-15T16:17:41Z<p>Hardyoyo: volunteer for Social at Game night</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: [[User:Anarchivist|Mark Matienzo]]<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* 9:30-10pm Game Night Cleanup: [[User:Phette23|Eric Phetteplace]]<br />
* 9:30-10pm Game Night Cleanup: [[User:hardyoyo|Hardy Pottinger]]<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: [[User:Kimpham54|Kim Pham]]<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Lydia Zvyagintseva<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Whitni''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: [[User:ChrisDay|Chris Day]]<br />
* PM volunteer: Lydia Zvyagintseva<br />
<br />
Friday, Day Four:<br />
* AM volunteer: [[User:ChrisDay|Chris Day]]<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); Kevin Clair (West)<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]] & [[User:Anarchivist|Mark Matienzo]]<br />
* During the conference: [[User:Anarchivist|Mark Matienzo]] & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
''[http://mailto:phette23@gmail.com Eric Phetteplace] can fill in one of the missing volunteering slots''<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Whitni''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466642019 Conference Volunteers2019-02-14T00:17:36Z<p>Hardyoyo: signing up for MC duty, Thursday afternoon</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: [[User:Kimpham54|Kim Pham]]<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: Lydia Zvyagintseva<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Whitni''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: [[User:ChrisDay|Chris Day]]<br />
* PM volunteer: 'Lydia Zvyagintseva<br />
<br />
Friday, Day Four:<br />
* AM volunteer: [[User:ChrisDay|Chris Day]]<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); Kevin Clair (West)<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]] & [[User:Anarchivist|Mark Matienzo]]<br />
* During the conference: [[User:Anarchivist|Mark Matienzo]] & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Whitni''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Social_Activities&diff=466452019 Social Activities2019-02-11T17:22:46Z<p>Hardyoyo: day change for the Winchester House trip</p>
<hr />
<div>__TOC__<br />
<br />
= Code4Lib 2019 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Tuesday, February 19th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Tuesday, February 19th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together, depending on where your group is coming from (off-site preconfs, travel, etc.)<br />
* Mastermind (if you have any questions): [mailto:b.yoose@gmail.com Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. These are labeled with the “Can Seat Multiple Groups of Six” in the restaurant listing.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Tuesday evening.'''<br />
<br />
NB! Many of this year's Newcomer Dinner options are not close to the convention hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.<br />
<br />
'''Restaurant list, sign ups, and transportation information now live on the [https://2019.code4lib.org/general-info/venues/#dinner Code4Lib website]!'''<br />
<br />
=== Conference Reception, Wednesday, February 20th ===<br />
<br />
* When: Wednesday, February 20th, 7 pm -9 pm<br />
* Where: [https://www.thetech.org/plan-your-visit The Tech Museum of Innovation]<br />
* Shuttle buses traveling from the hotel to the reception will be available for attendees. More details will be added as they become available.<br />
* '''Don't forget your conference nametag!'''<br />
<br />
Light hors d'oeuvres and drinks will be provided. More information about the reception, as well as transportation and security information, can be found on the [http://2019.code4lib.org/general-info/venues/#reception Code4Lib website].<br />
<br />
=== #LibTechWomen Meet-Up, Thursday, February 21st ===<br />
<br />
* When: Thursday, 2/21/19, 5:30 pm to 7:30 pm<br />
* Where: 2050 Lobby Bar, located in Conference Hotel<br />
* Food and beverages are available for purchase<br />
* Afterwards some of us will go to Game Night or Karaoke!<br />
<br />
[http://libtechwomen.org/ LibTechWomen] is a supportive space for women and their friends to network, develop skills, build confidence, and lead positive change. Are you a lurker? Are you a newcomer? All are welcome! Come meet wonderful colleagues in library technology!<br />
<br />
=== Game Night, Thursday, February 21st ===<br />
<br />
* When: Thursday, 2/21/19, 6:30 pm to 9:30 pm<br />
* Where: San Jose meeting room (Conference Hotel)<br />
* Food and beverages are available for purchase. '''No outside food or beverages are allowed in hotel meeting rooms.'''<br />
** People will be responsible for getting their own food and drink from the hotel lounge/bar, as well as bussing their own tables. On-site volunteers will help clean up at the end of the event as well.<br />
* Sing about your glorious victories or sorrowful defeats at Karaoke afterwards!<br />
<br />
Play games? Come join fellow code4libers in a few board or card games! Feel free to bring your own games - list any games you might bring with you at https://docs.google.com/spreadsheets/d/1muSFDDI-iRAVEzficXBg7dubDC4TcdiK7eFKrbpqypc/edit?usp=sharing.<br />
<br />
=== Karaoke Night, Thursday, February 21st ===<br />
<br />
* When: Thursday, 2/21/19, Time TBA<br />
* Where: 7 Bamboo Lounge, 162 Jackson St., San Jose, CA 95112 <br />
* Food and beverages are available for purchase<br />
* Rideshares and taxis highly recommended coming back to the conference hotel (visit the conference website for more information about transportation options)<br />
<br />
Sing like no one can hear you, dance like no one is watching... Groups can sign up to head over to the lounge at the DIY Events document at https://docs.google.com/document/d/1VVfaRFpYwXyZfRI5hRTorIW4hSzu4yg13S-R-M-EGoE/edit#heading=h.hz4hb9fkuzf4.<br />
<br />
<br />
=== Winchester Magical Mystery Tour, Friday February 22nd ===<br />
<br />
We'll be gathering for a tour the Winchester Mystery House https://en.wikipedia.org/wiki/Winchester_Mystery_House<br />
<br />
Contact: Kim Pham (kimpham on Slack)<br />
<br />
== Social and Food/Drink Map ==<br />
For a visual-ish view of recommended food, drink, and activities in San Jose and the surrounding area, please visit this awesome Google Map at https://drive.google.com/open?id=1UqZIAHg2qllhbHCsv4JRXkbNqJ1qGOht&usp=sharing.<br />
<br />
== Ideas, Local Event Outings, and More! ==<br />
Looking for something to do outside of what's listed above? We have a Google Doc for that! The DIY Events document at https://docs.google.com/document/d/1VVfaRFpYwXyZfRI5hRTorIW4hSzu4yg13S-R-M-EGoE/edit?usp=sharing has a variety of ideas to choose from, or you can add your own. You can also use this document to organize outings in one central place!<br />
<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: https://2019.code4lib.org/general-info/venues/<br />
<br />
<br />
[[Category:Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466442019 Conference Volunteers2019-02-09T21:01:38Z<p>Hardyoyo: volunteered for the whatever crew</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: ''Your Name Here''<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466432019 Conference Volunteers2019-02-09T20:59:03Z<p>Hardyoyo: volunteered to coordinate livestream QA</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: ''Your Name Here''<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: Hardy Pottinger<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466422019 Conference Volunteers2019-02-09T20:34:15Z<p>Hardyoyo: volunteering for preconference registration duty</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br />
* 8am - 10am: ''Your Name Here''<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=User:Hardyoyo&diff=46641User:Hardyoyo2019-02-09T20:30:29Z<p>Hardyoyo: more deets for me</p>
<hr />
<div>Twitter: @HardyPottinger<br />
<br />
Slack: hpottinger<br />
<br />
Github: hardyoyo<br />
<br />
Blog: http://hardyoyo.thebignow.com/<br />
<br />
ORCID: https://orcid.org/0000-0001-8549-9354</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=User:Hardyoyo&diff=46640User:Hardyoyo2019-02-09T20:26:35Z<p>Hardyoyo: made a stub user page for myself</p>
<hr />
<div>work in progress</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466392019 Conference Volunteers2019-02-09T20:03:49Z<p>Hardyoyo: removing my name from the CSV</p>
<hr />
<div>= Code4Lib 2019 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Community Support Volunteers ==<br />
<br />
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br />
<br />
Onsite Volunteer Committee Coordinator: N/A<br />
<br />
* Karen Coyle<br />
* Justin Coyne<br />
* Shaun Ellis<br />
* Erin Fahy<br />
* Bobbi Fox<br />
* Wayne Graham<br />
* Francis Kayiwa<br />
* Megan Kudzia<br />
* Anne Slaughter<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
== Conference Logistics & Registration ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Monday, day before:<br />
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br />
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br />
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br />
* 3pm - 6pm: ''Your Name Here''<br />
<br />
Tuesday, preconference day:<br />
* 8am - 10am: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<br />
* 1pm - 3pm: ''Your Name Here''<br />
<br />
Wednesday, day one:<br />
* 8am - 9:30am: ''Your Name Here''<br />
<br />
== Social Events ==<br />
<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day One:<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br />
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br />
* 7:30-8:30pm Reception: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
* 9:30-10pm Game Night Cleanup: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
Tuesday, Preconference Day:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Wednesday, Day One:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
* PM volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM volunteer: ''Your Name Here''<br />
* AM volunteer: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
<br />
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!<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== Livestream QA (Remote) ==<br />
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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
== IRC/Slack (Technical) ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br />
<br />
* Before the conference: [[User:Kimpham54|Kim Pham]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Dre<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<br />
<br />
== Session Timers ==<br />
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.<br />
<br />
Onsite Volunteer Committee Coordinator:<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: 'Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here''<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br />
* [[User:rtennant|Roy Tennant]]<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Social_Activities&diff=465712019 Social Activities2019-01-14T16:38:39Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2019 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Winchester Magical Mystery Tour, Thursday February 21st ===<br />
<br />
We'll be gathering for a tour the Winchester Mystery House https://en.wikipedia.org/wiki/Winchester_Mystery_House<br />
<br />
We promise to get back in time for game night!<br />
<br />
Contact: Hardy Pottinger (hpottinger on Slack), Kim Pham (kimpham on Slack)<br />
<br />
[[Category:Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2019_Social_Activities&diff=465702019 Social Activities2019-01-14T16:38:20Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2019 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Winchester Magical Mystery Tour, Thursday February 21st ===<br />
<br />
We'll be gathering for a tour the Winchester Mystery House https://en.wikipedia.org/wiki/Winchester_Mystery_House<br />
<br />
We promised to get back in time for game night!<br />
<br />
Contact: Hardy Pottinger (hpottinger on Slack), Kim Pham (kimpham on Slack)<br />
<br />
[[Category:Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46551Code4Lib 2019 Conference Committees2018-12-05T18:43:53Z<p>Hardyoyo: volunteered for the volunteer committee</p>
<hr />
<div>= Code4Lib 2019 Conference Committees =<br />
<br />
Hosting a conference is incredibly complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[http://doubletree3.hilton.com/en/hotels/california/doubletree-by-hilton-hotel-san-jose-JOSE-DT/index.html DoubleTree by Hilton]''' near the Airport, San José, CA<br />
* Dates: February 19 (pre-con) - 22, 2019<br />
** Pre-conferences: February 19, 2019<br />
** Main meeting: February 20-22, 2019<br />
** Post conference activities: Coming Soon<br />
<br />
== Local Planning Committee ==<br />
This committee is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.<br />
<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact<br />
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair<br />
* [[User:WhitniWatkins|Whitni Watkins]], Analog Devices, Inc. - Secondary Contact aka Co-Chair (if you want to volunteer and you've not served on any Code4Lib committees before, let me know, I'll step aside) <br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* [http://mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Documentarian<br />
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer<br />
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer<br />
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer<br />
* Cody Whitby, Virginia Commonwealth University - Volunteer<br />
* Laura Chuang - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* Mark Matienzo - Local Planning Contact <br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)<br />
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF) <br />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<br />
<br />
== Sponsorship Committee ==<br />
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Primary Contact aka Chair<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol], Long Beach City College - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* [mailto:dicossio@crimson.ua.edu Diana Cossio]- Documentarian <br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<br />
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer<br />
* [mailto:cmathieu@jpl.nasa.gov Camille Mathieu], JPL Library - Volunteer<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam], Purdue - Volunteer<br />
<br />
== Keynote Committee ==<br />
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br />
<br />
[[2019 Keynote Documents|2019 Keynote Documents]]<br />
<br />
* [mailto:axm1195@case.edu Andrew Mancuso] - Primary Contact aka Chair<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact <br />
* [mailto:lconrad@cca.edu Lisa Conrad] - Documentarian<br />
* [mailto:ehenry124@gmail.com Elizabeth Henry] - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp] - Volunteer<br />
* [mailto:crh92@case.edu Charlie Harper] - Volunteer<br />
<br />
== Pre-conference Committee ==<br />
This committee plans the pre-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br />
<br />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lydiaz@ualberta.ca Lydia Zvyagintseva] - Volunteer<br />
* [mailto:tod@uchicago.edu Tod Olson] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] - Volunteer<br />
* [[User:Kimpham54|Kim Pham]] - Volunteer<br />
<br />
== Program Committee == <br />
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br />
<br />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer <br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [[User:DanielDraper|Dan Draper]] - Volunteer<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - Volunteer<br />
<br />
== Scholarship Committee ==<br />
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.<br />
<br />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian <br />
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)<br />
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (Volunteer)<br />
<br />
== T-Shirt Committee ==<br />
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br />
<br />
[[2019 T-Shirt Documents|2019 T-Shirt Documents]]<br />
<br />
* [mailto:ewahl@folger.edu Emily Wahl] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:matienzo@stanford.edu Mark Matienzo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== Onsite Volunteer Committee ==<br />
This committee wrangles people to volunteer for the following duties:<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:hpottinger@library.ucla.edu Hardy Pottinger] UCLA Library - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Social Activities Committee ==<br />
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between). <br />
<br />
[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]<br />
<br />
Conference goers - The page you are looking for is at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair<br />
* [http://wiki.code4lib.org/User:NatashaAllen Natasha Allen] - Secondary Contact aka Co-Chair<br />
* [mailto:amcollie@stanford.edu Aaron Collier] - Local Planning Contact<br />
* Meredith Broadway - Documentarian<br />
* Ann S. - Volunteer<br />
<br />
== Streaming Video Committee ==<br />
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks (?), and, of course, actually running the camera during the conference.<br />
<br />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
<br />
== Code4Lib 2020 Host Voting Committee ==<br />
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br />
<br />
[[2020 Host Voting Documents|2020 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Roy Tennant - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lillyho@gmail.com Lilly HS HO] - Volunteer<br />
<br />
== Book Giveaway Committee ==<br />
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).<br />
<br />
[[2019 Book Giveaway Documents|2019 Book Giveaway Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:JieChen|Jie Chen]], Univ. of WI-Milwaukee Libraries - Volunteer<br />
<br />
== Accessibility Committee ==<br />
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).<br />
<br />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair<br />
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Whatever Committee ==<br />
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br />
<br />
[[2019 Whatever Documents|2019 Whatever Documents]]<br />
<br />
* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2019]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2018_Keynote_Speakers_Nominations&diff=455072018 Keynote Speakers Nominations2017-09-28T16:21:35Z<p>Hardyoyo: added linebreaks between Terry's links</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2018 in Washington, D.C. will open on '''September 18th''' and close on '''October 15, 2017'''.<br />
<br />
Voting will start on Monday, October 23, 2017 and continue through Monday, November 13, 2017.<br />
<br />
Please include a description and any relevant links and try to keep the list in alphabetical order.<br />
<br />
The criteria for nominating a candidate to act as keynote are below:<br />
*Speaker’s name (First Name, Last Name)<br />
*Brief description of individual (250-word max)<br />
*Pertinent links (Maximum of 3)<br />
*Contact information of candidate (email address)<br />
<br />
''We strongly encourage you to nominate speakers who are local to the D.C. Metropolitan Area.'' <br />
<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Nominee's Name ==<br />
<br />
Description of no more than 250 words.<br />
<br />
[[Link(s) with contact information for nominee]]<br />
<br />
</pre><br />
<br />
__TOC__<br />
<br />
==Jane Doe (example)==<br />
Jane works at ________, doing _______. <br />
<br />
Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.<br />
<br />
==Pamela Wright==<br />
Pamela Wright is the U.S. National Archives' first Chief Innovation Officer. She oversees the Agency's online public access Catalog, web, social media, and authorities programs as well as the Innovation Hub. She has hosted coding communities and worked with other institutions to help the Agency become a more digital, citizen-centric institution. She has a goldmine of content and adores coders who can do interesting and enlightening things with it. She launched the Citizen Archivist Dashboard, which has been a gateway for the public to engage in new ways with our content. She is currently collaborating with staff from the Smithsonian and Library of Congress on History Hub (see link below). <br />
<br />
[https://twitter.com/PamelaSW]<br />
<br />
[https://historyhub.history.gov/welcome]<br />
<br />
[https://www.linkedin.com/in/pamela-wright-8ab59861]<br />
<br />
<br />
==Veni Kunche==<br />
Veni Kunche is a coder, maker, and mentor who works at the U.S. Geological Survey (as a Sr. Software Engineer) and Blasterra (as CEO and Founder). At Blasterra, she focuses on developing programs for people learning to code, but also focuses on teaching women to code. She is based in D.C..<br />
<br />
[https://www.linkedin.com/in/venikunche/ Linkedin]<br />
<br />
[https://twitter.com/venikunche @venikunche]<br />
<br />
[http://www.codewithveni.com/ Code with Veni]<br />
<br />
==Shane Lin==<br />
Senior Developer at the University of Virginia's Scholars' Lab.<br />
<br />
Shane studies the history of computing and the impact of digital technology on culture and politics. His dissertation, “Kingdom of Code: Cryptography and the New Privacy” tracks the development of civilian encryption technology and the emergence of cryptography as an academic field of study, the debates over crypto regulation, and the concomitant construction of a new, far more expansive notion of privacy from 1975 to 2000. His perspectives on technology, encryption, and privacy would be especially interesting to a wide audience. <br />
<br />
<br />
[http://scholarslab.org/people/shane-lin/ Shane Lin]<br />
<br />
[http://scholarslab.org/digital-humanities/the-long-and-messy-history-of-privacy/ Privacy Post]<br />
<br />
==Jessica Marie Johnson==<br />
Jessica Marie Johnson is an assistant professor of history at Johns Hopkins University in Baltimore. Her work is focused around radical black feminist praxis in the digital humanities. One of her more recent projects is titled "The Codex," a triptych that also functions as an exploration of the Atlantic slave trade by using code and software applications. <br />
<br />
[http://history.jhu.edu/directory/jessica-johnson/]<br />
<br />
[https://lareviewofbooks.org/article/digital-humanities-interview-jessica-marie-johnson/#!]<br />
<br />
[http://dh.jmjafrx.com/]<br />
<br />
== Terry Brady ==<br />
Terry Brady is a software developer in Seattle working for the Georgetown University Library. Terry is the lead developer for DigitalGeorgetown. Terry is a committer for the DSpace repository platform. Terry has built applications for higher education, government, non-profit, and corporate institutions including LexisNexis and the National Archives and Records Administration--including the amazingly handy File-Analyzer. Strengthening communities is a passion of Terry's: he regularly participates in the DSpace Community Advisory Team meetings, and initiated the recent DSpace Users Group meeting hosted by Georgetown University in August of 2017. Terry does what all developers do, he writes code enthusiastically, and many times for no personal advantage, merely because it's work that needs doing, or is an interesting challenge. His work inspires that same approach in others; his observations on the work we all do will be equally inspiring.<br />
<br />
[https://github.com/terrywbrady/info GitHub]<br />
<br />
[https://github.com/Georgetown-University-Libraries/File-Analyzer File-Analyzer]<br />
<br />
[https://repository.library.georgetown.edu/ DigitalGeorgetown]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2018_Keynote_Speakers_Nominations&diff=455062018 Keynote Speakers Nominations2017-09-28T16:20:30Z<p>Hardyoyo: nominated Terry Brady</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2018 in Washington, D.C. will open on '''September 18th''' and close on '''October 15, 2017'''.<br />
<br />
Voting will start on Monday, October 23, 2017 and continue through Monday, November 13, 2017.<br />
<br />
Please include a description and any relevant links and try to keep the list in alphabetical order.<br />
<br />
The criteria for nominating a candidate to act as keynote are below:<br />
*Speaker’s name (First Name, Last Name)<br />
*Brief description of individual (250-word max)<br />
*Pertinent links (Maximum of 3)<br />
*Contact information of candidate (email address)<br />
<br />
''We strongly encourage you to nominate speakers who are local to the D.C. Metropolitan Area.'' <br />
<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><br />
<br />
== Nominee's Name ==<br />
<br />
Description of no more than 250 words.<br />
<br />
[[Link(s) with contact information for nominee]]<br />
<br />
</pre><br />
<br />
__TOC__<br />
<br />
==Jane Doe (example)==<br />
Jane works at ________, doing _______. <br />
<br />
Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.<br />
<br />
==Pamela Wright==<br />
Pamela Wright is the U.S. National Archives' first Chief Innovation Officer. She oversees the Agency's online public access Catalog, web, social media, and authorities programs as well as the Innovation Hub. She has hosted coding communities and worked with other institutions to help the Agency become a more digital, citizen-centric institution. She has a goldmine of content and adores coders who can do interesting and enlightening things with it. She launched the Citizen Archivist Dashboard, which has been a gateway for the public to engage in new ways with our content. She is currently collaborating with staff from the Smithsonian and Library of Congress on History Hub (see link below). <br />
<br />
[https://twitter.com/PamelaSW]<br />
<br />
[https://historyhub.history.gov/welcome]<br />
<br />
[https://www.linkedin.com/in/pamela-wright-8ab59861]<br />
<br />
<br />
==Veni Kunche==<br />
Veni Kunche is a coder, maker, and mentor who works at the U.S. Geological Survey (as a Sr. Software Engineer) and Blasterra (as CEO and Founder). At Blasterra, she focuses on developing programs for people learning to code, but also focuses on teaching women to code. She is based in D.C..<br />
<br />
[https://www.linkedin.com/in/venikunche/ Linkedin]<br />
<br />
[https://twitter.com/venikunche @venikunche]<br />
<br />
[http://www.codewithveni.com/ Code with Veni]<br />
<br />
==Shane Lin==<br />
Senior Developer at the University of Virginia's Scholars' Lab.<br />
<br />
Shane studies the history of computing and the impact of digital technology on culture and politics. His dissertation, “Kingdom of Code: Cryptography and the New Privacy” tracks the development of civilian encryption technology and the emergence of cryptography as an academic field of study, the debates over crypto regulation, and the concomitant construction of a new, far more expansive notion of privacy from 1975 to 2000. His perspectives on technology, encryption, and privacy would be especially interesting to a wide audience. <br />
<br />
<br />
[http://scholarslab.org/people/shane-lin/ Shane Lin]<br />
<br />
[http://scholarslab.org/digital-humanities/the-long-and-messy-history-of-privacy/ Privacy Post]<br />
<br />
==Jessica Marie Johnson==<br />
Jessica Marie Johnson is an assistant professor of history at Johns Hopkins University in Baltimore. Her work is focused around radical black feminist praxis in the digital humanities. One of her more recent projects is titled "The Codex," a triptych that also functions as an exploration of the Atlantic slave trade by using code and software applications. <br />
<br />
[http://history.jhu.edu/directory/jessica-johnson/]<br />
<br />
[https://lareviewofbooks.org/article/digital-humanities-interview-jessica-marie-johnson/#!]<br />
<br />
[http://dh.jmjafrx.com/]<br />
<br />
== Terry Brady ==<br />
Terry Brady is a software developer in Seattle working for the Georgetown University Library. Terry is the lead developer for DigitalGeorgetown. Terry is a committer for the DSpace repository platform. Terry has built applications for higher education, government, non-profit, and corporate institutions including LexisNexis and the National Archives and Records Administration--including the amazingly handy File-Analyzer. Strengthening communities is a passion of Terry's: he regularly participates in the DSpace Community Advisory Team meetings, and initiated the recent DSpace Users Group meeting hosted by Georgetown University in August of 2017. Terry does what all developers do, he writes code enthusiastically, and many times for no personal advantage, merely because it's work that needs doing, or is an interesting challenge. His work inspires that same approach in others; his observations on the work we all do will be equally inspiring.<br />
<br />
[https://github.com/terrywbrady/info GitHub]<br />
[https://github.com/Georgetown-University-Libraries/File-Analyzer File-Analyzer]<br />
[https://repository.library.georgetown.edu/ DigitalGeorgetown]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2017_Social_Activities&diff=449152017 Social Activities2017-03-05T16:42:42Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2017 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== UCLA Library DIIT Open House ===<br />
<br />
Stop by the Charles E. Young Research Library to see activity by the conference host's '''Digital Initiatives and Information Technology''' department.<br />
<br />
'''Details'''<br />
* Monday, March 6th, 4pm-6pm<br />
** drop in; stay as long as you like<br />
* [https://www.library.ucla.edu/events/code4lib-open-house More information]<br />
<br />
=== Newcomer Dinner, Monday, March 6th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, March 6th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''<br />
<br />
'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''<br />
<br />
<br />
=== Conference Reception, Tuesday, March 7th ===<br />
<br />
*When: 3/7/17, 6 pm - 8 pm<br />
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]<br />
<br />
Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].<br />
<br />
=== #LibTechWomen Meet-Up, Wednesday, March 8th ===<br />
<br />
[Please note TIME/LOCATION CHANGE; it will be a cab ride of 30-45 min.] <br />
<br />
* When: Wed. 3/8/17, 6:30 pm - 8:30 pm<br />
* Where: '''Yard House''' <br />
**13455 Maxella Ave, (Villa Marina Marketplace Mall), Marina Del Rey, CA 90292 (310) 822-7690<br />
**We have a HEATED PATIO reserved for "Code for Libraries."<br />
* We will meet at '''5:30 pm at the lobby''' to head out in multiple groups. Feel free to leave earlier to beat the traffic. <br />
* Sign up here: [https://docs.google.com/forms/d/e/1FAIpQLSdZUXThI7bAdjKgL33a2nOpy4uVj2eoEipXDCahwtpqfKtDGA/viewform https://docs.google.com/forms/d/e/1FAIpQLSdZUXThI7bAdjKgL33a2nOpy4uVj2eoEipXDCahwtpqfKtDGA/viewform]<br />
<br />
*Afterwards some of us will go to Play and Share!<br />
<br />
[http://libtechwomen.org/ LibTechWomen] is a supportive space for women and their friends to network, develop skills, build confidence, and lead positive change. Are you a lurker? Are you a newcomer? All are welcome! Come meet wonderful colleagues in library technology!<br />
<br />
=== Play and Share, Wednesday, March 8th ===<br />
<br />
*When: 3/8/17, 6:30 pm - 10:30 pm<br />
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA] <br />
<br />
Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.<br />
<br />
More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!<br />
<br />
====List of Games====<br />
* game title, who will bring it, any other info about the game<br />
<br />
* [http://www.gamewright.com/gamewright/index.php?section=games&page=game&show=260 Gubs], Hardy Pottinger, a friendly easy-to-pick-up game, strategic-ish, not as random as Flux.<br />
* [https://www.fantasyflightgames.com/en/products/android-netrunner-the-card-game/ NetRunner], Hardy Pottinger, I will bring the intro box set, I've never played, Eric Phetteplace has kindly agreed to teach me how to play. Wanna learn, too?<br />
* [https://www.fantasyflightgames.com/en/products/age-of-war/ Age of War], Matt Sherman, a simple dice rolling game of capturing Japanese castles.<br />
* [https://www.fantasyflightgames.com/en/products/arcana-revised-edition/ Arcana], Matt Sherman, a deckbuilding/bidding game of underworld guilds jockeying for power in a fantasy city.<br />
* [https://www.fantasyflightgames.com/en/products/blood-bowl-team-manager/ Blood Bowl: Team Manager], Matt Sherman, a game of fantasy football (i.e. orc and elves) representing managers running their teams trying to get the most fans in a season.<br />
* [http://www.explodingkittens.com/how/ Exploding Kittens], Linda Ballinger, can include Imploding Kittens expansion pack.<br />
* [https://www.boardgamegeek.com/boardgame/152567/basari-das-kartenspiel, Basari: The Card Game], Jon Gorman, A fun quick game where you seek to wheel and deal to get majorities in gems<br />
* [https://www.boardgamegeek.com/boardgame/1107/nyet, Nyet!], Jon Gorman, An interesting trick-taking game played over multiple rounds where each round people determine what the rules will be for the hand. (Note, this is the old 1997 version, not the pretty new one.)<br />
* [https://www.boardgamegeek.com/boardgame/56692/parade, Parade], Jon Gorman, a nice game where you are manipulating a line of cards trying to take the least amount of points possible. (Using a rage deck)<br />
* [https://www.boardgamegeek.com/boardgame/354/sticheln, Sticheln], Jon Gorman, Probably my favorite-trick taking game. Dirt simple: everyone chooses a pain color. Cards taken in that suit are face-value negative points, other cards are single points. (rage deck)<br />
* [https://boardgamegeek.com/boardgame/822/carcassonne Carcassonne], Eric Cahanin, Tile-placing strategy game for 2-5 players. Reasonably quick (45m) and easy to learn.<br />
* [http://www.nintendo.com/games/detail/1-2-switch 1-2 Switch], Steven Carl Anderson, Simple party games played on a tablet screen with detached controller. 2 players at a time but allows a mode for teams that works well for ~6 total players.<br />
* [https://boardgamegeek.com/boardgame/178900/codenames, Codenames], Jon Gorman, team-based game where you're trying to give one clue that will relate to multiple words in a grid.<br />
* [https://boardgamegeek.com/boardgame/161417/red7, Red7], Jon Gorman, A simple card game where you manipulate the rule of the games or the cards out to not be eliminated.<br />
* [http://www.perplext.com/packogame/, Pack o' Game], Jon Gorman, Actually 7 very small and portable games. I've played several of them and wouldn't try playing more.<br />
* [https://boardgamegeek.com/boardgame/98778/hanabi, Hanabi], Jon Gorman, A tricky cooperative game where you can see your teammates cards but not your own and must play them in order.<br />
<br />
== Social Map - Places of Interest==<br />
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
== Ideas ==<br />
Please add your idea with date/time!<br />
If you want to participate, please add your name.<br />
<br />
* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?<br />
* Jog4Lib - [[User:BenWallberg|Ben Wallberg]]<br />
* Trip to Getty<br />
* Hammer Museum<br />
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Thursday afternoon, 2:15 or 4:15 tour, $27)<br />
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure)<br />
<br />
== Local Food and Drink ==<br />
<br />
A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.<br />
<br />
[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.<br />
<br />
<br />
== LA Events ==<br />
<br />
=== Saturday and Sunday, March 4 & 5 ===<br />
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)<br />
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA<br />
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]<br />
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia<br />
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall<br />
<br />
=== Monday, March 6 ===<br />
<br />
=== Tuesday, March 7 ===<br />
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad<br />
<br />
=== Wednesday, March 8 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum<br />
<br />
=== Thursday, March 9 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum<br />
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row<br />
<br />
=== All days ===<br />
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center<br />
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park<br />
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre<br />
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/<br />
<br />
[[Category:Code4Lib2017]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2017_Social_Activities&diff=449142017 Social Activities2017-03-05T16:40:50Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2017 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== UCLA Library DIIT Open House ===<br />
<br />
Stop by the Charles E. Young Research Library to see activity by the conference host's '''Digital Initiatives and Information Technology''' department.<br />
<br />
'''Details'''<br />
* Monday, March 6th, 4pm-6pm<br />
** drop in; stay as long as you like<br />
* [https://www.library.ucla.edu/events/code4lib-open-house More information]<br />
<br />
=== Newcomer Dinner, Monday, March 6th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, March 6th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''<br />
<br />
'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''<br />
<br />
<br />
=== Conference Reception, Tuesday, March 7th ===<br />
<br />
*When: 3/7/17, 6 pm - 8 pm<br />
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]<br />
<br />
Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].<br />
<br />
=== #LibTechWomen Meet-Up, Wednesday, March 8th ===<br />
<br />
[Please note TIME/LOCATION CHANGE; it will be a cab ride of 30-45 min.] <br />
<br />
* When: Wed. 3/8/17, 6:30 pm - 8:30 pm<br />
* Where: '''Yard House''' <br />
**13455 Maxella Ave, (Villa Marina Marketplace Mall), Marina Del Rey, CA 90292 (310) 822-7690<br />
**We have a HEATED PATIO reserved for "Code for Libraries."<br />
* We will meet at '''5:30 pm at the lobby''' to head out in multiple groups. Feel free to leave earlier to beat the traffic. <br />
* Sign up here: [https://docs.google.com/forms/d/e/1FAIpQLSdZUXThI7bAdjKgL33a2nOpy4uVj2eoEipXDCahwtpqfKtDGA/viewform https://docs.google.com/forms/d/e/1FAIpQLSdZUXThI7bAdjKgL33a2nOpy4uVj2eoEipXDCahwtpqfKtDGA/viewform]<br />
<br />
*Afterwards some of us will go to Play and Share!<br />
<br />
[http://libtechwomen.org/ LibTechWomen] is a supportive space for women and their friends to network, develop skills, build confidence, and lead positive change. Are you a lurker? Are you a newcomer? All are welcome! Come meet wonderful colleagues in library technology!<br />
<br />
=== Play and Share, Wednesday, March 8th ===<br />
<br />
*When: 3/8/17, 6:30 pm - 10:30 pm<br />
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA] <br />
<br />
Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.<br />
<br />
More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!<br />
<br />
====List of Games====<br />
* game title, who will bring it, any other info about the game<br />
<br />
* [http://www.gamewright.com/gamewright/index.php?section=games&page=game&show=260 Gubs], Hardy Pottinger, a friendly easy-to-pick-up game, strategic-ish, not as random as Flux.<br />
* NetRunner, Hardy Pottinger, I will bring the intro box set, I've never played, Eric Phetteplace has kindly agreed to teach me how to play. Wanna learn, too?<br />
* [https://www.fantasyflightgames.com/en/products/age-of-war/ Age of War], Matt Sherman, a simple dice rolling game of capturing Japanese castles.<br />
* [https://www.fantasyflightgames.com/en/products/arcana-revised-edition/ Arcana], Matt Sherman, a deckbuilding/bidding game of underworld guilds jockeying for power in a fantasy city.<br />
* [https://www.fantasyflightgames.com/en/products/blood-bowl-team-manager/ Blood Bowl: Team Manager], Matt Sherman, a game of fantasy football (i.e. orc and elves) representing managers running their teams trying to get the most fans in a season.<br />
* [http://www.explodingkittens.com/how/ Exploding Kittens], Linda Ballinger, can include Imploding Kittens expansion pack.<br />
* [https://www.boardgamegeek.com/boardgame/152567/basari-das-kartenspiel, Basari: The Card Game], Jon Gorman, A fun quick game where you seek to wheel and deal to get majorities in gems<br />
* [https://www.boardgamegeek.com/boardgame/1107/nyet, Nyet!], Jon Gorman, An interesting trick-taking game played over multiple rounds where each round people determine what the rules will be for the hand. (Note, this is the old 1997 version, not the pretty new one.)<br />
* [https://www.boardgamegeek.com/boardgame/56692/parade, Parade], Jon Gorman, a nice game where you are manipulating a line of cards trying to take the least amount of points possible. (Using a rage deck)<br />
* [https://www.boardgamegeek.com/boardgame/354/sticheln, Sticheln], Jon Gorman, Probably my favorite-trick taking game. Dirt simple: everyone chooses a pain color. Cards taken in that suit are face-value negative points, other cards are single points. (rage deck)<br />
* [https://boardgamegeek.com/boardgame/822/carcassonne Carcassonne], Eric Cahanin, Tile-placing strategy game for 2-5 players. Reasonably quick (45m) and easy to learn.<br />
* [http://www.nintendo.com/games/detail/1-2-switch 1-2 Switch], Steven Carl Anderson, Simple party games played on a tablet screen with detached controller. 2 players at a time but allows a mode for teams that works well for ~6 total players.<br />
* [https://boardgamegeek.com/boardgame/178900/codenames, Codenames], Jon Gorman, team-based game where you're trying to give one clue that will relate to multiple words in a grid.<br />
* [https://boardgamegeek.com/boardgame/161417/red7, Red7], Jon Gorman, A simple card game where you manipulate the rule of the games or the cards out to not be eliminated.<br />
* [http://www.perplext.com/packogame/, Pack o' Game], Jon Gorman, Actually 7 very small and portable games. I've played several of them and wouldn't try playing more.<br />
* [https://boardgamegeek.com/boardgame/98778/hanabi, Hanabi], Jon Gorman, A tricky cooperative game where you can see your teammates cards but not your own and must play them in order.<br />
<br />
== Social Map - Places of Interest==<br />
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
== Ideas ==<br />
Please add your idea with date/time!<br />
If you want to participate, please add your name.<br />
<br />
* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?<br />
* Jog4Lib - [[User:BenWallberg|Ben Wallberg]]<br />
* Trip to Getty<br />
* Hammer Museum<br />
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Thursday afternoon, 2:15 or 4:15 tour, $27)<br />
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure)<br />
<br />
== Local Food and Drink ==<br />
<br />
A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.<br />
<br />
[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.<br />
<br />
<br />
== LA Events ==<br />
<br />
=== Saturday and Sunday, March 4 & 5 ===<br />
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)<br />
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA<br />
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]<br />
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia<br />
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall<br />
<br />
=== Monday, March 6 ===<br />
<br />
=== Tuesday, March 7 ===<br />
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad<br />
<br />
=== Wednesday, March 8 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum<br />
<br />
=== Thursday, March 9 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum<br />
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row<br />
<br />
=== All days ===<br />
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center<br />
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park<br />
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre<br />
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/<br />
<br />
[[Category:Code4Lib2017]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2017_Social_Activities&diff=448292017 Social Activities2017-02-23T04:33:44Z<p>Hardyoyo: added two games</p>
<hr />
<div>= Code4Lib 2017 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Monday, March 6th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, March 6th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''<br />
<br />
'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''<br />
<br />
<br />
=== Conference Reception, Tuesday, March 7th ===<br />
<br />
*When: 3/7/17, 6 pm - 8 pm<br />
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]<br />
<br />
Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].<br />
<br />
=== Play and Share, Wednesday, March 8th ===<br />
<br />
*When: 3/8/17, 6:30 pm - 10:30 pm<br />
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA] <br />
<br />
Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.<br />
<br />
More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!<br />
<br />
====List of Games====<br />
* game title, who will bring it, any other info about the game<br />
<br />
* [http://www.gamewright.com/gamewright/index.php?section=games&page=game&show=260 Gubs], Hardy Pottinger, a friendly easy-to-pick-up game, strategic-ish, not as random as Flux.<br />
* Magic The Gathering, Hardy Pottinger, some random intro deck, not brilliant, parent-class (presents enough challenge to keep all players amused, but if you play at all, you'll beat it).<br />
<br />
====List of Goodies====<br />
* brand, flavor, allergen alerts (if any)<br />
<br />
== Social Map - Places of Interest==<br />
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
== Ideas ==<br />
Please add your idea with date/time!<br />
If you want to participate, please add your name.<br />
<br />
* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?<br />
* Jog4Lib<br />
* Trip to Getty<br />
* Hammer Museum<br />
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Date/Time unsure)<br />
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure)<br />
<br />
== Local Food and Drink ==<br />
<br />
A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.<br />
<br />
[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.<br />
<br />
<br />
== LA Events ==<br />
<br />
=== Saturday and Sunday, March 4 & 5 ===<br />
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)<br />
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA<br />
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]<br />
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia<br />
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall<br />
<br />
=== Monday, March 6 ===<br />
<br />
=== Tuesday, March 7 ===<br />
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad<br />
<br />
=== Wednesday, March 8 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum<br />
<br />
=== Thursday, March 9 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum<br />
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row<br />
<br />
=== All days ===<br />
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center<br />
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park<br />
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre<br />
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/<br />
<br />
[[Category:Code4Lib2017]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2017_Social_Activities&diff=448282017 Social Activities2017-02-23T04:24:00Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2017 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Monday, March 6th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, March 6th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''<br />
<br />
'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''<br />
<br />
<br />
=== Conference Reception, Tuesday, March 7th ===<br />
<br />
*When: 3/7/17, 6 pm - 8 pm<br />
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]<br />
<br />
Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].<br />
<br />
=== Play and Share, Wednesday, March 8th ===<br />
<br />
*When: 3/8/17, 6:30 pm - 10:30 pm<br />
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA] <br />
<br />
Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.<br />
<br />
More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!<br />
<br />
====List of Games====<br />
* game title, who will bring it, any other info about the game<br />
<br />
====List of Goodies====<br />
* brand, flavor, allergen alerts (if any)<br />
<br />
== Social Map - Places of Interest==<br />
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
== Ideas ==<br />
Please add your idea with date/time!<br />
If you want to participate, please add your name.<br />
<br />
* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?<br />
* Jog4Lib<br />
* Trip to Getty<br />
* Hammer Museum<br />
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Date/Time unsure)<br />
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardy Pottinger (Date/Time unsure)<br />
<br />
== Local Food and Drink ==<br />
<br />
A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.<br />
<br />
[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.<br />
<br />
<br />
== LA Events ==<br />
<br />
=== Saturday and Sunday, March 4 & 5 ===<br />
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)<br />
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA<br />
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]<br />
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia<br />
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall<br />
<br />
=== Monday, March 6 ===<br />
<br />
=== Tuesday, March 7 ===<br />
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad<br />
<br />
=== Wednesday, March 8 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum<br />
<br />
=== Thursday, March 9 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum<br />
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row<br />
<br />
=== All days ===<br />
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center<br />
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park<br />
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre<br />
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/<br />
<br />
[[Category:Code4Lib2017]]</div>Hardyoyohttps://wiki.code4lib.org/index.php?title=2017_Social_Activities&diff=448272017 Social Activities2017-02-23T04:22:57Z<p>Hardyoyo: </p>
<hr />
<div>= Code4Lib 2017 Social Activities =<br />
<br />
The Social Activities Group is working on several events and social opportunities for after conference hours. We will be adding more events as they come along. Watch this page!<br />
<br />
Also, if you find a cool event to go to, and want to share the wealth with others, feel free to add the event to the page. :)<br />
<br />
== Planned Events ==<br />
<br />
=== Newcomer Dinner, Monday, March 6th ===<br />
<br />
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating <strike>discussions about</strike> demonstrations of the many uses of <strike>bacon</strike> <strike>XML</strike> <strike>EZProxy</strike> <strike>LibGuides alternatives</strike> <strike>spreadsheets</strike> documentation.<br />
<br />
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!<br />
<br />
'''Plans'''<br />
* When: Monday, March 6th<br />
* Suggested Time: 6 PM (ish) or whenever you can get your group together<br />
* Mastermind (if you have any questions): [mailto:becky.yoose@spl.org Becky Yoose]<br />
<br />
''Guidelines:''<br />
*Max of '''6''' per group<br />
**Please, no waitlisting<br />
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.<br />
*ID yourselves so we can get a good mix of new people and veterans in each group<br />
**New folks - n<br />
**c4l vets - v<br />
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')<br />
**Leader duties<br />
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks<br />
***Herd folks from hotel to restaurant (know where you're going!)<br />
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''<br />
<br />
'''NB! This year's Newcomer Dinner options are not close to the convention center and hotel. You will most likely be relying on public transportation, taxis, or ride-sharing services to get to your destination. Please plan accordingly.'''<br />
<br />
'''[http://2017.code4lib.org/venue/dinner.html Restaurant list, sign ups, and transportation information now available!]'''<br />
<br />
<br />
=== Conference Reception, Tuesday, March 7th ===<br />
<br />
*When: 3/7/17, 6 pm - 8 pm<br />
*Where: [http://www.fowler.ucla.edu/ Fowler Museum, UCLA]<br />
<br />
Enjoy several of the museum's galleries and spaces while getting a chance to meet other attendees outside of the conference room. Light hors d'oeuvres and drinks will be provided. More information about what exhibits will be open can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website].<br />
<br />
=== Play and Share, Wednesday, March 8th ===<br />
<br />
*When: 3/8/17, 6:30 pm - 10:30 pm<br />
*Where: [http://maps.ucla.edu/campus/?locid=268 Kerckhoff Hall, UCLA] <br />
<br />
Play games? Have some homemade (or “homemade”) treats to share? Want to find folks to play music with? We organized a large open room near the conference center with plenty of space for attendees to gather and socialize, play games and share goodies. We will provide tables and chairs for Board Game Night and some space for jam sessions. You are also welcome to bring stuff to share, from craft sodas and beers to baked goods to local treats - we’ll have a few tables set up for that as well.<br />
<br />
More venue information can be found on the [http://2017.code4lib.org/venue/reception.html Code4Lib website]. If you plan to bring something to play or share, please sign up below!<br />
<br />
====List of Games====<br />
* game title, who will bring it, any other info about the game<br />
<br />
====List of Goodies====<br />
* brand, flavor, allergen alerts (if any)<br />
<br />
== Social Map - Places of Interest==<br />
For a visual-ish view of recommended food, drink, and activities in LA, please visit this awesome [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
== Ideas ==<br />
Please add your idea with date/time!<br />
If you want to participate, please add your name.<br />
<br />
* More formalized outing to [http://www.getty.edu/visit/center/plan/ The Getty Center] on Sunday and/or Thursday afternoon?<br />
* Jog4Lib<br />
* Trip to Getty<br />
* Hammer Museum<br />
* [http://queenmary.com/tours-exhibits/tour-packages/queen-mary-passport/ Queen Mary Tour] -Chad Kluck (Date/Time unsure)<br />
* [http://mjt.org/ Museum of Jurassic Technology] ~Hardyoyo (Date/Time unsure)<br />
<br />
== Local Food and Drink ==<br />
<br />
A more visual list of food and drink places can be found on the [https://drive.google.com/open?id=11dBRFfMhYump8B5nCznsx-iVFVs&usp=sharing Google Map].<br />
<br />
[https://www.google.com/maps/d/viewer?mid=1jHOjCIJFMhfxNJy_XGhqZk6AHow&usp=sharing Where To Eat at UCLA] — a guide to food on campus.<br />
<br />
[https://www.zomato.com/los-angeles/restaurants/near/ucla Zomato] —The 200 or so restaurants and coffee shops in and around Westwood, sorted by distance.<br />
<br />
<br />
== LA Events ==<br />
<br />
=== Saturday and Sunday, March 4 & 5 ===<br />
*Saturday only - [http://www.printmuseum.org/ International Printing Museum] (You can also make an appointment during the week to see the museum!)<br />
*Saturday only - [http://cap.ucla.edu/calendar/details/jose_gonzalez_2017 José González & The Göteborg String Theory], Royce Hall, UCLA<br />
*Sunday only - [http://la.smorgasburg.com/ Smorgasburg, L.A.]<br />
*[http://www.discoverlosangeles.com/what-to-do/events/white-guy-bus-bruce-graham White Guy on The Bus], The Road on Magnolia<br />
*[http://laphil.org/tickets/adams-70-nixon-china/2017-03-05 Nixon in China, Los Angeles Philharmonic] John Adams conducts, at Walt Disney Concert Hall<br />
<br />
=== Monday, March 6 ===<br />
<br />
=== Tuesday, March 7 ===<br />
*[http://cap.ucla.edu/calendar/details/trisha_brown_17 Trisha Brown Dance Company - In Plain Site:LA], The Broad<br />
<br />
=== Wednesday, March 8 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/incident-at-oglala/ Incident at Oglala], Hammer Museum<br />
<br />
=== Thursday, March 9 ===<br />
*[https://hammer.ucla.edu/programs-events/2017/03/the-politics-and-problematics-of-representation/ The Politics and Problematics of Representation], Hammer Museum<br />
*[http://downtownartwalk.org/ Downtown LA Art Walk], Gallery Row<br />
<br />
=== All days ===<br />
*[http://www.getty.edu/art/exhibitions/breaking_news/index.html Breaking News: Turning the Lends on Mass Media], Getty Center<br />
*[http://www.laweekly.com/event/david-bowie-among-the-mexican-masters-7852901 David Bowie: Among the Mexican Masters], Forest Lawn Memorial Park<br />
*[https://www.centertheatregroup.org/tickets/ahmanson-theatre/2016-17/fun-home/ Fun Home], Ahmanson Theatre<br />
*[https://www.centertheatregroup.org/tickets/mark-taper-forum/2017-18/zoot-suit/ Zoot Suit] Mark Taper Forum<br />
<br />
==Getting Around==<br />
All info on getting to the hotel is on the conference website: http://2017.code4lib.org/venue/<br />
<br />
[[Category:Code4Lib2017]]</div>Hardyoyo