Code4Lib - User contributions [en]

2024 Conference Volunteers

2024-04-29T11:20:07Z

HeidiBurkhardt:

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* Heidi Burkhardt
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Tuesday, Day Two:
* AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: Michelle Navarro
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: Michelle Navarro
* PM volunteer: Michelle Navarro

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: Cary Gordon
* PM Volunteer: Barbara Cormack

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-04-29T11:19:30Z

HeidiBurkhardt: added instructions for how to sign up, used language from conf committee page

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and sign-up for one or more of the slots below.

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* Heidi Burkhardt
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Tuesday, Day Two:
* AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: Michelle Navarro
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: Michelle Navarro
* PM volunteer: Michelle Navarro

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: Cary Gordon
* PM Volunteer: Barbara Cormack

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-04-19T20:59:40Z

HeidiBurkhardt: added a volunteer spot

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* Heidi Burkhardt
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: Ange Zaytsev
* PM volunteer: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: Cary Gordon
* PM Volunteer: Barbara Cormack

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule
* Ange Zaytsev
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

2024 Conference Volunteers

2024-03-07T14:04:34Z

HeidiBurkhardt: volunteered for a slot

= Code4Lib 2024 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].

== Community Support Volunteers ==

See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.

== Concierge/Local Guides ==
Available after sessions to direct people to evening activities and local points of interest, etc.

If you're local to the area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.

* [[User:NatashaAllen|Natasha Allen]] (U-M)

Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a "LOCAL" tag

== Conference Logistics & Registration ==
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.

Onsite Volunteer Committee Coordinator: Hardy Pottinger

12 Noon - 1pm Monday, day one:
* Hardy Pottinger
* Heidi Burkhardt

8am - 9am Tuesday, day two:
* ''Your Name Here''
* ''Your Name Here''

== Social Events ==

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* ''Your Name Here''

Tuesday, Day Two:
* ''Your Name Here''

== Social Networking ==

Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator:

Monday, Day One:
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Thursday, Workshop Day:
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Mic-minders ==

Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM volunteer: ''Your Name Here''
* AM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== Livestream QA (Remote) ==
Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).

To report a problem (even if you're not an "official" volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM volunteer: ''Your Name Here''

== IRC/Slack (Technical) ==
Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.

Onsite Volunteer Committee Coordinator:

* Before the conference: ''Your Name Here''
* During the conference: ''Your Name Here''

==MCs==

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: Dre

Tuesday, Day Two:
* AM Volunteer: Eric Hellman
* PM Volunteer: Hardy Pottinger

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== Session Timers ==
Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.

Onsite Volunteer Committee Coordinator: ''Your Name Here''

Monday, Day One:
* PM Volunteer: ''Your Name Here''

Tuesday, Day Two:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

Wednesday, Day Three:
* AM Volunteer: ''Your Name Here''
* PM Volunteer: ''Your Name Here''

== The Whatever Crew ==
Volunteers who are willing to help with various tasks as needed during the conference.

* Hardy Pottinger
* ''Your Name Here''
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

* ''Your Name Here''

podium tech help:

* ''Your Name Here''

[[Category: Code4Lib2024]]

Code4Lib 2024 Conference Committees

2023-09-26T18:24:41Z

HeidiBurkhardt: added self to website working group

= Code4Lib 2024 Conference Committees =

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

==Planning Committee==
Also known as the Local Planning Committee, although there is no requirement for the members to be local.

[[2024 Planning Committee Documents|2024 Planning Committee Documents]]

* [[User:NatashaAllen|Natasha Allen]] (U-M) - Primary Contact, Chair
* Jesse Johnston (U Michigan) - Secondary Contact, Co-chair, documentarian
* Jennifer Cummings (Concentra) - Tertiary Contact
* Kathy Azevedo (Concentra) - Volunteer
* [[User:varnum|Ken Varnum]] (U-M) - Volunteer
* [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - Volunteer

== Website Working Group ==
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).

[[2024 Website Working Group Documents|2024 Website Working Group Documents]]

* Esmé Cowles - Primary Contact, Chair
* [[User:Phette23|Eric Phetteplace]] phette23@gmail.com - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Andy Pederson (apederson@unl.edu) - Accessibility Committee Contact
* Trip Kirkpatrick trip.kirkpatrick@yale.edu - Volunteer
* Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* Christine Salek (cmsalek@wisc.edu) - Volunteer
* [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - LPC liaison

== Budget and Sponsorship Committee ==
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.

[[2024 Budget and Sponsorship Documents|2024 Budget and Sponsorship Documents]]

* Jesse Johnston (UMich) - Primary Contact, Chair, and liaison to LPC
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Bohyun Kim - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
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.

From the chair: This committee will start work in late September. The work will wrap up in January, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Andromeda Yelton - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Lillian Hogendoorn (lillian.hogendoorn@utoronto.ca) - Volunteer
* Maccabee Levine (@maccabeelevine on slack) - Volunteer
* [[User:NatashaAllen|Natasha Allen]] - LPC Liaison

== Pre-conference Committee ==
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.

[[2024 Pre-conference Documents|2024 Pre-conference Documents]]

* Your Name Here - Primary Contact, Chair
* Ann Marie Mesco - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:SheriseKimura|Sherise Kimura]] - Volunteer
* Ken Rose - Volunteer
* [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Volunteer

== Program Committee ==
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.

[[2024 Program Documents|2024 Program Documents]]

* Your Name Here - Primary Contact, Chair
* [[User:MegoFranks|Mego Franks]] - Secondary Contact, CoChair - megofranks@gmail.com
* Your Name Here - Documentarian
* Matt Sherman - Volunteer
* Dre - Volunteer
* [[User:varnum|Ken Varnum]] - LPC liaison
* [[User:highermath|Cary Gordon]] - Volunteer
* [[User:MoniqueRio|Monique Rio]] - Volunteer

== Scholarship Committee ==
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.

Work will start in early October

* Chad Nelson - chad.nelson at ucop.edu, @bibliotechy on Slack - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
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.

'''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).

== T-Shirt Committee ==
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.

[[2024 T-Shirt Documents|2024 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''

[[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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.

2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Brandon Patterson - Primary Contact, Chair
* [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
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.

* [[User:DataGazetteer|Peter Murray]] - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - LPC Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2025 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2025 Host Voting Documents|2025 Host Voting Documents]]

*[[User:NatashaAllen|Natasha Allen]] (University of Michigan) - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2024 Accessibility Documents|2024 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Christine Salek (cmsalek@wisc.edu) - Volunteer
* Zhaneille Green (zbg@duke.edu) - Volunteer
* Andy Pederson (apederson@unl.edu) - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2024 Whatever Documents|2024 Whatever Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Elaine Kong (elainekong@pitt.edu) - Volunteer
* [[User:SamHansen|Sam Hansen]] - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2024]]

User:HeidiBurkhardt

2023-09-21T19:18:00Z

HeidiBurkhardt:

Web Project Manager and Content Strategist

University of Michigan Library

heidisb@umich.edu

@heidisb on Slack

User:HeidiBurkhardt

2023-09-21T19:17:02Z

HeidiBurkhardt:

Web Project Manager and Content Strategist

University of Michigan Library

heidisb@umich.edu

heidisb on Slack

User:HeidiBurkhardt

2023-09-08T11:01:05Z

HeidiBurkhardt:

Web Project Manager and Content Strategist

University of Michigan Library

User:HeidiBurkhardt

2023-09-08T11:00:34Z

HeidiBurkhardt: Created page with "Web Project Manager and Content Strategist University of Michigan Library"

Web Project Manager and Content Strategist
University of Michigan Library

Code4Lib 2024 Conference Committees

2023-09-08T10:59:57Z

HeidiBurkhardt: signed up for a committee

= Code4Lib 2024 Conference Committees =

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

==Planning Committee==
Also known as the Local Planning Committee, although there is no requirement for the members to be local.

[[2024 Planning Committee Documents|2024 Planning Committee Documents]]

* [[User:NatashaAllen|Natasha Allen]] (U-M) - Primary Contact, Chair
* Jesse Johnston (U Michigan) - Secondary Contact, Co-chair, documentarian
* Jennifer Cummings (Concentra) - Tertiary Contact
* Kathy Azevedo (Concentra) - Volunteer
* [[User:varnum|Ken Varnum]] (U-M) - Volunteer
* [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - Volunteer

== Website Working Group ==
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).

[[2024 Website Working Group Documents|2024 Website Working Group Documents]]

* Esmé Cowles - Primary Contact, Chair
* [[User:Phette23|Eric Phetteplace]] phette23@gmail.com - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Accessibility Committee Contact
* Trip Kirkpatrick trip.kirkpatrick@yale.edu - Volunteer
* Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer
* Christine Salek (cmsalek@wisc.edu) - Volunteer

== Budget and Sponsorship Committee ==
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.

[[2024 Budget and Sponsorship Documents|2024 Budget and Sponsorship Documents]]

* Jesse Johnston (UMich) - Primary Contact, Chair, and liaison to LPC
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Bohyun Kim - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Keynote Committee ==
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.

[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.

From the chair: This committee will start work in November or December. (You're welcome to sign up sooner, but you may not hear from me before November.) The work will wrap up in March, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Andromeda Yelton - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [[User:NatashaAllen|Natasha Allen]] - LPC Liaison

== Pre-conference Committee ==
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.

[[2024 Pre-conference Documents|2024 Pre-conference Documents]]

* Your Name Here - Primary Contact, Chair
* Ann Marie Mesco - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer, grip, and all-around lackey
* Ken Rose - Volunteer
* Your Name Here - Volunteer

== Program Committee ==
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.

[[2024 Program Documents|2024 Program Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Matt Sherman - Volunteer
* Dre - Volunteer
* [[User:varnum|Ken Varnum]] - LPC liaison
* [[User:highermath|Cary Gordon]] - Volunteer
* [[User:MoniqueRio|Monique Rio]] - Volunteer

== Scholarship Committee ==
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.

* Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
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.

'''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).

== T-Shirt Committee ==
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.

[[2024 T-Shirt Documents|2024 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

'''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''

[[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

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.

2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Streaming Video Committee ==
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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - LPC Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Code4Lib 2025 Host Voting Committee ==
This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process.

[[2025 Host Voting Documents|2025 Host Voting Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
This committee will assist attendees with IRC and Slack.

[[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Accessibility Committee ==
Document and address major points of the conference that are not accessible for conference attendees.

[[2024 Accessibility Documents|2024 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Christine Salek (cmsalek@wisc.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Whatever Committee ==
Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.

[[2024 Whatever Documents|2024 Whatever Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2024]]