Difference between pages "2023 Conference Volunteers" and "Code4Lib Journal Editorial Committee"

From Code4Lib
(Difference between pages)
Jump to: navigation, search
(Changed hashtag to #c4l23 since to follow the convention of previous years and is already in use in Mastodon)
 
m (Added CE for MEE)
 
Line 1: Line 1:
= Code4Lib 2023 Conference Volunteers =
+
This supplements the [http://journal.code4lib.org/editorial-committee Editorial Committee] page on the ''Journal'' website.
  
'''DRAFT/Work in Progress'''
+
=== Current Editors ===
  
Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].
+
* Ed Corrado (1-current; CE 10, 51)
 +
* Mark E. Eaton (56-current; CE 59)
 +
* Péter Király (23-current; CE 57)
 +
* Peter Murray (17-current; CE 20, 36, 49)
 +
* Ron Peterson (1-current; CE 3, 12, 18, 24, 33, 53)
 +
* Terry Reese (17-current; CE 21, 27, 31)
 +
* Mark Swenson (37-current; CE 52)
 +
* Krista Stapelfeldt (57-current)
  
== Community Support Volunteers ==
+
Technical Administrator: Jon Fackrell (52- )
  
See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.
+
=== Former Editors ===
 +
* Brighid M. Gonzales (37-58; CE 48, 58)
 +
* Sara Amato (17-57; CE 22, 29, 37, 46, 56)
 +
* Andrew Darby (3-56; CE 8, 19, 34, 54)
 +
* Eric Hanson (37-55; CE 50)
 +
* Junior Tidal (23-55; CE 55)
 +
* Rebecca Hirsch (37-49)
 +
* Carolin Moritz (44-46)
 +
* Carol Bean (1-44; CE 9, 16, 30, 38)
 +
* Christine Schwartz (3-7; CE 6)
 +
* Ed Summers (16-17)
 +
* Eric Lease Morgan (1-2; CE 2)
 +
* Gabriel Farrell (9-19; CE 13)
 +
* Jodi Schneider (1-8)
 +
* Jon Brinley (TA 1-14)
 +
* Ken Varnum (1-10; CE 4)
 +
* Meghan Finch (23-43; CE 32)
 +
* MJ Suhonos (10-14)
 +
* Norma Palomino (37)
 +
* Ryan Wick (TA 3-14)
 +
* Emily Lynema (1-16, CE 5)
 +
* Tim McGeary (10-16; CE 14)
 +
* Tim Lepczyk (10-17, CE 17)
 +
* Tod Olson (10-17; CE 15)
 +
* Jonathan Rochkind (1-20; CE 1)
 +
* Kelley McGrath (8-28; CE 11,26)
 +
* Shawn Averkamp (17- 29; CE 23, 28)
 +
* Heidi Elaine Dowdling (23-29; CE 28)
 +
* Dan Scott (23-29; CE 25)
 +
* Ruth K Tillman (29-41; CE 35, 40; TA 30-52)
 +
* Jason Thomale (23-32)
 +
* Tom Keays (1-29; CE 7; TA 15-29)
  
== 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.
+
'''Note''': "CE" = Coordinating Editor and "TA" = Technical Administrator
  
* ''Your Name Here''
+
[[Category: Code4Lib Journal]]
 
+
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: ''Your Name Here''
+
 
+
8am - 9am Wednesday, day one:
+
* Hardy Pottinger
+
* ''Your Name Here''
+
 
+
8am - 9am Thursday, day two:
+
* Hardy Pottinger
+
* ''Your Name Here''
+
 
+
== Social Events ==
+
 
+
Onsite Volunteer Committee Coordinator:
+
 
+
Wednesday, Day One:
+
* ''Your Name Here''
+
 
+
Thursday, Day Two:
+
* 11pm Game Night Cleanup: ''Your Name Here''
+
* 11pm Game Night Cleanup: ''Your Name Here''
+
 
+
== Social Networking ==
+
 
+
Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)
+
 
+
Onsite Volunteer Committee Coordinator:
+
 
+
Tuesday, Preconference Day:
+
*  AM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Wednesday, Day One:
+
*  AM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Friday, Day Three:
+
*  AM 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''
+
 
+
Wednesday, Day One:
+
*  AM volunteer: ''Your Name Here''
+
*  AM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM volunteer: ''Your Name Here''
+
*  AM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Friday, Day Three:
+
*  AM volunteer: ''Your Name Here''
+
*  AM volunteer: ''Your Name Here''
+
 
+
== Livestream Assistants (Onsite) ==
+
 
+
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!
+
 
+
Onsite Volunteer Committee Coordinator: ''Your Name Here''
+
 
+
Wednesday, Day One:
+
*  AM Volunteer: ''Your Name Here''
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM Volunteer: ''Your Name Here''
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
 
+
Friday, Day Three:
+
*  AM Volunteer: ''Your Name Here''
+
*  AM 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''
+
 
+
Wednesday, Day One:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM volunteer: ''Your Name Here''
+
 
+
Friday, Day Three:
+
*  AM 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''
+
 
+
Wednesday, Day One:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: Hardy Pottinger
+
 
+
Friday, Day Three:
+
*  AM 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''
+
 
+
Wednesday, Day One:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
 
+
Thursday, Day Two:
+
*  AM Volunteer: ''Your Name Here''
+
*  PM Volunteer: ''Your Name Here''
+
 
+
Friday, Day Three:
+
*  AM Volunteer: ''Your Name Here''
+
 
+
== The Whatever Crew ==
+
Volunteers who are willing to help with various tasks as needed during the conference.
+
 
+
* ''Your Name Here''
+
* ''Your Name Here''
+
* ''Your Name Here''
+
 
+
 
+
future potential volunteers:
+
 
+
* ''Your Name Here''
+
 
+
podium tech help:
+
 
+
* ''Your Name Here''
+
 
+
 
+
[[Category: Code4Lib2023]]
+

Latest revision as of 17:13, 25 September 2024

This supplements the Editorial Committee page on the Journal website.

Current Editors

  • Ed Corrado (1-current; CE 10, 51)
  • Mark E. Eaton (56-current; CE 59)
  • Péter Király (23-current; CE 57)
  • Peter Murray (17-current; CE 20, 36, 49)
  • Ron Peterson (1-current; CE 3, 12, 18, 24, 33, 53)
  • Terry Reese (17-current; CE 21, 27, 31)
  • Mark Swenson (37-current; CE 52)
  • Krista Stapelfeldt (57-current)

Technical Administrator: Jon Fackrell (52- )

Former Editors

  • Brighid M. Gonzales (37-58; CE 48, 58)
  • Sara Amato (17-57; CE 22, 29, 37, 46, 56)
  • Andrew Darby (3-56; CE 8, 19, 34, 54)
  • Eric Hanson (37-55; CE 50)
  • Junior Tidal (23-55; CE 55)
  • Rebecca Hirsch (37-49)
  • Carolin Moritz (44-46)
  • Carol Bean (1-44; CE 9, 16, 30, 38)
  • Christine Schwartz (3-7; CE 6)
  • Ed Summers (16-17)
  • Eric Lease Morgan (1-2; CE 2)
  • Gabriel Farrell (9-19; CE 13)
  • Jodi Schneider (1-8)
  • Jon Brinley (TA 1-14)
  • Ken Varnum (1-10; CE 4)
  • Meghan Finch (23-43; CE 32)
  • MJ Suhonos (10-14)
  • Norma Palomino (37)
  • Ryan Wick (TA 3-14)
  • Emily Lynema (1-16, CE 5)
  • Tim McGeary (10-16; CE 14)
  • Tim Lepczyk (10-17, CE 17)
  • Tod Olson (10-17; CE 15)
  • Jonathan Rochkind (1-20; CE 1)
  • Kelley McGrath (8-28; CE 11,26)
  • Shawn Averkamp (17- 29; CE 23, 28)
  • Heidi Elaine Dowdling (23-29; CE 28)
  • Dan Scott (23-29; CE 25)
  • Ruth K Tillman (29-41; CE 35, 40; TA 30-52)
  • Jason Thomale (23-32)
  • Tom Keays (1-29; CE 7; TA 15-29)


Note: "CE" = Coordinating Editor and "TA" = Technical Administrator