<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akorphan</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Akorphan"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/Akorphan"/>
		<updated>2026-05-28T03:01:39Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49129</id>
		<title>Code4Lib 2026 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49129"/>
				<updated>2026-02-26T14:30:06Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2026_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out during the Code4Lib 2026 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2026.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Monday, day one:&lt;br /&gt;
* Amy Rodriguez&lt;br /&gt;
* Doreen Chen&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* Emily Lynema&lt;br /&gt;
* Maureen Cresci Callahan&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One ([https://2026.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two ([https://2026.code4lib.org/general-info/social/#game-night Game Night]):&lt;br /&gt;
* Matt Sherman&lt;br /&gt;
* James Truitt&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three ([https://2026.code4lib.org/general-info/social/ Social Activities TBD]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l26), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Richard Higgins''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Richard Higgins''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: '''Brian Maass''' - US Central Time zone - ''brian.maass@unmc.edu'' &lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): '''Brian Maass''' - US Central Time zone - ''brian.maass@unmc.edu'' &lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: Matt Sherman&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Kate Deibel&lt;br /&gt;
*  PM Volunteer: Eric Hellman&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: Dre (unless someone else would like to do it; no seconds until everybody gets firsts)&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Jim Kammerer''&lt;br /&gt;
*  PM Volunteer: ''Celia Gavett''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Baowei''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* Matt Sherman&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2026]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49128</id>
		<title>Code4Lib 2026 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49128"/>
				<updated>2026-02-26T14:28:29Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2026_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out during the Code4Lib 2026 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2026.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Monday, day one:&lt;br /&gt;
* Amy Rodriguez&lt;br /&gt;
* Doreen Chen&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* Emily Lynema&lt;br /&gt;
* Maureen Cresci Callahan&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One ([https://2026.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two ([https://2026.code4lib.org/general-info/social/#game-night Game Night]):&lt;br /&gt;
* Matt Sherman&lt;br /&gt;
* James Truitt&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three ([https://2026.code4lib.org/general-info/social/ Social Activities TBD]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l26), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Richard Higgins''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Richard Higgins''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Trip Kirkpatrick''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: '''Brian Maass''' - US Central Time zone - ''brian.maass@unmc.edu'' &lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): '''Brian Maass''' - US Central Time zone - ''brian.maass@unmc.edu'' &lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: Matt Sherman&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Kate Deibel&lt;br /&gt;
*  PM Volunteer: Eric Hellman&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: Dre (unless someone else would like to do it; no seconds until every gets firsts)&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Jim Kammerer''&lt;br /&gt;
*  PM Volunteer: ''Celia Gavett''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Baowei''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* Matt Sherman&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2026]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49070</id>
		<title>Code4Lib 2026 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49070"/>
				<updated>2026-01-14T17:27:02Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2026_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out during the Code4Lib 2026 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2026.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Monday, day one:&lt;br /&gt;
* Amy Rodriguez&lt;br /&gt;
* Doreen Chen&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One ([https://2026.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two ([https://2026.code4lib.org/general-info/venues/#reception Reception]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three ([https://2026.code4lib.org/general-info/social/#tours Tours], [https://2025.code4lib.org/general-info/social/#game-night Game Night]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l26), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2026]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49069</id>
		<title>Code4Lib 2026 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&amp;diff=49069"/>
				<updated>2026-01-14T17:26:41Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2026_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out during the Code4Lib 2026 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2026.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Monday, day one:&lt;br /&gt;
* Amy Rodriguez&lt;br /&gt;
* Doreen Chen&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One ([https://2026.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two ([https://2026.code4lib.org/general-info/venues/#reception Reception]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three ([https://2026.code4lib.org/general-info/social/#tours Tours], [https://2025.code4lib.org/general-info/social/#game-night Game Night]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l26), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Dre''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]]&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2026]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Committees&amp;diff=48768</id>
		<title>Code4Lib 2026 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Committees&amp;diff=48768"/>
				<updated>2025-08-07T20:11:35Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Program Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib  Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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 2026 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 Chair, Primary Contact&lt;br /&gt;
&lt;br /&gt;
==Planning Committee==&lt;br /&gt;
Also known as the Local Planning Committee, although there is no requirement for the members to be local.&lt;br /&gt;
&lt;br /&gt;
[[2026 Planning Committee Documents|2026 Planning Committee Documents]]&lt;br /&gt;
&lt;br /&gt;
* Ann Marie Mesco - Primary Contact, Chair&lt;br /&gt;
* Ken Rose - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Erin Swift - Volunteer&lt;br /&gt;
* Joelen Pastva - Volunteer&lt;br /&gt;
* Lina Crowe - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2026 Website Working Group Documents|2026 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[2026 Budget and Sponsorship Documents]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Andromeda Yelton, Chair ''if someone else really wants to chair hit me up; I've done this a few times and I'm happy to do it again but I'm also happy to share the opportunity''&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Workshop Committee (Pre / Post-Conference)==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2026 Pre-conference Documents|2026 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2026 Program Documents|2026 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Dre - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Community Support Squad (CSS) ==&lt;br /&gt;
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://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2026 T-Shirt Documents|2026 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2026 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2026 Online Volunteer Documents|2026 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
2026 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2027 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2026 Host Voting Documents|2026 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees.&lt;br /&gt;
&lt;br /&gt;
[[2026 Accessibility Documents|2026 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2026 Whatever Documents|2026 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2026]]&lt;br /&gt;
[[Category:Conference Committees]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2025_Conference_Volunteers&amp;diff=48680</id>
		<title>2025 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2025_Conference_Volunteers&amp;diff=48680"/>
				<updated>2025-03-03T19:44:59Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2025_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out during the Code4Lib 2025 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2025.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Monday, day one:&lt;br /&gt;
* Kurt Lemai-Nguyen&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One ([https://2025.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two ([https://2025.code4lib.org/general-info/venues/#reception Reception]):&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three ([https://2025.code4lib.org/general-info/social/#tours Tours], [https://2025.code4lib.org/general-info/social/#game-night Game Night]):&lt;br /&gt;
* Kurt Lemai-Nguyen (tours)&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l25), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
* AM Volunteer: ''Your Name Here''&lt;br /&gt;
* PM volunteer: ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
* Backup volunteer (all day): ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* Mike Kastellec&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2025]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&amp;diff=48338</id>
		<title>2024 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&amp;diff=48338"/>
				<updated>2024-03-04T17:27:55Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2024 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: Hardy Pottinger&lt;br /&gt;
&lt;br /&gt;
12 Noon - 1pm Monday, day one:&lt;br /&gt;
* Hardy Pottinger&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Tuesday, day two:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Workshop Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM Volunteer: Dre&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: Hardy Pottinger&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2024]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2024_Conference_Committees&amp;diff=48151</id>
		<title>Code4Lib 2024 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2024_Conference_Committees&amp;diff=48151"/>
				<updated>2023-05-25T16:47:40Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2024 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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 2024 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 Chair, Primary Contact&lt;br /&gt;
&lt;br /&gt;
==Planning Committee==&lt;br /&gt;
Also known as the Local Planning Committee, although there is no requirement for the members to be local.&lt;br /&gt;
&lt;br /&gt;
[[2024 Planning Committee Documents|2024 Planning Committee Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Documentarian &amp;amp; Secondary Contact&lt;br /&gt;
* Your Name Here - Tertiary Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2024 Website Working Group Documents|2024 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Esmé Cowles - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Accessibility Committee Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here -Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2024 Budget and Sponsorship Documents|2024 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[https://drive.google.com/drive/u/1/folders/1BvNAQ0J_a9COYrrkLrofsz6qBkf_3JeH Keynote Documents] -- this is a Google Drive folder which has templates for all the communications you need to send, READMEs, an overview of our timeline, etc. It should cover what you need to run the process; just add committee members and stir. It's access-restricted; you can get sharing permissions from Andromeda Yelton Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here -Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2024 Pre-conference Documents|2024 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer, grip, and all-around lackey &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2024 Program Documents|2024 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Matt Sherman - Volunteer&lt;br /&gt;
* Dre - Volunteer&lt;br /&gt;
* [[User:highermath|Cary Gordon]] - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarshipPrimary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Community Support Squad (CSS) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''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).&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2024 T-Shirt Documents|2024 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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 Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - LPC Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2025 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2025 Host Voting Documents|2025 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees.&lt;br /&gt;
&lt;br /&gt;
[[2024 Accessibility Documents|2024 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2024 Whatever Documents|2024 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact, Chair&lt;br /&gt;
* Your Name Here - Secondary Contact, CoChair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2024]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib2023_Breakout_Sessions&amp;diff=48099</id>
		<title>Code4Lib2023 Breakout Sessions</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib2023_Breakout_Sessions&amp;diff=48099"/>
				<updated>2023-03-14T12:49:23Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Day 2 - March 16, 2023 ==&lt;br /&gt;
* ArchivesSpace API and Development Meetup - in First common area until further notice&lt;br /&gt;
* How to Defend Yourself against a Dagger-Armed Brigand in Quattrocento Italy&lt;br /&gt;
&lt;br /&gt;
== Day 3 - March 17, 2023 ==&lt;br /&gt;
* Your Idea Here&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&amp;diff=48080</id>
		<title>2023 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&amp;diff=48080"/>
				<updated>2023-03-08T23:11:31Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2023 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &amp;quot;LOCAL&amp;quot; tag&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: Hardy Pottinger&lt;br /&gt;
&lt;br /&gt;
8am - 9am Wednesday, day one:&lt;br /&gt;
* Hardy Pottinger&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
8am - 9am Thursday, day two:&lt;br /&gt;
* Hardy Pottinger&lt;br /&gt;
* Hector Correa&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
* 7am Run/Walk organizer: Eric Hellman&lt;br /&gt;
* 11pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
* 11pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Tuesday, Preconference Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM volunteer: Maccabee Levine&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: Hector Correa&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: Heather Greer Klein&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM volunteer: Maccabee Levine&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: Eric Hellman&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM Volunteer: Trey Pendragon&lt;br /&gt;
*  PM Volunteer: Hardy Pottinger&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
* Craig Rosenbeck&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
podium tech help:&lt;br /&gt;
&lt;br /&gt;
* ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2023]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&amp;diff=47875</id>
		<title>Code4Lib 2023 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&amp;diff=47875"/>
				<updated>2022-09-07T19:52:00Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: prog com vol&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2023 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Princeton University&lt;br /&gt;
* Dates: TBD&lt;br /&gt;
&lt;br /&gt;
== Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact&lt;br /&gt;
* Esmé Cowles - (escowles@princeton.edu) - Documentarian &amp;amp; Secondary Contact&lt;br /&gt;
* NAME - (EMAIL) - Tertiary Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2023 Website Working Group Documents|2023 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Keynote Documents|2023 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Pre-conference Documents|2023 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Program Documents|2023 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Dre (akorphan) - Volunteer&lt;br /&gt;
* Matt Sherman - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Scholarship Documents|2023 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Community Support Squad (CSS) ==&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
* Coordinator: &lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 T-Shirt Documents|2023 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Streaming Video Documents|2023 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2023 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2023 Host Voting Documents|2023 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees.&lt;br /&gt;
&lt;br /&gt;
[[2023 Accessibility Documents|2023 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2023 Whatever Documents|2023 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2023]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&amp;diff=47874</id>
		<title>Code4Lib 2023 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&amp;diff=47874"/>
				<updated>2022-09-07T19:48:08Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2023 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Princeton University&lt;br /&gt;
* Dates: TBD&lt;br /&gt;
&lt;br /&gt;
== Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact&lt;br /&gt;
* Esmé Cowles - (escowles@princeton.edu) - Documentarian &amp;amp; Secondary Contact&lt;br /&gt;
* NAME - (EMAIL) - Tertiary Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2023 Website Working Group Documents|2023 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Keynote Documents|2023 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Pre-conference Documents|2023 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Program Documents|2023 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Dre - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Scholarship Documents|2023 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Community Support Squad (CSS) ==&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
* Coordinator: &lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 T-Shirt Documents|2023 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2023 Streaming Video Documents|2023 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2023 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2023 Host Voting Documents|2023 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees.&lt;br /&gt;
&lt;br /&gt;
[[2023 Accessibility Documents|2023 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2023 Whatever Documents|2023 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* NAME - (EMAIL) - Primary Contact, Chair&lt;br /&gt;
* NAME - (EMAIL) - Secondary Contact, CoChair&lt;br /&gt;
* NAME - (EMAIL) - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2023]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2022_Conference_Committees&amp;diff=47733</id>
		<title>Code4Lib 2022 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2022_Conference_Committees&amp;diff=47733"/>
				<updated>2021-09-14T19:36:58Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Program Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2022 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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 2022 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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Your Name Here -conferences: &lt;br /&gt;
&lt;br /&gt;
== Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact&lt;br /&gt;
* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact&lt;br /&gt;
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian, Secondary Contact, Tertiary Contact&lt;br /&gt;
* Francis Kayiwa - (kayiwa@princeton.edu) - Tertiary Contact&lt;br /&gt;
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact&lt;br /&gt;
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact&lt;br /&gt;
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact&lt;br /&gt;
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2022 Website Working Group Documents|2022 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* - ex officio, fiscal host (CLIR/DLF)&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Keynote Documents|2022 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Francis Kayiwa - (kayiwa@princeton.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Daricus Larry (dlarry@arizona.edu) - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Pre-conference Documents|2022 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Rose Orcutt - (rmorcutt@buffalo.edu) - Documentarian/Planning Committee Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Program Documents|2022 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Daricus Larry (dlarry@arizona.edu) - Secondary Contact AKA CoChair&lt;br /&gt;
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Matt Sherman (matt.r.sherman@gmail.com) - Volunteer&lt;br /&gt;
* Dre (akorphan@ncsu.edu) - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Scholarship Documents|2022 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Community Support Squad (CSS) ==&lt;br /&gt;
This group enforces [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.&lt;br /&gt;
&lt;br /&gt;
'''Community Support Volunteers'''&lt;br /&gt;
&lt;br /&gt;
[[2022 Community Support Documents|2022 Community Support Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Co-Coordinator&lt;br /&gt;
* Your Name Here - Co-Coordinator&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 T-Shirt Documents|2022 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2022 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes virtual social activities.&lt;br /&gt;
&lt;br /&gt;
2022 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2022 Streaming Video Documents|2022 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2023 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2023 Host Voting Documents|2023 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Planning Committee Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Daricus Larry (dlarry@arizona.edu) - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees.&lt;br /&gt;
&lt;br /&gt;
[[2022 Accessibility Documents|2022 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2022 Whatever Documents|2022 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2022]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2021_Keynote_Speakers_Nominations&amp;diff=47556</id>
		<title>2021 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2021_Keynote_Speakers_Nominations&amp;diff=47556"/>
				<updated>2020-11-12T15:00:56Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Chuck Pell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2021 will take place March 22nd through March 26th 2021.&lt;br /&gt;
&lt;br /&gt;
''As the conference will be virtual this year, we encourage '''all''' nominations -- including those from international venues.'' &lt;br /&gt;
&lt;br /&gt;
'''We will be accepting nominations from November 10, 2020 until November 25, 2020.'''&lt;br /&gt;
&lt;br /&gt;
Please include a description and any relevant links. Please try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
[mailto:email_link.foo nominee's email address]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
[mailto:jane@nowhere.foo janes_email_address]&lt;br /&gt;
&lt;br /&gt;
==Cecily Walker==&lt;br /&gt;
&lt;br /&gt;
Cecily Walker is the Assistant Manager for Community Digital Initiatives &amp;amp; eLearning at Vancouver Public Library.  Her work centers on user experience, communications, marketing of library services, community digital initiatives, open data, content strategy, transforming the role of librarians and information professionals, and investigating the intersection of social issues, technology, and public librarianship. She is a leading thinker of the intersections on technologies, librarianship and the public good. I believe her work, thoughts and perspective will resonate with Code4Lib attendees.&lt;br /&gt;
&lt;br /&gt;
[https://cecily.info/ website]&lt;br /&gt;
&lt;br /&gt;
[https://circulatingideas.com/transcripts/cecily-walker/ podcast conversation]&lt;br /&gt;
&lt;br /&gt;
[https://www.vala.org.au/conferences/vala2020/conference-program/keynote-speakers/#cecilywalker past keynote speaker]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:cecily@cecily.info Cecily's email address]&lt;br /&gt;
&lt;br /&gt;
== Rudo Kemper ==&lt;br /&gt;
&lt;br /&gt;
Gave an outstanding talk at [https://csvconf.com/ csv,conf,v5] about working with South American indigenous communities to map &amp;amp; safeguard their stories using the open source project [https://terrastories.io/ Terrastories] ([https://youtu.be/j-mDnMjDnq4 talk is here]) . It covered issues of pure tech (architecting around limited internet access), participatory design (building a tool that was useful for the people in question to advance causes that matter to them), indigenous knowledge rights, tech as tool for political advocacy -- this talk was everything. He's on the board of https://native-land.ca/, works for https://www.digital-democracy.org/, studied human geography, and contributes code &amp;amp; docs to Terrastories as well as having worked on the ground in the Amazon.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/rudokemper Twitter @rudokemper]&lt;br /&gt;
&lt;br /&gt;
[mailto:rkemper@digital-democracy.org email]&lt;br /&gt;
&lt;br /&gt;
== Regina Gong ==&lt;br /&gt;
&lt;br /&gt;
Regina Gong is the Open Educational Resources (OER) &amp;amp; Student Success Librarian at Michigan State University (MSU) Libraries. Before joining MSU, Regina was the OER Project Manager at Lansing Community College (LCC) where she led a very successful OER initiative. Regina is well-known in the open education community and has done numerous national presentations and webinars on OER. She is a staunch advocate of openness, equity, and access through her involvement on the SPARC Open Education Advisory Group(link is external) (2019-2022), SPARC Steering Committee(link is external), and Executive Council member of the Community College Consortium for Open Educational Resources (CCCOER)(link is external) where she served as VP for professional development. She is also in the MI Statewide OER Steering Committee(link is external); 2019 Open Education Conference Program Committee(link is external), and an OER Research Group Fellow(link is external). Regina obtained her Masters in Library and Information Science (MLIS) at Wayne State University and is currently pursuing Ph.D. in the Higher, Adult, and Lifelong Education (HALE) Program at Michigan State University (MSU). I believe that Regina Gong will bring an important viewpoint related to open education and access and the role of libraries/museums of all types to consider.&lt;br /&gt;
&lt;br /&gt;
[https://sparcopen.org/news/2019/regina-gong-championing-oer-at-community-colleges/ Work championing open education]&lt;br /&gt;
[https://www.amigos.org/node/6013 past keynote]&lt;br /&gt;
[https://www.linkedin.com/in/regina-gong-37592164/ Linkedin profile]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:gongregi@msu.edu email]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alex Gil ==&lt;br /&gt;
&lt;br /&gt;
Alex Gil is the Digital Scholarship Librarian at Columbia University Libraries. He collaborates with faculty, students and library professionals leveraging computational and network technologies in humanities research, pedagogy and knowledge production. He coordinates the Butler Library Studio at Columbia University, a tech-light library innovation space focused on digital scholarship and pedagogy; co-founder and moderator of Columbia’s Group for Experimental Methods in the Humanities, a vibrant trans-disciplinary research cluster focused on experimental humanities; senior editor of sx archipelagos, a journal of Caribbean Digital Studies, and co-wrangler of The Caribbean Digital conference series. He is also founder and former chair of Global Outlook:Digital Humanities. Active digital projects include Ed, a digital platform for minimal editions of literary texts, and Wax for minimal exhibits of cultural artifacts; In The Same Boats, a visualization of trans-Atlantic intersections of black intellectuals in the 20th century; and most recently, the nimble tent interventions Torn Apart/Separados and Covid Maker Response. His projects are very exciting and can provide important discussions on global framework in network technologies. &lt;br /&gt;
&lt;br /&gt;
[https://www.elotroalex.com/profile/ Profile]&lt;br /&gt;
[https://studio.cul.columbia.edu/ Project]&lt;br /&gt;
[https://www.libraryjournal.com/?detailStory=alex-gil-movers-shakers-2020%E2%80%93change-agents LJ's Mover and Shaker Profile]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:agil@columbia.edu email]&lt;br /&gt;
&lt;br /&gt;
== Tatiana Mac ==&lt;br /&gt;
&lt;br /&gt;
Tatiana Mac (she/they) is an independent American engineer. She is an open source maintainer who created and is building Self-Defined, a modern dictionary about us; and Devs of Colour, a database that will prioritise finding undiscovered Black/brown talent through a thoughtful search algorithm.&lt;br /&gt;
As a consultant, she works directly with organisations to build clear and coherent products and design systems.&lt;br /&gt;
An international keynote speaker, she speaks on the intersection of technology and ethics, examining how our products both fit and define our social and environmental settings. You can view her recorded talks on YouTube.&lt;br /&gt;
She believes the trifecta of accessibility, performance, and inclusion can work symbiotically to improve our social landscape digitally and physically. When ethically-minded, she thinks technologists can dismantle exclusionary systems in favour of community-focused, inclusive ones.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://tatianamac.com Website]&lt;br /&gt;
[https://www.selfdefined.app/ Self-Defined]&lt;br /&gt;
[https://github.com/selfdefined/devsofcolour Devs of Colour]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:speaking@tatianamac.com email]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot; (excerpted from [https://www.tedmed.com/speakers/show?id=6472 Chuck's TEDMED bio])&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, his perspective will bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT] and was formerly the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
[mailto:chuck.pell@gmail.com Email Chuck]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2021_Keynote_Speakers_Nominations&amp;diff=47555</id>
		<title>2021 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2021_Keynote_Speakers_Nominations&amp;diff=47555"/>
				<updated>2020-11-12T15:00:39Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Chuck Pell&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2021 will take place March 22nd through March 26th 2021.&lt;br /&gt;
&lt;br /&gt;
''As the conference will be virtual this year, we encourage '''all''' nominations -- including those from international venues.'' &lt;br /&gt;
&lt;br /&gt;
'''We will be accepting nominations from November 10, 2020 until November 25, 2020.'''&lt;br /&gt;
&lt;br /&gt;
Please include a description and any relevant links. Please try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
[mailto:email_link.foo nominee's email address]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
[mailto:jane@nowhere.foo janes_email_address]&lt;br /&gt;
&lt;br /&gt;
==Cecily Walker==&lt;br /&gt;
&lt;br /&gt;
Cecily Walker is the Assistant Manager for Community Digital Initiatives &amp;amp; eLearning at Vancouver Public Library.  Her work centers on user experience, communications, marketing of library services, community digital initiatives, open data, content strategy, transforming the role of librarians and information professionals, and investigating the intersection of social issues, technology, and public librarianship. She is a leading thinker of the intersections on technologies, librarianship and the public good. I believe her work, thoughts and perspective will resonate with Code4Lib attendees.&lt;br /&gt;
&lt;br /&gt;
[https://cecily.info/ website]&lt;br /&gt;
&lt;br /&gt;
[https://circulatingideas.com/transcripts/cecily-walker/ podcast conversation]&lt;br /&gt;
&lt;br /&gt;
[https://www.vala.org.au/conferences/vala2020/conference-program/keynote-speakers/#cecilywalker past keynote speaker]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:cecily@cecily.info Cecily's email address]&lt;br /&gt;
&lt;br /&gt;
== Rudo Kemper ==&lt;br /&gt;
&lt;br /&gt;
Gave an outstanding talk at [https://csvconf.com/ csv,conf,v5] about working with South American indigenous communities to map &amp;amp; safeguard their stories using the open source project [https://terrastories.io/ Terrastories] ([https://youtu.be/j-mDnMjDnq4 talk is here]) . It covered issues of pure tech (architecting around limited internet access), participatory design (building a tool that was useful for the people in question to advance causes that matter to them), indigenous knowledge rights, tech as tool for political advocacy -- this talk was everything. He's on the board of https://native-land.ca/, works for https://www.digital-democracy.org/, studied human geography, and contributes code &amp;amp; docs to Terrastories as well as having worked on the ground in the Amazon.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/rudokemper Twitter @rudokemper]&lt;br /&gt;
&lt;br /&gt;
[mailto:rkemper@digital-democracy.org email]&lt;br /&gt;
&lt;br /&gt;
== Regina Gong ==&lt;br /&gt;
&lt;br /&gt;
Regina Gong is the Open Educational Resources (OER) &amp;amp; Student Success Librarian at Michigan State University (MSU) Libraries. Before joining MSU, Regina was the OER Project Manager at Lansing Community College (LCC) where she led a very successful OER initiative. Regina is well-known in the open education community and has done numerous national presentations and webinars on OER. She is a staunch advocate of openness, equity, and access through her involvement on the SPARC Open Education Advisory Group(link is external) (2019-2022), SPARC Steering Committee(link is external), and Executive Council member of the Community College Consortium for Open Educational Resources (CCCOER)(link is external) where she served as VP for professional development. She is also in the MI Statewide OER Steering Committee(link is external); 2019 Open Education Conference Program Committee(link is external), and an OER Research Group Fellow(link is external). Regina obtained her Masters in Library and Information Science (MLIS) at Wayne State University and is currently pursuing Ph.D. in the Higher, Adult, and Lifelong Education (HALE) Program at Michigan State University (MSU). I believe that Regina Gong will bring an important viewpoint related to open education and access and the role of libraries/museums of all types to consider.&lt;br /&gt;
&lt;br /&gt;
[https://sparcopen.org/news/2019/regina-gong-championing-oer-at-community-colleges/ Work championing open education]&lt;br /&gt;
[https://www.amigos.org/node/6013 past keynote]&lt;br /&gt;
[https://www.linkedin.com/in/regina-gong-37592164/ Linkedin profile]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:gongregi@msu.edu email]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Alex Gil ==&lt;br /&gt;
&lt;br /&gt;
Alex Gil is the Digital Scholarship Librarian at Columbia University Libraries. He collaborates with faculty, students and library professionals leveraging computational and network technologies in humanities research, pedagogy and knowledge production. He coordinates the Butler Library Studio at Columbia University, a tech-light library innovation space focused on digital scholarship and pedagogy; co-founder and moderator of Columbia’s Group for Experimental Methods in the Humanities, a vibrant trans-disciplinary research cluster focused on experimental humanities; senior editor of sx archipelagos, a journal of Caribbean Digital Studies, and co-wrangler of The Caribbean Digital conference series. He is also founder and former chair of Global Outlook:Digital Humanities. Active digital projects include Ed, a digital platform for minimal editions of literary texts, and Wax for minimal exhibits of cultural artifacts; In The Same Boats, a visualization of trans-Atlantic intersections of black intellectuals in the 20th century; and most recently, the nimble tent interventions Torn Apart/Separados and Covid Maker Response. His projects are very exciting and can provide important discussions on global framework in network technologies. &lt;br /&gt;
&lt;br /&gt;
[https://www.elotroalex.com/profile/ Profile]&lt;br /&gt;
[https://studio.cul.columbia.edu/ Project]&lt;br /&gt;
[https://www.libraryjournal.com/?detailStory=alex-gil-movers-shakers-2020%E2%80%93change-agents LJ's Mover and Shaker Profile]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:agil@columbia.edu email]&lt;br /&gt;
&lt;br /&gt;
== Tatiana Mac ==&lt;br /&gt;
&lt;br /&gt;
Tatiana Mac (she/they) is an independent American engineer. She is an open source maintainer who created and is building Self-Defined, a modern dictionary about us; and Devs of Colour, a database that will prioritise finding undiscovered Black/brown talent through a thoughtful search algorithm.&lt;br /&gt;
As a consultant, she works directly with organisations to build clear and coherent products and design systems.&lt;br /&gt;
An international keynote speaker, she speaks on the intersection of technology and ethics, examining how our products both fit and define our social and environmental settings. You can view her recorded talks on YouTube.&lt;br /&gt;
She believes the trifecta of accessibility, performance, and inclusion can work symbiotically to improve our social landscape digitally and physically. When ethically-minded, she thinks technologists can dismantle exclusionary systems in favour of community-focused, inclusive ones.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[https://tatianamac.com Website]&lt;br /&gt;
[https://www.selfdefined.app/ Self-Defined]&lt;br /&gt;
[https://github.com/selfdefined/devsofcolour Devs of Colour]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[mailto:speaking@tatianamac.com email]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot; (excerpted from [https://www.tedmed.com/speakers/show?id=6472 Chuck's TEDMED bio])&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, his perspective will bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT] and was formerly the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
[mailto:chuck.pell@gmail.com]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2021_Conference_Committees&amp;diff=47527</id>
		<title>Code4Lib 2021 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2021_Conference_Committees&amp;diff=47527"/>
				<updated>2020-10-15T17:42:00Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2021 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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 2021 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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Virtual&lt;br /&gt;
* Dates: TBD&lt;br /&gt;
** Pre-conferences: TBD&lt;br /&gt;
** Main meeting: TBD&lt;br /&gt;
** Post conference activities: TBD&lt;br /&gt;
&lt;br /&gt;
== Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Blake Carver - Primary Contact AKA Chair&lt;br /&gt;
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Secondary Contact AKA CoChair&lt;br /&gt;
* [mailto:jester@dltj.org Peter Murray] - Tertiary Contact AKA CoChair&lt;br /&gt;
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Documentarian&lt;br /&gt;
* [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer&lt;br /&gt;
* [mailto:abattel@emory.edu Andrew Battelini] - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2021 Website Working Group Documents|2021 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* [mailto:qum@miamioh.edu Meng Qu] - Documentarian&lt;br /&gt;
* [mailto:ranti.junus@gmail.com Ranti Junus] - Volunteer&lt;br /&gt;
* Andy Hickner (alh4014@med.cornell.edu) - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget and Sponsorship Committee ==&lt;br /&gt;
This group involves working with the LPC to close any budget gaps and talking to potential sponsors to find the level that is right for them.&lt;br /&gt;
&lt;br /&gt;
[[2021 Budget and Sponsorship Documents|2021 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Mary Jinglewski - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Janna Avon - Documentarian&lt;br /&gt;
* [[User:BrianMaass|Brian Maass]] (brian.maass@unmc.edu) - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* - ex officio, fiscal host (CLIR/DLF)&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 Keynote Documents|2021 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:clara.turp@mcgill.ca Clara Turp] - Primary Contact AKA Chair&lt;br /&gt;
* [mailto:dana.reijerkerk@stonybrook.edu Dana Reijerkerk] - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* [mailto:bobbi@bobbifox.net Bobbi Fox] - Documentarian&lt;br /&gt;
* [[User:Khaley|Kathleen Haley]] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 Pre-conference Documents|2021 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:casden@gmail.com Jason Casden] - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [mailto:brighidmgonzales@gmail.com Brighid Gonzales] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 Program Documents|2021 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:aaron.collier@stanford.edu Aaron Collier] - Primary Contact AKA Chair&lt;br /&gt;
* [mailto:akorphan@ncsu.edu Andreas Orphanides] - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Jessica McMillen (new) - Volunteer&lt;br /&gt;
* David Schober - Volunteer&lt;br /&gt;
* [[User:EmilyBoss|Emily Boss]] - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 Scholarship Documents|2021 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 T-Shirt Documents|2021 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* [[User:Khaley|Kathleen Haley]] - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* [[User:ChristyKarpinski|Christy Karpinski]] - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Online Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2021 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2021 Online Volunteer Documents|2021 Online Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* [mailto:jenn@concentra-cms.com Jennifer Cummings] &amp;amp; [mailto:kathy@concentra-cms.com Kathy Azevedo] - Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes virtual social activities.&lt;br /&gt;
&lt;br /&gt;
[[2021 Social Activities Documents|2021 Social Activities Documents]]&lt;br /&gt;
&lt;br /&gt;
* [[User:Yoosebj|Becky Yoose]]- Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* A.M. Serrano - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2021 Streaming Video Documents|2021 Streaming Video Documents]]&lt;br /&gt;
This will likely be part of the general conference planning.v&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2022 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2022 Host Voting Documents|2022 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [[User:NicoleLawrence|Nicole Lawrence]] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2021 Book Giveaway Documents|2021 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact AKA Chair&lt;br /&gt;
* Your Name Here - Secondary Contact AKA CoChair&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
This committee will assist attendees with IRC and Slack.&lt;br /&gt;
&lt;br /&gt;
[[2021 IRC and Slack Documents|2021 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Planning Committee Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees (virtual only, this year).&lt;br /&gt;
&lt;br /&gt;
[[2021 Accessibility Documents|2021 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2021 Whatever Documents|2021 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Planning Committee Contact&lt;br /&gt;
* [[User:LoriStethers|Lori Stethers]] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2021]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Streaming_Video_Documents&amp;diff=47418</id>
		<title>2020 Streaming Video Documents</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Streaming_Video_Documents&amp;diff=47418"/>
				<updated>2020-03-06T21:06:10Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: added notes column to remote presenter table&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Previous years: [[2014 Video Recording &amp;amp; Streaming|2014]], [[2015 Video Recording &amp;amp; Streaming|2015]], [[2016 Video Recording &amp;amp; Streaming|2016]], [[2018_Streaming_Video_Documents|2018]], [[2019_Streaming_Video_Documents|2019]]&lt;br /&gt;
&lt;br /&gt;
List of [[Code4Lib 2020 Conference Committees#Streaming_Video_Committee|volunteers]].  Thanks everyone!&lt;br /&gt;
&lt;br /&gt;
Streaming channel: [https://www.youtube.com/user/code4lib Code4Lib - YouTube]&lt;br /&gt;
&lt;br /&gt;
== Remote Presenters ==&lt;br /&gt;
&lt;br /&gt;
Code4Lib will be using [https://zoom.us/support/download Zoom] for remote presenters.&lt;br /&gt;
In addition to the software, having the proper audio setup is key for a successful presentation.&lt;br /&gt;
* '''Microphone''': The best option is a headset or earbuds so a microphone is close to your mouth.  Built-in laptop microphones are okay, but using them will make it harder for the audience to hear you.&lt;br /&gt;
* '''Speaker''': A headset or earbuds are required.  ''Do not use your computer's built-in speakers.''  The echo cancellation software is designed for small rooms and cannot handle the delay caused by large ballrooms.&lt;br /&gt;
&lt;br /&gt;
You can test your setup with a [https://zoom.us/test test Zoom call].&lt;br /&gt;
Be sure your microphone and speakers are set correctly in Zoom.&lt;br /&gt;
Also try sharing your screen on the test call so you understand how to start and stop screen sharing.&lt;br /&gt;
The audience will see everything on your screen, so quit/disable/turn-off notifications that come from chat programs, email clients, and similar tools.&lt;br /&gt;
&lt;br /&gt;
Plan to connect to the Zoom meeting 30 minutes before your talk to work out any connection or setup issues.&lt;br /&gt;
&lt;br /&gt;
=== Remote Speaker Schedule ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
  |+ Code4Lib 2020 Remote Presenters&lt;br /&gt;
|-&lt;br /&gt;
  ! Presenter !! Date/Time !! Short Title of Talk !! Zoom Meeting !! Notes&lt;br /&gt;
|-&lt;br /&gt;
  | Jen Diamond || Monday, 11:05 || [https://2020.code4lib.org/talks/The-Agile-Librarian-or-The-Library-Dev-Shop-Using-Agile-Methodology-to-Build-a-Digital-Library The Agile Librarian or The Library Dev Shop] || https://zoom.us/j/841148864 (A) || &lt;br /&gt;
|-&lt;br /&gt;
  | Mike Giarlo, Aaron Collier || Monday, 11:55 || [https://2020.code4lib.org/talks/Amplifying-Productivity-Joy-Lightweight-Tools-Techniques-to-Help-Teams-Improve-Collaboration-Communication Amplifying Productivity &amp;amp; Joy] || https://zoom.us/j/271812668 (B) || &lt;br /&gt;
|-&lt;br /&gt;
  | Bess Sadler || Tuesday, 11:25 || [https://2020.code4lib.org/talks/Design-Sprints-for-Democratization Design Sprints for Democratization] || https://zoom.us/j/271812668 (B) || &lt;br /&gt;
|-&lt;br /&gt;
  | Jacob Shelby || Tuesday, 1:35 || [https://2020.code4lib.org/talks/A-journey-not-a-destination-towards-a-more-usercentered-library-discovery-experience A Journey, Not a Destination] || https://zoom.us/j/271812668 (B) || Two on-site presenters will be on stage running slides&lt;br /&gt;
|-&lt;br /&gt;
  | Kate Deibel || Tuesday, 1:50 || [https://2020.code4lib.org/talks/Plaintext-HTML-PDF-and-EPUB3-Who-wins-the-Accessibility-Games Plaintext, HTML, PDF, and EPUB3&amp;amp;#58; Who wins the Accessibility Games?] || https://zoom.us/j/841148864 (A) || &lt;br /&gt;
|-&lt;br /&gt;
  | Eric Shows, Sara Rubinow, Katrina Gertz || Tuesday, 3:50 || [https://2020.code4lib.org/talks/Picturing-the-Digitization-Ecosystem Picturing the Digitization Ecosystem] || https://zoom.us/j/841148864 (A) || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Livestreaming team checklist with the presenter prior to talk ===&lt;br /&gt;
&lt;br /&gt;
* Check presenter's microphone level and sound quality&lt;br /&gt;
* Check presenter's speaker and ensure there is no echo&lt;br /&gt;
* Test screen-sharing (''start'' and ''stop'') with presenter&lt;br /&gt;
* Remind presenter to turn off notifications from chat programs, email clients, etc.&lt;br /&gt;
* Lock the meeting to prevent others from joining and interrupting the presenter.  (From the ''Participants'' panel, select ''More'' then ''Lock Meeting''.)&lt;br /&gt;
&lt;br /&gt;
=== Livestreaming team instructions bringing in remote presenters ===&lt;br /&gt;
&lt;br /&gt;
* On the laptop dedicated to providing video/audio to the A/V contractor's video switch (&amp;quot;RECEIVING ZOOM&amp;quot;), log in as `olf_host2@openlibraryfoundation.org` (password provided on-site)&lt;br /&gt;
* On your own device (&amp;quot;YOUR ZOOM&amp;quot;), download and install the Zoom client.  Log in as `olf_host3@openlibraryfoundation.org` (password provided on-site)&lt;br /&gt;
* 30 minutes before the remote presenter's start time, use YOUR ZOOM to connect to the Zoom meeting URL (listed in the table above) and work through the checklist for remote presenters&lt;br /&gt;
* 5 minutes before the remote presenter's start time, use RECEIVING ZOOM to connect to the Zoom meeting URL.  When connected, make the Zoom window go full-screen.&lt;br /&gt;
* At the presenter's start time, let the A/V contractor know that the remote presenter video/audio is ready&lt;br /&gt;
* At the end of the presentation, on the RECEIVING ZOOM machine take the Zoom window out of full-screen and end the meeting for all.&lt;br /&gt;
&lt;br /&gt;
== Encoding Setup ==&lt;br /&gt;
&lt;br /&gt;
Video sources;&lt;br /&gt;
# Feed from camera supplied by the A/V contractor (HDMI)&lt;br /&gt;
# Feed split from the podium computer (HDMI)&lt;br /&gt;
# Backup camera for speaker (HDMI)&lt;br /&gt;
# Backup camera for video of slides as displayed on screens (RCA)&lt;br /&gt;
&lt;br /&gt;
Audio source:&lt;br /&gt;
# Audio system feed to the encoding computer via cable terminated with 1/4&amp;quot; plug (one channel, mono is fine).&lt;br /&gt;
&lt;br /&gt;
Encoding computer:&lt;br /&gt;
* MacBook Pro&lt;br /&gt;
* Encoding/Streaming: [https://boinx.com/mimolive/ mimoLive] by Boinx software&lt;br /&gt;
&lt;br /&gt;
Other equipment:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
  |+ Equipment Needs and Sources&lt;br /&gt;
|-&lt;br /&gt;
  ! Item !! Model !! Connection / Port / Standard !! Source !! Notes&lt;br /&gt;
|-&lt;br /&gt;
  | Encoder || Macbook Pro || || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Backup camera on speaker || Panasonic HC-V110 || HDMI || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Backup camera on screen || Panasonic SDR-S50 || Composite || Peter || Backup for capturing projected content&lt;br /&gt;
|-&lt;br /&gt;
  | HDMI to USB3 || Blackmagic Shuttle (USB3), Qty 2 ||  || Peter || One purchased previously by Code4Lib local host committees&lt;br /&gt;
|-&lt;br /&gt;
  | HDMI cables ||   || 1m, 3m  || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Audo digitizer || Behringer UFO202 || || Peter || Might be able to use a Shuttle to do this&lt;br /&gt;
|-&lt;br /&gt;
  | Composite cable ||   || 1m  || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Tripod ||   ||   || Peter ||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== YouTube Streaming Setup ==&lt;br /&gt;
&lt;br /&gt;
Links below and thumbnails to the right bring up a larger sized image. &lt;br /&gt;
&lt;br /&gt;
You can set up all of the events in advance of the conference.&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_1.png|Create event on YouTube]] [[File:Streaming-Create_event,_step_1.png|thumbnail|Create event, step 1]]&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_2.png|Set advanced settings for YouTube event]] [[File:Streaming-Create_event,_step_2.png|thumbnail|Create event, step 2]]&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_3.png|Set thumbnail and stream key for YouTube event]] [[File:Streaming-Create_event,_step_3.png|thumbnail|Create event, step 3]]&lt;br /&gt;
&lt;br /&gt;
Use mimoLive to start streaming to the appropriate YouTube event.&lt;br /&gt;
# [[:File:Streaming-Start_stream.png|Start streaming from mimoLive]] [[File:Streaming-Start_stream.png|thumbnail|Start stream]]&lt;br /&gt;
&lt;br /&gt;
== Thoughts ==&lt;br /&gt;
&lt;br /&gt;
[[User:DataGazetteer|Peter Murray]] has been asked a couple of times about the setup being used at Code4Lib.  See [[2018_Streaming_Video_Documents|2018]] for previous thoughts.  Thoughts below come from 2020.&lt;br /&gt;
&lt;br /&gt;
Due to the [https://en.wikipedia.org/wiki/Coronavirus_disease_2019 COVID-19] outbreak, many presenters have travel concerns or outright travel bans from their institutions.&lt;br /&gt;
This is the first time in my memory where the Code4Lib meeting made a conscious effort to enable remote presenters to join the meeting at a significant scale.&lt;br /&gt;
To handle this, two Zoom meetings (labeled ''A'' and ''B'') were created using the Open Library Foundation's Zoom accounts.&lt;br /&gt;
These meetings were set to automatically start without a host present and to record in the cloud (in case network quality is such that the in-venue recording is not good).&lt;br /&gt;
Instructions were added to the top of this page, and a table of expected remote presentations created.&lt;br /&gt;
''Undoubtedly more to follow later...''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2020]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Streaming_Video_Documents&amp;diff=47417</id>
		<title>2020 Streaming Video Documents</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Streaming_Video_Documents&amp;diff=47417"/>
				<updated>2020-03-06T20:59:12Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Remote Speaker Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Previous years: [[2014 Video Recording &amp;amp; Streaming|2014]], [[2015 Video Recording &amp;amp; Streaming|2015]], [[2016 Video Recording &amp;amp; Streaming|2016]], [[2018_Streaming_Video_Documents|2018]], [[2019_Streaming_Video_Documents|2019]]&lt;br /&gt;
&lt;br /&gt;
List of [[Code4Lib 2020 Conference Committees#Streaming_Video_Committee|volunteers]].  Thanks everyone!&lt;br /&gt;
&lt;br /&gt;
Streaming channel: [https://www.youtube.com/user/code4lib Code4Lib - YouTube]&lt;br /&gt;
&lt;br /&gt;
== Remote Presenters ==&lt;br /&gt;
&lt;br /&gt;
Code4Lib will be using [https://zoom.us/support/download Zoom] for remote presenters.&lt;br /&gt;
In addition to the software, having the proper audio setup is key for a successful presentation.&lt;br /&gt;
* '''Microphone''': The best option is a headset or earbuds so a microphone is close to your mouth.  Built-in laptop microphones are okay, but using them will make it harder for the audience to hear you.&lt;br /&gt;
* '''Speaker''': A headset or earbuds are required.  ''Do not use your computer's built-in speakers.''  The echo cancellation software is designed for small rooms and cannot handle the delay caused by large ballrooms.&lt;br /&gt;
&lt;br /&gt;
You can test your setup with a [https://zoom.us/test test Zoom call].&lt;br /&gt;
Be sure your microphone and speakers are set correctly in Zoom.&lt;br /&gt;
Also try sharing your screen on the test call so you understand how to start and stop screen sharing.&lt;br /&gt;
The audience will see everything on your screen, so quit/disable/turn-off notifications that come from chat programs, email clients, and similar tools.&lt;br /&gt;
&lt;br /&gt;
Plan to connect to the Zoom meeting 30 minutes before your talk to work out any connection or setup issues.&lt;br /&gt;
&lt;br /&gt;
=== Remote Speaker Schedule ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
  |+ Code4Lib 2020 Remote Presenters&lt;br /&gt;
|-&lt;br /&gt;
  ! Presenter !! Date/Time !! Short Title of Talk !! Zoom Meeting&lt;br /&gt;
|-&lt;br /&gt;
  | Jen Diamond || Monday, 11:05 || [https://2020.code4lib.org/talks/The-Agile-Librarian-or-The-Library-Dev-Shop-Using-Agile-Methodology-to-Build-a-Digital-Library The Agile Librarian or The Library Dev Shop] || https://zoom.us/j/841148864 (A)&lt;br /&gt;
|-&lt;br /&gt;
  | Mike Giarlo, Aaron Collier || Monday, 11:55 || [https://2020.code4lib.org/talks/Amplifying-Productivity-Joy-Lightweight-Tools-Techniques-to-Help-Teams-Improve-Collaboration-Communication Amplifying Productivity &amp;amp; Joy] || https://zoom.us/j/271812668 (B)&lt;br /&gt;
|-&lt;br /&gt;
  | Bess Sadler || Tuesday, 11:25 || [https://2020.code4lib.org/talks/Design-Sprints-for-Democratization Design Sprints for Democratization] || https://zoom.us/j/271812668 (B)&lt;br /&gt;
|-&lt;br /&gt;
  | Jacob Shelby || Tuesday, 1:35 || [https://2020.code4lib.org/talks/A-journey-not-a-destination-towards-a-more-usercentered-library-discovery-experience A Journey, Not a Destination] || https://zoom.us/j/271812668 (B)&lt;br /&gt;
|-&lt;br /&gt;
  | Kate Deibel || Tuesday, 1:50 || [https://2020.code4lib.org/talks/Plaintext-HTML-PDF-and-EPUB3-Who-wins-the-Accessibility-Games Plaintext, HTML, PDF, and EPUB3&amp;amp;#58; Who wins the Accessibility Games?] || https://zoom.us/j/841148864 (A)&lt;br /&gt;
|-&lt;br /&gt;
  | Eric Shows, Sara Rubinow, Katrina Gertz || Tuesday, 3:50 || [https://2020.code4lib.org/talks/Picturing-the-Digitization-Ecosystem Picturing the Digitization Ecosystem] || https://zoom.us/j/841148864 (A)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Livestreaming team checklist with the presenter prior to talk ===&lt;br /&gt;
&lt;br /&gt;
* Check presenter's microphone level and sound quality&lt;br /&gt;
* Check presenter's speaker and ensure there is no echo&lt;br /&gt;
* Test screen-sharing (''start'' and ''stop'') with presenter&lt;br /&gt;
* Remind presenter to turn off notifications from chat programs, email clients, etc.&lt;br /&gt;
* Lock the meeting to prevent others from joining and interrupting the presenter.  (From the ''Participants'' panel, select ''More'' then ''Lock Meeting''.)&lt;br /&gt;
&lt;br /&gt;
=== Livestreaming team instructions bringing in remote presenters ===&lt;br /&gt;
&lt;br /&gt;
* On the laptop dedicated to providing video/audio to the A/V contractor's video switch (&amp;quot;RECEIVING ZOOM&amp;quot;), log in as `olf_host2@openlibraryfoundation.org` (password provided on-site)&lt;br /&gt;
* On your own device (&amp;quot;YOUR ZOOM&amp;quot;), download and install the Zoom client.  Log in as `olf_host3@openlibraryfoundation.org` (password provided on-site)&lt;br /&gt;
* 30 minutes before the remote presenter's start time, use YOUR ZOOM to connect to the Zoom meeting URL (listed in the table above) and work through the checklist for remote presenters&lt;br /&gt;
* 5 minutes before the remote presenter's start time, use RECEIVING ZOOM to connect to the Zoom meeting URL.  When connected, make the Zoom window go full-screen.&lt;br /&gt;
* At the presenter's start time, let the A/V contractor know that the remote presenter video/audio is ready&lt;br /&gt;
* At the end of the presentation, on the RECEIVING ZOOM machine take the Zoom window out of full-screen and end the meeting for all.&lt;br /&gt;
&lt;br /&gt;
== Encoding Setup ==&lt;br /&gt;
&lt;br /&gt;
Video sources;&lt;br /&gt;
# Feed from camera supplied by the A/V contractor (HDMI)&lt;br /&gt;
# Feed split from the podium computer (HDMI)&lt;br /&gt;
# Backup camera for speaker (HDMI)&lt;br /&gt;
# Backup camera for video of slides as displayed on screens (RCA)&lt;br /&gt;
&lt;br /&gt;
Audio source:&lt;br /&gt;
# Audio system feed to the encoding computer via cable terminated with 1/4&amp;quot; plug (one channel, mono is fine).&lt;br /&gt;
&lt;br /&gt;
Encoding computer:&lt;br /&gt;
* MacBook Pro&lt;br /&gt;
* Encoding/Streaming: [https://boinx.com/mimolive/ mimoLive] by Boinx software&lt;br /&gt;
&lt;br /&gt;
Other equipment:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
  |+ Equipment Needs and Sources&lt;br /&gt;
|-&lt;br /&gt;
  ! Item !! Model !! Connection / Port / Standard !! Source !! Notes&lt;br /&gt;
|-&lt;br /&gt;
  | Encoder || Macbook Pro || || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Backup camera on speaker || Panasonic HC-V110 || HDMI || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Backup camera on screen || Panasonic SDR-S50 || Composite || Peter || Backup for capturing projected content&lt;br /&gt;
|-&lt;br /&gt;
  | HDMI to USB3 || Blackmagic Shuttle (USB3), Qty 2 ||  || Peter || One purchased previously by Code4Lib local host committees&lt;br /&gt;
|-&lt;br /&gt;
  | HDMI cables ||   || 1m, 3m  || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Audo digitizer || Behringer UFO202 || || Peter || Might be able to use a Shuttle to do this&lt;br /&gt;
|-&lt;br /&gt;
  | Composite cable ||   || 1m  || Peter ||&lt;br /&gt;
|-&lt;br /&gt;
  | Tripod ||   ||   || Peter ||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== YouTube Streaming Setup ==&lt;br /&gt;
&lt;br /&gt;
Links below and thumbnails to the right bring up a larger sized image. &lt;br /&gt;
&lt;br /&gt;
You can set up all of the events in advance of the conference.&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_1.png|Create event on YouTube]] [[File:Streaming-Create_event,_step_1.png|thumbnail|Create event, step 1]]&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_2.png|Set advanced settings for YouTube event]] [[File:Streaming-Create_event,_step_2.png|thumbnail|Create event, step 2]]&lt;br /&gt;
# [[:File:Streaming-Create_event,_step_3.png|Set thumbnail and stream key for YouTube event]] [[File:Streaming-Create_event,_step_3.png|thumbnail|Create event, step 3]]&lt;br /&gt;
&lt;br /&gt;
Use mimoLive to start streaming to the appropriate YouTube event.&lt;br /&gt;
# [[:File:Streaming-Start_stream.png|Start streaming from mimoLive]] [[File:Streaming-Start_stream.png|thumbnail|Start stream]]&lt;br /&gt;
&lt;br /&gt;
== Thoughts ==&lt;br /&gt;
&lt;br /&gt;
[[User:DataGazetteer|Peter Murray]] has been asked a couple of times about the setup being used at Code4Lib.  See [[2018_Streaming_Video_Documents|2018]] for previous thoughts.  Thoughts below come from 2020.&lt;br /&gt;
&lt;br /&gt;
Due to the [https://en.wikipedia.org/wiki/Coronavirus_disease_2019 COVID-19] outbreak, many presenters have travel concerns or outright travel bans from their institutions.&lt;br /&gt;
This is the first time in my memory where the Code4Lib meeting made a conscious effort to enable remote presenters to join the meeting at a significant scale.&lt;br /&gt;
To handle this, two Zoom meetings (labeled ''A'' and ''B'') were created using the Open Library Foundation's Zoom accounts.&lt;br /&gt;
These meetings were set to automatically start without a host present and to record in the cloud (in case network quality is such that the in-venue recording is not good).&lt;br /&gt;
Instructions were added to the top of this page, and a table of expected remote presentations created.&lt;br /&gt;
''Undoubtedly more to follow later...''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2020]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Conference_Volunteers&amp;diff=47364</id>
		<title>2020 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Conference_Volunteers&amp;diff=47364"/>
				<updated>2020-03-03T16:12:50Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: MC times&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2020 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2020.code4lib.org/conduct/#officers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: N/A&lt;br /&gt;
&lt;br /&gt;
* Natasha Allen&lt;br /&gt;
* Eric Phetteplace&lt;br /&gt;
* Jeremy Friesen&lt;br /&gt;
* Anne Slaughter&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Wayne Graham&lt;br /&gt;
* Mike Giarlo&lt;br /&gt;
* Ann Marie Mesco&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
Saturday, day before:&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Sunday, preconference day:&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
* 1pm - 3pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, day one:&lt;br /&gt;
* 8am - 9:30am: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
* 6:30-7:30pm Reception: ''Your Name Here''&lt;br /&gt;
* 6:30-7:30pm Reception: ''Your Name Here''&lt;br /&gt;
* 7:30-8:30pm Reception: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter (#c4l19), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Sunday, Preconference Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Monday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Four:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
Monday, Day Two:&lt;br /&gt;
*  AM Volunteer:''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
To report a problem (even if you're not an &amp;quot;official&amp;quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Monday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
*  Before the conference: ''Your Name Here''&lt;br /&gt;
*  During the conference: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
Monday, Day One:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer:''Your Name Here''&lt;br /&gt;
Tuesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
future potential volunteers:&lt;br /&gt;
&lt;br /&gt;
podium tech help&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2020]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47215</id>
		<title>2020 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47215"/>
				<updated>2019-10-26T02:10:59Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Chuck Pell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the Pittsburgh area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
==Lea Kissner==&lt;br /&gt;
&lt;br /&gt;
Lea formerly built the privacy engineering team at Google (where she specifically valued building a diverse team to capture all sorts of threat models) and is now the Chief Privacy Officer at Humu and cofounder of the [https://www.usenix.org/conference/pepr19/ USENIX Conference on Privacy Engineering Practice and Respect]. She's whip-smart, candid, and funny.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/leakissner Twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== James Mickens ==&lt;br /&gt;
&lt;br /&gt;
James Mickens is a computer science professor and researcher currently at Harvard University and formerly of Microsoft Research. A well-travelled conference speaker, James has given keynotes and presentations from Oslo to Sidney, with hilarious titles such as &amp;quot;Life is Terrible: Let's Talk About the Web,&amp;quot; and &amp;quot;Life As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors That Are Beyond My Control.&amp;quot; James' presentation style reveals a breadth of experience in technology that few possess, and a zany and brilliant sense of humor.&lt;br /&gt;
&lt;br /&gt;
[https://mickens.seas.harvard.edu/ James Mickens at Harvard University ]&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/notjamesmickens Twitter]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=7Nj9ZjwOdFQ NDC Sydney Keynote]&lt;br /&gt;
&lt;br /&gt;
(I am currently auditing Prof. Mickens' class at Harvard -- can confirm he is like this all the time -- would be willing to speak to him personally. --andromeda)&lt;br /&gt;
&lt;br /&gt;
==Karen Sandler==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Karen Sandler is the executive director of the Software Freedom Conservancy, former executive director of the GNOME Foundation, an attorney, and former general counsel of the Software Freedom Law Center.&amp;quot; (per [https://en.wikipedia.org/wiki/Karen_Sandler wikipedia]) She's known for advocacy on copyleft and other copyright issues as well as on free software more generally; notably, e.g., because proprietary software means she cannot audit the implantable medical device that keeps her alive ([https://www.youtube.com/watch?v=GcWlD2Y6HNM OSCON talk]). The [https://sfconservancy.org/about/ Software Freedom Conservancy] is a fiscal sponsor, copyright holder &amp;amp; advocate, etc. for open source software projects. Sandler also co-organizes Outreachy, a paid internship program that particularly encourages people from underrepresented genders and races to contribute to FOSS, and was formerly on the advisory board of the Ada Initiative. She teaches entertainment law at Columbia from a copyright-rebel perspective.&lt;br /&gt;
&lt;br /&gt;
kms47@columbia.edu&lt;br /&gt;
&lt;br /&gt;
==Leo Lo  ==&lt;br /&gt;
&lt;br /&gt;
Leo Lo is the Associate University Librarian for learning and undergraduate services at Penn State University Libraries. Leo is a talented presenter, creative thinker and offers very interesting ideas relating to organizational research and development, appreciative inquiry, fostering collaborative works and communications including one's strengths and gifts to the organization. He would make an excellent speaker for Code4Lib when connecting to bigger frameworks within our communities/workflows.  &lt;br /&gt;
&lt;br /&gt;
More on [https://news.psu.edu/story/553306/2019/01/08/academics/lo-named-libraries-wide-associate-dean-learning-undergraduate Penn State News], [https://www.linkedin.com/in/leoslo/ Linked In], [https://digitalcommons.odu.edu/do/search/?q=author_lname%3A%22Lo%22%20author_fname%3A%22Leo%22&amp;amp;start=0&amp;amp;context=7048263&amp;amp;facet= ODU digital commons]&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot; (excerpted from [https://www.tedmed.com/speakers/show?id=6472 Chuck's TEDMED bio])&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, he is sure to bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT] and is the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
Contact Chuck via [https://physcient.com/contact-us/ Physcient, Inc.]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47214</id>
		<title>2020 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47214"/>
				<updated>2019-10-26T02:09:07Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Chuck Pell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the Pittsburgh area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
==Lea Kissner==&lt;br /&gt;
&lt;br /&gt;
Lea formerly built the privacy engineering team at Google (where she specifically valued building a diverse team to capture all sorts of threat models) and is now the Chief Privacy Officer at Humu and cofounder of the [https://www.usenix.org/conference/pepr19/ USENIX Conference on Privacy Engineering Practice and Respect]. She's whip-smart, candid, and funny.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/leakissner Twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== James Mickens ==&lt;br /&gt;
&lt;br /&gt;
James Mickens is a computer science professor and researcher currently at Harvard University and formerly of Microsoft Research. A well-travelled conference speaker, James has given keynotes and presentations from Oslo to Sidney, with hilarious titles such as &amp;quot;Life is Terrible: Let's Talk About the Web,&amp;quot; and &amp;quot;Life As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors That Are Beyond My Control.&amp;quot; James' presentation style reveals a breadth of experience in technology that few possess, and a zany and brilliant sense of humor.&lt;br /&gt;
&lt;br /&gt;
[https://mickens.seas.harvard.edu/ James Mickens at Harvard University ]&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/notjamesmickens Twitter]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=7Nj9ZjwOdFQ NDC Sydney Keynote]&lt;br /&gt;
&lt;br /&gt;
(I am currently auditing Prof. Mickens' class at Harvard -- can confirm he is like this all the time -- would be willing to speak to him personally. --andromeda)&lt;br /&gt;
&lt;br /&gt;
==Karen Sandler==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Karen Sandler is the executive director of the Software Freedom Conservancy, former executive director of the GNOME Foundation, an attorney, and former general counsel of the Software Freedom Law Center.&amp;quot; (per [https://en.wikipedia.org/wiki/Karen_Sandler wikipedia]) She's known for advocacy on copyleft and other copyright issues as well as on free software more generally; notably, e.g., because proprietary software means she cannot audit the implantable medical device that keeps her alive ([https://www.youtube.com/watch?v=GcWlD2Y6HNM OSCON talk]). The [https://sfconservancy.org/about/ Software Freedom Conservancy] is a fiscal sponsor, copyright holder &amp;amp; advocate, etc. for open source software projects. Sandler also co-organizes Outreachy, a paid internship program that particularly encourages people from underrepresented genders and races to contribute to FOSS, and was formerly on the advisory board of the Ada Initiative. She teaches entertainment law at Columbia from a copyright-rebel perspective.&lt;br /&gt;
&lt;br /&gt;
kms47@columbia.edu&lt;br /&gt;
&lt;br /&gt;
==Leo Lo  ==&lt;br /&gt;
&lt;br /&gt;
Leo Lo is the Associate University Librarian for learning and undergraduate services at Penn State University Libraries. Leo is a talented presenter, creative thinker and offers very interesting ideas relating to organizational research and development, appreciative inquiry, fostering collaborative works and communications including one's strengths and gifts to the organization. He would make an excellent speaker for Code4Lib when connecting to bigger frameworks within our communities/workflows.  &lt;br /&gt;
&lt;br /&gt;
More on [https://news.psu.edu/story/553306/2019/01/08/academics/lo-named-libraries-wide-associate-dean-learning-undergraduate Penn State News], [https://www.linkedin.com/in/leoslo/ Linked In], [https://digitalcommons.odu.edu/do/search/?q=author_lname%3A%22Lo%22%20author_fname%3A%22Leo%22&amp;amp;start=0&amp;amp;context=7048263&amp;amp;facet= ODU digital commons]&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, he is sure to bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT] and is the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.tedmed.com/speakers/show?id=6472 Chuck Pell's TEDMED bio]&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
Contact Chuck via [https://physcient.com/contact-us/ Physcient, Inc.]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47213</id>
		<title>2020 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47213"/>
				<updated>2019-10-26T02:06:44Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Chuck Pell */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the Pittsburgh area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
==Lea Kissner==&lt;br /&gt;
&lt;br /&gt;
Lea formerly built the privacy engineering team at Google (where she specifically valued building a diverse team to capture all sorts of threat models) and is now the Chief Privacy Officer at Humu and cofounder of the [https://www.usenix.org/conference/pepr19/ USENIX Conference on Privacy Engineering Practice and Respect]. She's whip-smart, candid, and funny.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/leakissner Twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== James Mickens ==&lt;br /&gt;
&lt;br /&gt;
James Mickens is a computer science professor and researcher currently at Harvard University and formerly of Microsoft Research. A well-travelled conference speaker, James has given keynotes and presentations from Oslo to Sidney, with hilarious titles such as &amp;quot;Life is Terrible: Let's Talk About the Web,&amp;quot; and &amp;quot;Life As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors That Are Beyond My Control.&amp;quot; James' presentation style reveals a breadth of experience in technology that few possess, and a zany and brilliant sense of humor.&lt;br /&gt;
&lt;br /&gt;
[https://mickens.seas.harvard.edu/ James Mickens at Harvard University ]&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/notjamesmickens Twitter]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=7Nj9ZjwOdFQ NDC Sydney Keynote]&lt;br /&gt;
&lt;br /&gt;
(I am currently auditing Prof. Mickens' class at Harvard -- can confirm he is like this all the time -- would be willing to speak to him personally. --andromeda)&lt;br /&gt;
&lt;br /&gt;
==Karen Sandler==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Karen Sandler is the executive director of the Software Freedom Conservancy, former executive director of the GNOME Foundation, an attorney, and former general counsel of the Software Freedom Law Center.&amp;quot; (per [https://en.wikipedia.org/wiki/Karen_Sandler wikipedia]) She's known for advocacy on copyleft and other copyright issues as well as on free software more generally; notably, e.g., because proprietary software means she cannot audit the implantable medical device that keeps her alive ([https://www.youtube.com/watch?v=GcWlD2Y6HNM OSCON talk]). The [https://sfconservancy.org/about/ Software Freedom Conservancy] is a fiscal sponsor, copyright holder &amp;amp; advocate, etc. for open source software projects. Sandler also co-organizes Outreachy, a paid internship program that particularly encourages people from underrepresented genders and races to contribute to FOSS, and was formerly on the advisory board of the Ada Initiative. She teaches entertainment law at Columbia from a copyright-rebel perspective.&lt;br /&gt;
&lt;br /&gt;
kms47@columbia.edu&lt;br /&gt;
&lt;br /&gt;
==Leo Lo  ==&lt;br /&gt;
&lt;br /&gt;
Leo Lo is the Associate University Librarian for learning and undergraduate services at Penn State University Libraries. Leo is a talented presenter, creative thinker and offers very interesting ideas relating to organizational research and development, appreciative inquiry, fostering collaborative works and communications including one's strengths and gifts to the organization. He would make an excellent speaker for Code4Lib when connecting to bigger frameworks within our communities/workflows.  &lt;br /&gt;
&lt;br /&gt;
More on [https://news.psu.edu/story/553306/2019/01/08/academics/lo-named-libraries-wide-associate-dean-learning-undergraduate Penn State News], [https://www.linkedin.com/in/leoslo/ Linked In], [https://digitalcommons.odu.edu/do/search/?q=author_lname%3A%22Lo%22%20author_fname%3A%22Leo%22&amp;amp;start=0&amp;amp;context=7048263&amp;amp;facet= ODU digital commons]&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, he is sure to bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [[https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT]] and is the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.tedmed.com/speakers/show?id=6472 Chuck Pell's TEDMED bio]&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
Contact Chuck via [https://physcient.com/contact-us/ Physcient, Inc.]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47212</id>
		<title>2020 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2020_Keynote_Speakers_Nominations&amp;diff=47212"/>
				<updated>2019-10-26T02:06:25Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: chuck pell&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the Pittsburgh area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
==Lea Kissner==&lt;br /&gt;
&lt;br /&gt;
Lea formerly built the privacy engineering team at Google (where she specifically valued building a diverse team to capture all sorts of threat models) and is now the Chief Privacy Officer at Humu and cofounder of the [https://www.usenix.org/conference/pepr19/ USENIX Conference on Privacy Engineering Practice and Respect]. She's whip-smart, candid, and funny.&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/leakissner Twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== James Mickens ==&lt;br /&gt;
&lt;br /&gt;
James Mickens is a computer science professor and researcher currently at Harvard University and formerly of Microsoft Research. A well-travelled conference speaker, James has given keynotes and presentations from Oslo to Sidney, with hilarious titles such as &amp;quot;Life is Terrible: Let's Talk About the Web,&amp;quot; and &amp;quot;Life As A Developer: My Code Does Not Work Because I Am A Victim Of Complex Societal Factors That Are Beyond My Control.&amp;quot; James' presentation style reveals a breadth of experience in technology that few possess, and a zany and brilliant sense of humor.&lt;br /&gt;
&lt;br /&gt;
[https://mickens.seas.harvard.edu/ James Mickens at Harvard University ]&lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/notjamesmickens Twitter]&lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=7Nj9ZjwOdFQ NDC Sydney Keynote]&lt;br /&gt;
&lt;br /&gt;
(I am currently auditing Prof. Mickens' class at Harvard -- can confirm he is like this all the time -- would be willing to speak to him personally. --andromeda)&lt;br /&gt;
&lt;br /&gt;
==Karen Sandler==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Karen Sandler is the executive director of the Software Freedom Conservancy, former executive director of the GNOME Foundation, an attorney, and former general counsel of the Software Freedom Law Center.&amp;quot; (per [https://en.wikipedia.org/wiki/Karen_Sandler wikipedia]) She's known for advocacy on copyleft and other copyright issues as well as on free software more generally; notably, e.g., because proprietary software means she cannot audit the implantable medical device that keeps her alive ([https://www.youtube.com/watch?v=GcWlD2Y6HNM OSCON talk]). The [https://sfconservancy.org/about/ Software Freedom Conservancy] is a fiscal sponsor, copyright holder &amp;amp; advocate, etc. for open source software projects. Sandler also co-organizes Outreachy, a paid internship program that particularly encourages people from underrepresented genders and races to contribute to FOSS, and was formerly on the advisory board of the Ada Initiative. She teaches entertainment law at Columbia from a copyright-rebel perspective.&lt;br /&gt;
&lt;br /&gt;
kms47@columbia.edu&lt;br /&gt;
&lt;br /&gt;
==Leo Lo  ==&lt;br /&gt;
&lt;br /&gt;
Leo Lo is the Associate University Librarian for learning and undergraduate services at Penn State University Libraries. Leo is a talented presenter, creative thinker and offers very interesting ideas relating to organizational research and development, appreciative inquiry, fostering collaborative works and communications including one's strengths and gifts to the organization. He would make an excellent speaker for Code4Lib when connecting to bigger frameworks within our communities/workflows.  &lt;br /&gt;
&lt;br /&gt;
More on [https://news.psu.edu/story/553306/2019/01/08/academics/lo-named-libraries-wide-associate-dean-learning-undergraduate Penn State News], [https://www.linkedin.com/in/leoslo/ Linked In], [https://digitalcommons.odu.edu/do/search/?q=author_lname%3A%22Lo%22%20author_fname%3A%22Leo%22&amp;amp;start=0&amp;amp;context=7048263&amp;amp;facet= ODU digital commons]&lt;br /&gt;
&lt;br /&gt;
== Chuck Pell ==&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A confessed 'congenital geek,' Chuck is inventor, artist, scientist and expressive raconteur. As a practitioner of Design Coup d'œil (the habit of seeing overarching structural issues at a glance), Chuck seeks the essential core of any system, whether science, art, or technology. He is most at home in novel situations, figuring things out on the fly. These tendencies have led Chuck to garner experience in surgical robotics, functional morphology, biomechanics, fluid dynamics, miniature robotics, autonomous underwater vehicles, ballistics, maritime communications, entertainment effects, teaching, design (graphic, exhibit and industrial) and filmmaking. Never at rest, he’s had 100 shows of his paintings and sculpture, with dozens of papers published in biology, engineering and patents issued or pending. Having raised millions for research and now on his third startup, Chuck has the nagging suspicion he’s become a serial entrepreneur.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Chuck Pell is a sculptor, roboticist, Emmy-winning television host, and force of nature. His philosophies towards creativity and invention include: uncover hidden assumptions, pursue surprise, and &amp;quot;fail early and often, when it's cheap.&amp;quot; His passionate approach to real-world problem solving has a lot to offer the world of GLAM-tech; combined with an avowed love of technology, libraries, and knowledge generally, he is sure to bring a wealth of insight and creativity to the Code4Lib community. Chuck is 1/4 of the way to an [[https://en.wikipedia.org/wiki/List_of_people_who_have_won_Academy,_Emmy,_Grammy,_and_Tony_Awards EGOT]] and is the consulting scientist for an asteroid mining company.&lt;br /&gt;
&lt;br /&gt;
* See [https://www.tedmed.com/talks/show?id=6987&amp;amp;videoId=6776 Chuck's TEDMED talk on the future of surgery] (cw: contains brief footage and schematics of surgical procedures)&lt;br /&gt;
* [https://www.tedmed.com/speakers/show?id=6472 Chuck Pell's TEDMED bio]&lt;br /&gt;
* [https://www.xplorationstation.com/show/Xploration-Earth-2050 Xploration Earth 2050]&lt;br /&gt;
&lt;br /&gt;
Contact Chuck via [[https://physcient.com/contact-us/ Physcient, Inc.]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&amp;diff=47037</id>
		<title>Code4Lib 2020 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&amp;diff=47037"/>
				<updated>2019-06-26T16:39:41Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Add self to program committee&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2020 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA&lt;br /&gt;
* Dates: March 08 (pre-con) - 22, 2020&lt;br /&gt;
** Pre-conferences: March 08, 2020&lt;br /&gt;
** Main meeting: March 09-11, 2020&lt;br /&gt;
** Post conference activities: Coming Soon&lt;br /&gt;
&lt;br /&gt;
== Local Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact&lt;br /&gt;
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact&lt;br /&gt;
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact&lt;br /&gt;
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact&lt;br /&gt;
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact&lt;br /&gt;
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact&lt;br /&gt;
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact&lt;br /&gt;
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact&lt;br /&gt;
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact&lt;br /&gt;
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact&lt;br /&gt;
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2020 Website Working Group Documents|2020 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]]  - Primary Contact aka Chair&lt;br /&gt;
* Julia Caffrey (newbie)  - Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [[User:KaitlinNewson|Kaitlin Newson]] (v) - Volunteer&lt;br /&gt;
* [[User:Ranti|Ranti Junus]] (v) - Volunteer&lt;br /&gt;
* [[User:Tomkeays|Tom Keays]] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget Committee ==&lt;br /&gt;
This group will focus on making sure we are appropriately planning for budgetary issues.   &lt;br /&gt;
&lt;br /&gt;
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)&lt;br /&gt;
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)&lt;br /&gt;
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF) &lt;br /&gt;
* [mailto:kerchner@gwu.edu Dan Kerchner] - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Keynote Documents|2020 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Pre-conference Documents|2020 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Program Documents|2020 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair &lt;br /&gt;
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact &lt;br /&gt;
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer&lt;br /&gt;
* [mailto:akorphan@ncsu.edu Dre] - Volunteer&lt;br /&gt;
* [mailto:mardenj@carnegielibrary.org Julia Marden] Carnegie Library of Pittsburgh - Documentarian? (new!) &lt;br /&gt;
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Scholarship Documents|2020 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Primary Contact aka Co-Chair &lt;br /&gt;
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian &lt;br /&gt;
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer&lt;br /&gt;
* [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer&lt;br /&gt;
* Your Name Here - (Volunteer)&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 T-Shirt Documents|2020 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee wrangles people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
'''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''&lt;br /&gt;
&lt;br /&gt;
[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka (Co-)Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* [mailto:jenn@concentra-cms.com Jennifer Cummings] &amp;amp; [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
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). &lt;br /&gt;
&lt;br /&gt;
[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]&lt;br /&gt;
&lt;br /&gt;
Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair&lt;br /&gt;
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2020 Streaming Video Documents|2020 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )&lt;br /&gt;
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair&lt;br /&gt;
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)&lt;br /&gt;
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2021 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2021 Host Voting Documents|2021 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Roy Tennant - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [mailto:lillyho@gmail.com Lilly HS HO] - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
Coordinate with freenode to ensure that the #code4lib IRC &amp;amp; Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.&lt;br /&gt;
&lt;br /&gt;
[[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).&lt;br /&gt;
&lt;br /&gt;
[[2020 Accessibility Documents|2020 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2020 Whatever Documents|2020 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2020]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46686</id>
		<title>2019 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46686"/>
				<updated>2019-02-15T16:58:48Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2019 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: N/A&lt;br /&gt;
&lt;br /&gt;
* Karen Coyle&lt;br /&gt;
* Justin Coyne&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
* Erin Fahy&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Wayne Graham&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Megan Kudzia&lt;br /&gt;
* Anne Slaughter&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Monday, day before:&lt;br /&gt;
*  3pm - 6pm: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
*  3pm - 6pm: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  3pm - 6pm: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  3pm - 6pm: [[User:Anarchivist|Mark Matienzo]]&lt;br /&gt;
&lt;br /&gt;
Tuesday, preconference day:&lt;br /&gt;
*  8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]&lt;br /&gt;
*  8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]&lt;br /&gt;
* 1pm - 3pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, day one:&lt;br /&gt;
* 8am - 9:30am: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
* 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)&lt;br /&gt;
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)&lt;br /&gt;
* 7:30-8:30pm Reception: ''Your Name Here''&lt;br /&gt;
* https://www.thetech.org/floor-maps Floor Map. Lower Level&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: [[User:hardyoyo|Hardy Pottinger]]&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Tuesday, Preconference Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM volunteer: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  AM volunteer: Thomas Guignard&lt;br /&gt;
*  PM volunteer: Lydia Zvyagintseva&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Whitni''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: [[User:ChrisDay|Chris Day]]&lt;br /&gt;
*  PM volunteer: Lydia Zvyagintseva&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM volunteer: [[User:ChrisDay|Chris Day]]&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Cary Gordon&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [mailto:fu@usna.edu Li Fu]&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [mailto:fu@usna.edu Li Fu]&lt;br /&gt;
*  PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: Hardy Pottinger&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  [[User:ElissaThomas|Elissa Thomas]] (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West)&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  Jeff Rynhart (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  Jeff Rynhart (West)&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here'' (East);  Kevin Clair (West)&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
*  Before the conference: [[User:Kimpham54|Kim Pham]] &amp;amp; [[User:Anarchivist|Mark Matienzo]]&lt;br /&gt;
*  During the conference: [[User:Anarchivist|Mark Matienzo]] &amp;amp; &amp;quot;Your Name Here&amp;quot; &amp;amp; [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:tallgood|Tammy Allgood Wolf]]&lt;br /&gt;
&lt;br /&gt;
''[http://mailto:phette23@gmail.com Eric Phetteplace] can fill in one of the missing volunteering slots''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here'' -- Dre will do this one if no other volunteer steps up, but he's already got one so feel free to snatch it.&lt;br /&gt;
*  PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: 'Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Whitni''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail&lt;br /&gt;
*  [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46638</id>
		<title>2019 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46638"/>
				<updated>2019-02-08T17:50:19Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2019 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: N/A&lt;br /&gt;
&lt;br /&gt;
* Karen Coyle&lt;br /&gt;
* Justin Coyne&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
* Erin Fahy&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Wayne Graham&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Megan Kudzia&lt;br /&gt;
* Hardy Pottinger&lt;br /&gt;
* Anne Slaughter&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Monday, day before:&lt;br /&gt;
*  3pm - 6pm: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
*  3pm - 6pm: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  3pm - 6pm: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, preconference day:&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
* 1pm - 3pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, day one:&lt;br /&gt;
* 8am - 9:30am: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
* 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)&lt;br /&gt;
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)&lt;br /&gt;
* 7:30-8:30pm Reception: ''Your Name Here''&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Tuesday, Preconference Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Cary Gordon&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [http://mailto:fu@usna.edu Li Fu]&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [http://mailto:fu@usna.edu Li Fu]&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
*  Before the conference: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  During the conference: ''Your Name Here'' &amp;amp; &amp;quot;Your Name Here&amp;quot; &amp;amp; [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Dre&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: 'Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail&lt;br /&gt;
*  [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46637</id>
		<title>2019 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&amp;diff=46637"/>
				<updated>2019-02-08T17:50:04Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2019 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Community Support Volunteers ==&lt;br /&gt;
&lt;br /&gt;
See https://2019.code4lib.org/conduct/#officers for more details, including contact information.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: N/A&lt;br /&gt;
&lt;br /&gt;
* Karen Coyle&lt;br /&gt;
* Justin Coyne&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
* Erin Fahy&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
* Wayne Graham&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Megan Kudzia&lt;br /&gt;
* Hardy Pottinger&lt;br /&gt;
* Anne Slaughter&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics &amp;amp; Registration ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Monday, day before:&lt;br /&gt;
*  3pm - 6pm: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
*  3pm - 6pm: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  3pm - 6pm: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  3pm - 6pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday, preconference day:&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
*  8am - 10am: ''Your Name Here''&lt;br /&gt;
* 1pm - 3pm: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, day one:&lt;br /&gt;
* 8am - 9:30am: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
* 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)&lt;br /&gt;
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)&lt;br /&gt;
* 7:30-8:30pm Reception: ''Your Name Here''&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
* 9:30-10pm Game Night Cleanup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
Tuesday, Preconference Day:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day One:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
*  PM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
*  AM volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: Cary Gordon&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [http://mailto:fu@usna.edu Li Fu]&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: [http://mailto:fu@usna.edu Li Fu]&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: &lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: [[User:DataGazetteer|Peter Murray]] (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  PM volunteer: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
*  Before the conference: [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
*  During the conference: ''Your Name Here'' &amp;amp; &amp;quot;Your Name Here&amp;quot; &amp;amp; [[User:Kimpham54|Kim Pham]]&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: ''Dre''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: [[User:rtennant|Roy Tennant]]&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Onsite Volunteer Committee Coordinator:&lt;br /&gt;
&lt;br /&gt;
Wednesday, Day Two:&lt;br /&gt;
*  AM Volunteer: 'Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday, Day Three:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
*  PM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday, Day Four:&lt;br /&gt;
*  AM Volunteer: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail&lt;br /&gt;
*  [[User:rtennant|Roy Tennant]]&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2019_Keynote_Speakers_Nominations&amp;diff=46452</id>
		<title>2019 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2019_Keynote_Speakers_Nominations&amp;diff=46452"/>
				<updated>2018-10-13T01:00:05Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Becky Yoose&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.&lt;br /&gt;
&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the San José area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/[https://example.com hyperlinks] that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
==Tara Robertson  ==&lt;br /&gt;
&lt;br /&gt;
Tara works at Mozilla as the Diversity &amp;amp; Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year. &lt;br /&gt;
&lt;br /&gt;
More on [https://tararobertson.ca Tara].&lt;br /&gt;
&lt;br /&gt;
[https://tararobertson.ca/2016/lita-keynote/ Not all information wants to be free,] LITA Closing Keynote, 2016.&lt;br /&gt;
&lt;br /&gt;
==Mark Matienzo==&lt;br /&gt;
&lt;br /&gt;
Mark works at Stanford as the Collaboration &amp;amp; Interoperability Architect for Digital Library Systems and Services. &lt;br /&gt;
&lt;br /&gt;
Mark has worked at the intersection of technology, libraries, and systems for over a decade, serving as a technologist, advocate, and facilitator for cross-institutional projects. Prior to joining Stanford, Mark worked as an archivist, technologist, and strategist specializing in born-digital materials and metadata management, at institutions including the Digital Public Library of America, Yale University Library, The New York Public Library, and the American Institute of Physics. Mark would be an excellent keynote speaker because their long track record of involvement in cross-disciplinary and intra-institutional initiatives has given them a unique exposure to projects that touch on all aspects of library systems and tools. In addition, they are an outspoken advocate on a wide range of issues including labor, the environment, and leadership in libraries. &lt;br /&gt;
&lt;br /&gt;
More on [https://matienzo.org/ Mark].&lt;br /&gt;
&lt;br /&gt;
==Raj Jayadev==&lt;br /&gt;
&lt;br /&gt;
Raj Jayadev is the cofounder of [https://www.siliconvalleydebug.org/ Silicon Valley De-Bug], a community organizing, advocacy, and multimedia storytelling organization based in San José, California. Since its inception in 2001, Silicon Valley De-Bug has been a platform for Silicon Valley's diverse communities to impact the political, cultural, and social landscape of the region, while also becoming a nationally recognized model for community-based justice work. For nearly fifteen years, the organization has been a platform for the least heard of Silicon Valley — youth, immigrants, low-income workers, the incarcerated — to impact the the political, cultural, and social landscape of the region. Through De-Bug, Jayadev and is colleagues also started a family organizing model called the [https://acjusticeproject.org/ Albert Cobarrubias Justice Project] – a methodology for families and communities to impact the outcome of cases of their loved ones and change the landscape of power in the courts. They call the approach [https://www.participatorydefense.org/ &amp;quot;participatory defense&amp;quot;] and are now implementing the model nationally. Jayadev is a [https://www.macfound.org/fellows/1014/ 2018 MacArthur Foundation Fellow] and has been an [https://www.ashoka.org/en/fellow/raj-jayadev Ashoka Fellow] and a Rosenberg Foundation Leading Edge Fellow. All three recognitions are to support De-Bug’s innovative social justice work both locally and nationally. His writing and work has appeared and been profiled in media outlets such as the New York Times, Time.com, and National Public Radio.&lt;br /&gt;
&lt;br /&gt;
More about [https://aapip.org/our-stories/conversation-with-25-leaders-in-action-raj-jayadev Raj] ([https://acjusticeproject.org/about/contact-us/ contact info]).&lt;br /&gt;
&lt;br /&gt;
==Karla Monterroso==&lt;br /&gt;
&lt;br /&gt;
Karla Monterroso is the CEO of [http://www.code2040.org/ Code2040], a community of Black and Latinx technologists and their allies who are diversifying tech to create a more equitable, inclusive, and prosperous economy. Through high-impact direct service programs, robust in-person and online community engagement, and dynamic storytelling and knowledge sharing, Code2040 empowers and mobilizes diversity champions across the industry. She believes Code2040 sits in the perfect intersection of a skills- and network-building opportunity for Black and Latinx tech talent and a systems-change opportunity for a critical segment of the country's economy. Karla has focused much of her career growing the people and program functions of rapidly scaling social enterprises driving youth advocacy and leadership. Since joining Code2040 in 2014, she has grown the number of students served from 25 to 4,000, ushered in several new successful programs, and stewarded critical organizational development practices and policies around values and racial equity. Her success and insights on racial justice and equity have landed her in publications such as Fast Company, NPR, Bloomberg, and more.&lt;br /&gt;
&lt;br /&gt;
More about [https://twitter.com/karlitaliliana Karla].&lt;br /&gt;
&lt;br /&gt;
==Rick Prelinger==&lt;br /&gt;
&lt;br /&gt;
Rick Prelinger is an archivist, writer, filmmaker, and librarian. He is currently [http://film.ucsc.edu/faculty/rick_prelinger Professor of Film &amp;amp; Digital Media] at University of California, Santa Cruz. His archival work currently focuses on collecting, recontextualizing, and exhibiting home movies and amateur films, and is a renowned speaker on preservation, archives, and material culture in the anthropocene.  In 1982, he founded [https://en.wikipedia.org/wiki/Prelinger_Archives Prelinger Archives], a collection of industrial, advertising, educational and amateur films that was acquired by the Library of Congress in 2002. With Megan Prelinger, he is the co-founder of [http://www.prelingerlibrary.org/home/ Prelinger Library], an appropriation-friendly private research library open to the public in downtown San Francisco.  Prelinger has also partnered with the Internet Archive (of which he is a board member) to make 2,100 films available online for free viewing, downloading and reuse. His archival feature Panorama Ephemera (2004) played in venues around the world. Prelinger has recently made several film programs that he categorizes as “historical interventions,” called Lost Landscapes of San Francisco (7 annual parts) and Lost Landscapes of Detroit (3 annual parts).&lt;br /&gt;
&lt;br /&gt;
More about [http://prelinger.com/ Rick]. &lt;br /&gt;
&lt;br /&gt;
==Safiya U. Noble==&lt;br /&gt;
&lt;br /&gt;
From her website: &amp;quot;Dr. Safiya Umoja Noble is an Assistant Professor at the University of Southern California (USC) Annenberg School of Communication, and is the author of a best-selling book on racist and sexist algorithmic bias in commercial search engines, entitled Algorithms of Oppression: How Search Engines Reinforce Racism. [...] Previously, she was an assistant professor in the Department of Information Studies in the Graduate School of Education and Information Studies at UCLA where she held appointments in the Departments of African American Studies, Gender Studies, and Education.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
More about [https://safiyaunoble.com/ Safiya].&lt;br /&gt;
&lt;br /&gt;
==Sarah Mei==&lt;br /&gt;
&lt;br /&gt;
Sarah Mei is a Ruby and JavaScript developer and the Chief Consultant at DevMynd Software. With Sarah Allen, she founded [http://railsbridge.org/ RailsBridge], a community that provides free two-day workshops for members of under-represented groups in tech who want to learn Ruby on Rails. She also founded [http://bridgefoundry.org/ BridgeFoundry] to expand the RailsBridge model to other communities. Sarah is a renowned speaker and author on topics such as technical collaboration and pair programming, fostering inclusive communities, and Ruby development.&lt;br /&gt;
&lt;br /&gt;
More about [http://www.sarahmei.com/blog/ Sarah].&lt;br /&gt;
&lt;br /&gt;
==October Montoya ==&lt;br /&gt;
&lt;br /&gt;
October Montoya is a PhD student in the Communications and Science Studies Departments at UC San Diego. They hold a BA in Ethnic Studies, and a BA in Feminist Studies from University of California at Santa Cruz where their thesis, &amp;quot;Digital Activism in the Land of Abundant Failure: Silicon Valley and the Radical Re-Making of the Borders between Place and Space&amp;quot; explored the relationship between geography, technology, displacement, and change-making in their hometown of San Jose, California. Prior to attending graduate school, October engaged in various grassroots and coalitional forms of community organizing in the Bay Area, and this continues to influence their research interests, projects, and goals. They are also a contributing editor of San Jose-based literary journal Cheers from the Wasteland.&lt;br /&gt;
&lt;br /&gt;
More about October: [https://www.cheersfromthewasteland.com/october-montoya.html Cheersfromthewasteland] [http://communication.ucsd.edu/people/phd-students/october-montoya.html communication.ucsd.edu].&lt;br /&gt;
&lt;br /&gt;
== Isaac Schlueter ==&lt;br /&gt;
&lt;br /&gt;
Creator of npm, the JavaScript package manager, and CEO of npm, Inc. Isaac has been working in open source technology for decades and was instrumental in Node's early development, taking over from Node's creator Ryan Dahl and leading the project for a few years. While his contributions to open source software are notable, Isaac also leads by example with regards to diversity in the tech industry and creating a positive company atmosphere at npm. The company has [https://www.npmjs.com/jobs a code conduct] and emphasizes a healthy work/life balance. &amp;quot;We believe that the best way to iterate towards success is by taking care of ourselves, our families, our users, and one another.&amp;quot; Isaac is local to Oakland, California.&lt;br /&gt;
&lt;br /&gt;
More about Isaac: [http://izs.me/resume.html izs.me] [https://twitter.com/izs @izs]&lt;br /&gt;
&lt;br /&gt;
== [http://www.code2040.org/mimi-fox-melton/ Mimi Fox Melton] ==&lt;br /&gt;
&lt;br /&gt;
Director, Community Mobilization for [http://www.code2040.org/ Code2040]. As a first generation Haitian-American, Mimi’s passion lives at the intersection of Black and Brown liberation and empowerment. In her role at CODE2040, she designs experiences to build and strengthen community while resourcing and connecting agents of equity and inclusion within the Black and Latinx tech community. Before CODE2040, Mimi co-founded and ran Code for Progress, a non-profit coding bootcamp that pays adults of color as they learn to code and start careers in social justice tech.&lt;br /&gt;
&lt;br /&gt;
[http://www.code2040.org/speaker-request/ Form for requesting her (or another Code2040 staffer) to speak]&lt;br /&gt;
&lt;br /&gt;
== Becky Yoose ==&lt;br /&gt;
&lt;br /&gt;
Becky Yoose is the Library Applications and Systems Manager for the Seattle Public Library, perennial Code4Lib MC and presenter, and wearer of many hats, both physical and metaphorical. She has wrangled both library people and data for over a decade, working at academic and public libraries of different shapes and sizes, from libraries built exclusively on proprietary systems to Open Source library technology shops. Becky's data work includes cataloging and metadata work to administrating library systems, data warehouses and patron data privacy.  Her library community work includes extensive involvement in code4lib, LibTechWomen, Mashcat, and Troublesome Catalogers and Magical Metadata Fairies, as well as bridging the library world to other communities like Write The Docs. Becky's work and interests fall into the many intersections of technology, culture, privacy, community, and libraries.&lt;br /&gt;
&lt;br /&gt;
At past Code4Lib conferences, Becky has spoken thoughtfully and passionately about key issues in our community, including sustainability and burnout, compassionate project development, and the ethics of data analytics. She works for tea and chocolate, and prefers to use lard for her pie crust, though she will make vegan butter pie crust on request.&lt;br /&gt;
&lt;br /&gt;
More about Becky: [http://yobj.net yobj.net]&lt;br /&gt;
&lt;br /&gt;
Previous C4L talks:&lt;br /&gt;
* [https://www.slideshare.net/yo_bj/c4l15yoose Your code does not exist in a vacuum]&lt;br /&gt;
* [https://2016.code4lib.org/slides/yoose_libtech_burnout.pdf The Modern Day Sisyphus: #libtech Burnout and You]&lt;br /&gt;
* And others too numerous to mention.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2019]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&amp;diff=46065</id>
		<title>Code4Lib 2019 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&amp;diff=46065"/>
				<updated>2018-06-04T23:08:10Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: fixa linka&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2019 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Bay Area, California (more info coming soon)&lt;br /&gt;
* Dates: we're looking at February-April, 2019&lt;br /&gt;
** Pre-conferences: Coming Soon&lt;br /&gt;
** Main meeting: Coming Soon&lt;br /&gt;
** Post conference activities: Coming Soon&lt;br /&gt;
&lt;br /&gt;
== Local Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [mailto:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact&lt;br /&gt;
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact&lt;br /&gt;
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact&lt;br /&gt;
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact&lt;br /&gt;
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact&lt;br /&gt;
* Ray Pun, Fresno State - Tertiary Contact&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Secondary Contact aka Co-Chair&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget Committee ==&lt;br /&gt;
This group will focus on making sure we are appropriately planning for budgetary issues.   &lt;br /&gt;
&lt;br /&gt;
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Mark Matienzo - Local Planning Contact &lt;br /&gt;
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)&lt;br /&gt;
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF) &lt;br /&gt;
* [mailto:swayh@oclc.org Hank Sway] - Volunteer&lt;br /&gt;
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Keynote Documents|2019 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Program Documents|2019 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair &lt;br /&gt;
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact &lt;br /&gt;
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer&lt;br /&gt;
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer&lt;br /&gt;
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Scholarship Documents|2019 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair &lt;br /&gt;
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian &lt;br /&gt;
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] (Volunteer)&lt;br /&gt;
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] (Volunteer)&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 T-Shirt Documents|2019 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
This committee wrangles &amp;lt;s&amp;gt;tributes&amp;lt;/s&amp;gt; people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka (Co-)Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
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). &lt;br /&gt;
&lt;br /&gt;
[[2019 Social Activities Documents|2019 Social Activities Documents]]&lt;br /&gt;
&lt;br /&gt;
Conference goers - The page you are looking for is at [[2019 Social Activities]]&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2019 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2019 Host Voting Documents|2019 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Wifi and Electrical ==&lt;br /&gt;
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.&lt;br /&gt;
&lt;br /&gt;
[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact &lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2019 Book Giveaway Documents|2019 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
Coordinate with freenode to ensure that the #code4lib IRC &amp;amp; Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.&lt;br /&gt;
&lt;br /&gt;
[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).&lt;br /&gt;
&lt;br /&gt;
[[2019 Accessibility Documents|2019 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2019 Whatever Documents|2019 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&amp;diff=45950</id>
		<title>Code4Lib 2019 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&amp;diff=45950"/>
				<updated>2018-04-26T16:24:59Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Program Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2019 Conference Committees =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact (LPC) to each committee.&lt;br /&gt;
&lt;br /&gt;
== Location and Dates ==&lt;br /&gt;
&lt;br /&gt;
* Location: Bay Area, California (more info coming soon)&lt;br /&gt;
* Dates: we're looking at February-April, 2019&lt;br /&gt;
** Pre-conferences: Coming Soon&lt;br /&gt;
** Main meeting: Coming Soon&lt;br /&gt;
** Post conference activities: Coming Soon&lt;br /&gt;
&lt;br /&gt;
== Local Planning Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [mailto:nicole.esque@gmail.com Nicole Johnson], BePress - co-chair, Primary Contact&lt;br /&gt;
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact&lt;br /&gt;
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact&lt;br /&gt;
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact&lt;br /&gt;
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact&lt;br /&gt;
&lt;br /&gt;
== Website Working Group ==&lt;br /&gt;
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).  &lt;br /&gt;
&lt;br /&gt;
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Budget Committee ==&lt;br /&gt;
This group will focus on making sure we are appropriately planning for budgetary issues.   &lt;br /&gt;
&lt;br /&gt;
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF) &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Sponsorship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Keynote Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Keynote Documents|2019 Keynote Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Program Committee == &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Program Documents|2019 Program Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* [https://lib.ncsu.edu/akorphan Dre] - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer &lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.&lt;br /&gt;
&lt;br /&gt;
== Scholarship Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Scholarship Documents|2019 Scholarship Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair &lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian &lt;br /&gt;
* Your Name Here - Volunteer &lt;br /&gt;
* Your Name Here - Volunteer &lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 T-Shirt Documents|2019 T-Shirt Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
This committee wrangles &amp;lt;s&amp;gt;tributes&amp;lt;/s&amp;gt; people to volunteer for the following duties:&lt;br /&gt;
&lt;br /&gt;
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka (Co-)Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact (Southern California)&lt;br /&gt;
* Your Name Here - Local Planning Contact (Chattanooga)&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
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). &lt;br /&gt;
&lt;br /&gt;
[[2019 Social Activities Documents|2019 Social Activities Documents]]&lt;br /&gt;
&lt;br /&gt;
Conference goers - The page you are looking for is at [[2019 Social Activities]]&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Code4Lib 2019 Host Voting Committee ==&lt;br /&gt;
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. &lt;br /&gt;
&lt;br /&gt;
[[2019 Host Voting Documents|2019 Host Voting Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Wifi and Electrical ==&lt;br /&gt;
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.&lt;br /&gt;
&lt;br /&gt;
[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact/Local Planning Contact &lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Book Giveaway Committee ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
[[2019 Book Giveaway Documents|2019 Book Giveaway Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact (Southern California)&lt;br /&gt;
* Your Name Here - Local Planning Contact (Chattanooga)&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== IRC and Slack Committee ==&lt;br /&gt;
Coordinate with freenode to ensure that the #code4lib IRC &amp;amp; Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.&lt;br /&gt;
&lt;br /&gt;
[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Accessibility Committee ==&lt;br /&gt;
Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).&lt;br /&gt;
&lt;br /&gt;
[[2019 Accessibility Documents|2019 Accessibility Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact (Southern California)&lt;br /&gt;
* Your Name Here - Local Planning Contact (Chattanooga)&lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.&lt;br /&gt;
&lt;br /&gt;
[[2019 Whatever Documents|2019 Whatever Documents]]&lt;br /&gt;
&lt;br /&gt;
* Your Name Here - Primary Contact aka Chair&lt;br /&gt;
* Your Name Here - Secondary Contact aka Co-Chair&lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Local Planning Contact &lt;br /&gt;
* Your Name Here - Documentarian&lt;br /&gt;
* Your Name Here - Volunteer&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2019]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&amp;diff=45747</id>
		<title>2018 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&amp;diff=45747"/>
				<updated>2018-01-31T22:20:39Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Dre!!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2018 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the DC area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Monday 2/12:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday 2/13:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: [mailto:durden@umd.edu David Durden]&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup &amp;amp; Sessions==&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Preconference Setup and sessions Tuesday 2/13:&lt;br /&gt;
*  Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Tuesday 2/13:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
Livestream assitants 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!&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*  Before the conference: [[User:Anarchivist|Mark Matienzo]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD (AM?): Becky Yoose&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD (AM, but not if that's when my talk is): Dre&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  AM Session: Mary Jinglewski&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]&lt;br /&gt;
*  Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  [mailto:bomanca@miamioh.edu Craig Boman]&lt;br /&gt;
*  [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2018]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&amp;diff=45746</id>
		<title>2018 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&amp;diff=45746"/>
				<updated>2018-01-31T22:19:29Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: dre!&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2018 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the DC area (or know it very well), you can pick up a white &amp;quot;LOCAL&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Monday 2/12:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday 2/13:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: [mailto:durden@umd.edu David Durden]&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup &amp;amp; Sessions==&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Preconference Setup and sessions Tuesday 2/13:&lt;br /&gt;
*  Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Tuesday 2/13:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
Livestream assitants 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!&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
*  Time TBD: ''Your Name Here'' (East);  ''Your Name Here'' (West);&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
*  Before the conference: [[User:Anarchivist|Mark Matienzo]]&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD (AM?): Becky Yoose&lt;br /&gt;
*  Time TBD (whenever my talk's not, but not Wednesday AM): Dre&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD:''Your Name Here''&lt;br /&gt;
*  Time TBD: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  AM Session: Mary Jinglewski&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Wednesday 2/14:&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]&lt;br /&gt;
&lt;br /&gt;
Thursday 2/15:&lt;br /&gt;
*  Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]&lt;br /&gt;
*  Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Friday 2/16:&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
*  Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  [mailto:bomanca@miamioh.edu Craig Boman]&lt;br /&gt;
*  [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2018]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2018_Keynote_Speakers_Nominations&amp;diff=45509</id>
		<title>2018 Keynote Speakers Nominations</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2018_Keynote_Speakers_Nominations&amp;diff=45509"/>
				<updated>2017-10-02T14:00:35Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nominations for invited speakers/keynotes for Code4Lib 2018 in Washington, D.C. will open on '''September 18th''' and close on '''October 15, 2017'''.&lt;br /&gt;
&lt;br /&gt;
Voting will start on Monday, October 23, 2017 and continue through Monday, November 13, 2017.&lt;br /&gt;
&lt;br /&gt;
Please include a description and any relevant links and try to keep the list in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
The criteria for nominating a candidate to act as keynote are below:&lt;br /&gt;
*Speaker’s name (First Name, Last Name)&lt;br /&gt;
*Brief description of individual (250-word max)&lt;br /&gt;
*Pertinent links (Maximum of 3)&lt;br /&gt;
*Contact information of candidate (email address)&lt;br /&gt;
&lt;br /&gt;
''We strongly encourage you to nominate speakers who are local to the D.C. Metropolitan Area.'' &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please follow the formatting guidelines:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Nominee's Name ==&lt;br /&gt;
&lt;br /&gt;
Description of no more than 250 words.&lt;br /&gt;
&lt;br /&gt;
[[Link(s) with contact information for nominee]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Jane Doe (example)==&lt;br /&gt;
Jane works at ________, doing _______. &lt;br /&gt;
&lt;br /&gt;
Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.&lt;br /&gt;
&lt;br /&gt;
== Terry Brady ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[https://github.com/terrywbrady/info GitHub]&lt;br /&gt;
[https://github.com/Georgetown-University-Libraries/File-Analyzer File-Analyzer]&lt;br /&gt;
[https://repository.library.georgetown.edu/ DigitalGeorgetown]&lt;br /&gt;
&lt;br /&gt;
==Jessica Marie Johnson==&lt;br /&gt;
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 &amp;quot;The Codex,&amp;quot; a triptych that also functions as an exploration of the Atlantic slave trade by using code and software applications. &lt;br /&gt;
&lt;br /&gt;
[http://history.jhu.edu/directory/jessica-johnson/]&lt;br /&gt;
[https://lareviewofbooks.org/article/digital-humanities-interview-jessica-marie-johnson/#!]&lt;br /&gt;
[http://dh.jmjafrx.com/]&lt;br /&gt;
&lt;br /&gt;
==Veni Kunche==&lt;br /&gt;
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..&lt;br /&gt;
&lt;br /&gt;
[https://www.linkedin.com/in/venikunche/ Linkedin]&lt;br /&gt;
[https://twitter.com/venikunche @venikunche]&lt;br /&gt;
[http://www.codewithveni.com/ Code with Veni]&lt;br /&gt;
&lt;br /&gt;
==Shane Lin==&lt;br /&gt;
Senior Developer at the University of Virginia's Scholars' Lab.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
[http://scholarslab.org/people/shane-lin/ Shane Lin]&lt;br /&gt;
[http://scholarslab.org/digital-humanities/the-long-and-messy-history-of-privacy/ Privacy Post]&lt;br /&gt;
&lt;br /&gt;
==Pamela Wright==&lt;br /&gt;
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).   &lt;br /&gt;
&lt;br /&gt;
[https://twitter.com/PamelaSW]&lt;br /&gt;
[https://historyhub.history.gov/welcome]&lt;br /&gt;
[https://www.linkedin.com/in/pamela-wright-8ab59861]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Bess Sadler ==&lt;br /&gt;
&lt;br /&gt;
Bess Sadler is a library coding (and Code4Lib) institution. Bess has been building digital repositories for over fifteen years. She is a co-founder of both the Blacklight and &amp;lt;s&amp;gt;Hydra&amp;lt;/s&amp;gt; Samvera software projects, and is a passionate advocate for open source software and DevOps culture. Before joining DCE, Bess was the Manager for Application Development at Stanford University Library, where she managed a portfolio that included EarthWorks, Library Systems, DevOps, linked data infrastructure development, and strategic planning for long term digital preservation and sustainable development practices.  In her spare time, Bess enjoys gardening, cooking, contributing to social justice movements, and reading comic books.&lt;br /&gt;
&lt;br /&gt;
https://twitter.com/eosadler&lt;br /&gt;
https://curationexperts.com/who-we-are/&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2017_Conference_Volunteers&amp;diff=44813</id>
		<title>2017 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2017_Conference_Volunteers&amp;diff=44813"/>
				<updated>2017-02-21T17:55:49Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: added mc&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2017 Conference Volunteers =&lt;br /&gt;
&lt;br /&gt;
Call for volunteers during the actual conference, as opposed to the conference planning committees.&lt;br /&gt;
&lt;br /&gt;
== Concierge/Local Guides ==&lt;br /&gt;
Available after sessions to direct people to evening activities and local points of interest, etc.&lt;br /&gt;
&lt;br /&gt;
If you're local to the Los Angeles area (or know it very well), you can pick up a {insert color} &amp;quot;Local Guide&amp;quot; ribbon at check-in.  Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Monday 3/6:&lt;br /&gt;
*  8a-12p: [mailto:bobbi_fox@harvard.edu Bobbi Fox]&lt;br /&gt;
*  12p-4p: [mailto:lolliffe@getty.edu Lawrence Olliffe]&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7:&lt;br /&gt;
*  8a-12p: ''Your Name Here'', ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup &amp;amp; Sessions==&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Preconference Setup Monday 3/6:&lt;br /&gt;
*  8a-9:30a: 6 UCLA&lt;br /&gt;
*  12:30p-2p: 6 UCLA&lt;br /&gt;
&lt;br /&gt;
Preconference Sessions Monday 3/6:&lt;br /&gt;
*  11:45a-12:15p at Powell: ''Your Name Here''&lt;br /&gt;
*  11:45a-12:15p at Young: ''Your Name Here''&lt;br /&gt;
*  11:45a-12:15p at Science &amp;amp; Engineering Library: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
*  4:15p-4:45p at Powell: ''Your Name Here''&lt;br /&gt;
*  4:15p-4:45p at Young: [mailto:kimpham54@gmail.com Kim Pham]&lt;br /&gt;
*  4:15p-4:45p at Science &amp;amp; Engineering Library: ''Your Name Here'', ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc.&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8:&lt;br /&gt;
*  6p-9p: ''Your Name Here''&lt;br /&gt;
*  8p-11p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7:&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
*  1p-5p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8:&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
*  1p-5p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 3/9:&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Mic-minders ==&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7:&lt;br /&gt;
*  9a-12p: ''Your Name Here''&lt;br /&gt;
*  1p-5p: [mailto:mheller1@luc.edu Margaret Heller]&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8:&lt;br /&gt;
*  9a-12p: ''Your Name Here''&lt;br /&gt;
*  1p-5p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 3/9:&lt;br /&gt;
*  9a-12p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream Assistants (Onsite) ==&lt;br /&gt;
Livestream assitants 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!&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7:&lt;br /&gt;
*  8a-12p: [mailto:mlevy@ushmm.org Michael Levy]&lt;br /&gt;
*  8a-12p: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
&lt;br /&gt;
*  12:30p-5p: ''Your Name Here''&lt;br /&gt;
*  12:30p-5p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8:&lt;br /&gt;
*  8a-12p: [[User:Khaley|Kathleen Haley]]&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
*  12:30p-5p: ''Your Name Here''&lt;br /&gt;
*  12:30p-5p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 3/9:&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
*  8a-12p: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Livestream QA (Remote) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7:&lt;br /&gt;
*  9a-12p: [mailto:jswierc1@swarthmore.edu Julie Swierczek] (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)&lt;br /&gt;
*  1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8:&lt;br /&gt;
*  9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)&lt;br /&gt;
*  1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)&lt;br /&gt;
&lt;br /&gt;
Thursday 3/9:&lt;br /&gt;
*  9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)&lt;br /&gt;
&lt;br /&gt;
== IRC/Slack (Technical) ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]&lt;br /&gt;
&lt;br /&gt;
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]&lt;br /&gt;
* Your name here&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday 3/7 &lt;br /&gt;
*  AM: [[User:Yoosebj|Becky]], who shall continue her reign as Destroyer of Names.&lt;br /&gt;
*  PM: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday 3/8&lt;br /&gt;
*  AM: Dre, but feel free to boot me if someone desperately wants to MC and slots are full.&lt;br /&gt;
*  PM1: [[User:highermath|Cary Gordon]]&lt;br /&gt;
*  PM2: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday 3/9 &lt;br /&gt;
*  AM: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
*  Primary: ''Your Name Here''&lt;br /&gt;
*  Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
*  Primary: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
*  Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
*  Primary: ''Your Name Here''&lt;br /&gt;
*  Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*  Primary: [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
*  Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
*  Primary: ''Your Name Here''&lt;br /&gt;
*  Backup: ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
&lt;br /&gt;
*  Lawrence Olliffe&lt;br /&gt;
*  [mailto:bobbi_fox@harvard.edu Bobbi Fox]&lt;br /&gt;
*  [mailto:mheller1@luc.edu Margaret Heller]&lt;br /&gt;
*  [mailto:matt.r.sherman@gmail.com Matt Sherman]&lt;br /&gt;
*  ''Your Name Here''&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2017]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43871</id>
		<title>2016 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43871"/>
				<updated>2016-02-08T13:49:23Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* The Whatever Crew */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2016 Volunteers sign-up page.  As conference plans evolve, the page will be periodically updated with new opportunities to volunteer.  When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.&lt;br /&gt;
&lt;br /&gt;
For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon/Concierge ==&lt;br /&gt;
&lt;br /&gt;
Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Sunday:&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Chad Nelson&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Monday:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Sheraton Society Hill (Conference Hotel):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Chemical Heritage Foundation:&lt;br /&gt;
* Anna Headley (CHF contact)&lt;br /&gt;
* Michelle DiMeo (CHF contact)&lt;br /&gt;
&lt;br /&gt;
Franklin Hall:&lt;br /&gt;
* Scott Ziegler (venue contact at APS)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter and IRC:&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Tuesday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Livestream ==&lt;br /&gt;
Volunteers for the livestream will assist the livestream technician with conferencee streaming.  Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC (Technical) ==&lt;br /&gt;
&lt;br /&gt;
Access:&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Helper:&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration Desk ==&lt;br /&gt;
Assists with handing out registration materials to attendees.&lt;br /&gt;
&lt;br /&gt;
Monday AM (8:00-9:30):&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
*  Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Monday PM (12:00-1:30):&lt;br /&gt;
*&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Tuesday AM (7:00-9:30):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* David Lacy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
* Anna Headley&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
* Dre&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
* Dre&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2016]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43870</id>
		<title>2016 Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2016_Conference_Volunteers&amp;diff=43870"/>
				<updated>2016-02-08T13:48:41Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2016 Volunteers sign-up page.  As conference plans evolve, the page will be periodically updated with new opportunities to volunteer.  When you sign up please either include some way to contact you or send your contact information to Kathleen Haley (Chair for Volunteers) at KHaley AT mwa DOT org.&lt;br /&gt;
&lt;br /&gt;
For general questions, or if you identify a volunteer need not covered in the list below, feel free to contact Kathleen or David Uspal (LPC Committee Contact for Volunteers) at david DOT uspal AT villanova DOT edu.&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon/Concierge ==&lt;br /&gt;
&lt;br /&gt;
Helps with greeting newcomers, directing people to evening activities and local points of interest, etc. and being generally awesome to the community.&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conference Logistics ==&lt;br /&gt;
&lt;br /&gt;
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.&lt;br /&gt;
&lt;br /&gt;
Sunday:&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Chad Nelson&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Monday:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
Sheraton Society Hill (Conference Hotel):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Chemical Heritage Foundation:&lt;br /&gt;
* Anna Headley (CHF contact)&lt;br /&gt;
* Michelle DiMeo (CHF contact)&lt;br /&gt;
&lt;br /&gt;
Franklin Hall:&lt;br /&gt;
* Scott Ziegler (venue contact at APS)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
&lt;br /&gt;
Answering general questions on Twitter and IRC:&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)&lt;br /&gt;
&lt;br /&gt;
Tuesday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Livestream ==&lt;br /&gt;
Volunteers for the livestream will assist the livestream technician with conferencee streaming.  Their main duty will be to serve as a backup minder of the equipment in case the technician needs to step aside for a break.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC (Technical) ==&lt;br /&gt;
&lt;br /&gt;
Access:&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people.&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Helper:&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration Desk ==&lt;br /&gt;
Assists with handing out registration materials to attendees.&lt;br /&gt;
&lt;br /&gt;
Monday AM (8:00-9:30):&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
*  Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Monday PM (12:00-1:30):&lt;br /&gt;
*&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
Tuesday AM (7:00-9:30):&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* David Lacy&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Shaun Ellis&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
* Anna Headley&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
* Dre&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Session Timers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
Tuesday AM:&lt;br /&gt;
* &lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM:&lt;br /&gt;
* Lauren Gala&lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM:&lt;br /&gt;
*  Lauren Gala&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== The Whatever Crew ==&lt;br /&gt;
Volunteers who are willing to help with various tasks as needed during the conference. &lt;br /&gt;
* &lt;br /&gt;
* Katherine Lynch&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2016]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&amp;diff=42751</id>
		<title>2015 Lightning Talks</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Lightning_Talks&amp;diff=42751"/>
				<updated>2015-02-11T01:13:29Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: information design slides&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
==Lightning Talks==&lt;br /&gt;
&amp;lt;big&amp;gt;'''Lightning talk signup will begin after the opening session, on a (physical) sign up board.  As spots fill, we'll add them here for convenient reference.'''&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Tuesday 14:30 PM to 15:30 PM==&lt;br /&gt;
# Automated Entity Extractions to Relate Library Resources - Kyle Banerjee&lt;br /&gt;
# ResCarta Recap&lt;br /&gt;
# [https://drive.google.com/file/d/0B6S516ceOR1nalpHOGFJdFVnclk/view?usp=sharing Information Design Thoughts] - Dre&lt;br /&gt;
# Vufind &amp;amp; Worldcat Discovery API - Karen Coombs&lt;br /&gt;
# Video Accessibility - Jason Ronallo&lt;br /&gt;
# ILS and Payment Systems - Josh Weisman&lt;br /&gt;
# Fedora 4 Migration - Adam Wead&lt;br /&gt;
# [[https://gist.github.com/cbeer/4082dd15b62090f94b98 LDPath]] - Chris Beer&lt;br /&gt;
# [[https://drive.google.com/file/d/0B5jVboA5eH6ATHhSRnZCczhvLVE/view?usp=sharing Self-Deposit of Scientific Data]] - Darren Hardy&lt;br /&gt;
# Bread - Mx. Matienzo&lt;br /&gt;
&lt;br /&gt;
==Wednesday 11:00 AM to 12:00 PM==&lt;br /&gt;
# &lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
==Thursday 10:15 AM to 11:00 AM==&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42710</id>
		<title>2015 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42710"/>
				<updated>2015-02-10T16:29:22Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: whatever else&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2015 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup Help ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Eric Frierson (at frierson)&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.&lt;br /&gt;
&lt;br /&gt;
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.&lt;br /&gt;
&lt;br /&gt;
*Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
== Beverage Share Setup/Teardown ==&lt;br /&gt;
&lt;br /&gt;
Help set up and clean up after the Tuesday event at the Ebay offices.&lt;br /&gt;
&lt;br /&gt;
* Karen Estlund - setup&lt;br /&gt;
* John Sarnowski - clean up (at ResCarta)&lt;br /&gt;
* Dominic Bordelon - clean up&lt;br /&gt;
* Whitni Watkins - setup (at NimbleLibrarian)&lt;br /&gt;
* Ben Armintor - both/either (barmintor)&lt;br /&gt;
* Bobbi Fox - setup&lt;br /&gt;
* Matt Critchlow - clean up&lt;br /&gt;
* Francis Kayiwa - clean up&lt;br /&gt;
&lt;br /&gt;
We need volunteers to let attendees and/or the OLCC in through the doors and direct them upstairs throughout the event.&lt;br /&gt;
&lt;br /&gt;
== IRC Helpers ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson (bibliotechy)&lt;br /&gt;
* Mx Matienzo (anarchivist; as needed)&lt;br /&gt;
&lt;br /&gt;
One of the easiest ways to participate is to go to [http://webchat.freenode.net/ Freenode Webchat] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter &amp;quot;#code4lib&amp;quot; as the &amp;quot;Channel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you've managed to get into the channel without help, type &amp;quot;@helpers&amp;quot; (without the quotes) to see a list of #code4lib helpers.&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people&lt;br /&gt;
&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
'''Monday'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.  &lt;br /&gt;
'''Tuesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
'''Wednesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
&lt;br /&gt;
==Video Streaming==&lt;br /&gt;
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.&lt;br /&gt;
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.&lt;br /&gt;
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.&lt;br /&gt;
&lt;br /&gt;
You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.&lt;br /&gt;
&lt;br /&gt;
'''Video Team will meet in the ballroom on Tuesday morning at 8 AM'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Steven Anderson (at scande3)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Steven Anderson (at scande3)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr, go big or go home)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
*Terry R., likes to put birds on things&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Eric, mumbler extraordinaire&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
*Cary, taller than Becky, will not sing.&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
*Dre, less hatted than Becky, guaranteed to accidentally trip over something (either physical or verbal), and most importantly totally here on Thursday&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Maura Carbone&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
* Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
* Eric Phetteplace (at phette23)&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Else Needs to be Done ==&lt;br /&gt;
&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
* Dre (cell 401 261 8444 please don't send me weird crap)&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42707</id>
		<title>2015 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_During_the_Conference_Volunteers&amp;diff=42707"/>
				<updated>2015-02-10T16:07:40Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Added thursday MC&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2015 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Preconference Setup Help ==&lt;br /&gt;
&lt;br /&gt;
Help manage preconference sessions, setting up projectors, etc.&lt;br /&gt;
&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Eric Frierson (at frierson)&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
1-2 person(s) to take questions for sessions (assuming there's time during the session) via Twitter/IRC, and adding resources to lanyrd schedule (slides, notes, resources mentioned, etc.) Make a note if you can only do one or both.&lt;br /&gt;
&lt;br /&gt;
Consider directing people with questions to presenter on twitter/IRC (if applicable) if there is no time for questions.&lt;br /&gt;
&lt;br /&gt;
*Whitni Watkins (at NimbleLibrarian)&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
&lt;br /&gt;
== Beverage Share Setup/Teardown ==&lt;br /&gt;
&lt;br /&gt;
Help set up and clean up after the Tuesday event at the Ebay offices.&lt;br /&gt;
&lt;br /&gt;
* Karen Estlund - setup&lt;br /&gt;
* John Sarnowski - clean up (at ResCarta)&lt;br /&gt;
* Dominic Bordelon - clean up&lt;br /&gt;
* Whitni Watkins - setup (at NimbleLibrarian)&lt;br /&gt;
* Ben Armintor - both/either (barmintor)&lt;br /&gt;
* Bobbi Fox - setup&lt;br /&gt;
* Matt Critchlow - clean up&lt;br /&gt;
* Francis Kayiwa - clean up&lt;br /&gt;
&lt;br /&gt;
We need volunteers to let attendees and/or the OLCC in through the doors and direct them upstairs throughout the event.&lt;br /&gt;
&lt;br /&gt;
== IRC Helpers ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson (bibliotechy)&lt;br /&gt;
* Mx Matienzo (anarchivist; as needed)&lt;br /&gt;
&lt;br /&gt;
One of the easiest ways to participate is to go to [http://webchat.freenode.net/ Freenode Webchat] with your web browser. Choose a nickname (anything works so long as it is unique; if you want to be anonymous pick appropriately). Enter &amp;quot;#code4lib&amp;quot; as the &amp;quot;Channel&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
If you've managed to get into the channel without help, type &amp;quot;@helpers&amp;quot; (without the quotes) to see a list of #code4lib helpers.&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people&lt;br /&gt;
&lt;br /&gt;
* Mx Matienzo (anarchivist)&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
'''Monday'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Whitni Watkins (at NimbleLibrarian) -- if we only need one desk volunteer, let me know.  &lt;br /&gt;
'''Tuesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
'''Wednesday'''&lt;br /&gt;
* Christina Harlow (at cm_harlow)&lt;br /&gt;
* Bobbi Fox&lt;br /&gt;
&lt;br /&gt;
==Video Streaming==&lt;br /&gt;
We need two volunteers for each session, one at the front near the speaker and one at the rear at the camera/encoder.&lt;br /&gt;
We will have a brief training on Monday Afternoon. If you can't make the training, we will perform magic knowledge transfer.&lt;br /&gt;
This is not a highly technical position, if you can recognize a video camera two times out of three, you're in.&lt;br /&gt;
&lt;br /&gt;
You are welcome to work multiple sessions, or all of them. This will get you really good karma and many free drinks.&lt;br /&gt;
&lt;br /&gt;
'''Video Team will meet in the ballroom on Tuesday morning at 8 AM'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Steven Anderson (at scande3)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Steven Anderson (at scande3)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
&lt;br /&gt;
* Ashley Blewer (at ablwr, go big or go home)&lt;br /&gt;
* Josh Wilson (at bluestraggler || joshwilsonnc at gmail)&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
*Terry R., likes to put birds on things&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Eric, mumbler extraordinaire&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
*Cary, taller than Becky, will not sing.&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
*Dre, less hatted than Becky, guaranteed to accidentally trip over something (either physical or verbal), and most importantly totally here on Thursday&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
'''Tuesday AM'''&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Tuesday PM'''&lt;br /&gt;
*Maura Carbone&lt;br /&gt;
* Francis Kayiwa (Mr. Sweetie Poo https://www.youtube.com/watch?v=xAnVNXaa5oA)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday AM'''&lt;br /&gt;
* John Sarnowski (at ResCarta)&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
'''Wednesday PM'''&lt;br /&gt;
* Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
'''Thursday AM'''&lt;br /&gt;
* Eric Phetteplace (at phette23)&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Else Needs to be Done ==&lt;br /&gt;
&lt;br /&gt;
* Sarah Simpkin (at sarahsimpkin)&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42693</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42693"/>
				<updated>2015-02-09T21:21:18Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Added slides to fail4lib&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions. &lt;br /&gt;
&lt;br /&gt;
== Preconference Schedule ==&lt;br /&gt;
See below for further information on each session.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Presentations workshop (1: Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  [[code4lib/Write The Docs barcamp]] (5)&lt;br /&gt;
|-&lt;br /&gt;
| '''Broadway I &amp;amp; II (70)''' || Linked Data Workshop (56: Bringing their own projector) || Intro to Git &amp;amp; possibly beyond (40: Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Broadway III &amp;amp; IV (70)''' || Visualizing Library Data (60: Needs: projector)  || Intro to Docker (52)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) ||  Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating - must be in this room - limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || (Empty) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || DPLA API Workshop (34: Bringing their own projector) &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Pre-conferences ==&lt;br /&gt;
===MORNING:===&lt;br /&gt;
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
This hands on workshop will step through the components of the application framework and the process of customizing the application.&lt;br /&gt;
&lt;br /&gt;
'''TRAINING OUTLINE'''&lt;br /&gt;
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015&lt;br /&gt;
&lt;br /&gt;
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.&lt;br /&gt;
 &lt;br /&gt;
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.&lt;br /&gt;
&lt;br /&gt;
==== Delivering and Preserving GIS Data ====&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
* Eliot Jordan, Princeton University&lt;br /&gt;
&lt;br /&gt;
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
'''[https://stanford.box.com/geohydra-code4lib2015 Slides]'''  [http://slides.com/eliotjordan/practical-experience-with-geoserver/ Slides (GeoServer)]&lt;br /&gt;
&lt;br /&gt;
====Linked Data Workshop====&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.&lt;br /&gt;
&lt;br /&gt;
[http://goo.gl/QrUIYE LD Workshop Materials]&lt;br /&gt;
&lt;br /&gt;
====RailsBridge: Intro to programming in Ruby on Rails====&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Laney McGlohon, Stanford University, laneymcg@stanford.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''&lt;br /&gt;
To help the class run smoothly please complete the install fest before attending the class.  If you have problems contact us!&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].&lt;br /&gt;
&lt;br /&gt;
====Replace yourself with a painfully complex bash script...or try Ansible====&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.&lt;br /&gt;
&lt;br /&gt;
====Visualizing Library Data====&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.&lt;br /&gt;
&lt;br /&gt;
===FULL DAY:===&lt;br /&gt;
&lt;br /&gt;
====Code Retreat====&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.&lt;br /&gt;
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
====Code4Arc ====&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems.  Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator.  We encourage others to chime in here to expand the list of tools available to touch and play with. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Ryan Rotter - sysadmin/developer&lt;br /&gt;
# Matt LaChance&lt;br /&gt;
# Maureen Callahan - archivist, often-times product owner&lt;br /&gt;
# Liza Harrell-Edge - end-user&lt;br /&gt;
# Jessica Venlet - end-user/archivist (can be there in the afternoon)&lt;br /&gt;
# Andrew Berger - &amp;quot;digital&amp;quot; archivist&lt;br /&gt;
# Bill Kelm - sysadmin&lt;br /&gt;
# Jeremy Floyd - end-user (archivist turned metadata librarian)&lt;br /&gt;
# Sara Amato (morning only)  - end-user&lt;br /&gt;
# Julie Hardesty (afternoon only) - end-user (metadata librarian)&lt;br /&gt;
&lt;br /&gt;
====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''&lt;br /&gt;
&lt;br /&gt;
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
===AFTERNOON:===&lt;br /&gt;
==== A hands-on introduction to GeoBlacklight ====&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==== CollectionSpace: Getting it up and running at your museum ====&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org&lt;br /&gt;
&lt;br /&gt;
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org&lt;br /&gt;
&lt;br /&gt;
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections.&lt;br /&gt;
&lt;br /&gt;
If possible, please bring a laptop capable of running the latest version of VirtualBox (www.virtualbox.org).  I've prepared a VirtualBox machine for the workshop that I will share with you at the beginning of the session.&lt;br /&gt;
&lt;br /&gt;
==== Dive into Hydra  ====&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software.   Dive into Hydra is a course that bootstraps you into the Hydra software framework.  We'll start at the basics and walk you through the various layers of the Hydra stack.   We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository.  Participants who have prior exposure to web programming will get the most out of this course.  It's recommended (but not required) that you attend &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
==== DPLA API Workshop: ====&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.&lt;br /&gt;
&lt;br /&gt;
==== Fail4Lib 2015 ====&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
'''[https://docs.google.com/presentation/d/1pdatzBjVIs1YDQL3CUhWjvSj_u5Y-9pOLZvb-PAdUaU/edit?usp=sharing SLIDES]'''&lt;br /&gt;
&lt;br /&gt;
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.&lt;br /&gt;
&lt;br /&gt;
''Readings''&lt;br /&gt;
&lt;br /&gt;
'''Case Study 1: The Healthcare.gov rollout'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries  (The Verge): Thanks a lot, healthcare.gov]&lt;br /&gt;
&lt;br /&gt;
* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]&lt;br /&gt;
&lt;br /&gt;
* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]&lt;br /&gt;
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]&lt;br /&gt;
&lt;br /&gt;
'''Case Study 2: The Challenger disaster'''&lt;br /&gt;
&lt;br /&gt;
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]&lt;br /&gt;
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.&lt;br /&gt;
&lt;br /&gt;
* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]&lt;br /&gt;
&lt;br /&gt;
* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]&lt;br /&gt;
* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]&lt;br /&gt;
&lt;br /&gt;
==== Intro to Docker ====&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu&lt;br /&gt;
&lt;br /&gt;
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.&lt;br /&gt;
&lt;br /&gt;
==== Intro to Git &amp;amp; possibly beyond ====&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
==== Presentations workshop ====&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42581</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=42581"/>
				<updated>2015-02-02T23:38:31Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: Added readings for code4lib&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions. &lt;br /&gt;
&lt;br /&gt;
== Preconference Schedule (draft) ==&lt;br /&gt;
There may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib. See below for further information on each session.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (9: Needs: projector, internet connection, and power strips) || Intro to Git &amp;amp; possibly beyond (40: Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor B (30)''' || Code Retreat (18: Needs whiteboard, dry-erase markers, projector) || Code Retreat (15: Needs whiteboard, dry-erase markers, projector) &lt;br /&gt;
|-&lt;br /&gt;
| '''Parlor C (30)''' || [[code4lib/Write The Docs barcamp]] (8: Needs: projector/screen, flipboard/whiteboard, power sources for laptops) ||  [[code4lib/Write The Docs barcamp]] (5)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' I (320) || '''CANCELLED''': [UXtravaganza] || Presentations workshop (1: Needs: projector/screen)&lt;br /&gt;
|-&lt;br /&gt;
| '''Grand Ballroom''' II (200) || Visualizing Library Data (60: Needs: projector)  || DPLA API Workshop (34: Bringing their own projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (1: Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (13: Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (25: Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (5: Needs: Projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (20: Need projector) || Intro to Docker (52)&lt;br /&gt;
|-&lt;br /&gt;
| '''Studio (35)''' || Linked Data Workshop (56: Bringing their own projector) || Dive into Hydra (29: Needs: projector/screen; Requests: classroom style seating)&lt;br /&gt;
|-&lt;br /&gt;
| '''Directors (35)''' || Code4Arc (20: Needs: projector) || Code4Arc (18: Needs: projector)&lt;br /&gt;
|-&lt;br /&gt;
| '''Council (45)''' || Delivering and Preserving GIS Data (10: Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (19: Needs: projector, outlets; Requests: list of attendees)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Pre-conferences ==&lt;br /&gt;
===MORNING:===&lt;br /&gt;
==== Coding Custom Solutions for Every Department in the Library with File Analyzer ====&lt;br /&gt;
Morning, Galleria I&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
This hands on workshop will step through the components of the application framework and the process of customizing the application.&lt;br /&gt;
&lt;br /&gt;
TRAINING OUTLINE&lt;br /&gt;
* https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training-Code4Lib-2015&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Julie Swierczek&lt;br /&gt;
&lt;br /&gt;
====Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable:====&lt;br /&gt;
Morning, Parlor A&lt;br /&gt;
* Karen A. Coombs, OCLC, coombsk@oclc.org&lt;br /&gt;
&lt;br /&gt;
Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.&lt;br /&gt;
 &lt;br /&gt;
We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Josh Wilson&lt;br /&gt;
&lt;br /&gt;
==== Delivering and Preserving GIS Data ====&lt;br /&gt;
Morning, Council&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
&lt;br /&gt;
====Linked Data Workshop====&lt;br /&gt;
Morning, Studio&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Logan Cox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Eben English&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Naomi Dushay (probably)&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# David Bass&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Chrissy Rissmeyer&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
# Brooke Sansosti&lt;br /&gt;
# Richard Tan&lt;br /&gt;
&lt;br /&gt;
====RailsBridge: Intro to programming in Ruby on Rails====&lt;br /&gt;
Morning, Galleria II&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Laney McGlohon, Stanford University, laneymcg@stanford.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
''HOME WORK: Please do in advance!! http://docs.railsbridge.org/installfest/''&lt;br /&gt;
To help the class run smoothly please complete the install fest before attending the class.  If you have problems contact us!&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
#Sarah Bavier&lt;br /&gt;
# Christina Salazar&lt;br /&gt;
&lt;br /&gt;
====Replace yourself with a painfully complex bash script...or try Ansible====&lt;br /&gt;
Morning, Galleria III&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Coral Sheldon-Hess&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Anna Headley&lt;br /&gt;
# Chelsea Lobdell&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Chris Sharp&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
&lt;br /&gt;
====Visualizing Library Data====&lt;br /&gt;
Morning, Grand Ballroom II&lt;br /&gt;
* Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs&lt;br /&gt;
&lt;br /&gt;
Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Ashley Blewer!&lt;br /&gt;
# Bobbi Fox&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Joshua Gomez&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Andy Mardesich&lt;br /&gt;
# Tao Zhao&lt;br /&gt;
# Chris Hallberg&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Eben English&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Steve Meyer&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Andrew Pasterfield&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Naomi Dushay (maybe)&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Greg Bem (Morning only)&lt;br /&gt;
# Dominic Bordelon&lt;br /&gt;
&lt;br /&gt;
===FULL DAY:===&lt;br /&gt;
&lt;br /&gt;
====Code Retreat====&lt;br /&gt;
Full Day, Parlor B&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.&lt;br /&gt;
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Mike Giarlo&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Devon Smith&lt;br /&gt;
# Barbara Hui&lt;br /&gt;
# Carol Bean&lt;br /&gt;
# Matt Connolly&lt;br /&gt;
# James Van Mil&lt;br /&gt;
# Glen Horton&lt;br /&gt;
&lt;br /&gt;
====Code4Arc ====&lt;br /&gt;
Full Day, Directors&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
* Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org&lt;br /&gt;
* Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com&lt;br /&gt;
&lt;br /&gt;
What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? &lt;br /&gt;
&lt;br /&gt;
Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems.  Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
* Panel type conversations about the State of Art in Archives &lt;br /&gt;
* Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed &lt;br /&gt;
* Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)&lt;br /&gt;
&lt;br /&gt;
Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator.  We encourage others to chime in here to expand the list of tools available to touch and play with. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Laney McGlohon - developer&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Ryan Rotter - sysadmin/developer&lt;br /&gt;
# Matt LaChance&lt;br /&gt;
# Maureen Callahan - archivist, often-times product owner&lt;br /&gt;
# Liza Harrell-Edge - end-user&lt;br /&gt;
# Jessica Venlet - end-user/archivist (can be there in the afternoon)&lt;br /&gt;
# Andrew Berger - &amp;quot;digital&amp;quot; archivist&lt;br /&gt;
# Bill Kelm - sysadmin&lt;br /&gt;
# Jeremy Floyd - end-user (archivist turned metadata librarian)&lt;br /&gt;
&lt;br /&gt;
====[http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp code4lib/Write The Docs barcamp]====&lt;br /&gt;
Full day, Parlor C&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
'''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''&lt;br /&gt;
&lt;br /&gt;
Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. &lt;br /&gt;
&lt;br /&gt;
Remember, like metadata, documentation is a love note to the future.&lt;br /&gt;
&lt;br /&gt;
More information about Write the Docs at http://conf.writethedocs.org/ There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
'''Full day'''&lt;br /&gt;
# &lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Whitni Watkins&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
# Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. &lt;br /&gt;
# Chris Sharp&lt;br /&gt;
# Julie Swierczek&lt;br /&gt;
&lt;br /&gt;
===AFTERNOON:===&lt;br /&gt;
==== A hands-on introduction to GeoBlacklight ====&lt;br /&gt;
Afternoon, Council&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
&lt;br /&gt;
==== CollectionSpace: Getting it up and running at your museum ====&lt;br /&gt;
Afternoon, Galleria II&lt;br /&gt;
* Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org&lt;br /&gt;
* Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org&lt;br /&gt;
&lt;br /&gt;
This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org&lt;br /&gt;
&lt;br /&gt;
Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Terry Brady&lt;br /&gt;
# Sharon Clapp&lt;br /&gt;
&lt;br /&gt;
==== Dive into Hydra  ====&lt;br /&gt;
Afternoon, Studio&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software.   Dive into Hydra is a course that bootstraps you into the Hydra software framework.  We'll start at the basics and walk you through the various layers of the Hydra stack.   We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository.  Participants who have prior exposure to web programming will get the most out of this course.  It's recommended (but not required) that you attend &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
# Peggy Griesinger&lt;br /&gt;
# Mike Price&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Bass&lt;br /&gt;
# Scott Fisher&lt;br /&gt;
# Brian E. Davis&lt;br /&gt;
# Sarah Bavier&lt;br /&gt;
# Christina Salazar&lt;br /&gt;
&lt;br /&gt;
==== DPLA API Workshop: ====&lt;br /&gt;
Afternoon, Grand Ballroom II&lt;br /&gt;
* Audrey Altman, DPLA&lt;br /&gt;
* Mark Breedlove, DPLA&lt;br /&gt;
* Mark Matienzo, DPLA&lt;br /&gt;
* Tom Johnson, DPLA&lt;br /&gt;
&lt;br /&gt;
The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
# Ranti Junus&lt;br /&gt;
# Jean Rainwater&lt;br /&gt;
# Mita Williams&lt;br /&gt;
# Margaret Heller&lt;br /&gt;
# Bohyun Kim&lt;br /&gt;
# Steven Anderson&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Sarah Simpkin&lt;br /&gt;
# Mark Jarrell&lt;br /&gt;
# Heather Pitts&lt;br /&gt;
# Kathryn Stine&lt;br /&gt;
# Andrew Woods&lt;br /&gt;
# Greg Bem&lt;br /&gt;
# Brooke Sansosti&lt;br /&gt;
&lt;br /&gt;
==== Fail4Lib 2015 ====&lt;br /&gt;
Afternoon, Galleria I&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.&lt;br /&gt;
&lt;br /&gt;
''Readings''&lt;br /&gt;
&lt;br /&gt;
'''Case Study 1: The Healthcare.gov rollout'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.theverge.com/us-world/2013/12/3/5163228/healthcare-gov-obamacare-website-shows-how-government-can-do-tech-better Adrianne Jeffries  (The Verge): Thanks a lot, healthcare.gov]&lt;br /&gt;
&lt;br /&gt;
* [http://www.forbes.com/sites/lorenthompson/2013/12/03/healthcare-gov-diagnosis-the-government-broke-every-rule-of-project-management/ Loren Thompson (Forbes): Healthcare.gov diagnosis: the government broke every rule of project management]&lt;br /&gt;
&lt;br /&gt;
* Optional, nice summary: [http://npengage.com/nonprofit-technology/lessons-learned-from-the-healthcare-gov-rollout/ Bo Crader (npEngage): Lessons learned from the healthcare.gov rollout]&lt;br /&gt;
* Optional, very enterprisey: [http://www.enterprisetech.com/2014/04/04/hyperscale-lessons-healthcare-gov/ Alex Woodie (EnterpriseTech): The hyperscale lessons of healthcare.gov]&lt;br /&gt;
&lt;br /&gt;
'''Case Study 2: The Challenger disaster'''&lt;br /&gt;
&lt;br /&gt;
* [http://ethics.tamu.edu/Portals/3/Case%20Studies/Shuttle.pdf Engineering Ethics: The Space Shuttle Challenger disaster (case study instructor's guide)]&lt;br /&gt;
** This is designed as an instructor's guide, but the summary material beginning on page 3 stands on its own as a case study report. The instructor's materials on the first couple pages are also worth reading.&lt;br /&gt;
&lt;br /&gt;
* [http://www.nbcnews.com/id/3077541/ns/technology_and_science-space/t/shuttle-report-blames-nasa-culture/ NBC News: Shuttle report blames NASA culture]&lt;br /&gt;
&lt;br /&gt;
* Optional, good technical detail: [http://en.wikipedia.org/wiki/Space_Shuttle_Challenger_disaster Wikipedia: Space Shuttle Challenger disaster]&lt;br /&gt;
* Optional: [http://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt Richard Feynman: Appendix F: Personal observations on the reliability of the Shuttle (Rogers Commission excerpt)]&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
# Ray Schwartz&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
# Bret Davidson&lt;br /&gt;
# Hannah Sommers&lt;br /&gt;
&lt;br /&gt;
==== Intro to Docker ====&lt;br /&gt;
Afternoon, Galleria III&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, University of Maryland Libraries , fkayiwa at umd dot edu&lt;br /&gt;
&lt;br /&gt;
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
#  Jim Hahn&lt;br /&gt;
#  Joshua Gomez&lt;br /&gt;
#  Bobbi Fox&lt;br /&gt;
#  Ray Schwartz&lt;br /&gt;
#  Megan Kudzia&lt;br /&gt;
# Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)&lt;br /&gt;
# Cary Gordon (uses Docker in production on AWS)&lt;br /&gt;
# Eric Phetteplace&lt;br /&gt;
# Esther Verreau&lt;br /&gt;
# Charlie Morris&lt;br /&gt;
# Anna Headley (voting for afternoon, compliments ansible)&lt;br /&gt;
# Shaun Ellis&lt;br /&gt;
# Mark Mounts&lt;br /&gt;
# Matt Critchlow&lt;br /&gt;
# Ray Henry&lt;br /&gt;
# Eric Frierson&lt;br /&gt;
# Sara Amato&lt;br /&gt;
# David Lacy&lt;br /&gt;
# David Uspal&lt;br /&gt;
# Matt Bernhardt&lt;br /&gt;
# Brendan Quinn&lt;br /&gt;
# Anjanette Young&lt;br /&gt;
# Kevin S. Clarke&lt;br /&gt;
&lt;br /&gt;
==== Intro to Git &amp;amp; possibly beyond ====&lt;br /&gt;
Afternoon, Parlor A&lt;br /&gt;
* Erin Fahy, Stanford University, efahy@stanford.edu&lt;br /&gt;
* Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu&lt;br /&gt;
&lt;br /&gt;
We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:&lt;br /&gt;
* What is a Distributed Version Control System?&lt;br /&gt;
* What's the difference between Git and Github.com?&lt;br /&gt;
* How to initialize new Git projects locally and on a remote server/Github&lt;br /&gt;
* Cloning/Forking existing projects and keeping up to date&lt;br /&gt;
* The wonderful world of Git branches&lt;br /&gt;
* Interactive rebasing&lt;br /&gt;
* Contributing code to existing projects &amp;amp; what pull requests are&lt;br /&gt;
* How to handle merge conflicts&lt;br /&gt;
* Overview of workflows and branch best practices&lt;br /&gt;
* (time allowing) Advanced git: pre/post hooks, submodules, anything else?&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
# Jeannie Graham&lt;br /&gt;
# Derek Merleaux&lt;br /&gt;
# Laurie Reeves&lt;br /&gt;
# Bojana Skarich&lt;br /&gt;
# Heidi Frank&lt;br /&gt;
# Jason Raitz&lt;br /&gt;
# Emily Lynema&lt;br /&gt;
# Brian E. Davis&lt;br /&gt;
# Dominic Bordelon&lt;br /&gt;
# Richard Tan&lt;br /&gt;
&lt;br /&gt;
==== Presentations workshop ====&lt;br /&gt;
Afternoon, Grand Ballroom I&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=41891</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=41891"/>
				<updated>2014-11-03T20:00:52Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Fail4Lib 2015 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)&lt;br /&gt;
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu&lt;br /&gt;
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
=== Proposal formatting guidelines: ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Preconference Title: ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Facilitator's name, affiliation, and email address&lt;br /&gt;
* Second facilitator's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Proposals ==&lt;br /&gt;
&lt;br /&gt;
Post your ideas here!&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
&lt;br /&gt;
=== A hand's on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
# Andrew Battista&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
1. Jim Hahn&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.&lt;br /&gt;
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software.   Dive into Hydra is a course that bootstraps you into the Hydra software framework.  We'll start at the basics and walk you through the various layers of the Hydra stack.   We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository.  Participants who have prior exposure to web programming will get the most out of this course.  It's recommended (but not required) that you attend &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
''Placeholder for now - more information will be available before the proposal deadline''. More information about Write the Docs at http://docs.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Archivematica for users and developers ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.&lt;br /&gt;
&lt;br /&gt;
In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration.&lt;br /&gt;
&lt;br /&gt;
For the afternoon, we plan to bring the two groups together to discuss, share use cases, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessions. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Coding Custom Solutions for Every Department in the Library with File Analyzer ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Terry Brady, Georgetown University Library, twb27@georgetown.edu&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.&lt;br /&gt;
&lt;br /&gt;
* Analyzing Marc Records for the Cataloging department&lt;br /&gt;
* Transferring ILS invoices for the University Account System for the Acquisitions department &lt;br /&gt;
* Delivering patron fines to the Bursar’s office for the Access Service department&lt;br /&gt;
* Summarizing student worker timesheet data for the Finance department&lt;br /&gt;
* Validating counter compliant reports for the Electronic Resources department&lt;br /&gt;
* Preparing ingest packages for the Digital Services department&lt;br /&gt;
* Validating checksums for the Preservation department&lt;br /&gt;
&lt;br /&gt;
This hands on workshop will step through the components of the application framework.  Workshop participants will install and develop custom File Analyzer tasks in this session.&lt;br /&gt;
&lt;br /&gt;
The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=41869</id>
		<title>2015 Preconference Proposals</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&amp;diff=41869"/>
				<updated>2014-10-31T17:16:36Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Instructions ==&lt;br /&gt;
Thank you for considering proposing a pre-conference! Here are a few details:&lt;br /&gt;
&lt;br /&gt;
* We will be taking pre-conference proposals until '''November 7, 2014'''&lt;br /&gt;
* If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu&lt;br /&gt;
* Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]&lt;br /&gt;
* If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)&lt;br /&gt;
* If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu&lt;br /&gt;
* '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions&lt;br /&gt;
* Please use the template for proposals provided in the pre-formatted block below&lt;br /&gt;
&lt;br /&gt;
=== Proposal formatting guidelines: ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Preconference Title: ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Morning]&amp;quot;''' &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Facilitator's name, affiliation, and email address&lt;br /&gt;
* Second facilitator's name, affiliation, email address, if second speaker&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Proposals ==&lt;br /&gt;
&lt;br /&gt;
Post your ideas here!&lt;br /&gt;
&lt;br /&gt;
=== Delivering and Preserving GIS Data ===&lt;br /&gt;
 &lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== A hand's on introduction to GeoBlacklight ===&lt;br /&gt;
&lt;br /&gt;
'''Half Day [Afternoon]'''&lt;br /&gt;
&lt;br /&gt;
* Darren Hardy, Stanford University, drh@stanford.edu&lt;br /&gt;
* Jack Reed, Stanford University, pjreed@stanford.edu&lt;br /&gt;
&lt;br /&gt;
GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &amp;quot;Delivering and Preserving GIS Data&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
# Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
===RailsBridge: Intro to programming in Ruby on Rails===&lt;br /&gt;
'''&amp;quot;Half-Day&amp;quot; [morning]'''&lt;br /&gt;
* Contact Carolyn Cole, Penn State University, carolyn@psu.edu&lt;br /&gt;
* Additional instructors welcome&lt;br /&gt;
&lt;br /&gt;
Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.&lt;br /&gt;
&lt;br /&gt;
RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Replace yourself with a painfully complex bash script...or try Ansible ===&lt;br /&gt;
'''Half Day [Morning]'''&lt;br /&gt;
&lt;br /&gt;
* Chad Nelson, chad dot nelson @ lyrasis dot org&lt;br /&gt;
* Blake Carver, Blake dot carver @lyrasis dot org&lt;br /&gt;
&lt;br /&gt;
Abstract: &lt;br /&gt;
&lt;br /&gt;
[http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
=== Intro to Docker ===&lt;br /&gt;
'''Half Day [Whenever]'''&lt;br /&gt;
&lt;br /&gt;
* John Fink, McMaster University, john dot fink at gmail dot com&lt;br /&gt;
* Francis Kayiwa, Kayiwa Consulting , francis dot kayiwa at gmail dot com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
[http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
1. Jim Hahn&lt;br /&gt;
&lt;br /&gt;
=== Code Retreat ===&lt;br /&gt;
'''Full Day'''&lt;br /&gt;
&lt;br /&gt;
* Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu&lt;br /&gt;
* Additional facilitators welcome; Especially if you have CodeRetreat experience.&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
&amp;quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.&lt;br /&gt;
By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.&lt;br /&gt;
Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&amp;quot; [http://coderetreat.org/about About Code Retreat]&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
=== Presentations workshop ===&lt;br /&gt;
 &lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;'''  (but could be expanded based on interest)&lt;br /&gt;
&lt;br /&gt;
* Chris Beer, Stanford University, cabeer@stanford.edu&lt;br /&gt;
* Additional facilitators welcome.&lt;br /&gt;
&lt;br /&gt;
This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.&lt;br /&gt;
 &lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#Vicky Steeves&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Dive into Hydra  ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Half Day [Afternoon]&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Justin Coyne, Data Curation Experts, justin@curationexperts.com&lt;br /&gt;
* Bess Sadler, Stanford University, bess@stanford.edu&lt;br /&gt;
&lt;br /&gt;
Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software.   Dive into Hydra is a course that bootstraps you into the Hydra software framework.  We'll start at the basics and walk you through the various layers of the Hydra stack.   We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository.  Participants who have prior exposure to web programming will get the most out of this course.  It's recommended (but not required) that you attend &amp;quot;RailsBridge&amp;quot; prior to this workshop.&lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Maura Carbone&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
=== code4lib/Write The Docs barcamp ===&lt;br /&gt;
 &lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''', with options for jumping in for half a day&lt;br /&gt;
&lt;br /&gt;
* code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu&lt;br /&gt;
* Write the Docs contacts: TBA&lt;br /&gt;
&lt;br /&gt;
Abstract&lt;br /&gt;
&lt;br /&gt;
''Placeholder for now - more information will be available before the proposal deadline''. More information about Write the Docs at http://docs.writethedocs.org/&lt;br /&gt;
&lt;br /&gt;
There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). &lt;br /&gt;
&lt;br /&gt;
''Interested in Attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
'''Full day'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Morning'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
'''Afternoon'''&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Linked Data Workshop ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Karen Estlund, University of Oregon, kestlund@uoregon.edu&lt;br /&gt;
* Tom Johnson, DPLA, tom@dp.la&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
Developer-focused linked data workshop. More info to come.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
# Logan Cox&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
=== Archivematica for users and developers ===&lt;br /&gt;
&lt;br /&gt;
One of:&lt;br /&gt;
'''&amp;quot;Full Day&amp;quot;''' &lt;br /&gt;
&lt;br /&gt;
* Sarah Romkey, Artefactual Systems, sromkey@artefactual.com&lt;br /&gt;
* Justin Simpson, Artefactual Systems, jsimpson@artefactual.com&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
&lt;br /&gt;
This is a workshop intended for both end-users of Archivematica (librarians, archivists, systems administrators) as well as developers who are interested in Archivematica feature development, or use of Archivematica back-end features for integration into other projects.&lt;br /&gt;
&lt;br /&gt;
In the morning, the end-users will meet with Sarah for a hands-on Archivematica training session. We will discuss processing configurations, use cases, and installation/hosting options for Archivematica. We will also demonstrate DIP upload to Archivematica's access system, AtoM. During this time, developers will meet with Justin and other Artefactual developers for a hackaton style session focusing on Archivematica development and integration.&lt;br /&gt;
&lt;br /&gt;
For the afternoon, we plan to bring the two groups together to discuss, share use cases, and have breakout sessions focused on specific topics that arose from the morning and afternoon sessions. &lt;br /&gt;
&lt;br /&gt;
When signing up, please indicate if you are an end-user or a developer.&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Fail4Lib 2015 ===&lt;br /&gt;
'''Half Day [TBD, probably afternoon]'''&lt;br /&gt;
&lt;br /&gt;
Contacts: &lt;br /&gt;
* Andreas Orphanides, akorphan (at) ncsu.edu&lt;br /&gt;
* Jason Casden, jmcasden (at) ncsu.edu&lt;br /&gt;
&lt;br /&gt;
Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.&lt;br /&gt;
&lt;br /&gt;
This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)&lt;br /&gt;
&lt;br /&gt;
The schedule may include the following:&lt;br /&gt;
&lt;br /&gt;
* Case studies. Avoid our own mistakes by bearing witness to the failures of others.&lt;br /&gt;
* Confessionals, for those willing to share. Let's learn from our own (and each others') failures.&lt;br /&gt;
* Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.&lt;br /&gt;
&lt;br /&gt;
''Interested in attending''&lt;br /&gt;
&lt;br /&gt;
If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here&lt;br /&gt;
&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
#&lt;br /&gt;
&lt;br /&gt;
[[Category:Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2015_Conference_Committees&amp;diff=41457</id>
		<title>2015 Conference Committees</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2015_Conference_Committees&amp;diff=41457"/>
				<updated>2014-08-13T00:11:05Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Onsite Volunteer Committee */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Code4Lib 2015 Committees =&lt;br /&gt;
&lt;br /&gt;
If you are interested in helping out with a particular part of the Code4Lib 2015 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term).  Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site.  Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference.  Please 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.&lt;br /&gt;
&lt;br /&gt;
We will assign a local contact to each committee.&lt;br /&gt;
&lt;br /&gt;
== Book Give-Away Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.&lt;br /&gt;
&lt;br /&gt;
Need about 2 months to get books shipped to the conference location.&lt;br /&gt;
&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== Keynote Speakers Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.&lt;br /&gt;
&lt;br /&gt;
* [[User:Phette23|Eric Phetteplace]]&lt;br /&gt;
&lt;br /&gt;
== Onsite Volunteer Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.&lt;br /&gt;
* Whitni Watkins&lt;br /&gt;
* Dre&lt;br /&gt;
&lt;br /&gt;
== Pre-conference Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
* [[User:ChristinaHarlow|Christina]]&lt;br /&gt;
&lt;br /&gt;
== Program Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* mx matienzo&lt;br /&gt;
* cbeer&lt;br /&gt;
* Tod Olson&lt;br /&gt;
* [[User:Cynthia|Arty]]&lt;br /&gt;
* [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
&lt;br /&gt;
== Scholarships Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Sarah Shealy - v&lt;br /&gt;
* Ruth Kitchin Tillman&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Bohyun Kim&lt;br /&gt;
* Mairelys Lemus-Rojas&lt;br /&gt;
&lt;br /&gt;
== Social Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
The committee plans, proposes, and organizes the evening activities.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose - v(committee member 4 life)&lt;br /&gt;
* Sarah Shealy&lt;br /&gt;
* Bohyun Kim&lt;br /&gt;
* Whitni Watkins&lt;br /&gt;
&lt;br /&gt;
== Sponsorships Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the sponsorship activities.  Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference.  These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.&lt;br /&gt;
&lt;br /&gt;
* Roy Tennant, OCLC, firstnamelastname@gmail.com&lt;br /&gt;
&lt;br /&gt;
== Streaming Video Committee ==&lt;br /&gt;
&lt;br /&gt;
*[[User:highermath|Cary Gordon]] has equipment, experience and domain knowledge to share.&lt;br /&gt;
*[[User:RileyChilds|Riley Childs]] has Knowledge and the YouTube Account credentials (he will consult but conf attendance is iffy)&lt;br /&gt;
&lt;br /&gt;
== T-Shirt Committee ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
*[[User:ChristinaHarlow|Christina]]&lt;br /&gt;
*[[User:jgo|Joshua Gomez]]&lt;br /&gt;
&lt;br /&gt;
== Voting Activities Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Whatever Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee does whatever the organizers can't talk anyone else into doing.&lt;br /&gt;
&lt;br /&gt;
* Francis Kayiwa&lt;br /&gt;
* Becky Yoose (will do things for mortgage payment assistance)&lt;br /&gt;
* [[User:ChristinaHarlow|Christina]]&lt;br /&gt;
* [[User:Ssimpkin|Sarah Simpkin]]&lt;br /&gt;
* Ranti Junus&lt;br /&gt;
* Whitni Watkins&lt;br /&gt;
&lt;br /&gt;
== Wifi / Electrical / IRC ==&lt;br /&gt;
&lt;br /&gt;
This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community.&lt;br /&gt;
&lt;br /&gt;
* [[User:highermath|Cary Gordon]], cgordon@chillco.com&lt;br /&gt;
* [[User:RileyChilds|Riley Childs]] is able to assist with Wireless planning and IRC stuffs, rchilds@cucawarriors.com  (he will consult but conf attendance is iffy)&lt;br /&gt;
&lt;br /&gt;
= Documentation =&lt;br /&gt;
To help with documention, no need to sign up, just start editing.&lt;br /&gt;
* [[How To Plan A Code4LibCon]]&lt;br /&gt;
&lt;br /&gt;
== Documentation Interest Group ==&lt;br /&gt;
Promote ongoing documentation efforts.&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2015]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40972</id>
		<title>2014 Lessons Learned</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40972"/>
				<updated>2014-03-27T14:01:34Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)&lt;br /&gt;
&lt;br /&gt;
'''Venue planning and negotiation'''&lt;br /&gt;
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have.  &lt;br /&gt;
* Venue negotiation takes a significant amount of time.  Total of nearly four (5) months of visits, informational calls, and negotiations.&lt;br /&gt;
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.&lt;br /&gt;
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight.&lt;br /&gt;
&lt;br /&gt;
'''Registration'''&lt;br /&gt;
* The venue of C4L2014 could hold 350 people&lt;br /&gt;
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325.  This filled in approximately 48 hours.&lt;br /&gt;
* Demand for Code4Lib 2014 was 420 based on registrations and wait list.  &lt;br /&gt;
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.&lt;br /&gt;
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.&lt;br /&gt;
&lt;br /&gt;
'''Sponsorships'''&lt;br /&gt;
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships.  The registration cost of $165 per person covered another 46.8%.  The remaining balance of C4L2013 covered the remaining 6-7%.  &lt;br /&gt;
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.&lt;br /&gt;
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.&lt;br /&gt;
&lt;br /&gt;
'''T-shirts'''&lt;br /&gt;
* Getting sizing that works for everyone is hard.&lt;br /&gt;
** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.&lt;br /&gt;
* There may be some design fatigue in the community.&lt;br /&gt;
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)&lt;br /&gt;
* When putting out a call for any graphics, ensure that the formats submitted are usable in production.&lt;br /&gt;
&lt;br /&gt;
'''Food and Beverage'''&lt;br /&gt;
* Coffee in unlimited quantities is valued more highly than food at breaks.&lt;br /&gt;
* Using negotiation to buy &amp;quot;off menu&amp;quot; will save money.&lt;br /&gt;
&lt;br /&gt;
'''Pre-Conferences'''&lt;br /&gt;
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.&lt;br /&gt;
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.&lt;br /&gt;
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.&lt;br /&gt;
&lt;br /&gt;
'''A/V'''&lt;br /&gt;
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).&lt;br /&gt;
&lt;br /&gt;
'''Organizing Volunteers'''&lt;br /&gt;
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.&lt;br /&gt;
'''IRC'''&lt;br /&gt;
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) &lt;br /&gt;
*Start the process to get the freenode limit raised a month before to plan for any kinks!&lt;br /&gt;
&lt;br /&gt;
'''Ideas'''&lt;br /&gt;
* Lanyards for whether it is OK to take photographs&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40970</id>
		<title>2014 Lessons Learned</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40970"/>
				<updated>2014-03-27T13:46:13Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)&lt;br /&gt;
&lt;br /&gt;
'''Venue planning and negotiation'''&lt;br /&gt;
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have.  &lt;br /&gt;
* Venue negotiation takes a significant amount of time.  Total of nearly four (5) months of visits, informational calls, and negotiations.&lt;br /&gt;
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.&lt;br /&gt;
* Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight.&lt;br /&gt;
&lt;br /&gt;
'''Registration'''&lt;br /&gt;
* The venue of C4L2014 could hold 350 people&lt;br /&gt;
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325.  This filled in approximately 48 hours.&lt;br /&gt;
* Demand for Code4Lib 2014 was 420 based on registrations and wait list.  &lt;br /&gt;
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.&lt;br /&gt;
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.&lt;br /&gt;
&lt;br /&gt;
'''Sponsorships'''&lt;br /&gt;
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships.  The registration cost of $165 per person covered another 46.8%.  The remaining balance of C4L2013 covered the remaining 6-7%.  &lt;br /&gt;
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.&lt;br /&gt;
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.&lt;br /&gt;
&lt;br /&gt;
'''T-shirts'''&lt;br /&gt;
* Getting sizing that works for everyone is hard.&lt;br /&gt;
* There may be some design fatigue in the community.&lt;br /&gt;
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)&lt;br /&gt;
* When putting out a call for any graphics, ensure that the formats submitted are usable in production.&lt;br /&gt;
&lt;br /&gt;
'''Food and Beverage'''&lt;br /&gt;
* Coffee in unlimited quantities is valued more highly than food at breaks.&lt;br /&gt;
* Using negotiation to buy &amp;quot;off menu&amp;quot; will save money.&lt;br /&gt;
&lt;br /&gt;
'''Pre-Conferences'''&lt;br /&gt;
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.&lt;br /&gt;
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.&lt;br /&gt;
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.&lt;br /&gt;
&lt;br /&gt;
'''A/V'''&lt;br /&gt;
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).&lt;br /&gt;
&lt;br /&gt;
'''Organizing Volunteers'''&lt;br /&gt;
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.&lt;br /&gt;
'''IRC'''&lt;br /&gt;
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) &lt;br /&gt;
*Start the process to get the freenode limit raised a month before to plan for any kinks!&lt;br /&gt;
&lt;br /&gt;
'''Ideas'''&lt;br /&gt;
* Lanyards for whether it is OK to take photographs&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40969</id>
		<title>2014 Lessons Learned</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&amp;diff=40969"/>
				<updated>2014-03-27T13:42:53Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)&lt;br /&gt;
&lt;br /&gt;
'''Venue planning and negotiation'''&lt;br /&gt;
* A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have.  &lt;br /&gt;
* Venue negotiation takes a significant amount of time.  Total of nearly four (5) months of visits, informational calls, and negotiations.&lt;br /&gt;
* Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.&lt;br /&gt;
&lt;br /&gt;
'''Registration'''&lt;br /&gt;
* The venue of C4L2014 could hold 350 people&lt;br /&gt;
* To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325.  This filled in approximately 48 hours.&lt;br /&gt;
* Demand for Code4Lib 2014 was 420 based on registrations and wait list.  &lt;br /&gt;
* Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.&lt;br /&gt;
* CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.&lt;br /&gt;
&lt;br /&gt;
'''Sponsorships'''&lt;br /&gt;
* 46.8% of the estimated cost of C4L2014 was provided by sponsorships.  The registration cost of $165 per person covered another 46.8%.  The remaining balance of C4L2013 covered the remaining 6-7%.  &lt;br /&gt;
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.&lt;br /&gt;
* The Code4Lib2014 Sponsorship Prospectus was a '''significant''' tool in raising money this year.&lt;br /&gt;
&lt;br /&gt;
'''T-shirts'''&lt;br /&gt;
* Getting sizing that works for everyone is hard.&lt;br /&gt;
* There may be some design fatigue in the community.&lt;br /&gt;
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)&lt;br /&gt;
* When putting out a call for any graphics, ensure that the formats submitted are usable in production.&lt;br /&gt;
&lt;br /&gt;
'''Food and Beverage'''&lt;br /&gt;
* Coffee in unlimited quantities is valued more highly than food at breaks.&lt;br /&gt;
* Using negotiation to buy &amp;quot;off menu&amp;quot; will save money.&lt;br /&gt;
&lt;br /&gt;
'''Pre-Conferences'''&lt;br /&gt;
* Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.&lt;br /&gt;
* Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.&lt;br /&gt;
* Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.&lt;br /&gt;
&lt;br /&gt;
'''A/V'''&lt;br /&gt;
* When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).&lt;br /&gt;
&lt;br /&gt;
'''Organizing Volunteers'''&lt;br /&gt;
* It's helpful to have a local representative on all volunteer committees to help grease the wheels.&lt;br /&gt;
'''IRC'''&lt;br /&gt;
*Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) &lt;br /&gt;
*Start the process to get the freenode limit raised a month before to plan for any kinks!&lt;br /&gt;
&lt;br /&gt;
'''Ideas'''&lt;br /&gt;
* Lanyards for whether it is OK to take photographs&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_Social_Activities&amp;diff=40689</id>
		<title>2014 Social Activities</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_Social_Activities&amp;diff=40689"/>
				<updated>2014-03-18T01:12:34Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* Newcomer Dinner, Monday 3/24 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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!&lt;br /&gt;
&lt;br /&gt;
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. :)&lt;br /&gt;
&lt;br /&gt;
== Planned Events ==&lt;br /&gt;
&lt;br /&gt;
=== Newcomer Dinner, Monday 3/24 ===&lt;br /&gt;
&lt;br /&gt;
First time at code4lib? Join fellow c4l newbies and veterans for an evening of food, socializing, and stimulating &amp;lt;strike&amp;gt;discussions about&amp;lt;/strike&amp;gt; demonstrations of the many uses of &amp;lt;strike&amp;gt;bacon&amp;lt;/strike&amp;gt; &amp;lt;strike&amp;gt;XML&amp;lt;/strike&amp;gt; EZProxy alternatives.&lt;br /&gt;
&lt;br /&gt;
Code4Lib veterans, you're invited too. Join us in welcoming the newcomers!&lt;br /&gt;
&lt;br /&gt;
'''Plans'''&lt;br /&gt;
* When: Monday 3/24&lt;br /&gt;
* Time: 6 PM (ish) or whenever you can get your group together&lt;br /&gt;
* Mastermind (if you have any questions): [mailto:yoosebec@grinnell.edu Becky Yoose]&lt;br /&gt;
&lt;br /&gt;
''Guidelines:''&lt;br /&gt;
*Max of '''6''' per group&lt;br /&gt;
**Please, no waitlisting&lt;br /&gt;
**Some restaurants can hold multiple groups of six. It is up to you to investigate the venue to see if this is possible.&lt;br /&gt;
*ID yourselves so we can get a good mix of new people and veterans in each group&lt;br /&gt;
**New folks - n&lt;br /&gt;
**c4l vets - v&lt;br /&gt;
*One leader needed for each location (declare yourself! - '''Vets are highly encouraged to lead the group''')&lt;br /&gt;
**Leader duties&lt;br /&gt;
***Make reservations if required; otherwise make sure that the restaurant can handle a group of 6 rowdy library tech type folks&lt;br /&gt;
***Herd folks from hotel to restaurant (know where you're going!)&lt;br /&gt;
*See a restaurant that's not listed? Feel free to add one, '''but please make sure that it is open that Monday evening.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Restaurants'''&lt;br /&gt;
&lt;br /&gt;
'''Under .5 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://bukuraleigh.com/buku/ bu ku] (Global street food)&lt;br /&gt;
# Bohyun Kim - v (leader) Reservation at 6:15; Meet at the hotel lobby at 6pm (Twitter: [http://twitter.com/bohyunkim @bohyunkim] if u need to get in touch)&lt;br /&gt;
# Junior Tidal - n&lt;br /&gt;
# Brian Rogers - n&lt;br /&gt;
# Vanessa Lucas - n&lt;br /&gt;
# Ashley Blewer - n&lt;br /&gt;
# Paula Gray-Overtoom - v&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://www.oxfordraleigh.com/ The Oxford] (Gastropub)&lt;br /&gt;
# Roy Tennant - v (leader) 6:30 reservation set - please email roytennant on Google mail to provide contact info&lt;br /&gt;
# David Bass - n&lt;br /&gt;
# Dan Moore - n&lt;br /&gt;
# Jack Reed - n&lt;br /&gt;
# Sean Hendricks - n&lt;br /&gt;
# Lauren Magnuson -v (ish - only been once before)&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://www.sonoraleigh.com/index.php Sono] (Japanese)&lt;br /&gt;
&lt;br /&gt;
[http://www.lavoltarestaurant.com/ La Volta] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://ac-restaurants.com/pooles/ Poole's] (Local food)&lt;br /&gt;
# Jean Rainwater - v (leader)&lt;br /&gt;
# Cynthia (Arty) Ng&lt;br /&gt;
# Catelynne Sahadath -n&lt;br /&gt;
# Maura Carbone -n&lt;br /&gt;
# Kate Hill -n&lt;br /&gt;
# Martin Haye - v (twice at c4l)&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://calaveraraleigh.com/ Calavera Empanada &amp;amp; Tequila Bar] (Empanada)&lt;br /&gt;
&lt;br /&gt;
[http://bigeasync.com/ The Big Easy] (New Orleans/Creole)&lt;br /&gt;
&lt;br /&gt;
[http://postatuscangrille.com/ Posta Tuscan Grille] (Italian)&lt;br /&gt;
&lt;br /&gt;
# Julia Bauder - v&lt;br /&gt;
# Brian Riley - n&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.mecca-restaurant.com/ The Mecca] (Diner/Southern)&lt;br /&gt;
&lt;br /&gt;
[http://busybeeraleigh.com/ Busy Bee Cafe] (American)&lt;br /&gt;
# Ken Varnum - v (leader) -- reservation for 6 people at 6:15. Send me your contact info at varnum umich edu.&lt;br /&gt;
# Josh Wilson - v(ish, as in: once)&lt;br /&gt;
# Kristen Wilson - n&lt;br /&gt;
# Michael Blake - n&lt;br /&gt;
# Zahra Ashktorab - n (I'm landing later that evening and will join if you are still out at around 8:30/9)&lt;br /&gt;
# Emily Reynolds - n &lt;br /&gt;
# Wendy Hagenmaier - n&lt;br /&gt;
# '''Full group!''' (I'll take 7 names, since one of us will be joining us later if we're still there)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ac-restaurants.com/beasleys/ Beasley's Chicken + Honey] (Southern)&lt;br /&gt;
# Rosalyn Metz - v (leader)&lt;br /&gt;
# Chad Nelson - v (insubordinator)&lt;br /&gt;
# Andrew Pasterfield - v&lt;br /&gt;
# Aaron Coburn - n&lt;br /&gt;
# Arcadia Falcone -n&lt;br /&gt;
# Mike Beccaria - v&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://ac-restaurants.com/chucks/ Chuck's] (Burgers)&lt;br /&gt;
&lt;br /&gt;
[http://ororaleigh.com/ Oro] (Tapas vegan options)&lt;br /&gt;
&lt;br /&gt;
[http://www.jimmyvsraleigh.com/ Jimmy V's Osteria and Bar] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://bidamanda.com/ Bida Manda] (Laotian)&lt;br /&gt;
# Dre - v (leader) -- Reservations at 6:15, meet at hotel lobby at 5:45. No, it won't take us half an hour to get there. Dre looks like [http://www.lib.ncsu.edu/staff/akorphan/ this handsome fella]. My e-mail address is on that page if you'd like to exchange contact info.&lt;br /&gt;
# Heather Rayl - n&lt;br /&gt;
# Ranti Junus - v&lt;br /&gt;
# Jennifer Kishi - n&lt;br /&gt;
# Nabil Kashyap - n&lt;br /&gt;
# Laura Wrubel - n&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://sitti-raleigh.com/index1.php Sitti] (Lebanese) - Meet in the hotel lobby at 6 pm; look for the short woman in the big brown hat&lt;br /&gt;
# Becky Yoose - v (benevolent dictator/leader) contact me at b.yoose at the google machine in case you might run late&lt;br /&gt;
# Michael Gibney - n&lt;br /&gt;
# Steven Holloway - n&lt;br /&gt;
# Jeffrey Mudge - n&lt;br /&gt;
# Arie Nugraha - n&lt;br /&gt;
# Lisa Rabey - n&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://www.thepit-raleigh.com/ The Pit Authentic Barbecue] (BBQ)&lt;br /&gt;
&lt;br /&gt;
Group 1&lt;br /&gt;
# Joshua Gomez - v (leader)  (I have reservations for 6 people at 6pm. Send me your contact info: gomezjn_AT_usc_DOT_edu)&lt;br /&gt;
# Andrew Darby - v&lt;br /&gt;
# Tammy Allgood Wolf - n&lt;br /&gt;
# Jim LeFager - n&lt;br /&gt;
# Michael Daul - n&lt;br /&gt;
# Natasha Nunn - n&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
Group 2 (Can we keep this mostly newbies, please?) - '''Reservations for 6 at 6:15 PM'''&lt;br /&gt;
# Mx Matienzo - v (leader)&lt;br /&gt;
# Cary Gordon - v&lt;br /&gt;
# Mark Breedlove - n&lt;br /&gt;
# Coral Sheldon-Hess - n (pumpkin cornbread!?!?!)&lt;br /&gt;
# Violeta Ilik&lt;br /&gt;
# Robin Taylor - n&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
Group 3  (I have reservations for 6 people at 6pm. Send me your contact info: justin@curationexperts.com)&lt;br /&gt;
# Justin Coyne - v  (leader)&lt;br /&gt;
# Rachel Vacek- n&lt;br /&gt;
# Devin Higgins - n&lt;br /&gt;
# John Rees - n&lt;br /&gt;
# Andrew Gordon - n&lt;br /&gt;
# Bobbi Fox -v&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
Group 4  (Riley made reservations for 6:15)&lt;br /&gt;
# Jon Stroop - v  (leader, but Riley did the work. Contact: jpstroop@gmail.com)&lt;br /&gt;
# [[Riley Childs]] - n&lt;br /&gt;
# David Lacy - v&lt;br /&gt;
# Shaun Ellis - v&lt;br /&gt;
# William Hicks&lt;br /&gt;
# Eleanor Dickson - n&lt;br /&gt;
# '''Full group!''' &lt;br /&gt;
&lt;br /&gt;
Group V (Declan made reservations for 6 at 6p. Contact: declan@declan.net)&lt;br /&gt;
# Declan Fleming - v (leader)&lt;br /&gt;
# Mike Giarlo - v&lt;br /&gt;
# YOUR NAME HERE (need newbies!)&lt;br /&gt;
&lt;br /&gt;
[http://www.gravyraleigh.com/ Gravy] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://theboroughraleigh.com/ The Borough] (Pub)&lt;br /&gt;
&lt;br /&gt;
[http://www.theremedydiner.com/ The Remedy Diner] (Diner (lots of Veg*n options))&lt;br /&gt;
# Erin White - v (leader)&lt;br /&gt;
# Linda Ballinger - v(ish)&lt;br /&gt;
# Terry Brady - v (been one other time)&lt;br /&gt;
# Gabe Ormsby - n&lt;br /&gt;
# Eric James - v&lt;br /&gt;
# Jenny Gubernick - n&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
[http://www.centroraleigh.com/ Centro] (Mexican)&lt;br /&gt;
&lt;br /&gt;
[http://www.beerknurd.com/stores/raleigh/ Flying Saucer] (Pub)&lt;br /&gt;
&lt;br /&gt;
[http://brewmastersbarandgrill.com/ Brewmasters Bar and Grill] (Brewpub)&lt;br /&gt;
# Esmé Cowles - v (leader)&lt;br /&gt;
# Christina Salazar - v/n&lt;br /&gt;
# Francis Kayiwa - v (follower)&lt;br /&gt;
# Megan Kudzia - v&lt;br /&gt;
# Zahra Ashktorab - n &lt;br /&gt;
# David Drexler - v (ish)&lt;br /&gt;
# '''Full group!'''&lt;br /&gt;
&lt;br /&gt;
'''.5 to 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.518west.com/ 518 West Italian Cafe] (Italian)&lt;br /&gt;
&lt;br /&gt;
[http://boylanbridge.com/ Boylan Bridge Brewpub] (Brewpub)&lt;br /&gt;
&lt;br /&gt;
[http://www.mantraindiancuisinebar.com/ Mantra] (Indian)&lt;br /&gt;
&lt;br /&gt;
[http://mtfujinc.com/SushiO/ Sushi O] (Asian)&lt;br /&gt;
&lt;br /&gt;
[http://zakyrestaurant.com/ Zaky Restaurant] (Mediterranean)&lt;br /&gt;
&lt;br /&gt;
[http://sullivanssteakhouse.com/raleigh/ Sullivan's Steakhouse] (Steak)&lt;br /&gt;
&lt;br /&gt;
[http://bia-restaurant.com/ Bia ] (New American)&lt;br /&gt;
&lt;br /&gt;
[http://www.18seaboard.com/index.html 18 Seaboard] (Contemporary American)&lt;br /&gt;
&lt;br /&gt;
[http://sushibluescafe.com Sushi Blues Cafe] (Japanese)&lt;br /&gt;
&lt;br /&gt;
[http://www.therockfordrestaurant.com/About.aspx Rockford] (American)&lt;br /&gt;
&lt;br /&gt;
[http://www.tylerstaproom.com/ Tyler's Restaurant and Taproom] (Pub)&lt;br /&gt;
&lt;br /&gt;
[http://bluemangoraleigh.com/ Blue Mango] (Indian)&lt;br /&gt;
&lt;br /&gt;
[http://mellowmushroom.com/store/raleigh Mellow Mushroom] (Pizza)&lt;br /&gt;
&lt;br /&gt;
[http://tascabrava.com/index2.html Tasca Brava] (Spanish)&lt;br /&gt;
&lt;br /&gt;
[http://clockworkraleigh.com/index.html Clockwork] (Pub)&lt;br /&gt;
&lt;br /&gt;
[http://dostaquitosnc.com/ Dos Taquitos] (Mexican)&lt;br /&gt;
&lt;br /&gt;
[http://nappertandysraleighnc.com/ Napper Tandy's Irish Pub] (Pub)&lt;br /&gt;
&lt;br /&gt;
[http://www.thaiphoonbistro.com/ Thaiphoon bistro] (Thai)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''More than 1 mile from hotel'''&lt;br /&gt;
&lt;br /&gt;
[http://www.peacechinanc.com/ Peace China] (Chinese)&lt;br /&gt;
&lt;br /&gt;
[http://www.ddandnb.com/ Davids Dumpling and Noodle Bar] (Asian)&lt;br /&gt;
&lt;br /&gt;
[http://www.abyssiniarestaurant.net/5.html Abyssinia Ethiopian Restaurant] (Ethiopian)&lt;br /&gt;
&lt;br /&gt;
=== James B. Hunt Library Reception and Tour, Tuesday 3/25 ===&lt;br /&gt;
&lt;br /&gt;
A reception and tour of the James B. Hunt Library on NCSU's Centennial Campus will take place on Tuesday, March 25, 5:00-7:30 PM. See the library, which opened in January 2013, through the eyes of the students in the over 3,000 Instagram photos in the [http://d.lib.ncsu.edu/myhuntlibrary My #HuntLibrary] project.  The furniture alone has generated interest, as shown on the [http://chairsofhuntlibrary.tumblr.com/ Chairs of Hunt Library] Tumbler site.&lt;br /&gt;
&lt;br /&gt;
'''Travel to Hunt'''&lt;br /&gt;
&lt;br /&gt;
Buses will begin loading at the Sheraton at 5:00 PM after the day's sessions have concluded. The Hunt Library is 4 miles from the Sheraton.&lt;br /&gt;
&lt;br /&gt;
'''Reception'''&lt;br /&gt;
&lt;br /&gt;
Pizza and light snacks will be made available in the Multipurpose Room, along with soft drinks and beer from the [http://www.ncsu.edu/foodscience/Sheppard/NCSU-12004%20Brewery%20Brochure1.pdf NC State Brewery].&lt;br /&gt;
&lt;br /&gt;
'''Tour'''&lt;br /&gt;
&lt;br /&gt;
Attendees will be welcome to embark on a self-guided tour of the library.  Library staff will be on hand at selected locations, including hi-tech spaces such as the [http://www.lib.ncsu.edu/huntlibrary/bookBot bookBot] robotic book delivery system, the [http://www.lib.ncsu.edu/spaces/teaching-and-visualization-lab Teaching &amp;amp; Visualization Lab], the [http://www.lib.ncsu.edu/spaces/creativity-studio Creativity Studio], the [http://www.lib.ncsu.edu/spaces/game-lab Game Lab], and the [http://www.lib.ncsu.edu/spaces/makerspace Makerspace].&lt;br /&gt;
&lt;br /&gt;
'''Travel back to the Sheraton'''&lt;br /&gt;
&lt;br /&gt;
Buses will begin to load for the return trip at 6:45 PM.  The last bus will leave the Hunt Library at approximately 7:45 PM.&lt;br /&gt;
&lt;br /&gt;
=== #libtechwomen meetup, Tuesday 3/25 ===&lt;br /&gt;
&lt;br /&gt;
An informal meetup for women and their friends in library technology for networking and fun. Come join us! Learn more about #libtechwomen at [http://libtechwomen.org/about.html].&lt;br /&gt;
&lt;br /&gt;
'''Where''': [http://www.raleightimesbar.com/ The Raleigh Times Bar] 14 E Hargett St Raleigh, NC 27601. 7 minute walk from the Sheraton.&lt;br /&gt;
&lt;br /&gt;
'''When''': Evening after the tour :c) (Starting at 730P on)&lt;br /&gt;
&lt;br /&gt;
'''Cost''': No drink minimum.&lt;br /&gt;
&lt;br /&gt;
'''Contact''': Lisa Rabey [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]&lt;br /&gt;
&lt;br /&gt;
'''Signup''': Everyone welcome. Just show up!&lt;br /&gt;
&lt;br /&gt;
=== A/V Geeks Present: When Computers Were Young, Wednesday 3/26 ===&lt;br /&gt;
&lt;br /&gt;
[http://www.avgeeks.com/wp2/ A/V Geeks] maintains a collection of over 23,000 old 16mm educational films from various decades of the 20th century, including such classics as [http://www.avgeeks.com/wp2/library-story-the-1952/ The Library Story (1952)], many obtained from school and government auctions. Media archaeologist [http://www.indyweek.com/indyweek/skip-elsheimer/Content?oid=1183990 Skip Elsheimer] holds themed showings of selected films at events around the Triangle and in other states.  &lt;br /&gt;
&lt;br /&gt;
This event, [http://kingsbarcade.com/2014/03/26/av-geeks-present-when-computers-where-young/ When Computers Were Young], will include &amp;quot;Actual 16mm school films that introduce us to the wonderful world of computers and their potential future -- all before Google!&amp;quot;  Films will include Disney's Ethics in the Computer Age and more.  This showing is an all ages, public event that is part of a series of monthly shows held at [http://kingsbarcade.com/ Kings Barcade], but the event has been scheduled and themed with the Code4Lib crowd in mind.&lt;br /&gt;
&lt;br /&gt;
'''When:''' Doors open at 7:30 PM.&lt;br /&gt;
&lt;br /&gt;
'''Where:''' Located two blocks from the Sheraton, Kings is a 250-capacity live music venue with a full bar and several local beers on tap.  Kings is directly connected with the [http://neptunesparlour.com/ Neptunes Parlour], a cocktail lounge with classic arcade games, pinball, and nightly DJ's.  The new [http://garlandraleigh.com/ Garland] Indian restaurant, operated by the same owners, is also downstairs.&lt;br /&gt;
&lt;br /&gt;
'''Cost:''' The event is free with a suggested $5 donation.  &lt;br /&gt;
&lt;br /&gt;
'''Signup:''' Please add your name to the [http://wiki.code4lib.org/index.php/2014_AVGeeks_Signup sign up list] if you would like to attend so that we can inform the organizers about the level of interest&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Library Tech Cast Round table: Wednesday Evening  ===&lt;br /&gt;
The Library Tech Cast will be hosting a live Round table somewhere at the Sheraton, we are looking for about 5 people who would be interested. We are planning to disscus the conf and what has been going on etc.&lt;br /&gt;
&lt;br /&gt;
See [http://librarytechcast.com/c4l-show http://librarytechcast.com/c4l-show http://librarytechcast.com/c4l-show]for details!&lt;br /&gt;
&lt;br /&gt;
Please contact Riley@LibraryTechCast.com if you have any questions!&lt;br /&gt;
&lt;br /&gt;
'''Location:''' TBD (in a conference room? we are working this out)&lt;br /&gt;
&lt;br /&gt;
'''Time:''' TBD, sometime after the afternoon session, (six-ish?) &lt;br /&gt;
&lt;br /&gt;
'''Signup:''' Please put your Name and Email Address Below!&lt;br /&gt;
&lt;br /&gt;
*Riley Childs, Riley@TFSGEO.com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Social Map - Places of Interest==&lt;br /&gt;
&lt;br /&gt;
[https://maps.google.com/maps/ms?msid=211601269129937460559.0004d8d5902e5e3d04b05&amp;amp;msa=0&amp;amp;ll=35.782519,-78.640223&amp;amp;spn=0.01464,0.01929 Code4Lib 2014 Amenities Map, Downtown Raleigh, NC] - Amenities that are within walking distance of the Sheraton or the R Line circulator&lt;br /&gt;
&lt;br /&gt;
New York Times: [http://mobile.nytimes.com/2014/03/09/travel/36-hours-in-raleigh-nc.html?referrer 36 Hours in Raleigh NC] (March 6, 2014)&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
&lt;br /&gt;
''Add your own ideas here''&lt;br /&gt;
&lt;br /&gt;
'''Game Night'''&lt;br /&gt;
&lt;br /&gt;
Time and location to be determined&lt;br /&gt;
&lt;br /&gt;
I can bring some board games if people are interested. I have a decent [http://boardgamegeek.com/collection/user/vacekrae?geekranks=Board+Game+Rank&amp;amp;columns=title%7Cstatus%7Cversion%7Crating%7Cbggrating%7Cplays%7Ccomment%7Ccommands&amp;amp;own=1&amp;amp;ff=1&amp;amp;subtype=boardgame collection]. Let me know via email at vacekrae on gmail.&lt;br /&gt;
&lt;br /&gt;
'''Trolley Pub'''&lt;br /&gt;
&lt;br /&gt;
14 person pedal-powered [http://trolleypub.com/raleigh/ trolleys].  Can be booked for pub crawls in downtown or in the Warehouse District. BYOB allowed. Private tours for 8-14 people can be booked for $350 for two hour time slots between 11:00 AM and midnight.  Smaller groups of 1-6 people can also by 'Mixer' tickets for $30 (shared trolley).&lt;br /&gt;
&lt;br /&gt;
'''Brewpub Walk'''&lt;br /&gt;
&lt;br /&gt;
Three brewpubs can be found along a [http://goo.gl/maps/haOiD 1.2 mile walk] through the Warehouse District west from the Sheraton.&lt;br /&gt;
NOTE: Trophy Brewing, the westernmost brewpub, has great pizza but limited seating.  To finish with dinner, go in smaller numbers if eating at Trophy, or go around the corner to Irregardless Cafe, which has veg*n options.  Alternatively, start at Trophy and go the opposite direction and eat in the Warehouse District or downtown where there are many dining options.&lt;br /&gt;
&lt;br /&gt;
'''NCAA Tournament Game at PNC Arena'''&lt;br /&gt;
&lt;br /&gt;
[http://www.thepncarena.com/events/detail/2014-ncaa-division-i-mens-basketball-tournament Third Round Division I Men's basketball game], Sunday March 23. If anyone else is crazy enough to pay the money for tickets email rosalynmetz [at] the gmail&lt;br /&gt;
&lt;br /&gt;
== Local Events ==&lt;br /&gt;
&lt;br /&gt;
[http://www.godowntownraleigh.com/explore/arts Map of downtown arts and cultural entertainment]&lt;br /&gt;
&lt;br /&gt;
[http://www.godowntownraleigh.com/event-calendar/2014/3 Calendar of downtown events]&lt;br /&gt;
&lt;br /&gt;
[http://www.godowntownraleigh.com/explore/shopping Map of downtown shopping]&lt;br /&gt;
&lt;br /&gt;
=== Exhibits, Showings, Museums ===&lt;br /&gt;
&lt;br /&gt;
*[http://naturalsciences.org/ North Carolina Museum of Natural Sciences]&lt;br /&gt;
**[http://naturalsciences.org/nature-research-center Nature Research Center]&lt;br /&gt;
**Exhibit - [http://naturalsciences.org/exhibits/special-exhibits Birds of Paradise: Amazing Avian Evolution] (final day March 23)&lt;br /&gt;
&lt;br /&gt;
*[http://www.ncdcr.gov/ncmoh/Home.aspx North Carolina Museum of History] Exhibits: &lt;br /&gt;
**[http://www.godowntownraleigh.com/event/exhibit-opening-cedars-in-the-pines Cedars in the Pines]&lt;br /&gt;
**[http://www.ncdcr.gov/ncmoh/SeeOurExhibits/CurrentExhibits/NorthCarolinaandtheCivilWar/The_Bitter_End.aspx North Carolina and the Civil War: The Bitter End, 1864-1865]&lt;br /&gt;
**[http://www.ncdcr.gov/ncmoh/SeeourExhibits/CurrentExhibits/Watergate.aspx Watergate: Political Scandal &amp;amp; the Presidency]&lt;br /&gt;
&lt;br /&gt;
*[http://www.nchistoricsites.org/capitol/ North Carolina State Capitol]&lt;br /&gt;
&lt;br /&gt;
*[http://camraleigh.org/2014nc-arts-council-artist-fellowship/ NC Arts Council Artist Fellowship Award Exhibition] at the [http://camraleigh.org/ Contemporary Arts Museum]&lt;br /&gt;
&lt;br /&gt;
*[http://ncartmuseum.org/calendar/ NC Museum of Art Calendar]&lt;br /&gt;
&lt;br /&gt;
*[http://www.godowntownraleigh.com/explore/arts/art-galleries Downtown Raleigh Art Galleries]&lt;br /&gt;
&lt;br /&gt;
*[http://artspacenc.org/about-us/visit/ ArtSpace]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raleighcitymuseum.org/index.shtml City of Raleigh Museum]&lt;br /&gt;
&lt;br /&gt;
*[http://calendar.activedatax.com/ncstate/EventList.aspx?fromdate=3/1/2014&amp;amp;todate=3/31/2014&amp;amp;display=Month&amp;amp;type=public&amp;amp;eventidn=9669&amp;amp;view=EventDetails&amp;amp;information_id=27372 Remnants of the Floating World: Japanese Art from the Permanent Collection] at the [http://www.ncsu.edu/gregg/index.html NCSU Gregg Museum of Art &amp;amp; Design]&lt;br /&gt;
&lt;br /&gt;
*[http://www.joellane.org/ Joel Lane Museum House]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raleighnc.gov/parks/content/PRecRecreation/Articles/MordecaiHistoricPark2.html Mordecai Historic Park]&lt;br /&gt;
&lt;br /&gt;
=== Outside Activities ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.triangleglides.com/ Triangle Glides] Segway tours, standup paddleboard rentals&lt;br /&gt;
&lt;br /&gt;
* [http://www.raleighnc.gov/parks/content/PRecDesignDevelop/Articles/CapitalAreaGreenwayTrailSystem.html Capital Area Greenway Trail System]&lt;br /&gt;
&lt;br /&gt;
* [http://www.ncartmuseum.org/museum_park/visit_park/ NC Museum of Art: Museum Park] Scenic trails and outdoor art&lt;br /&gt;
&lt;br /&gt;
* [http://www.nps.gov/nr/travel/raleigh/index.htm National Register of Historic Places]&lt;br /&gt;
&lt;br /&gt;
* [http://www.ncsu.edu/jcraulstonarboretum/index.php JC Raulston Arboretum]&lt;br /&gt;
&lt;br /&gt;
=== Run Clubs ===&lt;br /&gt;
&lt;br /&gt;
'''Monday Night'''&lt;br /&gt;
* [http://www.nogrunclub.com/ Nog Run Club] - 6:00 PM at Tir Na Nog Irish Pub: 3-5 mile routes, followed by team trivia, $1 pasta, and beer specials&lt;br /&gt;
&lt;br /&gt;
'''Tuesday Night'''&lt;br /&gt;
* [https://www.facebook.com/events/553725497983418/ Natty Greene's Run Club] - 6:00 PM at Natty Greene's Brewery: 1, 3, 5 mile routes&lt;br /&gt;
* Big Boss Run Club - 7:00 PM at [http://bigbossbrewing.com/age-verification.aspx?returnTo=%2f Big Boss Brewery]: 3-6 mile routes followed by beer specials&lt;br /&gt;
&lt;br /&gt;
'''Wednesday Night'''&lt;br /&gt;
* Margarita Run Club - 6:00 PM at [http://www.centroraleigh.com/ Centro] restaurant: 3-5 mile routes followed by taco bar and margarita specials&lt;br /&gt;
* [http://www.ymcatriangle.org/programs-services/fitness-wellness/walking-running-clubs/alexander-family-ymca-0 Trophy Brewery Runs] - 6:00 PM at Trophy Brewing: 1, 3, 5 mile routes&lt;br /&gt;
&lt;br /&gt;
== Local Food ==&lt;br /&gt;
&lt;br /&gt;
[http://www.godowntownraleigh.com/explore/dining Map of Downtown Restaurants &amp;amp; Dining]&lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&lt;br /&gt;
[http://www.newsobserver.com/2014/01/30/3577164/2014-best-restaurants-in-the-triangle.html News &amp;amp; Observer 2014 Best Restaurants of the Triangle]&lt;br /&gt;
&lt;br /&gt;
[http://www.indyweek.com/indyweek/LocationSearch?locationSection=1218750 Indy Weekly Triangle Dining Guide]&lt;br /&gt;
&lt;br /&gt;
'''Fayetteville St. District''' (0-0.4 miles north)&lt;br /&gt;
&lt;br /&gt;
* [http://clydecoopersbbq.com/ Clyde Cooper's BBQ] (since 1938)&lt;br /&gt;
* [http://garlandraleigh.com/ Garland] Indian&lt;br /&gt;
* [http://ac-restaurants.com/beasleys/ Beasley's Chicken &amp;amp; Honey] Fried Chicken, Chicken and Waffles (''Ashley Christiansen'')&lt;br /&gt;
* [http://www.sonoraleigh.com/ Sono] Sushi&lt;br /&gt;
* [http://www.capitalclub16.com/Capital_Club_16/Home.html Capital Club 16] Eclectic pub grub&lt;br /&gt;
* [http://sitti-raleigh.com/ Sitti] Lebanese&lt;br /&gt;
* [http://ororaleigh.com/ Oro] Tapas (vegan options)&lt;br /&gt;
* [http://www.centroraleigh.com/ Centro] Mexican&lt;br /&gt;
* [http://www.centroraleigh.com/ Chuck's Burgers] (''Ashley Christiansen'')&lt;br /&gt;
* [http://www.oakcitymeatball.com/ Oak City Meatball Shoppe]&lt;br /&gt;
* [http://www.gravyraleigh.com/ Gravy] Italian-American&lt;br /&gt;
* [http://busybeeraleigh.com/ Busy Bee Cafe] American&lt;br /&gt;
* [http://www.mecca-restaurant.com/ Mecca] Diner/southern&lt;br /&gt;
* [http://bukuraleigh.com/buku/ Buku] Global street food&lt;br /&gt;
* [http://www.boltbistro.com/ Bolt] Bistro, Steakhouse, Seafood&lt;br /&gt;
&lt;br /&gt;
'''Moore Square''' (0.3-0.5 miles east)&lt;br /&gt;
&lt;br /&gt;
* [http://bidamanda.com/ Bida Manda] Laotian&lt;br /&gt;
* [http://www.theremedydiner.com/ Remedy Diner] Veg*n and non-veg*n&lt;br /&gt;
* [http://www.cafeluna.com/ Cafe Luna] Italian (Tuscan)&lt;br /&gt;
* [http://calaveraraleigh.com/ Calavera] Empanadas and tequila&lt;br /&gt;
* [http://www.bigedscitymarket.com/ Big Ed's] Diner&lt;br /&gt;
* [http://www.mosdiner.net/ Mo's Diner] American (New)&lt;br /&gt;
&lt;br /&gt;
'''Warehouse District''' (0.2-0.7 miles west)&lt;br /&gt;
&lt;br /&gt;
* [http://www.thepit-raleigh.com/ The Pit] Whole-hog, pit-coooked BBQ&lt;br /&gt;
* [http://thefictionkitchen.com/ Fiction Kitchen] Veg*n&lt;br /&gt;
* [http://ac-restaurants.com/pooles/ Poole's Diner] American/Diner (''Ashley Christiansen'')&lt;br /&gt;
* [http://joseandsons.com/ Jose and Sons] Mexican/Southern fusion&lt;br /&gt;
* [http://humblepierestaurant.com/ Humble Pie] Tapas (Live jazz on Wed.)&lt;br /&gt;
* [http://www.heatseekershrimp.com/ Five Star] Asian (Traditional and creative)&lt;br /&gt;
* [http://roastgrill.com/ Roast Grill] Just hot dogs (''as seen on Man v. Food'')&lt;br /&gt;
&lt;br /&gt;
'''Glenwood South''' (0.6-1.3 miles northwest)&lt;br /&gt;
&lt;br /&gt;
* [http://www.42ndstoysterbar.com/ 42nd St. Oyster Bar] Seafood&lt;br /&gt;
* [http://therockfordrestaurant.com/ Rockford] American (New)/Pub grub&lt;br /&gt;
* [http://www.518west.com/ 518 West] Italian&lt;br /&gt;
* [http://www.second-empire.com/ Second Empire] American (New)&lt;br /&gt;
&lt;br /&gt;
'''Seaboard Station/Person St.''' (1.0-1.2 miles north)&lt;br /&gt;
&lt;br /&gt;
* [http://www.18seaboard.com/ Seaboard Station] Southern, American (New)&lt;br /&gt;
* [http://jbetskis.com/ J. Betskis] Central &amp;amp; Eastern European&lt;br /&gt;
* [https://www.facebook.com/pages/Stanbury/359649790802483 Stanbury] Contemporary&lt;br /&gt;
* [http://piebirdraleigh.com/ Piebird] Sweet and savory pies&lt;br /&gt;
* [http://stationraleigh.com/ The Station] American (Traditional)&lt;br /&gt;
&lt;br /&gt;
'''West towards NC State''' (1.2-2.2 miles west)&lt;br /&gt;
&lt;br /&gt;
* [http://www.irregardless.com/ Irregardless Cafe] veg*n options&lt;br /&gt;
* [http://www.abyssiniarestaurant.net/5.html Abysinnia] Ethiopian&lt;br /&gt;
* [http://www.ddandnb.com/ Davids Dumpling &amp;amp; Noodle Bar] Asian&lt;br /&gt;
&lt;br /&gt;
'''Five Points''' (2.5 miles north)&lt;br /&gt;
&lt;br /&gt;
* [http://bloomsburybistro.com/bistro.restaurant.raleigh/ Bloomsbury Bistro] American (New)&lt;br /&gt;
* [https://nofo.com/ NOFO @ The Pig] American (New), Brunch&lt;br /&gt;
* [http://lillyspizza.com/ Lilly's Pizza] Pizza and beer&lt;br /&gt;
&lt;br /&gt;
'''Other Inside-the-Beltline Raleigh'''&lt;br /&gt;
&lt;br /&gt;
* [http://guasaca.com/ Guasaca] Venezuelan (6 miles)&lt;br /&gt;
* [http://glenwoodgrill.com/ Glenwood Grill] American (Traditional), Southern (4 miles)&lt;br /&gt;
&lt;br /&gt;
=== Desserts ===&lt;br /&gt;
&lt;br /&gt;
* [https://viderichocolatefactory.com/ Videri Chocolate Factory]&lt;br /&gt;
* [http://www.escazuchocolates.com/ Escazu Artisan Chocolates]&lt;br /&gt;
* [https://plus.google.com/113675251912407366356/about?gl=us&amp;amp;hl=en Crema] Ice cream&lt;br /&gt;
&lt;br /&gt;
=== Coffee ===&lt;br /&gt;
&lt;br /&gt;
* [http://morningtimes-raleigh.com/ Morning Times] (wifi) -- 3 blocks&lt;br /&gt;
* [http://ac-restaurants.com/joule/ Joule Coffee] (''Ashley Christiansen'', wifi, breakfast/lunch -- CNN eatocracy [http://eatocracy.cnn.com/2014/02/21/5-hottest-new-coffee-spots-in-the-u-s/ 5 hottest new coffee spots in the US]) -- 3 blocks&lt;br /&gt;
* [http://beneluxcoffee.com/ Benelux Coffee] (wifi) -- 4 blocks&lt;br /&gt;
* [http://www.sostacafe.com/ Sosta Cafe] (wifi, lunch) -- 2 blocks&lt;br /&gt;
* [http://www.cafemuertos.com/ Cafe de los Muertos] (wifi) -- 5 blocks&lt;br /&gt;
* [http://www.cafehelios.com/ Cafe Helios] (wifi, breakfast/lunch) -- 1.1 miles&lt;br /&gt;
&lt;br /&gt;
There is a Starbucks in the lobby of the Marriott, next to the Sheraton.&lt;br /&gt;
&lt;br /&gt;
== Local Drinks ==&lt;br /&gt;
&lt;br /&gt;
[http://www.godowntownraleigh.com/explore/nightlife Map of Bars, Clubs &amp;amp; Live Entertainment]&lt;br /&gt;
&lt;br /&gt;
=== Bars ===&lt;br /&gt;
&lt;br /&gt;
'''Fayetteville St. District'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.raleightimesbar.com/ Raleigh Times] Draft Magazine Top 100 beer bar&lt;br /&gt;
* [http://www.busybeeraleigh.com/ Busy Bee] Draft Magazine Top 100 beer bar (The Hive is upstairs)&lt;br /&gt;
* [http://foundationnc.com/ Foundation] Cocktails, bourbon, local beer&lt;br /&gt;
* [http://neptunesparlour.com/ Neptunes Parlour] Cocktails, local beer&lt;br /&gt;
* [http://ac-restaurants.com/fox/ Fox Liquor Bar] Cocktails, local beer (''Ashley Christiansen'')&lt;br /&gt;
* [http://www.slimsraleigh.com/ Slim's] Dive bar (live music)&lt;br /&gt;
&lt;br /&gt;
'''Moore Square'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.yelp.com/biz/landmark-tavern-raleigh Landmark Tavern] beer, back patio&lt;br /&gt;
* [http://www.tnnirishpub.com/ Tir Na Nog] Irish pub&lt;br /&gt;
* [http://calaveraraleigh.com/ Calavera] Empanadas and 40 tequila varieties&lt;br /&gt;
* [http://woodyscitymarket.com/ Woody's] Beer and wings&lt;br /&gt;
&lt;br /&gt;
'''Warehouse District'''&lt;br /&gt;
&lt;br /&gt;
* [http://brewmastersbarandgrill.com/ Brewmasters] Grill, 2012 Draft Magazine Top 100 beer bar&lt;br /&gt;
* [http://www.crankarmbrewing.com/ Crank Arm Brewing] Brewpub&lt;br /&gt;
* [http://www.beerknurd.com/stores/raleigh/ Flying Saucer] Beer&lt;br /&gt;
* [http://boylanbridge.com/ Boylan Bridge Brewpub] Brewpub&lt;br /&gt;
&lt;br /&gt;
'''Glenwood South'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.cgracebar.com/ C Grace] Cocktails and live jazz&lt;br /&gt;
* [http://clockworkraleigh.com/ Clockwork] Retro cocktail lounge&lt;br /&gt;
&lt;br /&gt;
'''Seaboard Station/Person St.'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.tylerstaproom.com/ Tyler's Tap Room] Beer&lt;br /&gt;
* [https://www.facebook.com/personstreetbar Person Street Bar]&lt;br /&gt;
&lt;br /&gt;
'''Best places for groups to watch NCAA Championship Games'''&lt;br /&gt;
&lt;br /&gt;
* [http://woodyscitymarket.com/ Woody's]&lt;br /&gt;
* [http://www.jimmyvsraleigh.com/ Jimmy V's]&lt;br /&gt;
* [http://www.tylerstaproom.com/ Tyler's]&lt;br /&gt;
&lt;br /&gt;
=== Breweries ===&lt;br /&gt;
&lt;br /&gt;
[http://www.ncbeer.org/brewery-map/ Map of NC Breweries]&lt;br /&gt;
&lt;br /&gt;
'''Walking Distance'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.crankarmbrewing.com/ Crank Arm Brewing] (0.3 miles)&lt;br /&gt;
* [http://boylanbridge.com/ Boylan Bridge Brewpub] (0.9 miles)&lt;br /&gt;
* [http://trophybrewing.com/ Trophy Brewing &amp;amp; Pizza Company] (1.2 miles)&lt;br /&gt;
&lt;br /&gt;
[http://goo.gl/maps/haOiD Possible brewpub walking tour] [NOTE: Trophy has great pizza but limited seating.  To finish with dinner consider going the opposite direction and eating in the Warehouse District or downtown]&lt;br /&gt;
&lt;br /&gt;
'''Greater Raleigh'''&lt;br /&gt;
&lt;br /&gt;
* [http://bigbossbrewing.com/‎ Big Boss Brewing] (3.5 miles, Raleigh)&lt;br /&gt;
* [http://raleighbrewingcompany.com/ Raleigh Brewing Company] (4 miles, Raleigh)&lt;br /&gt;
* [http://www.lynnwoodgrill.com/node/10 Lynnwood Brewing Concern] (9 miles, Raleigh)&lt;br /&gt;
* [http://www.loneriderbeer.com/ Lone Rider] (13 miles, Raleigh)&lt;br /&gt;
* [http://gizmobrewworks.com/ Gizmo Brewworks] (12 miles, Raleigh)&lt;br /&gt;
* [http://www.aviatorbrew.com/ Aviator Brewing Company] (17 miles, Fuquay Varina)&lt;br /&gt;
* [http://hosannabrewing.com/ Hosanna Brewery] (14 miles, Fuquay Varina)&lt;br /&gt;
* [http://deepriverbrewing.com/ Deep River Brewing] (16 miles, Clayton)&lt;br /&gt;
* [http://www.carolinabrew.com/ Carolina Brewing] (19 miles, Holly Springs)&lt;br /&gt;
* [http://www.bombshellbeer.com/ Bombshell Beer] (18 miles, Holly Springs)&lt;br /&gt;
* [http://www.whitestreetbrewing.com/ White Street Brewing] (18 miles, Wake Forest)&lt;br /&gt;
&lt;br /&gt;
'''Greater Triangle'''&lt;br /&gt;
&lt;br /&gt;
* [http://trianglebrewery.com/ Triangle Brewing] (Durham)&lt;br /&gt;
* [http://www.fullsteam.ag/beer/ Fullsteam] (Durham)&lt;br /&gt;
* [http://bullcityburgerandbrewery.com/Bull_City_Burger_and_Brewery/Home.html Bull City Burger &amp;amp; Brewing] (Durham)&lt;br /&gt;
* [http://thetopofthehill.com/ Top of the Hill] (Chapel Hill)&lt;br /&gt;
* [http://steelstringbrewery.com/ Steel String Craft Brewery] (Carrboro)&lt;br /&gt;
* [http://www.mysterybrewing.com/ Mystery Brewing] (Hillsborough)&lt;br /&gt;
* [http://whiterabbitbrewery.com/ White Rabbit Brewing] (Angiers)&lt;br /&gt;
* [http://doublebarleybrewing.com/ Double Barley Brewing] (Wilson Mills)&lt;br /&gt;
&lt;br /&gt;
Other nanobrews: [http://subnoir.net/ Sub Noir Brewing] (Raleigh), [http://starpointbrewing.com/ StarPoint Brewing] (Carrboro), [http://ponysaurusbrewing.com/ Ponysaurus] (Durham), [https://www.facebook.com/sourwoodbrewingco Sourwood Brewing Company - Cider] (Durham)&lt;br /&gt;
&lt;br /&gt;
=== Bottle Shops ===&lt;br /&gt;
&lt;br /&gt;
* [http://tastybeverageco.com/ Tasty Beverage Company] About 1200 packaged beers and 6 draft beers (0.3 mile)&lt;br /&gt;
* [http://paddyobeers.com/ Paddy O'Beers] Bottle shop and tasting room (0.4 mile)&lt;br /&gt;
* [https://plus.google.com/116185965486400371099/about?gl=us&amp;amp;hl=en The Bottle Shop at Tyler's Taproom] (1.0 mile)&lt;br /&gt;
* [http://www.wineauthorities.com/ Wine Authorities] (1.3 miles)&lt;br /&gt;
&lt;br /&gt;
==Raleigh Events March 23-27==&lt;br /&gt;
&lt;br /&gt;
[https://www.mergerecords.com/25k Merge Records 25k] (March 22) Chapel Hill to Durham run, with post race party and bands at Motorco music hall (celebrating 25th year of Merge Records label)&lt;br /&gt;
&lt;br /&gt;
===Sunday March 23===&lt;br /&gt;
&lt;br /&gt;
* Apparently there's going to be [http://www.thepncarena.com/events/detail/2014-ncaa-division-i-mens-basketball-tournament some basketball game] at PNC Arena...&lt;br /&gt;
** If anyone else is crazy enough to pay the money for tickets email rosalynmetz [at] the gmail&lt;br /&gt;
* Another basketball game - [http://www.visitraleigh.com/includes/calendar-of-events/Cary-Invasion-vs-East-Carolina-Stealth/26414/ Cary Invasion vs. East Carolina Stealth], 6 pm&lt;br /&gt;
* [http://www.visitraleigh.com/includes/calendar-of-events/Civil-Rights-Through-Song/25383/ Civil Rights Through Song], Burning Coal Theater Company, at Murphrey School Auditorium, 2 pm&lt;br /&gt;
* Romeo and Juliet - Carolina Ballet at [http://www.dukeenergycenterraleigh.com/event/carolina-ballet-private-event-3340 Fletcher Opera Theater]&lt;br /&gt;
* [http://calendar.activedatax.com/ncstate/EventList.aspx?fromdate=3/1/2014&amp;amp;todate=3/31/2014&amp;amp;display=Month&amp;amp;type=public&amp;amp;eventidn=9568&amp;amp;view=EventDetails&amp;amp;information_id=27101 LEO (the anti-gravity show)], NCSU Center Stage, 3 pm&lt;br /&gt;
* [http://triangleyarncrawl.com/ Triangle Yarn Crawl]&lt;br /&gt;
* [http://nuvyug.net/ India Fest] at Dorton Arena&lt;br /&gt;
* [http://www.godowntownraleigh.com/event/at-the-movies-frost-and-nixon At the Movies: Frost/Nixon] at NC Museum of History (free movie and lecture associated with the [http://www.ncdcr.gov/ncmoh/SeeourExhibits/CurrentExhibits/Watergate.aspx Watergate exhibit])&lt;br /&gt;
&lt;br /&gt;
===Monday March 24===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tuesday, March 25===&lt;br /&gt;
* [http://www.visitraleigh.com/includes/calendar-of-events/NHL-Carolina-Hurricanes-vs-New-York-Islanders/24787/ NHL Carolina Hurricanes vs. New York Islanders], 7pm (for free bus see [http://www.godowntownraleigh.com/get-around/pepsi-caniac-coach Pepsi Caniac Coach])&lt;br /&gt;
&lt;br /&gt;
* Job opportunity - AWS is hiring for Seattle-based positions. [https://aws.amazon.com/careers/raleigh-storage-hiring-2014/?sc_channel=sm&amp;amp;sc_campaign=hiringevent&amp;amp;sc_publisher=fb&amp;amp;sc_medium=std&amp;amp;sc_content=raleigh&amp;amp;sc_category=hiringevent Social gathering information], 6pm - 9pm&lt;br /&gt;
&lt;br /&gt;
===Wednesday, March 26===&lt;br /&gt;
&lt;br /&gt;
===Thursday, March 27===&lt;br /&gt;
&lt;br /&gt;
* [http://www.ncsu.edu/dance/events/PDP_SPR2014.html Panoramic Dance Project] at NCSU's Titmus Theater&lt;br /&gt;
* [http://www.dukeenergycenterraleigh.com/event/north-carolina-artists-exhibition-3994 2014 Artists Exhibition - Raleigh Fine Arts Society] at Betty Ray McCain Art Gallery&lt;br /&gt;
* [http://www.ncdcr.gov/ncmoh/Home.aspx Watergate: Politics, Scandal, and the Media] Panel discussion at the NC Museum of History (reservation required)&lt;br /&gt;
* [http://www.visitraleigh.com/includes/calendar-of-events/Raleigh-Beer-Guide-Kickoff-Party/26790/ Raleigh Beer Guide Kickoff Party] All 15 Greater Raleigh breweries on tap.&lt;br /&gt;
&lt;br /&gt;
== Music ==&lt;br /&gt;
&lt;br /&gt;
'''Sunday March 23'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.thepourhousemusichall.com/event/447527-matt-schofield-raleigh/ Matt Schofield] at Pour House&lt;br /&gt;
* Action Bronson at [http://www.catscradle.com/events/ Cat's Cradle] (in Carrboro)&lt;br /&gt;
* Casanovas in Heat at [http://www.slimsraleigh.com/ Slim's]&lt;br /&gt;
&lt;br /&gt;
'''Monday March 24'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.dpacnc.com/events/detail/csn Crosby, Stills &amp;amp; Nash] at Durham Performing Arts Center (in Durham)&lt;br /&gt;
* [http://southlandballroom.com/events/asleep-wheel/ Asleep at the Wheel] at Southland Ballroom&lt;br /&gt;
* Devils Wears Prada, with Ghost Inside, others at [http://www.lincolntheatre.com/schedule.htm Lincoln Theater]&lt;br /&gt;
* [http://www.thepourhousemusichall.com/event/497289-daley-raleigh/ Daley] at Pour House&lt;br /&gt;
&lt;br /&gt;
'''Tuesday March 25'''&lt;br /&gt;
&lt;br /&gt;
* Three 6 Mafia at [http://www.lincolntheatre.com/schedule.htm Lincoln Theater]&lt;br /&gt;
* [http://kingsbarcade.com/2014/03/25/kings-presents-axxaabraxas-captured-tracks-at-slims/ Axxa/Abraxas] at Slim's&lt;br /&gt;
* [http://www.thepourhousemusichall.com/event/497341-coast-2-coast-live-raleigh/ Coast 2 Coast Live Interactive Showcase] at Pour House&lt;br /&gt;
* Open Mic Night at [http://www.deepsouththebar.com/ Deep South]&lt;br /&gt;
&lt;br /&gt;
'''Wednesday March 26'''&lt;br /&gt;
&lt;br /&gt;
* [http://www.thepourhousemusichall.com/event/479771-pigeons-playing-ping-pong-raleigh/ Pigeons Playing Ping Pong] and Imperial Blend at [http://www.thepourhousemusichall.com/ Pour House]&lt;br /&gt;
* Mang (Ween tribute) at [http://www.slimsraleigh.com/ Slim's]&lt;br /&gt;
* Free Jazz Night at [http://humblepierestaurant.com/ Humble Pie]&lt;br /&gt;
* Open Mic Night at [http://www.deepsouththebar.com/ Deep South]&lt;br /&gt;
&lt;br /&gt;
'''Thursday March 27'''&lt;br /&gt;
&lt;br /&gt;
* Local Beer/Local Band night at [http://www.tnnirishpub.com/ Tir Na Nog]&lt;br /&gt;
* [http://www.thepourhousemusichall.com/event/497347-blue-sky-black-death-raleigh/ Blue Sky Black Death] at Pour House&lt;br /&gt;
* [http://www.deepsouththebar.com/event/492779-unifier-jessica-long-new-raleigh/ Unifier, Jessica Long &amp;amp; The New Kind] at Deep South&lt;br /&gt;
* [http://kingsbarcade.com/2014/03/27/good-graeff/ Good Graeff] at Kings Barcade&lt;br /&gt;
* Triathalon with Giant Giants at [http://www.slimsraleigh.com/ Slim's]&lt;br /&gt;
* [http://southlandballroom.com/events/alchemystics/ Alchemystics] at Southland Ballroom&lt;br /&gt;
* Sarah Colonna (Comedy) at [https://center-stage.seatengine.com/venues/goodnights Goodnight's Comedy]&lt;br /&gt;
&lt;br /&gt;
'''More Music Venues in the Greater Triangle'''&lt;br /&gt;
&lt;br /&gt;
* Raleigh: [http://themaywoodraleigh.com/ Maywood]&lt;br /&gt;
* Chapel Hill/Carrboro: [http://www.catscradle.com/ Cat's Cradle], [http://www.local506.com/calendar/ Local 506], [http://caverntavern.com/ The Cave], [http://www.chapelhillunderground.com/ Underground], [https://www.carolinaperformingarts.org/ Memorial Hall]&lt;br /&gt;
* Durham: [http://motorcomusic.com/ Motorco], [http://www.thepinhook.com/ Pinhook]&lt;br /&gt;
* Saxapahaw: [http://www.hawriverballroom.com/ Haw River Ballroom]&lt;br /&gt;
[[Category:Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_During_the_Conference_Volunteers&amp;diff=40476</id>
		<title>2014 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_During_the_Conference_Volunteers&amp;diff=40476"/>
				<updated>2014-03-04T17:36:51Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2014 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
For 2014, we might assign 1-2 person(s) to take questions for sessions (assuming there's time) via Twitter/IRC. Just a thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
CONCENTRA will be working at the registration desk. We are looking for possibly one person to be a code4lib presence at the desk on Tuesday morning.&lt;br /&gt;
&lt;br /&gt;
Tuesday 8-9 am&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
&lt;br /&gt;
* Dre, destroyer of cookies, doesn't look as good in a hat as Becky.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*Rosalyn, not as entertaining as Becky&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=2014_During_the_Conference_Volunteers&amp;diff=40475</id>
		<title>2014 During the Conference Volunteers</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=2014_During_the_Conference_Volunteers&amp;diff=40475"/>
				<updated>2014-03-04T17:36:40Z</updated>
		
		<summary type="html">&lt;p&gt;Akorphan: /* MCs */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;code4lib 2014 During the Conference Volunteers&lt;br /&gt;
&lt;br /&gt;
== Hospitality Suite Committee ==&lt;br /&gt;
&lt;br /&gt;
This committee makes arrangements for any hospitality suite amenities (technology, snacks, games, icebreakers...) we may want.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Welcome Wagon Committee ==&lt;br /&gt;
&lt;br /&gt;
Offers conference newcomers an opportunity to self-identify; offers oldtimers an opportunity to meet newcomers. May also want to constitute a year-round variation for #code4lib.&lt;br /&gt;
&lt;br /&gt;
* Becky Yoose (b.yoose at google)&lt;br /&gt;
&lt;br /&gt;
== Social Networking ==&lt;br /&gt;
Responsible for non-IRC social networking presence.&lt;br /&gt;
&lt;br /&gt;
For 2014, we might assign 1-2 person(s) to take questions for sessions (assuming there's time) via Twitter/IRC. Just a thought.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC Evangelists ==&lt;br /&gt;
Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== IRC Access ==&lt;br /&gt;
Look into technology/procedures to make connecting to, and maintaining a connection to, IRC less painful.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration Desk Volunteers==&lt;br /&gt;
&lt;br /&gt;
CONCENTRA will be working at the registration desk. We are looking for possibly one person to be a code4lib presence at the desk on Tuesday morning.&lt;br /&gt;
&lt;br /&gt;
Tuesday 8-9 am&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==MCs==&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
&lt;br /&gt;
* Dre, destroyer of cookies, doesn't look as good in a hat as Becky.&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
&lt;br /&gt;
*Becky, destroyer of last names, singer of badly adapted show tunes &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
*Rosalyn, not as entertaining as Becky&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
&lt;br /&gt;
== Session Timer Volunteers ==&lt;br /&gt;
&lt;br /&gt;
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop with a stopwatch program).  It's good to have two people in each slot to back each other up in case of machinery failure.&lt;br /&gt;
&lt;br /&gt;
'''Schedule for Session Timers'''&lt;br /&gt;
&lt;br /&gt;
Tuesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Tuesday PM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Wednesday PM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Thursday AM&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Raffles ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2014]]&lt;/div&gt;</summary>
		<author><name>Akorphan</name></author>	</entry>

	</feed>