Code4Lib - User contributions [en]

MDC/2018/Registration

2018-07-07T19:42:12Z

AmyWickner: Registered, lucky 33

Registration for the [[MDC/2018| 2018 C4L DC/MD/VA]] Meetup.

Registration is free, but please do register by adding your name to this list if you are planning to attend, so we can plan accordingly! We have a maximum capacity of 50.

You need to have a wiki account to update this page. See instructions for requesting a new account on the [[Special:UserLogin|Login Page]] Or, send email to [[User:DavidDurden|David Durden]], [mailto:durden@umd.edu durden@umd.edu] to be added to the list.

# [[User:DavidDurden|David Durden]], University of Maryland Libraries
# [mailto:jkoivist@umd.edu Joseph Koivisto], University of Maryland Libraries
# [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries
# Ian Hardy, Washington Research Library Consortium
# [[User:JefferyGerhard|Jeff Gerhard]], Georgetown Law Library
#[mailto:thschone@umd.edu Tiffany Schoneboom], University of Maryland Libraries
# [mailto:ahendric Anne Hendrick], University of Maryland Libraries
# [mailto:nfrau@umd.edu Neil Frau-Cortes], University of Maryland Libraries
# [[User:dkerchner|Dan Kerchner]], George Washington University Libraries
# [mailto:acoren@umd.edu Ashleigh Coren], University of Maryland Libraries
# [mailto:calvara1@umd.edu Carlos Alvarado], University of Maryland Libraries
# [mailto:JFroustet@asce.org Jeff Froustet], American Society of Civil Engineers
# [mailto:Chuck.Schoppet@ARS.USDA.GOV Chuck Schoppet], National Agricultural Library
# [[User:Lwrubel|Laura Wrubel]], George Washington University
# [mailto:swiesner@umd.edu Susan Weisner], University of Maryland Libraries
# [mailto:ladavis@loc.gov Laura Davis], Library of Congress
# [mailto:delphonse@cua.edu Arlia Delphonse], Catholic University of America
# [mailto:blparker@umd.edu Bria Parker], University of Maryland Libraries
# [mailto:afsmith@umd.edu Austin Smith], University of Maryland Libraries
# [mailto:ewahl@folger.edu Emily Wahl], Folger Shakespeare Library
# [mailto:jsly@umd.edu Jordan Sly], University of Maryland Libraries
# [mailto:jacky.hart.ctr@dot.gov Jacky Hart], U.S. Department of Transportation
# [mailto:laura.farley.ctr@dot.gov Laura Farley], U.S. Department of Transportation
# [mailto:jansen@umd.edu Greg Jansen], University of Maryland, School of Information Studies
# [mailto:khoupt@umd.edu Kiri Houpt], University of Maryland
# [mailto:frenchrb@jmu.edu Rebecca French], JMU Libraries
# [mailto:khes@loc.gov Kirk Hess] Library of Congress
# [mailto:peter.burslem@umuc.edu Peter Burslem], UMUC Library
# [mailto:westgard@umd.edu Joshua Westgard], University of Maryland Libraries
# [mailto:kbreneman@ubalt.edu Kyle Breneman], University of Baltimore Library
# [mailto:christina.pikas@jhuapl.edu Christina Pikas], Johns Hopkins University Applied Physics Laboratory
# [mailto:ladonna.smith@pgcmls.info LaDonna Smith], Prince George's County Memorial Library System
# [[User:AmyWickner|Amy Wickner]]
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#

== Waitlist ==

#
#
#
#
#

2018 Scholarship Documents

2018-06-05T15:36:02Z

AmyWickner: add page for meeting minutes

The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Committee re: funding available for awards. The committee connects scholarship winners with conference coordinators to plan travel and arrangements, and provides additional informational support leading up to and at the conference.

[[2018_Scholarship_Documents/Meetings|Meetings]]

[[2018_Scholarship_Documents/Timeline and tasks|Timeline and tasks]]

[[2018_Scholarship_Documents/Call_for_applications|Call for applications]]

[[2018_Scholarship_Documents/Disseminating_the_call|Disseminating the call]]

[[2018_Scholarship_Documents/Application_form|Application form]]

[[2018_Scholarship_Documents/Application_evaluation_rubric|Application evaluation rubric]]

[[2018_Scholarship_Documents/Contacting_references|Contacting references]]

[[2018_Scholarship_Documents/Applicant_notifications|Applicant notifications]]

[[2018_Scholarship_Documents/Scholarship_announcement|Scholarship announcement]]

[[2018_Scholarship_Documents/Logistics_emails|Logistics emails]]

[[2018_Scholarship_Documents/Buddy_system|Buddy system]]

[[2018_Scholarship_Documents/First-Timers_Guide_for_Scholarship_Awardees|First-Timers' Guide for Scholarship Awardees]]

[[2018_Scholarship_Documents/Post-conference_feedback|Post-conference feedback]]

[[2018_Scholarship_Documents/Lessons_learned|Lessons learned]]

2018 Scholarship Documents/Post-conference feedback

2018-06-05T15:00:47Z

AmyWickner: add request for feedback text, moved intro text into Selected Responses section

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Request for Feedback ==
Hi everyone,

Thank you very much for participating in Code4Lib 2018! It was an honor to have you there, and great to meet quite a few of you in person. I hope you've had safe travels home and that this finds you well.

As part of wrapping up and reflecting on our work, the Scholarship Committee would very much appreciate any feedback you'd like to share about your experience with this program. We've put together an extremely open-ended survey for anonymous input: [link]

If anyone would prefer a 1-1 conversation, I'm happy to listen and/or recruit another member of the committee for such a conversation.

We welcome more than one round of feedback, for example if you have thoughts to share now while the experience is fresh, or next month after time for reflection. This email address will remain active but far less frequently checked for the rest of the spring. Please also feel free to contact me directly with any pressing concerns.

Thank you again, and best wishes, 
Amy

on behalf of the Code4Lib 2018 Scholarship Committee

== Selected Responses ==
2018 scholarship recipients shared post-conference feedback with the Scholarship Committee via anonymous survey (questions are below). After answering each question, survey takers indicated sharing permission for that set of comments: "Who may see feedback about [survey question]?" Additional feedback is available to members of the 2018 Local Planning Committee as well as future local planning and scholarship committees. Please contact the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|2018 Scholarship Committee]] for more information.

=== Application process ===
''Please tell us about your experience with the scholarship application process, including the call for applications, application form and requirements, and any other reflections and experiences.''
* "The application process was incredibly quick and painless. The hardest part was writing about why I thought I deserved the scholarship without allowing the impostor syndrome to kick in."
* "The application process seemed pretty straightforward. I could see how some students could find it difficult get a reference from a professor if they work full time in another field while going to school."

=== Communication ===
''Please tell us about your experience communicating with the Scholarship Committee during the application processes, planning process, and conference.''
* "Communication was amazing, but at times overwhelming. The information dump lead me to missing some important aspects of the conference for scholarship winners - such as the buddy system."

=== Buddy system ===
''If you participated in the conference buddy system, please tell us about your experience.''
* "I did not participate in the buddy system because I missed that in the scholarship emails."

=== Conference logistics & travel planning ===
''Please tell us about your experience with travel planning and conference logistics, including working with Concentra, the Scholarship Committee, and any other resources.''
* "The only complaint I have about logistics, is that there was no obvious way to book a hotel room and have it charged to the scholarship fund. I ended up placing the reservation myself, and having the scholarship committee later add the reservation to the scholarship fund."

=== Conference attendance ===
''Please tell us about your experience attending the conference.''
* "A++++ would do again in a heartbeat if given the opportunity."

=== Additional feedback ===
''Please use this space to share anything else you'd like us to know.''

2018 Scholarship Documents/Applicant notifications

2018-06-05T14:55:57Z

AmyWickner: add Waitlist No Award Notification

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Application Receipt Confirmation ==
Hello,

Thank you for your interest in the 2018 Code4Lib Diversity Scholarship. This email is to inform you that we have received your application, and will begin reviewing applications shortly. Applicants will be notified of the status of their application in early December.

Thank you, 
2018 Code4lib Diversity Scholarship Committee

== Award Notification ==
Dear [applicant's name],

Congratulations! We’re pleased to let you know that the Code4Lib Scholarship Committee has selected you to receive a scholarship to support your attendance at Code4Lib 2018 in Washington, D.C., February 13-16, 2018. These scholarships were made possible by donations from MIT Libraries, DuraSpace, The School of Information Sciences at the University of Illinois, Temple University Libraries, Smithsonian Libraries, The Ohio State University Libraries, and the Code4Lib community.

Please let us know as soon as possible whether you will be able to accept this award and attend the conference. We would very much appreciate a reply by '''Tuesday, December 5'''. Once you have confirmed, you will receive an email from CONCENTRA Conference Management Services inviting you to register for the conference and pre-conference sessions (February 13) at no cost. [https://2018.code4lib.org/general-info/attend Registration] opens on Wednesday, December 6, at 12pm EST, and spots are being held for scholarship recipients.

'''Logistics'''

Each scholarship award covers up to $1,500. Attending both the conference ($350) and the pre-conference day ($60) leaves $1,090 remaining to cover other expenses, including transportation, lodging, and any meals not provided by the conference. If your costs are less than the total award, you will only be reimbursed for the amount spent. If you choose not to register for the preconference day, the remainder would be $1,150. Original receipts are required for reimbursement, which will be handled on site during the conference.

If you choose to stay in the [https://2018.code4lib.org/general-info/venues/ Omni Shoreham Hotel] (official conference venue), CONCENTRA will handle your hotel reservation and the Local Planning Committee will arrange to pay the cost ($182/night) directly; you won’t need to wait for reimbursement for those funds. If you choose other lodgings, you will need to submit your receipts for reimbursement after the conference.

The Scholarship Committee is available to help with travel planning. We’ll follow up with more information about traveling to and attending the conference, once you've confirmed acceptance.

'''One-on-one meetings & buddy system'''

Members of the Scholarship Committee will be available to meet one-on-one to answer any questions you might have about attending Code4Lib. Please let us know if you'd be interested in such a meeting and one of us will follow up to set up a time.

Additionally, members of the Code4Lib community are available to act as conference buddies. This can be a great resource, especially for newcomers. Please let us know if you're interested in being matched with a buddy.

We look forward to seeing you in Washington, D.C., in February. If you will be unable to attend the conference, or choose to decline the scholarship, please let us know as soon as possible.

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

== No Award Notification ==
Dear [applicant's name],

Thank you very much for submitting your Code4Lib 2018 Diversity Scholarship application. The Scholarship Committee received 77 impressive applications for a limited number of scholarships. Unfortunately, your application was not one of those selected for a scholarship for Code4Lib 2018. Thank you again for your time, energy, and interest in Code4Lib. We encourage you to apply again next year.

We would also like to highlight opportunities to follow and participate in Code4Lib 2018 remotely. These include a [https://www.youtube.com/user/code4lib/ livestream of all sessions on YouTube]; via [https://twitter.com/search?q=%23c4l18 #c4l18] on Twitter; and on Slack at [https://code4lib.slack.com https://code4lib.slack.com]. Again, we encourage you to both apply for a scholarship next year and participate in Code4Lib online. Please let us know if you have any questions or comments.

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

== Waitlist Notification ==
Dear [applicant's name],

Thank you very much for submitting your Code4Lib 2018 Diversity Scholarship application. The Scholarship Committee received 77 impressive applications for a limited number of scholarships, and your application has been waitlisted for Code4Lib 2018. We will notify you by Tuesday, December 5, if a spot opens or additional funding becomes available. If you are no longer interested in receiving a diversity scholarship, please let us know as soon as possible.

Thank you again for your time, energy, and interest in Code4Lib, and for your patience during the application process. In the meantime, please let us know if you have any questions or comments,

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

== Waitlist No Award Notification ==

Dear [applicant name],

Thank you again for your continuing interest in Code4Lib and patience with the application review process. Despite a final push for sponsorship and community support, we are unfortunately unable to offer additional scholarship funding to attend Code4Lib 2018. We strongly encourage you to apply again next year.

We would also like to highlight opportunities to follow and participate in Code4Lib 2018 remotely. These include a [https://www.youtube.com/user/code4lib/ livestream of all sessions on YouTube]; via [https://twitter.com/search?q=%23c4l18 #c4l18] and [https://twitter.com/search?q=%23code4lib #code4lib] on Twitter; and on Slack at [https://code4lib.slack.com https://code4lib.slack.com]. Please consider participating in Code4Lib 2018 and the Code4Lib community online!

Thank you very much again for your time. Please let us know if you have any questions or comments.

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

2018 Scholarship Documents/Timeline and tasks

2018-06-05T14:42:32Z

AmyWickner: add task: coordinate with conference MCs

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

The 2018 Scholarship Committee used this timeline to track tasks and deadlines. Committee members signed up for tasks based on interest and capacity.

{| class="wikitable"
|-
! Task / milestone
! Date(s)
! Notes
! Team
|-
| Call for committee volunteers
|
|
| ALL
|-
| Initial committee meetings
| 6/28, 7/19
|
| ALL as available
|-
| ''Call for individual donations to the Angel Fund''
|
| ''Sponsorship Comm aims to have funding confirmed by early October but there may be late additions''
| ''Sponsorship Committee''
|-
| Finalize number of scholarship recipient seats to hold for registration
| 9/15
| Settled on 15
| ALL - email discussion
|-
| Finalize call for applications & application format
| 10/16
|
| Anastasia, Aisha, Chad
|-
| Put out call for applications
| 10/16
| Includes identifying channels, communities, organizations to target
| Anastasia, Aisha, Kat
|-
| Reminder call
| 11/3
|
| Aisha, Kat
|-
| Create evaluation rubric
| 11/10
|
| Amy (draft), ALL (edits)
|-
| Application deadline
| 11/17
|
| Tod, Todd
|-
| Confirm application receipt
| 11/20
|
| Todd
|-
| Follow up about missing information
| 11/20
|
| Todd
|-
| Review & rate applications individually
| 11/18-11/28
| "Individually" as in each committee member
| ALL
|-
| Committee meeting to discuss applications, choose recipients
| 11/29 2:00 PM
|
| ALL - multiple meetings if needed or send written feedback
|-
| Request references
| 11/29
| Can be via email or Skype/phone
| Kat, Mairelys, Ruth, Elvia, Amy
|-
| ''Finalize number of available scholarships; notify LPC of registration spots to release''
| ''12/5''
|
| ''Budget & sponsorship committees''
|-
| Reference deadline
| 12/1 12:00 PM
|
| Kat, Mairelys, Ruth, Elvia, Amy
|-
| Notify recipients, waitlisted, non-recipients; ask recipients for confirmation, offer 1-1 meetings & conference buddy
| 12/1
|
| Tod, Chad
|-
| Recipients confirm participation, meeting interest, buddy system interest
| 12/5
|
| Elvia
|-
| Follow up with waitlisted applicants
| 12/5
|
| Amy
|-
| Announce awardees
| 12/12
|
| Elvia
|-
| Recruit conference buddies
| 12/12
| Can put in the same email as awardee announcement
| Elvia
|-
| Match awardees with conference buddies
| Dec/Jan
| Assume ongoing basis - some awardees may change their minds or people may volunteer late
| Todd, Elvia
|-
| Travel & housing planning
| week of 12/11
| A Very Informative Email
| Kat, Kate
|-
| Coordinate with CONCENTRA: awardee names & contact email
| Dec asap
| Rolling as confirmations come in
| Amy
|-
| ''Housing preference''
| ''Dec asap''
|
| ''Jenn @ CONCENTRA''
|-
| 1-on-1 meetings with awardees
| Dec/Jan
| Welcome, Q&A about anything
| Ruth, Kat, Todd
|-
| Coordinate with conference MC(s): scholarship winners recognition, name pronunciation
| 2/6-2/12
|
| Amy
|-
| Conference guide / social stuff email
| 1/29/18
|
| ALL
|-
| Conference!
|colspan="3"|2/13-2/16
|-
| Conference on-site contacts
| 2/12-2/16
|
| Todd, Amy
|-
| Pre-preconference meetup
| 2/12
|
| Amy, Mairelys, Kate
|-
| Group lunch
| 2/15
|
|
|-
| Lessons learned
| February 2018
|
| ALL
|-
| Post-conference feedback
| February 2018
| Create & send survey, review feedback
| Amy (survey & email), ALL (review feedback)
|-
| Documentation
| Spring 2018
| Share committee documents & participant feedback with other committees and/or post on wiki as appropriate
| Amy, Aisha
|-
|}

2018 Scholarship Documents/Contacting references

2018-06-05T14:38:11Z

AmyWickner: add link to all 2018 scholarship committee documents

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Top 12 Applicants ==

Dear [reference contact's name],

This email is in reference to [applicant’s name] application for a Diversity Scholarship to attend the 2018 Code4Lib Conference next February in Washington, D.C. (conference info: [https://2018.code4lib.org/ https://2018.code4lib.org/]). [applicant’s name] is one of our final candidates for a scholarship and has listed you as a professional reference.

Will you please share with us very briefly whether you would recommend [applicant’s name] for a scholarship and why? We would appreciate hearing from you anytime before 12 PM EST on Friday, December 1. Please feel free to email your response, or we would be happy to schedule a phone call.

If you have any questions, please let us know at code4libaward@gmail.com by replying to this email. Thank you very much in advance.

Sincerely,

[committee member's name]

on behalf of the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

== Waitlist ==

Dear [reference contact's name],

This email is in reference to [applicant’s name] application for a Diversity Scholarship to attend the 2018 Code4Lib Conference next February in Washington, D.C. (conference info: [https://2018.code4lib.org/ https://2018.code4lib.org/]). [applicant’s name] has been waitlisted for a scholarship and has listed you as a professional reference.

Will you please share with us very briefly whether you would recommend [applicant’s name] for a scholarship and why? We would appreciate hearing from you anytime before 12 PM EST on Friday, December 1. Please feel free to email your response, or we would be happy to schedule a phone call.

If you have any questions, please let us know at code4libaward@gmail.com by replying to this email. Thank you very much in advance.

Sincerely,

[committee member's name]

on behalf of the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

2018 Scholarship Documents/Applicant notifications

2018-06-05T14:33:52Z

AmyWickner: added Application Receipt Confirmation

2018 Scholarship Documents/Buddy system

2018-04-29T02:35:13Z

AmyWickner: description of conference buddy system for 2018 scholarship recipients

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

The 2018 Scholarship Committee recruited conference buddies for scholarship recipients as part of [[2018_Scholarship_Documents/Scholarship_announcement|announcing scholarship winners]]. Volunteers contacted the committee with some basic information:
* Name
* Contact information
* Professional background (one line)
* Relevant interests
* Any other notes on participating in the buddy system

The committee matched volunteers with awardees who expressed interest in the buddy program and connected them via email.

2018 Scholarship Documents/Post-conference feedback

2018-04-29T02:27:07Z

AmyWickner: post-conference feedback for the 2018 scholarship program

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

2018 scholarship recipients shared post-conference feedback with the Scholarship Committee via anonymous survey (questions are below). Additional feedback is available to members of the 2018 Local Planning Committee as well as future local planning and scholarship committees. After answering each question, survey takers indicated sharing permission for that set of comments: "Who may see feedback about [survey question]?" Please contact the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|2018 Scholarship Committee]] for more information.

== Application process ==
''Please tell us about your experience with the scholarship application process, including the call for applications, application form and requirements, and any other reflections and experiences.''
* "The application process was incredibly quick and painless. The hardest part was writing about why I thought I deserved the scholarship without allowing the impostor syndrome to kick in."
* "The application process seemed pretty straightforward. I could see how some students could find it difficult get a reference from a professor if they work full time in another field while going to school."

== Communication ==
''Please tell us about your experience communicating with the Scholarship Committee during the application processes, planning process, and conference.''
* "Communication was amazing, but at times overwhelming. The information dump lead me to missing some important aspects of the conference for scholarship winners - such as the buddy system."

== Buddy system ==
''If you participated in the conference buddy system, please tell us about your experience.''
* "I did not participate in the buddy system because I missed that in the scholarship emails."

== Conference logistics & travel planning ==
''Please tell us about your experience with travel planning and conference logistics, including working with Concentra, the Scholarship Committee, and any other resources.''
* "The only complaint I have about logistics, is that there was no obvious way to book a hotel room and have it charged to the scholarship fund. I ended up placing the reservation myself, and having the scholarship committee later add the reservation to the scholarship fund."

== Conference attendance ==
''Please tell us about your experience attending the conference.''
* "A++++ would do again in a heartbeat if given the opportunity."

== Additional feedback ==
''Please use this space to share anything else you'd like us to know.''

2018 Scholarship Documents/Disseminating the call

2018-04-29T01:45:30Z

AmyWickner: add link to list of all 2018 Scholarship Committee docs

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

The 2018 Scholarship Committee disseminated the call for applications to at least the following outlets/groups:
* CODE4LIB list
* Asian Pacific American Librarians Association (APALA)
* ALCTScentral (Association for Library Collections & Technical Services)
* We Here
* Black Caucus of the American Library Association
* REFORMA
* Bibliotecas para la Gente
* Joint Council of Librarians of Color
* American Indian Library Association
* Gay, Lesbian, Bisexual, Transgender Round Table of ALA
* ALA New Members Round Table
* Library Information Technology Association
* ALA Think Tank
* University of Illinois iSchool Alumni Connections
* St. John's University Division of Library & Information Science alumni group
* Library Leadership & Management Association (LLAMA) New Professional Section
* I Need A Library Job
* Association of College & Research Libraries (ACRL) College Libraries Section
* ALA Learning Roundtable
* California Libraries
* DIAL-CARL (Diversity In Academic Libraries - California Academic & Research Libraries)
* Library Employee Support Network
* Ethnic and Multicultural Information Exchange Round Table (EMIERT)
* University of Illinois iSchool Students of Color
* ACRL Residency Interest Group
* LLAMA Diversity Officers Discussion Group
* APALA mentoring channels
* LLAMA mentoring channels
* ALCTS mentoring program
* New York's Libraries Information Network (NYLINE)
* Digital Cultural Heritage DC Meetup
* DLF-ANNOUNCE (Digital Library Federation)
* DPLA Hubs (Digital Public Library of America)
* Roy Rosenzweig Center for History and New Media
* University of Maryland iSchool
* Society of American Archivists (SAA) Students and New Archivists Roundtable
* National Digital Stewardship Alliance
* SAA Archivists and Archives of Color Section
* Hear Me Code
* dh+lib
* ACRL Digital Humanities SIG
* Women Who Code DC
* Black Girls Code
* Maryland Institute for Technology in the Humanities
* Hack Library School
* University of Maryland Division of Student Affairs
* California Library Information eXchange
* California Academic Reference Librarians Discussion Interest Group - South

2018 Scholarship Documents/Disseminating the call

2018-04-29T01:44:06Z

AmyWickner: list of groups & outlets contacted to publicize the 2018 call for scholarship applications

The 2018 Scholarship Committee disseminated the call for applications to at least the following outlets/groups:
* CODE4LIB list
* Asian Pacific American Librarians Association (APALA)
* ALCTScentral (Association for Library Collections & Technical Services)
* We Here
* Black Caucus of the American Library Association
* REFORMA
* Bibliotecas para la Gente
* Joint Council of Librarians of Color
* American Indian Library Association
* Gay, Lesbian, Bisexual, Transgender Round Table of ALA
* ALA New Members Round Table
* Library Information Technology Association
* ALA Think Tank
* University of Illinois iSchool Alumni Connections
* St. John's University Division of Library & Information Science alumni group
* Library Leadership & Management Association (LLAMA) New Professional Section
* I Need A Library Job
* Association of College & Research Libraries (ACRL) College Libraries Section
* ALA Learning Roundtable
* California Libraries
* DIAL-CARL (Diversity In Academic Libraries - California Academic & Research Libraries)
* Library Employee Support Network
* Ethnic and Multicultural Information Exchange Round Table (EMIERT)
* University of Illinois iSchool Students of Color
* ACRL Residency Interest Group
* LLAMA Diversity Officers Discussion Group
* APALA mentoring channels
* LLAMA mentoring channels
* ALCTS mentoring program
* New York's Libraries Information Network (NYLINE)
* Digital Cultural Heritage DC Meetup
* DLF-ANNOUNCE (Digital Library Federation)
* DPLA Hubs (Digital Public Library of America)
* Roy Rosenzweig Center for History and New Media
* University of Maryland iSchool
* Society of American Archivists (SAA) Students and New Archivists Roundtable
* National Digital Stewardship Alliance
* SAA Archivists and Archives of Color Section
* Hear Me Code
* dh+lib
* ACRL Digital Humanities SIG
* Women Who Code DC
* Black Girls Code
* Maryland Institute for Technology in the Humanities
* Hack Library School
* University of Maryland Division of Student Affairs
* California Library Information eXchange
* California Academic Reference Librarians Discussion Interest Group - South

2018 Scholarship Documents/Lessons learned

2018-04-29T01:18:19Z

AmyWickner: 2018 Scholarship Committee lessons learned

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Writing & editing ==
* Match requirements to call language to criteria.
* Consider whether “merit” is demonstrable and can be evaluated, or if alternative language cuts closer to what's actually happening.
* Copy edit EVERYTHING. If a date changes in one place, make sure it's updated everywhere else. This includes copy going out to mailing lists, text in forms, website content, anything posted on the code4lib wiki. ctrl+F 2018, 2019, etc. Everyone can help copy edit, but the buck stops with the committee chair.
* Thank sponsors in basically everything that goes out. List them first.

== Document management ==
* Collect preferred email addresses for e.g. Google Drive before starting to share folders and docs.
* Make clear which versions of a given doc are active draft, inactive draft, finalized.
* Try not to duplicate work - confirm a document doesn't exist before starting a new one.
* Create and bequeath organized documents for the next year's committee! don't make them start from scratch.
* Make a disposal plan for documents with personal information that shouldn't be shared with next year's committee.

== Privacy & security ==
* Ask applicants for the minimum amount of information needed to make decisions.
* Manage document sharing along a similar principle: Share documents (especially those containing personal info) only with people/accounts that really need access, e.g. only committee members need to see applications.
* Find a secure way to share logins and passwords OR use a reflector.

== Timeline ==
* Get familiar with timeline dependencies as early as possible and make sure everyone in the committee is aware of them.
* Make sure the local planning committee and anyone else responsible for setting the master timeline are getting information about and accounting for any work plans we set as a committee -- otherwise will default to a previous year's schedule.
* Pushing back on LPC decisions is probably okay -- test out earlier rather than later whether this is true.

== Clear communication channels ==
* Communicate from official account as much as possible, if using. Use it to send out call for applications, notify applicants, announce recipients, call for buddies, etc.
* Be clear in advance who will monitor new/shared communication channels (Twitter, Slack channel, email account) & answer questions. Who’s responsible? Who has time to do this?
* Set regular times to check in with LPC about committee status. Don't assume LPC remembers that your committee exists.
* Don't assume people are on email, Twitter, Slack, whatever at the same time you are.
* Respect people's time (fellow committee members, scholarship applicants and recipients, conference coordinators, other Code4Lib committees) by providing enough time to reply if needed, sending reminders, and replying promptly if at all possible.
* If you don't know, ask.

== Task distribution ==
* Clearly identify all-hands tasks, 2-3-person tasks, and 1-person tasks.
* Committee work will always involve someone taking on more than they're able to do, both out of wanting to help and also changing work/life circumstances. Have a contingency plan for when someone responsible for a certain part of the committee charge inevitably gets sick or has a jam-packed month at work. Make it 100% okay to communicate this and ask for help, and agree on how the handoff will work. Identify primaries and backups for each task. Prepare to adjust if it seems like one person is everyone's backup or ends up carrying all of the weight.
* LPC are dealing with tons of responsibilities and many of them are first-timers to event organizing and/or code4lib. If something needs attention, be extremely explicit about that and give a timeframe.

2018 Scholarship Documents/Timeline and tasks

2018-04-29T01:11:28Z

AmyWickner: timeline (tasks & deadlines) for 2018 Scholarship Committee

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

The 2018 Scholarship Committee used this timeline to track tasks and deadlines. Committee members signed up for tasks based on interest and capacity.

{| class="wikitable"
|-
! Task / milestone
! Date(s)
! Notes
! Team
|-
| Call for committee volunteers
|
|
| ALL
|-
| Initial committee meetings
| 6/28, 7/19
|
| ALL as available
|-
| ''Call for individual donations to the Angel Fund''
|
| ''Sponsorship Comm aims to have funding confirmed by early October but there may be late additions''
| ''Sponsorship Committee''
|-
| Finalize number of scholarship recipient seats to hold for registration
| 9/15
| Settled on 15
| ALL - email discussion
|-
| Finalize call for applications & application format
| 10/16
|
| Anastasia, Aisha, Chad
|-
| Put out call for applications
| 10/16
| Includes identifying channels, communities, organizations to target
| Anastasia, Aisha, Kat
|-
| Reminder call
| 11/3
|
| Aisha, Kat
|-
| Create evaluation rubric
| 11/10
|
| Amy (draft), ALL (edits)
|-
| Application deadline
| 11/17
|
| Tod, Todd
|-
| Confirm application receipt
| 11/20
|
| Todd
|-
| Follow up about missing information
| 11/20
|
| Todd
|-
| Review & rate applications individually
| 11/18-11/28
| "Individually" as in each committee member
| ALL
|-
| Committee meeting to discuss applications, choose recipients
| 11/29 2:00 PM
|
| ALL - multiple meetings if needed or send written feedback
|-
| Request references
| 11/29
| Can be via email or Skype/phone
| Kat, Mairelys, Ruth, Elvia, Amy
|-
| ''Finalize number of available scholarships; notify LPC of registration spots to release''
| ''12/5''
|
| ''Budget & sponsorship committees''
|-
| Reference deadline
| 12/1 12:00 PM
|
| Kat, Mairelys, Ruth, Elvia, Amy
|-
| Notify recipients, waitlisted, non-recipients; ask recipients for confirmation, offer 1-1 meetings & conference buddy
| 12/1
|
| Tod, Chad
|-
| Recipients confirm participation, meeting interest, buddy system interest
| 12/5
|
| Elvia
|-
| Follow up with waitlisted applicants
| 12/5
|
| Amy
|-
| Announce awardees
| 12/12
|
| Elvia
|-
| Recruit conference buddies
| 12/12
| Can put in the same email as awardee announcement
| Elvia
|-
| Match awardees with conference buddies
| Dec/Jan
| Assume ongoing basis - some awardees may change their minds or people may volunteer late
| Todd, Elvia
|-
| Travel & housing planning
| week of 12/11
| A Very Informative Email
| Kat, Kate
|-
| * Coordinate with CONCENTRA: awardee names & contact email
| Dec asap
| Rolling as confirmations come in
| Amy
|-
| * ''Housing preference''
| ''Dec asap''
|
| ''Jenn @ CONCENTRA''
|-
| * 1-on-1 meetings with awardees
| Dec/Jan
| Welcome, Q&A about anything
| Ruth, Kat, Todd
|-
| Conference guide / social stuff email
| 1/29/18
|
| ALL
|-

| Conference!
|colspan="3"|2/13-2/16
|-
| * Conference on-site contacts
| 2/12-2/16
|
| Todd, Amy
|-
| * Pre-preconference meetup
| 2/12
|
| Amy, Mairelys, Kate
|-
| * Group lunch
| 2/15
|
|
|-
| Lessons learned
| February 2018
|
| ALL
|-
| Post-conference feedback
| February 2018
| Create & send survey, review feedback
| Amy (survey & email), ALL (review feedback)
|-
| Documentation
| Spring 2018
| Share committee documents & participant feedback with other committees and/or post on wiki as appropriate
| Amy, Aisha
|-
|}

2018 Scholarship Documents/Application evaluation rubric

2018-04-27T20:19:26Z

AmyWickner: 2018 scholarship evaluation process, scoring rubric, and sources good & bad

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Application components ==
[[2018_Scholarship_Documents/Application_form#Diversity_Scholarship_Eligibility.2C_Criteria.2C_and_Requirements|Eligibility criteria]]

[[2018_Scholarship_Documents/Application_form#How_to_Apply|Application components]]

== Evaluation process ==
10 of 13 members of the scholarship committee reviewed and rated applications according to the rubric below (20 possible points). A group of 11 met to review and discuss scores. We identified 12 top candidates based on highest average score, as well as a 5-person waitlist ranked by averaged application score.

== Evaluation rubric ==
{| class="wikitable"
|-
! Category
! 0
! 1
! 2
! 3
! 4
|-
| '''Eligibility''' 1 pt possible
| Under 18 and/or does not self-identify as a member of a group not well represented in the code4lib community.
| 18 and older AND self-identifies as member of a group not well represented in the code4lib community.
|-
| '''Financial need''' 2 pts possible
| Does not cite a financial need for this scholarship.
| Cites a financial need for this scholarship.
| Explains current personal circumstances that support a need for this scholarship, including but not limited to (and in no particular order): family responsibilities; full- or part-time student status; lack of employment; part-time work or other contingent employment; lack of employer-funded professional development; expenses or other circumstances that create a financial need.
|-
| '''Describe interest in and plans for participating in Code4Lib 2018''' 4 pts possible
| Does not express interest in participating in Code4Lib 2018
| Expresses interest in participating in Code4Lib 2018.
| Expresses interest in participating in Code4Lib 2018 and provides reasons for this interest. Discusses plans for participation in Code4Lib 2018.
| Expresses interest in participating in Code4Lib 2018 and discusses plans for participation. Links interest in Code4Lib 2018 to personal and/or professional goals, interests and/or activities. Links interest and plans to specific elements of Code4Lib 2018 (e.g. CodeOfConduct4Lib, pre-conference, lightning talks, range of session topics, childcare).
| Clearly, persuasively, and critically expresses interest in participating in Code4Lib 2018; describes plans for participation; links interest in Code4Lib 2018 to personal and/or professional goals, interests and/or activities; and links interest and plans to specific elements of Code4Lib 2018 (e.g. CodeOfConduct4Lib, pre-conference, lightning talks, range of session topics, childcare).
|-
| '''Describe anticipated benefits of participation in Code4Lib 2018''' 4 pts possible
| Does not discuss benefits of participating in Code4Lib 2018
| Discusses benefits of participating in Code4Lib 2018.
| Discusses benefits of participating in Code4Lib 2018 and links benefits to personal and/or professional goals, interests, and/or activities.
| Discusses benefits of participating in Code4Lib 2018 and links benefits to specific personal and/or professional goals, interests, and/or activities. Links benefits of participating to specific elements of Code4Lib 2018 (e.g. CodeOfConduct4Lib, pre-conference, lightning talks, range of session topics, childcare).
| Clearly persuasively, and critically discusses benefits of participating in Code4Lib 2018; links benefits to specific personal and/or professional goals, interests, and/or activities; and links benefits of participating to specific elements of Code4Lib 2018 (e.g. CodeOfConduct4Lib, pre-conference, lightning talks, range of session topics, childcare).
|-
| '''Describe interest in / plans for engaging with Code4Lib community''' 4 pts possible
| Does not express interest in participating in the general Code4Lib community OR discuss reservations about participating.
| Expresses interest in participating in the general Code4Lib community and/or discusses reservations about participating.
| Expresses interest in participating in the general Code4Lib community. Discusses plans for participating in the general Code4Lib community.
| Expresses interest in participating in the general Code4Lib community. Discusses plans for participating. Links interest in the general Code4Lib community to personal and/or professional goals, interests and/or activities. Links interest and plans to specific elements of the general Code4Lib community (e.g. CodeOfConduct4Lib, conferences, local meetups, journal, online community, wiki).
| Clearly, persuasively, and critically expresses interest in participating in the general Code4Lib community; describes plans for participation; links interest in the general Code4Lib community to personal and/or professional goals, interests and/or activities; and links interest and plans to specific elements of the general Code4Lib community (e.g. CodeOfConduct4Lib, conferences, local meetups, journal, online community, wiki).
|-
| '''Describe anticipated benefits of engaging with Code4Lib community''' 4 pts possible
| Does not discuss benefits of participating in the general Code4Lib community.
| Mentions anticipated benefits of participating in the general Code4Lib community.
| Discusses anticipated benefits of participating in the general Code4Lib community and links benefits to personal and/or professional goals, interests, and/or activities.
| Discusses anticipated benefits of participating in the general Code4Lib community and links benefits to specific personal and/or professional goals, interests, and/or activities. Links benefits of participating to specific elements of the general Code4Lib community (e.g. CodeOfConduct4Lib, conferences, local meetups, journal, online community, wiki).
| Clearly, persuasively, and critically discusses anticipated benefits of participating in the general Code4Lib community; links benefits to specific personal and/or professional goals, interests, and/or activities; and links benefits of participating to specific elements of the general Code4Lib community (e.g. CodeOfConduct4Lib, conferences, local meetups, journal, online community, wiki).
|-
| '''CodeOfConduct4Lib''' 1 pt possible
| Application material does not adhere to the CodeOfConduct4Lib
| Application material adheres to the CodeOfConduct4Lib
|}

== References & Sources ==
Annotated list of evaluation examples (helpful and unhelpful) that we consulted while designing the rubric above:

[https://www.northeastern.edu/universityscholars/wp-content/uploads/2015/01/Evaluation-rubric.pdf Northeastern University Scholars Independent Research Fellowship]
* [https://undergraduate.northeastern.edu/research/awards/summer-scholars-independent-research-fellowship/ Application guidelines]
* project- and output-focused
* emphasis on clarity & feasibility

[https://www.gips.org/assets/site/Foundation/images/Scholarships/CPI%20Scholarship%20Scoring%20Rubric.pdf Grand Island Public Schools Career  Pathways  Institute]
* evaluates applications for demonstration of financial need
* multiple opportunities for applications to build a case through personal experience

[https://studentlife.mst.edu/media/studentsupport/studentlife/documents/Scoring%20Rubric.pdf Donald D. Myers Scholarship Scoring Rubric (Missouri University of Science & Technology)]
* expresses values like quantitative over qualitative data, the importance of "passion"

[https://www.kdp.org/resources/pdf/scholarshipsandgrants/Scoringrubric.pdf Kappa Delta Pi 2016 Scholarship Review Rubric]
* asks evaluators to rate 1-5 without explaining criteria for each rating

[http://www.keegoharboroptimist.org/wp-content/uploads/2013/01/SCORING-RUBRIC-2013-2014.pdf Keego Harbor Optimist Scholarship Rubric]
* Gives overall definitions of 1-5 first, then lists areas for evaluation

[https://www.elks.org/SharedElksOrg/enf/images/EvaluatingBrochures.pdf Elks National Foundation Scholarship Judges Manual - Evaluating Applications] 🦌🦌🦌

[https://learningforward.org/docs/default-source/pdf/rubric-final.pdf Learning Forward Foundation Scholarships and Grants Scoring Rubric]
* separate section for application completeness
* each scoring categories addresses multiple criteria

[https://www.lrs.org/ripl-2016-scholarship-application-rubric/ Research Institute for Public Libraries Scholarship Application Rubric]
* in addition to rating answers to application questions, includes 3 overall categories for evaluating applications: written communication skills, commitment to learning about data, commitment to incorporating research and evaluation into workflow, "passion for making data sing"

[https://aauw-sd.aauw.net/files/2014/01/NCCWSL-Scholarship-Application-Scoring-Rubric.pdf Scoring Rubric – Student Application for State AAUW Funds to Attend National Conference for College Women Student Leaders (NCCWSL)]
* rewards specificity
* writing skills weighted equivalent to experience

[https://www.aauw.org/what-we-do/educational-funding-and-awards/selected-professions-fellowships/spf-application/ AAUW Selected Professions Fellowships Criteria for Selection and Application Review]
* gives percentages rather than point values for weighting criteria

[https://www.aauw.org/resource/cap-grant-application-instructions/ AAUW Campus Action Project Grant Instructions]
* public-facing list of selection criteria rather than a table/rubric structure

[http://www.ala.org/acrl/liaison-grant-funding-evaluation-rubric ACRL Liaison Grant Funding Evaluation Rubric]
* evaluation seems to address both grant application and project outcomes
* note at the bottom: ''If a proposal is scored “0” in any category or earns a total score of “0-5” the applicant will receive feedback from the Chair or Vice-Chair.''

[http://www.ala.org/acrl/immersion/characteristics ACRL Immersion Program Characteristics of Successful Applicants]
* rubrics for specific tracks (Teacher, Program, Intentional Teaching, Assessment, Teaching with Technology) no longer online
* [http://www.ala.org/acrl/conferences/immersion/scholarships current scholarships page] lists criteria rather than a rubric

[http://www.ala.org/aasl/awards/innovative American Association of School Librarians Innovative Reading Grant]
* [http://www.ala.org/aasl/sites/ala.org.aasl/files/content/aaslawards/docs/InnovativeReadingGrantRatingSheet.pdf Grant Rating Sheet]
* [http://www.ala.org/aasl/sites/ala.org.aasl/files/content/aaslawards/docs/InnovativeReadingGrantRubric.pdf Rating Rubric]
* space for comments in rating sheet

[http://www.nationalhumanservices.org/index.php?option=com_content&view=article&catid=19:site-content&id=98:rubrics National Organization for Human Services Rubrics for Awards, Scholarships, and Grants]
* [http://www.nationalhumanservices.org/assets/Rubrics/rubrics%20-%20howard%20harris%20professional%20developmen%20award.pdf Howard Harris Professional Development Award Rubric]
* [http://www.nationalhumanservices.org/assets/Rubrics/rubrics%20-%20research%20grant.pdf Research Grant]
* little explanation for what each rating means

2018 Scholarship Documents/Application form

2018-04-27T19:10:43Z

AmyWickner: Formatting changes

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Code4Lib 2018 Diversity Scholarships ==
As part of Code4lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups and achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our 2018 Diversity Scholarship program! The Code4Lib Scholarship Committee hopes to award 15 Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1200 for travel costs, lodging, and conference fees for selected applicants to attend the 2018 Code4Lib Conference in Los Angeles, CA. The deadline for applications is Friday, November 17, 2017 at 11:59 PM ET.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort, and giving us feedback on their experience.

Code4Lib conference 2018: http://2018.code4lib.org/

=== Diversity Scholarship Eligibility, Criteria, and Requirements ===

* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively contributing to the mission and goals of the Code4Lib Conference.
* The scholarship recipients will be selected based upon their merit and financial needs.

=== How to Apply ===

Complete the following form including:
* Your contact information
* Your brief letter of interest, no more than 500 words, which:
** Identifies your eligibility for a diversity scholarship
** Describes how you see yourself benefiting from and participating in Code4Lib2018 conference and the general Code4Lib community.
* Your current resume or CV
* Contact information for one reference that can speak to your professional goals and/or achievements

All documents in the application materials should be submitted as a single PDF file with file name LASTNAME-FIRSTNAME

For directions on creating a PDF File, see: [http://www.wikihow.com/Convert-a-Microsoft-Word-Document-to-PDF-Format http://www.wikihow.com/Convert-a-Microsoft-Word-Document-to-PDF-Format]

=== Application Form ===
''Required fields marked with *''

Name (Last Name, First Name)*

Preferred Pronouns

Preferred Email Address*

Upload together as 1 PDF file: Letter of interest (max 500 words) and current CV/resume*

Reference (Last Name, First Name)*

Reference Position and/or Title

Reference Email Address*

Reference Phone Number*

=== About Code4Lib Scholarship Notifications ===
The application deadline is Friday, November 17, 2017 at 11:59PM ET.

The scholarship committee will notify all applicants during the week of Monday, December 4, 2017 regardless of award results.

2018 Scholarship Documents/Logistics emails

2018-04-27T19:06:58Z

AmyWickner: add link to list of all 2018 Scholarship Committee docs

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Logistics Email 1 ==
Dear Code4Lib 2018 Scholarship Awardees,

We’re excited to have you attend the Code4Lib 2018 Conference as a scholarship awardee. This email covers two things: website bios/social media handles and travel logistics.

'''Website Bios/Social Media Handles'''

We will be putting the list of awardees on the Code4Lib 2018 website. If you would like, please feel free to submit a short, 2-sentence bio (your background, why you are interested in Code4Lib…) and/or your Twitter Handle to be included on the website. Both are optional! Also, if you are a member of Slack and would like to interact with the Code4Lib community there, please feel free to send us your Slack handle to be added to the group.

'''Travel Logistics'''

To facilitate your attendance, the Scholarship Committee is available to help with any travel logistics. Please let us know if you have any questions as you plan your travel. If you have expressed interest in a 1-1 meeting, members of the scholarship committee will be contacting you individually to schedule one.

'''Getting to Washington, D.C.'''

If you will be flying to Washington, D.C., we recommend flying into DCA (Reagan National) or BWI (Baltimore-Washington) as these airports have rail or subway connections to the District. If you are on the East Coast, you may find travel via Amtrak to Union Station easier. Greyhound, Megabus, and Bolt Bus also have stops in or near Union Station.

'''Getting around'''

There are numerous ways to get around DC and the surrounding metro area, including mass transit, commuter rail, taxis, Uber/Lyft, and bikeshare. Some resources you may want to refer to are:

'''''Mass Transit'''''
* The Omni Shoreham is a block away from the Woodley Park Metro station, on the Red Line. From here, visitors can access Dupont Circle, Gallery Place/Chinatown, Union Station, and other neighborhoods without a transfer. Transfer points at Metro Center and Gallery Place provide access to all other metro lines.
* To purchase a fare card in advance: [https://www.wmata.com/fares/smartrip/ https://www.wmata.com/fares/smartrip/]. A first time purchases of a SmarTrip card costs $10, and comes pre-loaded with $8. Paper fare cards are not accepted on Metro. Unlike some metro systems, WMATA prices are based on distance traveled. Rail fares also depend on the time of day with higher pricing during commuter hours. Bus fare is $2 for regular buses and $4.25 for express, using a SmarTrip card. Contact Kathleen Bell with any questions or to have a SmarTrip card purchased for you.
* Trip planning, Metro and bus route information can be found at [https://www.wmata.com/ https://www.wmata.com/].
* Some additional resources for trip planning and real-time updates on delays or arrivals are [https://dcmetrohero.com/ https://dcmetrohero.com/], [https://citymapper.com/dc|https://citymapper.com/dc], and [https://transitapp.com/|https://transitapp.com/].
* Two regional trains service Union Station and other points. MARC ([https://mta.maryland.gov/marc-train https://mta.maryland.gov/marc-train]) serves Maryland locations, including BWI and Baltimore. VRE ([https://www.vre.org/ https://www.vre.org/]) connects northern Virginia locations, including Manassas and Fredericksburg.

'''''Walking, Cycling, and Multimodal Transportation'''''
* DC is a pedestrian-friendly city, and the hotel is centrally located near nightlife, sightseeing attractions, museums, etc.
* Capital Bikeshare ([https://www.capitalbikeshare.com/ https://www.capitalbikeshare.com/]) is DC’s primary bikeshare system (visitors can buy a daily membership for unlimited 30 minute rentals). A bikeshare station is located within a block of the conference venue.
* District Mobility ([https://districtmobility.org/ https://districtmobility.org/]) is another resource with data about how DC residents get from point to point.

'''Conference logistics'''

The Code4Lib 2018 schedule is now live: [https://2018.code4lib.org/schedule/ https://2018.code4lib.org/schedule/]. The main conference takes place at the Omni Shoreham Hotel February 14-16. Breakfast and snack breaks are provided for all conference days, and lunch will be provided on Days 1 & 2. A reception is scheduled to follow Day 2. Information about these venues is available here: [https://2018.code4lib.org/general-info/venues/ https://2018.code4lib.org/general-info/venues/]

Preconference workshops ([https://2018.code4lib.org/workshops/ https://2018.code4lib.org/workshops/]) take place February 13 at the Omni Shoreham and venues across the city.
* If you register for a preconference at a DC Public Library (DCPL) branch, please use this page to get directions: [https://www.dclibrary.org/hours-locations https://www.dclibrary.org/hours-locations].
* For the preconference held at the Catholic University of America (CUA) Law School Building, you can find directions via Google Maps: [https://www.google.com/maps/place/Columbus+School+of+Law+The+Catholic+University+of+America/@38.9360427,-76.9990536,17z/ https://www.google.com/maps/place/Columbus+School+of+Law+The+Catholic+University+of+America/@38.9360427,-76.9990536,17z/]

Childcare and accessibility accommodations ([http://2018.code4lib.org/general-info/venues/#accommodations http://2018.code4lib.org/general-info/venues/#accommodations]) are available for all four days of the conference. The registration form asks for information about attendees’ needs in these areas, but please feel free to follow up anytime with changes or additional requests. More information will become available on the conference website closer to the event dates.

Finally, we invite you to look over the conference page on resources for conduct and safety: [https://2018.code4lib.org/conduct/ https://2018.code4lib.org/conduct/]. These include: CodeOfConduct4Lib, emergency resources, information about duty officers, and the conference photography policy.

Let us know if you have any questions, we know this is a lot of information to digest!

Congratulations!

== Logistics Email 2 ==
Dear Code4Lib 2018 Scholarship Awardees,

The conference is just two weeks away! We're following up with some information about reimbursement, as well as attending and navigating the conference.

'''Reimbursements'''

Jenn Cummings and Kathy Azevedo are your primary contacts for logistics and reimbursements. You can reach them by email at ''(email)'', and find them at the conference at the registration table. As a reminder, here's some information about reimbursements from their initial email in December:

''Original receipts are required for reimbursement, which will be handled on site during the conference. Please bring (or email this address) a copy of the attached form, completed, as well as those original receipts for things such a transportation, lodging and meals not provided by the conference to the event and you will be given a reimbursement check on-site.'' 
''[include attachment]''

'''Scholarship Committee contact information'''

If you have any questions for the Scholarship Committee while getting to or at the conference, you're welcome to contact Todd Stoffer ''(phone, email)'' and Amy Wickner ''(phone, email)''. We'll be at the conference most days and are happy to help with anything that comes up.

'''Code4Lib First-Timer's Guide'''

Lastly, we've pooled our collective experience to put together a [[2018_Scholarship_Documents/First-Timers_Guide_for_Scholarship_Awardees|conference guide for first-time attendees]]. We hope it'll make your Code4Lib 2018 experience a welcoming and interesting one.

As always, please get in touch with any questions or concerns. Thanks for reading, and we look forward to meeting you next month!

2018 Scholarship Documents/Logistics emails

2018-04-27T19:04:34Z

AmyWickner: text of advance logistics emails sent to 2018 Code4Lib scholarship recipients

== Logistics Email 1 ==
Dear Code4Lib 2018 Scholarship Awardees,

We’re excited to have you attend the Code4Lib 2018 Conference as a scholarship awardee. This email covers two things: website bios/social media handles and travel logistics.

'''Website Bios/Social Media Handles'''

We will be putting the list of awardees on the Code4Lib 2018 website. If you would like, please feel free to submit a short, 2-sentence bio (your background, why you are interested in Code4Lib…) and/or your Twitter Handle to be included on the website. Both are optional! Also, if you are a member of Slack and would like to interact with the Code4Lib community there, please feel free to send us your Slack handle to be added to the group.

'''Travel Logistics'''

To facilitate your attendance, the Scholarship Committee is available to help with any travel logistics. Please let us know if you have any questions as you plan your travel. If you have expressed interest in a 1-1 meeting, members of the scholarship committee will be contacting you individually to schedule one.

'''Getting to Washington, D.C.'''

If you will be flying to Washington, D.C., we recommend flying into DCA (Reagan National) or BWI (Baltimore-Washington) as these airports have rail or subway connections to the District. If you are on the East Coast, you may find travel via Amtrak to Union Station easier. Greyhound, Megabus, and Bolt Bus also have stops in or near Union Station.

'''Getting around'''

There are numerous ways to get around DC and the surrounding metro area, including mass transit, commuter rail, taxis, Uber/Lyft, and bikeshare. Some resources you may want to refer to are:

'''''Mass Transit'''''
* The Omni Shoreham is a block away from the Woodley Park Metro station, on the Red Line. From here, visitors can access Dupont Circle, Gallery Place/Chinatown, Union Station, and other neighborhoods without a transfer. Transfer points at Metro Center and Gallery Place provide access to all other metro lines.
* To purchase a fare card in advance: [https://www.wmata.com/fares/smartrip/ https://www.wmata.com/fares/smartrip/]. A first time purchases of a SmarTrip card costs $10, and comes pre-loaded with $8. Paper fare cards are not accepted on Metro. Unlike some metro systems, WMATA prices are based on distance traveled. Rail fares also depend on the time of day with higher pricing during commuter hours. Bus fare is $2 for regular buses and $4.25 for express, using a SmarTrip card. Contact Kathleen Bell with any questions or to have a SmarTrip card purchased for you.
* Trip planning, Metro and bus route information can be found at [https://www.wmata.com/ https://www.wmata.com/].
* Some additional resources for trip planning and real-time updates on delays or arrivals are [https://dcmetrohero.com/ https://dcmetrohero.com/], [https://citymapper.com/dc|https://citymapper.com/dc], and [https://transitapp.com/|https://transitapp.com/].
* Two regional trains service Union Station and other points. MARC ([https://mta.maryland.gov/marc-train https://mta.maryland.gov/marc-train]) serves Maryland locations, including BWI and Baltimore. VRE ([https://www.vre.org/ https://www.vre.org/]) connects northern Virginia locations, including Manassas and Fredericksburg.

'''''Walking, Cycling, and Multimodal Transportation'''''
* DC is a pedestrian-friendly city, and the hotel is centrally located near nightlife, sightseeing attractions, museums, etc.
* Capital Bikeshare ([https://www.capitalbikeshare.com/ https://www.capitalbikeshare.com/]) is DC’s primary bikeshare system (visitors can buy a daily membership for unlimited 30 minute rentals). A bikeshare station is located within a block of the conference venue.
* District Mobility ([https://districtmobility.org/ https://districtmobility.org/]) is another resource with data about how DC residents get from point to point.

'''Conference logistics'''

The Code4Lib 2018 schedule is now live: [https://2018.code4lib.org/schedule/ https://2018.code4lib.org/schedule/]. The main conference takes place at the Omni Shoreham Hotel February 14-16. Breakfast and snack breaks are provided for all conference days, and lunch will be provided on Days 1 & 2. A reception is scheduled to follow Day 2. Information about these venues is available here: [https://2018.code4lib.org/general-info/venues/ https://2018.code4lib.org/general-info/venues/]

Preconference workshops ([https://2018.code4lib.org/workshops/ https://2018.code4lib.org/workshops/]) take place February 13 at the Omni Shoreham and venues across the city.
* If you register for a preconference at a DC Public Library (DCPL) branch, please use this page to get directions: [https://www.dclibrary.org/hours-locations https://www.dclibrary.org/hours-locations].
* For the preconference held at the Catholic University of America (CUA) Law School Building, you can find directions via Google Maps: [https://www.google.com/maps/place/Columbus+School+of+Law+The+Catholic+University+of+America/@38.9360427,-76.9990536,17z/ https://www.google.com/maps/place/Columbus+School+of+Law+The+Catholic+University+of+America/@38.9360427,-76.9990536,17z/]

Childcare and accessibility accommodations ([http://2018.code4lib.org/general-info/venues/#accommodations http://2018.code4lib.org/general-info/venues/#accommodations]) are available for all four days of the conference. The registration form asks for information about attendees’ needs in these areas, but please feel free to follow up anytime with changes or additional requests. More information will become available on the conference website closer to the event dates.

Finally, we invite you to look over the conference page on resources for conduct and safety: [https://2018.code4lib.org/conduct/ https://2018.code4lib.org/conduct/]. These include: CodeOfConduct4Lib, emergency resources, information about duty officers, and the conference photography policy.

Let us know if you have any questions, we know this is a lot of information to digest!

Congratulations!

== Logistics Email 2 ==
Dear Code4Lib 2018 Scholarship Awardees,

The conference is just two weeks away! We're following up with some information about reimbursement, as well as attending and navigating the conference.

'''Reimbursements'''

Jenn Cummings and Kathy Azevedo are your primary contacts for logistics and reimbursements. You can reach them by email at ''(email)'', and find them at the conference at the registration table. As a reminder, here's some information about reimbursements from their initial email in December:

''Original receipts are required for reimbursement, which will be handled on site during the conference. Please bring (or email this address) a copy of the attached form, completed, as well as those original receipts for things such a transportation, lodging and meals not provided by the conference to the event and you will be given a reimbursement check on-site.'' 
''[include attachment]''

'''Scholarship Committee contact information'''

If you have any questions for the Scholarship Committee while getting to or at the conference, you're welcome to contact Todd Stoffer ''(phone, email)'' and Amy Wickner ''(phone, email)''. We'll be at the conference most days and are happy to help with anything that comes up.

'''Code4Lib First-Timer's Guide'''

Lastly, we've pooled our collective experience to put together a [[2018_Scholarship_Documents/First-Timers_Guide_for_Scholarship_Awardees|conference guide for first-time attendees]]. We hope it'll make your Code4Lib 2018 experience a welcoming and interesting one.

As always, please get in touch with any questions or concerns. Thanks for reading, and we look forward to meeting you next month!

2018 Scholarship Documents/Scholarship announcement

2018-04-27T18:51:03Z

AmyWickner: add link to list of all 2018 Scholarship Committee docs; update awardee name to honor previous request

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

The Code4Lib Scholarship Committee is pleased to announce the Code4Lib 2018 Conference Diversity Scholarship awardees. The scholarship provides up to $1500 per awardee to cover the costs of attending the 2018 Code4Lib conference in Washington, D.C., February 13-16, 2018.

These scholarships were made possible by generous donations from MIT Libraries, DuraSpace, The School of Information Sciences at the University of Illinois, Temple University Libraries, Smithsonian Libraries, The Ohio State University Libraries, Blacklight, and the Code4Lib community.

Many thanks to all of the donors who made these scholarships possible!

The committee received applications from 77 highly qualified candidates this year, and it was a humbling experience to select just thirteen recipients.

Congratulations to all Code4Lib scholarship recipients!

Nicola Andrews 
Carly Bogen 
Laura Chuang 
Yi Ding 
Lev Earle 
Crystal Felima 
Tiffany Henry 
Alyssa Loera 
Dominique Luster 
Sonoe Nakasone 
Gina Nortonsmith 
Mattie Schraeder 
Jessica Whu

The Scholarship Committee is also seeking several conference buddies for our scholarship recipients. To volunteer, please reply to code4libaward@gmail.com.

In general, a conference buddy’s goal is to help the scholarship recipient get the most out of the conference. The two of you can decide how best to do that. Some suggestions for volunteer buddies:

* attend a meet and greet for Diversity Scholarship awardees
* contact the scholarship recipient before the conference
* arrange to meet at least once near the beginning of the conference
* introduce your buddy around at the reception
* join your buddy at a Newcomers Dinner

Please don't feel like you have to be a multi-year veteran of Code4Lib to be a conference buddy. If you've attended at least one (or otherwise know the community), you can be a buddy!

The Code4Lib 2018 Scholarship Committee

Elvia Arroyo-Ramirez 
Kathleen Kim Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

2018 Scholarship Documents/Scholarship announcement

2018-04-27T18:47:41Z

AmyWickner: text of 2018 Code4Lib scholarship recipients announcement sent to c4l list and posted on conference website

The Code4Lib Scholarship Committee is pleased to announce the Code4Lib 2018 Conference Diversity Scholarship awardees. The scholarship provides up to $1500 per awardee to cover the costs of attending the 2018 Code4Lib conference in Washington, D.C., February 13-16, 2018.

These scholarships were made possible by generous donations from MIT Libraries, DuraSpace, The School of Information Sciences at the University of Illinois, Temple University Libraries, Smithsonian Libraries, The Ohio State University Libraries, Blacklight, and the Code4Lib community.

Many thanks to all of the donors who made these scholarships possible!

The committee received applications from 77 highly qualified candidates this year, and it was a humbling experience to select just thirteen recipients.

Congratulations to all Code4Lib scholarship recipients!

Nicola Andrews 
Carly Bogen 
Laura Chuang 
Yi Ding 
Lev Earle 
Crystal Felima 
Tiffany Henry 
Alyssa Loera 
Dominique Luster 
Sonoe Nakasone 
Gina Nortonsmith 
Mattie Schraeder-Urbanowicz 
Jessica Whu

The Scholarship Committee is also seeking several conference buddies for our scholarship recipients. To volunteer, please reply to code4libaward@gmail.com.

In general, a conference buddy’s goal is to help the scholarship recipient get the most out of the conference. The two of you can decide how best to do that. Some suggestions for volunteer buddies:

* attend a meet and greet for Diversity Scholarship awardees
* contact the scholarship recipient before the conference
* arrange to meet at least once near the beginning of the conference
* introduce your buddy around at the reception
* join your buddy at a Newcomers Dinner

Please don't feel like you have to be a multi-year veteran of Code4Lib to be a conference buddy. If you've attended at least one (or otherwise know the community), you can be a buddy!

The Code4Lib 2018 Scholarship Committee

Elvia Arroyo-Ramirez 
Kathleen Kim Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

2018 Scholarship Documents/Applicant notifications

2018-04-27T18:42:02Z

AmyWickner: text of award, no award, and waitlist notifications sent to 2018 Code4Lib scholarship applicants

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Award Notification ==
Dear [applicant's name],

Congratulations! We’re pleased to let you know that the Code4Lib Scholarship Committee has selected you to receive a scholarship to support your attendance at Code4Lib 2018 in Washington, D.C., February 13-16, 2018. These scholarships were made possible by donations from MIT Libraries, DuraSpace, The School of Information Sciences at the University of Illinois, Temple University Libraries, Smithsonian Libraries, The Ohio State University Libraries, and the Code4Lib community.

Please let us know as soon as possible whether you will be able to accept this award and attend the conference. We would very much appreciate a reply by '''Tuesday, December 5'''. Once you have confirmed, you will receive an email from CONCENTRA Conference Management Services inviting you to register for the conference and pre-conference sessions (February 13) at no cost. [https://2018.code4lib.org/general-info/attend Registration] opens on Wednesday, December 6, at 12pm EST, and spots are being held for scholarship recipients.

'''Logistics'''

Each scholarship award covers up to $1,500. Attending both the conference ($350) and the pre-conference day ($60) leaves $1,090 remaining to cover other expenses, including transportation, lodging, and any meals not provided by the conference. If your costs are less than the total award, you will only be reimbursed for the amount spent. If you choose not to register for the preconference day, the remainder would be $1,150. Original receipts are required for reimbursement, which will be handled on site during the conference.

If you choose to stay in the [https://2018.code4lib.org/general-info/venues/ Omni Shoreham Hotel] (official conference venue), CONCENTRA will handle your hotel reservation and the Local Planning Committee will arrange to pay the cost ($182/night) directly; you won’t need to wait for reimbursement for those funds. If you choose other lodgings, you will need to submit your receipts for reimbursement after the conference.

The Scholarship Committee is available to help with travel planning. We’ll follow up with more information about traveling to and attending the conference, once you've confirmed acceptance.

'''One-on-one meetings & buddy system'''

Members of the Scholarship Committee will be available to meet one-on-one to answer any questions you might have about attending Code4Lib. Please let us know if you'd be interested in such a meeting and one of us will follow up to set up a time.

Additionally, members of the Code4Lib community are available to act as conference buddies. This can be a great resource, especially for newcomers. Please let us know if you're interested in being matched with a buddy.

We look forward to seeing you in Washington, D.C., in February. If you will be unable to attend the conference, or choose to decline the scholarship, please let us know as soon as possible.

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

== No Award Notification ==
Dear [applicant's name],

Thank you very much for submitting your Code4Lib 2018 Diversity Scholarship application. The Scholarship Committee received 77 impressive applications for a limited number of scholarships. Unfortunately, your application was not one of those selected for a scholarship for Code4Lib 2018. Thank you again for your time, energy, and interest in Code4Lib. We encourage you to apply again next year.

We would also like to highlight opportunities to follow and participate in Code4Lib 2018 remotely. These include a [https://www.youtube.com/user/code4lib/ livestream of all sessions on YouTube]; via [https://twitter.com/search?q=%23c4l18 #c4l18] on Twitter; and on Slack at [https://code4lib.slack.com https://code4lib.slack.com]. Again, we encourage you to both apply for a scholarship next year and participate in Code4Lib online. Please let us know if you have any questions or comments.

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

== Waitlist Notification ==
Dear [applicant's name],

Thank you very much for submitting your Code4Lib 2018 Diversity Scholarship application. The Scholarship Committee received 77 impressive applications for a limited number of scholarships, and your application has been waitlisted for Code4Lib 2018. We will notify you by Tuesday, December 5, if a spot opens or additional funding becomes available. If you are no longer interested in receiving a diversity scholarship, please let us know as soon as possible.

Thank you again for your time, energy, and interest in Code4Lib, and for your patience during the application process. In the meantime, please let us know if you have any questions or comments,

Sincerely,

[[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

Elvia Arroyo-Ramirez 
Kathleen Bell 
Anastasia Chiu 
Aisha Conner-Gaten 
Kate Dohe 
Brooke Johnson 
Mairelys Lemus-Rojas 
Chad Nelson 
Tod Olson 
Marco Seiferle-Valencia 
Todd Stoffer 
Ruth Kitchin Tillman 
Amy Wickner

2018 Scholarship Documents/Contacting references

2018-04-27T18:15:36Z

AmyWickner: text of reference requests sent to contacts given by top 12 and waitlisted 2018 Code4Lib scholarship applicants

== Top 12 Applicants ==

Dear [reference contact's name],

This email is in reference to [applicant’s name] application for a Diversity Scholarship to attend the 2018 Code4Lib Conference next February in Washington, D.C. (conference info: [https://2018.code4lib.org/ https://2018.code4lib.org/]). [applicant’s name] is one of our final candidates for a scholarship and has listed you as a professional reference.

Will you please share with us very briefly whether you would recommend [applicant’s name] for a scholarship and why? We would appreciate hearing from you anytime before 12 PM EST on Friday, December 1. Please feel free to email your response, or we would be happy to schedule a phone call.

If you have any questions, please let us know at code4libaward@gmail.com by replying to this email. Thank you very much in advance.

Sincerely,

[committee member's name]

on behalf of the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

== Waitlist ==

Dear [reference contact's name],

This email is in reference to [applicant’s name] application for a Diversity Scholarship to attend the 2018 Code4Lib Conference next February in Washington, D.C. (conference info: [https://2018.code4lib.org/ https://2018.code4lib.org/]). [applicant’s name] has been waitlisted for a scholarship and has listed you as a professional reference.

Will you please share with us very briefly whether you would recommend [applicant’s name] for a scholarship and why? We would appreciate hearing from you anytime before 12 PM EST on Friday, December 1. Please feel free to email your response, or we would be happy to schedule a phone call.

If you have any questions, please let us know at code4libaward@gmail.com by replying to this email. Thank you very much in advance.

Sincerely,

[committee member's name]

on behalf of the [[Code4Lib_2018_Conference_Committees#Scholarship_Committee|Code4Lib 2018 Scholarship Committee]]

2018 Scholarship Documents/First-Timers Guide for Scholarship Awardees

2018-04-27T18:09:45Z

AmyWickner: add link to list of all 2018 Scholarship Committee docs

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

Welcome to your first Code4Lib Conference! This guide aims to help you get the most out of your conference experience! If there is anything else you wonder about that isn’t in the guide, please let us know: code4libaward@gmail.com

== What to bring ==
'''Comfortable shoes.''' Conference rooms are clustered together in the hotel but there may be significant walking involved in getting lunch or dinner, taking public transportation, etc.

'''Layers.''' The conference hotel tends to be quite warm, while D.C. is very cold in February. Bring layers to be comfortable during travel and conference sessions, and while exploring the hotel and neighborhood.

'''Tote or backpack.''' Code4Lib is not a swag-heavy event, but a name tag, lanyard, and t-shirt are included with registration. Bringing a bag will help accommodate these items, as well as any free stickers etc. picked up along the way.

'''Chargers and travel outlet.''' Outlets in the hotel and session rooms may be limited, and most attendees will be using mobile devices of some kind. Consider bringing a small travel outlet or power strip if you need to charge multiple devices at once.

'''Snacks and a water bottle.''' Lunch is provided; breakfast and dinner are not. We mistakenly indicated in a previous email that breakfast would be provided. Conference organizers provide food and beverages during breaks, and make an effort to accommodate a range of dietary needs and preferences. However, you may also wish to bring or pick up additional snacks from a nearby grocery store to help sustain energy throughout the day. The conference hotel is very warm; a water bottle will help offset any dehydration.

'''Travel mug.''' Coffee, tea, and hot water are available during conference breaks. Bring a travel mug if you’d like to bring beverages into the main session and breakout rooms, and want to avoid using paper cups.

== At the conference ==
'''Conference venue.''' Here's a floor plan of the Omni Shoreham Hotel (main venue): https://www.omnihotels.com/-/media/images/hotels/wassho/meetings/floorplans/washington-dc-shoreham-spec-floor-plans.pdf Locations and specific rooms for preconference sessions will be linked from the Preconference Workshops page shortly: [https://2018.code4lib.org/workshops/ https://2018.code4lib.org/workshops/]

'''Registration.''' Upon entering the Omni Shoreham Hotel, follow signs to the Code4Lib registration table. You’ll receive a name tag and conference t-shirt (if requested during registration) and your choice of lanyard. Lanyard color indicates whether other conference-goers and organizers have permission to take your photo: red means '''''no''''', yellow means '''''ask permission''''', and green means '''''yes'''''.

'''Conference format.''' Code4Lib is a single-track conference, which means that all attendees occupy the same room for the keynote addresses and presentations. When choosing a seat, consider which locations will allow you to see the screen(s), be in or out of range of livestream cameras as desired, move in and out of the room as needed, and otherwise be comfortable.

'''Q&A.''' Time for questions and answers is available at the end of each keynote or presentation “group,” rather than between presentations. Runners will come to you with a microphone if you raise your hand to ask a question - please use the mic! Conference organizers will also monitor the code4lib Slack channel, IRC, and #c4l18 hashtag on Twitter for questions that they will then relay to speakers.

'''Lightning talks & breakout sessions.''' If interested, you’ll have a chance to sign up to give a lightning talk on each day of the conference, and/or to facilitate breakout sessions on Days 1 and 2. Lightning talks are 5-minute presentations and breakout sessions are 55-minute group discussions and/or workshops, both on topics of your choice. The conference MC will announce when sign-up sheets are available adjacent to the main conference room. See examples of lightning talk topics from the 2016 conference here: [https://wiki.code4lib.org/2016_Lightning_Talks https://wiki.code4lib.org/2016_Lightning_Talks]

'''Poster session.''' In addition to presentations and breakouts, an interactive poster session will take place in the foyer of the Regency Ballroom on Day 2 (3-3:35pm).

'''Scheduling your day.''' Code4Lib offers 3-4 full days of activity, including post-conference social events. 5- and 15-minute breaks are built in throughout the schedule, but it’s completely okay to step out of or skip sessions if you need a longer break. The hotel is located in a walkable neighborhood, and you can also take advantage of quiet rooms ([https://2018.code4lib.org/general-info/accessibility#quietroom https://2018.code4lib.org/general-info/accessibility#quietroom]) and other spaces throughout the hotel.

'''Buddy program.''' If you’re participating in the buddy program, your buddy is a great resource for navigating the conference, including answering questions about session topics and meeting presenters and others in the Code4Lib community. Feel free to check in with your buddy if you have a question, moment to think, or a helpful suggestion!

'''Locals.''' Conference attendees who live in or know the D.C. area and are willing to help with directions and recommendations will have white LOCAL ribbons attached to their name tags.

'''Volunteers and volunteering.''' Code4Lib is an entirely volunteer-run organization and event, so many of the people you interact with at the conference will be working in that capacity, including some first-timers. There may be hiccups, but we do our best to answer questions and support conference participants’ needs, and are open to feedback. And, if you have any interest in going behind the scenes, the Onsite Volunteer Committee is currently recruiting folks to help with small tasks throughout the conference week. See this page for more information about onsite volunteers and volunteering: [https://wiki.code4lib.org/2018_Conference_Volunteers https://wiki.code4lib.org/2018_Conference_Volunteers]

'''Accessibility.''' If you need assistance at any point in the Omni Shoreham Hotel, please contact a duty officer ([https://2018.code4lib.org/conduct/#officers https://2018.code4lib.org/conduct/#officers]) or inquire at the conference registration table. Additional support will be available at DC Public Library branches during preconference sessions, and via Capitol police and Library of Congress staff during the reception. We'll add details here as they become available. You can reach the Accessibility Committee with any questions at code4lib.accessibility@gmail.com. The Department of Justice toll-free ADA Information Line provides information and materials to the public about the requirements of the ADA: [https://www.ada.gov/infoline.htm https://www.ada.gov/infoline.htm]

'''Conduct and safety.''' Become familiar with the guidelines and resources listed on this page: [https://2018.code4lib.org/conduct/ https://2018.code4lib.org/conduct/] They include: the community code of conduct, emergency resources, photography policy, and how to contact Duty Officers. These volunteers are available to provide support for anyone who has been harassed, threatened, abused, or feels the CodeOfConduct4Lib has been violated during the conference.

== Group activities (all optional) ==
'''Orientation.''' Members of the Scholarship Committee will be in the lobby of the Omni Shoreham Hotel for a brief meet-up on Monday, February 12, at 8pm. Come say hi! We’re excited to meet you and will be happy to answer any last-minute questions.

'''Newcomer dinner.''' The Newcomer Dinners are group dinners of up to six people, geared for Code4Lib rookies and (slightly) more veteran members of the community to meet one another. They are scheduled for Tuesday, February 13 (pre-conference day). See this page for more information and to sign up in advance: [https://2018.code4lib.org/general-info/venues/#dinner https://2018.code4lib.org/general-info/venues/#dinner]

'''Scholarship recipients acknowledgement.''' The conference MC will read out the names of scholarship awardees during afternoon announcements on Day 1 of the conference (Wednesday, February 14), to thundering applause. Please stand and be recognized if you’re comfortable doing so!

'''Group lunch.''' Scholarship awardees, buddies, and members of the Scholarship Committee are all invited to get together at lunch on Day 2 of the conference (Thursday, February 15). We’ll meet outside the main conference room at noon to walk over. Consider it a chance to check in about how the conference is going so far, and reflect on the week.

'''Social activities.''' The Social Activities Committee has posted a number of social activities on this page: [https://wiki.code4lib.org/2018_Social_Activities https://wiki.code4lib.org/2018_Social_Activities] They take place throughout the conference week at venues across D.C. Public transit, rideshare, or cabs are required to travel to and from these venues.

2018 Scholarship Documents/First-Timers Guide for Scholarship Awardees

2018-04-27T18:07:44Z

AmyWickner: text of Code4Lib First-Timers' Guide shared with scholarship recipients

Welcome to your first Code4Lib Conference! This guide aims to help you get the most out of your conference experience! If there is anything else you wonder about that isn’t in the guide, please let us know: code4libaward@gmail.com

== What to bring ==
'''Comfortable shoes.''' Conference rooms are clustered together in the hotel but there may be significant walking involved in getting lunch or dinner, taking public transportation, etc.

'''Layers.''' The conference hotel tends to be quite warm, while D.C. is very cold in February. Bring layers to be comfortable during travel and conference sessions, and while exploring the hotel and neighborhood.

'''Tote or backpack.''' Code4Lib is not a swag-heavy event, but a name tag, lanyard, and t-shirt are included with registration. Bringing a bag will help accommodate these items, as well as any free stickers etc. picked up along the way.

'''Chargers and travel outlet.''' Outlets in the hotel and session rooms may be limited, and most attendees will be using mobile devices of some kind. Consider bringing a small travel outlet or power strip if you need to charge multiple devices at once.

'''Snacks and a water bottle.''' Lunch is provided; breakfast and dinner are not. We mistakenly indicated in a previous email that breakfast would be provided. Conference organizers provide food and beverages during breaks, and make an effort to accommodate a range of dietary needs and preferences. However, you may also wish to bring or pick up additional snacks from a nearby grocery store to help sustain energy throughout the day. The conference hotel is very warm; a water bottle will help offset any dehydration.

'''Travel mug.''' Coffee, tea, and hot water are available during conference breaks. Bring a travel mug if you’d like to bring beverages into the main session and breakout rooms, and want to avoid using paper cups.

== At the conference ==
'''Conference venue.''' Here's a floor plan of the Omni Shoreham Hotel (main venue): https://www.omnihotels.com/-/media/images/hotels/wassho/meetings/floorplans/washington-dc-shoreham-spec-floor-plans.pdf Locations and specific rooms for preconference sessions will be linked from the Preconference Workshops page shortly: [https://2018.code4lib.org/workshops/ https://2018.code4lib.org/workshops/]

'''Registration.''' Upon entering the Omni Shoreham Hotel, follow signs to the Code4Lib registration table. You’ll receive a name tag and conference t-shirt (if requested during registration) and your choice of lanyard. Lanyard color indicates whether other conference-goers and organizers have permission to take your photo: red means '''''no''''', yellow means '''''ask permission''''', and green means '''''yes'''''.

'''Conference format.''' Code4Lib is a single-track conference, which means that all attendees occupy the same room for the keynote addresses and presentations. When choosing a seat, consider which locations will allow you to see the screen(s), be in or out of range of livestream cameras as desired, move in and out of the room as needed, and otherwise be comfortable.

'''Q&A.''' Time for questions and answers is available at the end of each keynote or presentation “group,” rather than between presentations. Runners will come to you with a microphone if you raise your hand to ask a question - please use the mic! Conference organizers will also monitor the code4lib Slack channel, IRC, and #c4l18 hashtag on Twitter for questions that they will then relay to speakers.

'''Lightning talks & breakout sessions.''' If interested, you’ll have a chance to sign up to give a lightning talk on each day of the conference, and/or to facilitate breakout sessions on Days 1 and 2. Lightning talks are 5-minute presentations and breakout sessions are 55-minute group discussions and/or workshops, both on topics of your choice. The conference MC will announce when sign-up sheets are available adjacent to the main conference room. See examples of lightning talk topics from the 2016 conference here: [https://wiki.code4lib.org/2016_Lightning_Talks https://wiki.code4lib.org/2016_Lightning_Talks]

'''Poster session.''' In addition to presentations and breakouts, an interactive poster session will take place in the foyer of the Regency Ballroom on Day 2 (3-3:35pm).

'''Scheduling your day.''' Code4Lib offers 3-4 full days of activity, including post-conference social events. 5- and 15-minute breaks are built in throughout the schedule, but it’s completely okay to step out of or skip sessions if you need a longer break. The hotel is located in a walkable neighborhood, and you can also take advantage of quiet rooms ([https://2018.code4lib.org/general-info/accessibility#quietroom https://2018.code4lib.org/general-info/accessibility#quietroom]) and other spaces throughout the hotel.

'''Buddy program.''' If you’re participating in the buddy program, your buddy is a great resource for navigating the conference, including answering questions about session topics and meeting presenters and others in the Code4Lib community. Feel free to check in with your buddy if you have a question, moment to think, or a helpful suggestion!

'''Locals.''' Conference attendees who live in or know the D.C. area and are willing to help with directions and recommendations will have white LOCAL ribbons attached to their name tags.

'''Volunteers and volunteering.''' Code4Lib is an entirely volunteer-run organization and event, so many of the people you interact with at the conference will be working in that capacity, including some first-timers. There may be hiccups, but we do our best to answer questions and support conference participants’ needs, and are open to feedback. And, if you have any interest in going behind the scenes, the Onsite Volunteer Committee is currently recruiting folks to help with small tasks throughout the conference week. See this page for more information about onsite volunteers and volunteering: [https://wiki.code4lib.org/2018_Conference_Volunteers https://wiki.code4lib.org/2018_Conference_Volunteers]

'''Accessibility.''' If you need assistance at any point in the Omni Shoreham Hotel, please contact a duty officer ([https://2018.code4lib.org/conduct/#officers https://2018.code4lib.org/conduct/#officers]) or inquire at the conference registration table. Additional support will be available at DC Public Library branches during preconference sessions, and via Capitol police and Library of Congress staff during the reception. We'll add details here as they become available. You can reach the Accessibility Committee with any questions at code4lib.accessibility@gmail.com. The Department of Justice toll-free ADA Information Line provides information and materials to the public about the requirements of the ADA: [https://www.ada.gov/infoline.htm https://www.ada.gov/infoline.htm]

'''Conduct and safety.''' Become familiar with the guidelines and resources listed on this page: [https://2018.code4lib.org/conduct/ https://2018.code4lib.org/conduct/] They include: the community code of conduct, emergency resources, photography policy, and how to contact Duty Officers. These volunteers are available to provide support for anyone who has been harassed, threatened, abused, or feels the CodeOfConduct4Lib has been violated during the conference.

== Group activities (all optional) ==
'''Orientation.''' Members of the Scholarship Committee will be in the lobby of the Omni Shoreham Hotel for a brief meet-up on Monday, February 12, at 8pm. Come say hi! We’re excited to meet you and will be happy to answer any last-minute questions.

'''Newcomer dinner.''' The Newcomer Dinners are group dinners of up to six people, geared for Code4Lib rookies and (slightly) more veteran members of the community to meet one another. They are scheduled for Tuesday, February 13 (pre-conference day). See this page for more information and to sign up in advance: [https://2018.code4lib.org/general-info/venues/#dinner https://2018.code4lib.org/general-info/venues/#dinner]

'''Scholarship recipients acknowledgement.''' The conference MC will read out the names of scholarship awardees during afternoon announcements on Day 1 of the conference (Wednesday, February 14), to thundering applause. Please stand and be recognized if you’re comfortable doing so!

'''Group lunch.''' Scholarship awardees, buddies, and members of the Scholarship Committee are all invited to get together at lunch on Day 2 of the conference (Thursday, February 15). We’ll meet outside the main conference room at noon to walk over. Consider it a chance to check in about how the conference is going so far, and reflect on the week.

'''Social activities.''' The Social Activities Committee has posted a number of social activities on this page: [https://wiki.code4lib.org/2018_Social_Activities https://wiki.code4lib.org/2018_Social_Activities] They take place throughout the conference week at venues across D.C. Public transit, rideshare, or cabs are required to travel to and from these venues.

2018 Scholarship Documents

2018-04-27T17:47:48Z

AmyWickner: fix wiki links

The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Committee re: funding available for awards. The committee connects scholarship winners with conference coordinators to plan travel and arrangements, and provides additional informational support leading up to and at the conference.

[[2018_Scholarship_Documents/Timeline and tasks|Timeline and tasks]]

[[2018_Scholarship_Documents/Call_for_applications|Call for applications]]

[[2018_Scholarship_Documents/Disseminating_the_call|Disseminating the call]]

[[2018_Scholarship_Documents/Application_form|Application form]]

[[2018_Scholarship_Documents/Application_evaluation_rubric|Application evaluation rubric]]

[[2018_Scholarship_Documents/Contacting_references|Contacting references]]

[[2018_Scholarship_Documents/Applicant_notifications|Applicant notifications]]

[[2018_Scholarship_Documents/Scholarship_announcement|Scholarship announcement]]

[[2018_Scholarship_Documents/Logistics_emails|Logistics emails]]

[[2018_Scholarship_Documents/Buddy_system|Buddy system]]

[[2018_Scholarship_Documents/First-Timers_Guide_for_Scholarship_Awardees|First-Timers' Guide for Scholarship Awardees]]

[[2018_Scholarship_Documents/Post-conference_feedback|Post-conference feedback]]

[[2018_Scholarship_Documents/Lessons_learned|Lessons learned]]

2018 Scholarship Documents/Application form

2018-04-27T04:27:42Z

AmyWickner: text of Code4Lib 2018 scholarship application form

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Code4Lib 2018 Diversity Scholarships ==
=== Description ===
As part of Code4lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups and achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our 2018 Diversity Scholarship program! The Code4Lib Scholarship Committee hopes to award 15 Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1200 for travel costs, lodging, and conference fees for selected applicants to attend the 2018 Code4Lib Conference in Los Angeles, CA. The deadline for applications is Friday, November 17, 2017 at 11:59 PM ET.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort, and giving us feedback on their experience.

Code4Lib conference 2018: http://2018.code4lib.org/

'''Diversity Scholarship Eligibility, Criteria, And Requirements'''

* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively contributing to the mission and goals of the Code4Lib Conference.
* The scholarship recipients will be selected based upon their merit and financial needs.

'''How to Apply'''

Complete the following form including:
* Your contact information
* Your brief letter of interest, no more than 500 words, which:
** Identifies your eligibility for a diversity scholarship
** Describes how you see yourself benefiting from and participating in Code4Lib2018 conference and the general Code4Lib community.
* Your current resume or CV
* Contact information for one reference that can speak to your professional goals and/or achievements

All documents in the application materials should be submitted as a single PDF file with file name LASTNAME-FIRSTNAME

For directions on creating a PDF File, see: [http://www.wikihow.com/Convert-a-Microsoft-Word-Document-to-PDF-Format http://www.wikihow.com/Convert-a-Microsoft-Word-Document-to-PDF-Format]

=== Application Form ===
''Required fields marked with *''

Name (Last Name, First Name)*

Preferred Pronouns

Preferred Email Address*

Upload together as 1 PDF file: Letter of interest (max 500 words) and current CV/resume*

Reference (Last Name, First Name)*

Reference Position and/or Title

Reference Email Address*

Reference Phone Number*

=== About Code4Lib Scholarship Notifications ===
The application deadline is Friday, November 17, 2017 at 11:59PM ET.

The scholarship committee will notify all applicants during the week of Monday, December 4, 2017 regardless of award results.

2018 Scholarship Documents/Call for applications

2018-04-27T04:17:48Z

AmyWickner: add link to page with all 2018 scholarship docs

[[2018_Scholarship_Documents|2018 Scholarship Committee Documents]]

== Code4Lib 2018 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* MIT Libraries (2 scholarships)
* Duraspace (1 scholarship)
* The School of Information Sciences at the University of Illinois (1 scholarship)
* Temple University Libraries (2 scholarships)
* Smithsonian Libraries (1 scholarship)
* The Ohio State University Libraries (2 scholarships)
* [https://2018.code4lib.org/general-info/angel-fund Diversity Scholarships Angel Fund] (1 scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2018.code4lib.org/general-info/scholarships 2018 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award 15 Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2018 Code4Lib Conference in Washington, D.C.. The deadline for applications is November 17, 2017 at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2018: [https://2018.code4lib.org https://2018.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2018.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/Re2sJwXPjgi2mi2F2

You will need to prepare:
# Your brief letter of interest, no more than 500 words, which:
## Identifies your eligibility for a diversity scholarship
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community
# Your current resume or CV
# Contact information for one reference who can speak to your professional goals and/or achievements

Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.

The application deadline is '''Friday, November 17, 2017 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by Friday, December 1, 2017, regardless of award results.

2018 Scholarship Documents

2018-04-27T04:15:45Z

AmyWickner: Nesting pages under 2018_Scholarship_Documents/

The Code4Lib Scholarship Committee solicits submissions and selects winners of the scholarship(s), in close communication with the Sponsorship Committee re: funding available for awards. The committee connects scholarship winners with conference coordinators to plan travel and arrangements, and provides additional informational support leading up to and at the conference.

[[2018_Scholarship_Documents/Timeline and tasks|Timeline and tasks]]

[[2018_Scholarship_Documents/Call for applications|Call for applications]]

[[2018_Scholarship_Documents/Disseminating the call|Disseminating the call]]

[[2018_Scholarship_Documents/Application form|Application form]]

[[2018_Scholarship_Documents/Application evaluation rubric|Application evaluation rubric]]

[[2018_Scholarship_Documents/Contacting references|Contacting references]]

[[2018_Scholarship_Documents/Applicant notifications|Applicant notifications]]

[[2018_Scholarship_Documents/Scholarship announcement|Scholarship announcement]]

[[2018_Scholarship_Documents/Logistics emails|Logistics emails]]

[[2018_Scholarship_Documents/Buddy system|Buddy system]]

[[2018_Scholarship_Documents/First-Timers' Guide for Scholarship Awardees|First-Timers' Guide for Scholarship Awardees]]

[[2018_Scholarship_Documents/Post-conference feedback|Post-conference feedback]]

[[2018_Scholarship_Documents/Lessons learned|Lessons learned]]

Call for applications

2018-04-27T04:13:14Z

AmyWickner: AmyWickner moved page Call for applications to 2018 Scholarship Documents/Call for applications: Should have nested this page under 2018_Scholarship_Documents/ from the start

#REDIRECT [[2018 Scholarship Documents/Call for applications]]

2018 Scholarship Documents/Call for applications

2018-04-27T04:13:13Z

AmyWickner: AmyWickner moved page Call for applications to 2018 Scholarship Documents/Call for applications: Should have nested this page under 2018_Scholarship_Documents/ from the start

== Code4Lib 2018 Diversity Scholarships ==
We would like to thank our sponsors for supporting the Code4Lib 2018 Diversity Scholarships. Currently, 10 scholarships are fully funded.

* MIT Libraries (2 scholarships)
* Duraspace (1 scholarship)
* The School of Information Sciences at the University of Illinois (1 scholarship)
* Temple University Libraries (2 scholarships)
* Smithsonian Libraries (1 scholarship)
* The Ohio State University Libraries (2 scholarships)
* [https://2018.code4lib.org/general-info/angel-fund Diversity Scholarships Angel Fund] (1 scholarship)

As part of Code4Lib's ongoing commitment to reducing economic barriers that prevent participation for underrepresented groups, and to achieving a balanced representation of the human experience, we are pleased to announce that we are now seeking applicants for our [https://2018.code4lib.org/general-info/scholarships 2018 Diversity Scholarship program!] The Code4Lib Scholarship Committee hopes to award 15 Diversity Scholarships, based on merit and need. Each scholarship will cover up to $1,500 for travel costs, lodging, and conference fees for selected applicants to attend the 2018 Code4Lib Conference in Washington, D.C.. The deadline for applications is November 17, 2017 at 11:59 PM ET.

The scholarship will cover conference registration and hotel accommodations up front to scholarship awardees. Other incidentals like travel and meals may be reimbursed based on the amount awarded. Reimbursement will be managed independently at the conference. Pairing up housing with other scholarship awardees or conference attendees may also be accommodated. Please contact code4libaward@gmail.com with any questions about this arrangement. We want to ensure that financial issues do not discourage anyone from applying to this award.

We do not expect scholarship recipients to be responsible for being an ambassador for their group or an educator of others during the conference. While learning and exchange may happen as a result of interactions between participants, scholarship recipients are encouraged to focus on getting the most out of their experience and have no special duties or obligations apart from conference attendance, engaged participation to their comfort level, and giving us feedback on their experience.

Code4Lib conference 2018: [https://2018.code4lib.org https://2018.code4lib.org]

=== About Code4Lib ===
Code4Lib ([https://code4lib.org https://code4lib.org]) seeks to maintain a vibrant and diverse community of technology minded folks. We are developers and technologists for libraries, museums, and archives who have a strong commitment to open technologies. Code4Lib began as a simple mailing list in 2003 and held its first face-to-face meeting in 2005 in Chicago. The first official annual conference was held in 2006 in Corvallis, Oregon. Code4Lib is dedicated to providing a harassment-free community experience for everyone regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. For more information, please see our emerging '''[https://github.com/code4lib/code-of-conduct/blob/master/code_of_conduct.md CodeofConduct4Lib]'''. Code4Lib is dedicated to being a diverse and inclusive community of technologists seeking to share ideas and build collaboration.

=== Diversity Scholarship Eligibility, Criteria, And Requirements ===
* An applicant must be a member of a group not well-represented within the code4lib community, including but not limited to: women, people of color, LGBTQ+, ability/disability, non-binary gender identities, etc. We also invite applications from members of underrepresented and/or marginalized groups that don't fit into the categories listed above.
* An applicant must be interested in actively engaging with the Code4Lib community. For more information about Code4Lib, see the [https://2018.code4lib.org/general-info/about-c4l About Code4Lib Page].
* Applications will be evaluated based upon merit and financial needs.

=== Registration Details ===
Registration spots and hotel rooms are being held for scholarship recipients. If you can attend only if you receive a scholarship, there is no need to register for the conference or book a hotel room when registration opens. Code4Lib will assist you with both registration and hotel arrangements. If you register for the conference or book a hotel room, you will reimbursed along with other expenses. Reimbursement for expenses will be provided to recipients during the conference.

=== How to Apply ===
Submit your application materials via the Code4Lib online form: https://goo.gl/forms/Re2sJwXPjgi2mi2F2

You will need to prepare:
# Your brief letter of interest, no more than 500 words, which:
## Identifies your eligibility for a diversity scholarship
## Describes how you see yourself benefiting from and participating in the Code4Lib 2018 conference and the general Code4Lib community
# Your current resume or CV
# Contact information for one reference who can speak to your professional goals and/or achievements

Please note: Your brief letter of interest and current CV/resume should be '''combined into a single pdf'''. Your file should follow a “Lastname-Firstname.pdf” naming convention. Questions can be directed to code4libaward@gmail.com.

The application deadline is '''Friday, November 17, 2017 at 11:59 PM ET'''.

The scholarship committee will notify all applicants by Friday, December 1, 2017, regardless of award results.

2018 Scholarship Documents/Call for applications

2018-04-27T04:07:43Z

AmyWickner: text of Code4Lib 2018 scholarships call for applications

Code4Lib 2018 Conference Committees

2018-04-27T03:52:10Z

AmyWickner: /* Scholarship Committee */

= Code4Lib 2018 Conference Committees =

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

* We will assign a local contact (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

* All committees and committee members abides by [https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md the Code4Lib Code of Conduct].
== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

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

[https://drive.google.com/drive/folders/0By3fUWhy9lUCeFN5SzVpVFB2N0U Website Working Group Documents (G Drive)]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University Libraries - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* [[User:ranti|Ranti Junus]] - Volunteer
* [[User:Kimpham54|Kim Pham]] - Volunteer
* [mailto:meag.sullivan@gmail.com Meaghan Sullivan] - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* [Your name here] - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* [[User:Dkerchner|Dan Kerchner]], George Washington University Libraries - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:morganem2015@gmail.com Morgan McKeehan] - Volunteer
* [mailto:selizabethgreen@gmail.com Sarah Green] - 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.

[[2018 Keynote Documents|2018 Keynote Documents]]

* [mailto:charles.harper@case.edu Charlie Harper], Case Western Reserve University - Primary Contact aka Chair
* [mailto:cleak@gmu.edu Carl Leak], George Mason University - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:maurini.strub@louisville.edu Maurini Strub], University of Louisville - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman], Miami University Libraries - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* [mailto:rdean@msu.edu Robin Dean], Michigan State University - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:johnna.percell@dc.gov Johnna Percell], DC Public Libraries - Volunteer
* [mailto:zhangj@cua.edu Jane Zhang], Catholic University of America - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [[User:Kimpham54|Kim Pham]] - 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.

[[2018 Program Documents|2018 Program Documents]]

* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - 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.

[[2018 Scholarship Documents]]

* [[User:AmyWickner|Amy Wickner]] - Primary Contact aka Chair
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:aisha.connerg@gmail.com Aisha Conner-Gaten] - Documentarian
* Brooke Johnson - Volunteer
* [[User:ToddStoffer | Todd Stoffer]], NCSU Libraries - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [mailto:elvia.arroyo@gmail.com Elvia Arroyo-Ramirez], Princeton University - Volunteer
* [mailto:anastasia.chiu@stonybrook.edu Anastasia Chiu] - Volunteer
* [[User:RuthKitchinTillman|Ruth Kitchin Tillman]] - Volunteer
* Marco Seiferle-Valencia - Volunteer
* Chad Nelson - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Joslyn Jones, Prince William County Library System, Chair
* [mailto:ccox@ubalt.edu Carolyn Cox], University of Baltimore - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:ssmith35@gmu.edu Stephanie Smith], George Mason University Libraries - Volunteer
* [mailto:ewahl@folger.edu Emily Wahl], Folger Shakespeare Library - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* [mailto:kere@loc.gov Kelly Revak] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:LibbyM@si.edu Monique Libby], Smithsonian Libraries - Volunteer
* [mailto:durden@umd.edu David Durden], University of Maryland Libraries - Volunteer
* [mailto:jkoivist@umd.edu Joseph Koivisto], University of Maryland Libraries - Volunteer

== Social Activities Committee ==
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).



Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:djiao@jhu.edu Dazhi Jiao], Johns Hopkins University - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* [mailto:nan.lov2010@gmail.com Nancy Lovas], Library of Congress - Primary Contact aka Chair
* [mailto:crh92@case.edu Charlie Harper] - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:cheever@cua.edu Erin Cheever] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* [[User:Anarchivist|Mark Matienzo]] - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* [mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Co-Chair
* [mailto:katherly@upenn.edu Katherine Lynch], University of Pennsylvania Libraries - Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:elandav@lib.msu.edu Elisa Landaverde], MSU Libraries - Volunteer
* [mailto:wmann@gmu.edu Wendy Mann], George Mason University Libraries - Volunteer
* [mailto:mpolchow@gmu.edu Michelle Polchow], George Mason University Libraries - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer

[[Category:Code4Lib2018]]

2018 Scholarship Documents

2018-04-27T03:50:43Z

AmyWickner: big list of 2018 Scholarship Committee docs; updates committee description to more closely convey the work done in 2018

Code4Lib 2018 Conference Committees

2017-11-28T21:54:54Z

AmyWickner: /* Scholarship Committee */ Belated membership updates

= Code4Lib 2018 Conference Committees =

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

* We will assign a local contact (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

* All committees and committee members abides by [https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md the Code4Lib Code of Conduct].
== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University Libraries - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* [[User:ranti|Ranti Junus]] - Volunteer
* [[User:Kimpham54|Kim Pham]] - Volunteer
* [mailto:meag.sullivan@gmail.com Meaghan Sullivan] - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* [Your name here] - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* [[User:Dkerchner|Dan Kerchner]], George Washington University Libraries - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:morganem2015@gmail.com Morgan McKeehan] - Volunteer
* [mailto:selizabethgreen@gmail.com Sarah Green] - 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.

[[2018 Keynote Documents|2018 Keynote Documents]]

* [mailto:charles.harper@case.edu Charlie Harper], Case Western Reserve University - Primary Contact aka Chair
* [mailto:cleak@gmu.edu Carl Leak], George Mason University - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:maurini.strub@louisville.edu Maurini Strub], University of Louisville - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman], Miami University Libraries - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* [mailto:rdean@msu.edu Robin Dean], Michigan State University - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:johnna.percell@dc.gov Johnna Percell], DC Public Libraries - Volunteer
* [mailto:zhangj@cua.edu Jane Zhang], Catholic University of America - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [[User:Kimpham54|Kim Pham]] - 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.

[[2018 Program Documents|2018 Program Documents]]

* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* [[User:AmyWickner|Amy Wickner]] - Primary Contact aka Chair
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:aisha.connerg@gmail.com Aisha Conner-Gaten] - Documentarian
* Brooke Johnson - Volunteer
* [[User:ToddStoffer | Todd Stoffer]], NCSU Libraries - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [mailto:elvia.arroyo@gmail.com Elvia Arroyo-Ramirez], Princeton University - Volunteer
* [mailto:anastasia.chiu@stonybrook.edu Anastasia Chiu] - Volunteer
* [[User:RuthKitchinTillman|Ruth Kitchin Tillman]] - Volunteer
* Marco Seiferle-Valencia - Volunteer
* Chad Nelson - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Joslyn Jones, Prince William County Library System, Chair
* [mailto:ccox@ubalt.edu Carolyn Cox], University of Baltimore - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:ssmith35@gmu.edu Stephanie Smith], George Mason University Libraries - Volunteer
* [mailto:ewahl@folger.edu Emily Wahl], Folger Shakespeare Library - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* [mailto:kere@loc.gov Kelly Revak] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:LibbyM@si.edu Monique Libby], Smithsonian Libraries - Volunteer
* [mailto:durden@umd.edu David Durden], University of Maryland Libraries - Volunteer
* [mailto:jkoivist@umd.edu Joseph Koivisto], University of Maryland Libraries - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez]- Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:djiao@jhu.edu Dazhi Jiao], Johns Hopkins University - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* [mailto:nan.lov2010@gmail.com Nancy Lovas], Library of Congress - Primary Contact aka Chair
* [mailto:crh92@case.edu Charlie Harper] - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:cheever@cua.edu Erin Cheever] - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* [mailto:deibel@uw.edu Kate Deibel], University of Washington Libraries - Co-Chair
* [mailto:katherly@upenn.edu Katherine Lynch], University of Pennsylvania Libraries - Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Elisa Landaverde, MSU Libraries - Volunteer
* [mailto:wmann@gmu.edu Wendy Mann], George Mason University Libraries - Volunteer
* [mailto:mpolchow@gmu.edu Michelle Polchow], George Mason University Libraries - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer

[[Category:Code4Lib2018]]

Code4Lib 2018 Conference Committees

2017-07-24T15:20:43Z

AmyWickner: Updated membership

= Code4Lib 2018 Conference Committees =

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

* We will assign a local contact (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

* All committees and committee members abides by [https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md the Code4Lib Code of Conduct].
== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:Kimpham54|Kim Pham]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University Libraries - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* [[User:ranti|Ranti Junus]] - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* Your Name Here - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* [[User:Dkerchner|Dan Kerchner]], George Washington University Libraries - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:morganem2015@gmail.com Morgan McKeehan] - Volunteer
* [mailto:selizabethgreen@gmail.com Sarah Green] - 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.

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:cleak@gmu.edu Carl Leak], George Mason University - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:maurini.strub@louisville.edu Maurini Strub], University of Louisville - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman], Miami University Libraries - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* [mailto:rdean@msu.edu Robin Dean], Michigan State University - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:johnna.percell@dc.gov Johnna Percell], DC Public Libraries - Volunteer
* [mailto:zhangj@cua.edu Jane Zhang], Catholic University of America - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [[User:Kimpham54|Kim Pham]] - 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.

[[2018 Program Documents|2018 Program Documents]]

* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* [[User:AmyWickner|Amy Wickner]] - Primary Contact aka Chair
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:aisha.connerg@gmail.com Aisha Conner-Gaten] - Documentarian
* Brooke Johnson - Volunteer
* [[User:ToddStoffer | Todd Stoffer]], NCSU Libraries - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [mailto:elvia.arroyo@gmail.com Elvia Arroyo] - Volunteer
* [mailto:anastasia.chiu@stonybrook.edu Anastasia Chiu] - Volunteer
* [[User:RuthKitchinTillman|Ruth Kitchin Tillman]] - Volunteer
* Marco Seiferle-Valencia

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Joslyn Jones, Prince William County Library System, Chair
* [mailto:ccox@ubalt.edu Carolyn Cox], University of Baltimore - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:ssmith35@gmu.edu Stephanie Smith], George Mason University Libraries - Volunteer
* [mailto:eengland@jhu.edu Elizabeth England], Johns Hopkins University - Volunteer
* [mailto:ewahl@folger.edu Emily Wahl], Folger Shakespeare Library - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* [mailto:kere@loc.gov Kelly Revak] - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:LibbyM@si.edu Monique Libby], Smithsonian Libraries - Volunteer
* [mailto:durden@umd.edu David Durden], University of Maryland Libraries - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez]- Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* [mailto:deibel@uw.edu Kate Deibel], University of Washington Libraries - Co-Chair
* [mailto:katherly@upenn.edu Katherine Lynch], University of Pennsylvania Libraries - Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Elisa Landaverde, MSU Libraries - Volunteer
* [mailto:wmann@gmu.edu Wendy Mann], George Mason University Libraries - Volunteer
* [mailto:mpolchow@gmu.edu Michelle Polchow], George Mason University Libraries - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer

[[Category:Code4Lib2018]]

User:AmyWickner

2017-07-24T15:20:20Z

AmyWickner:

Amy Wickner 
Electronic Records Archivist 
University of Maryland Libraries 
[mailto:adw3@umd.edu adw3@umd.edu] 
[https://www.lib.umd.edu/special lib.umd.edu/special]

Code4Lib 2018 Conference Committees

2017-07-04T23:00:20Z

AmyWickner: /* Scholarship Committee */ New members!

= Code4Lib 2018 Conference Committees =

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

* We will assign a local contact (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

* All committees and committee members abides by [https://github.com/code4lib/antiharassment-policy/blob/master/code_of_conduct.md the Code4Lib Code of Conduct].
== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* [[User:Kimpham54|Kim Pham]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* [[User:ranti|Ranti Junus]] - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* Your Name Here - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:morganem2015@gmail.com Morgan McKeehan] - Volunteer
* Your Name Here - 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.

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:cleak@gmu.edu Carl Leak], George Mason University - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman], Miami University Libraries - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* [mailto:rdean@msu.edu Robin Dean], Michigan State University - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* [mailto:johnna.percell@dc.gov Johnna Percell], DC Public Libraries - Volunteer
* [mailto:zhangj@cua.edu Jane Zhang], Catholic University of America - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [[User:Kimpham54|Kim Pham]] - 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.

[[2018 Program Documents|2018 Program Documents]]

* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* [[User:AmyWickner|Amy Wickner]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:aisha.connerg@gmail.com Aisha Conner-Gaten] - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Brooke Johnson - Volunteer
* [[User:ToddStoffer | Todd Stoffer]], NCSU Libraries - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer
* [mailto:tod@uchicago.edu Tod Olson], U. Chicago - Volunteer
* [mailto:elvia.arroyo@gmail.com Elvia Arroyo] - Volunteer
* [mailto:anastasia.chiu@stonybrook.edu Anastasia Chiu] - Volunteer
* [[User:RuthKitchinTillman|Ruth Kitchin Tillman]] - Volunteer
* Marco Seiferle-Valencia
* Joanna Chen Cham

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:ssmith35@gmu.edu Stephanie Smith], George Mason University Libraries - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez]- Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* [mailto:deibel@uw.edu Kate Deibel], University of Washington Libraries - Co-Chair
* [mailto:katherly@upenn.edu Katherine Lynch], University of Pennsylvania Libraries - Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Elisa Landaverde, MSU Libraries - Volunteer
* [mailto:wmann@gmu.edu Wendy Mann], George Mason University Libraries - Volunteer
* [mailto:mpolchow@gmu.edu Michelle Polchow], George Mason University Libraries - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* [mailto:kbell9@gmu.edu Kathleen Bell], George Mason University - Volunteer

[[Category:Code4Lib2018]]

MDC/2017/Registration

2017-06-19T16:11:20Z

AmyWickner: signed up

Registration for the [[MDC/2017| 2017 C4L DC/MD/VA]] Meetup.

Registration is free, but please do register by adding your name to this list if you are planning to attend, so we can plan accordingly! We have a maximum capacity of 48.

You need to have a wiki account to update this page. See instructions for requesting a new account on the [[Special:UserLogin|Login Page]] Or, send email to [[User:BenWallberg|Ben Wallberg]], [mailto:wallberg@umd.edu wallberg@umd.edu] to be added to the list.

# [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries
# [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library
# [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries
# [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries
# [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries
# [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University
# [mailto:jame@loc.gov Jaime Mears], Library of Congress
# [mailto:racheltrent@gwu.edu Rachel Trent], George Washington University
# [mailto:eengland@jhu.edu Elizabeth England], Johns Hopkins University
# [mailto:lwoodford@jhu.edu Lora Woodford], Johns Hopkins University
# [mailto:lamandafrench@gwu.edu Amanda French], George Washington University
# Esmé Cowles, Princeton University
# Wendy Mann
# [mailto:sweissman@stsci.edu Sarah Weissman], Space Telescope Science Institute, Mikulski Archive
# Sarah Hovde, Folger Shakespeare Library
# [mailto:abesottedphoenix@yahoo.com Brooke]
# [mailto:mlevy@ushmm.org Michael Levy], United States Holocaust Memorial Museum
# Laura Davis
# Rachel Curtis
# Tracy Meehleib
# [mailto:kbreneman@ubalt.edu Kyle Breneman], University of Baltimore
# [mailto:ccox@ubalt.edu Carolyn Cox], University of Baltimore
# Lorena Ramirez-Lopez
# [[User:DrewHeles|Drew Heles]], Johns Hopkins University
# [[User:AmyWickner|Amy Wickner]]
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#

Code4Lib 2018 Conference Committees

2017-04-24T11:27:37Z

AmyWickner: /* Keynote Committee */ un-volunteering

= Code4Lib 2018 Conference Committees =

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

* We will assign a local contact (LPC) to each committee.

* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter.

== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* Your Name Here - Primary Contact aka Chair
* [[User:Phette23|Eric Phetteplace]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* [[User:EkaGrguric|Eka Grguric]] - Volunteer
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer
* [[User:MattCalsada|Matt Calsada]] - Volunteer
* Your Name Here - Volunteer

== Budget Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* [Your name here] - Documentarian
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

== Sponsorship Committee ==
This group will focus on fundraising and managing contacts with potential sponsors.

* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* [mailto:liblna@emory.edu Laura Akerman] - Volunteer (v)
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

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

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Nick Kerelchuk - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Program Documents|2018 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Co-Chair of 2017 Program committee, Happy to help with carry over.
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [[User:AmyWickner|Amy Wickner]] - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Brooke Johnson - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2019 Host Voting Documents|2019 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* Your Name Here - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2018]]

Code4Lib 2018 Conference Committees

2017-04-12T19:31:10Z

AmyWickner: /* Scholarship Committee */ volunteered

= Code4Lib 2018 Conference Committees =

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

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* Your Name Here - Primary Contact aka Chair
* [[User:Phette23|Eric Phetteplace]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* Your Name Here - Documentarian
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

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

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:AmyWickner|Amy Wickner]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Program Documents|2018 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Co-Chair of 2017 Program committee, Happy to help with carry over.
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* [[User:AmyWickner|Amy Wickner]] - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Brooke Johnson - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Host Voting Documents|2018 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* Your Name Here - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2018]]

Code4Lib 2018 Conference Committees

2017-04-12T19:30:27Z

AmyWickner: /* Keynote Committee */

= Code4Lib 2018 Conference Committees =

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

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* Your Name Here - Primary Contact aka Chair
* [[User:Phette23|Eric Phetteplace]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* Your Name Here - Documentarian
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

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

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:AmyWickner|Amy Wickner]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Program Documents|2018 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Co-Chair of 2017 Program committee, Happy to help with carry over.
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Brooke Johnson - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Host Voting Documents|2018 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* Your Name Here - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2018]]

User:AmyWickner

2017-04-12T19:29:28Z

AmyWickner: basics

Amy Wickner 
University of Maryland Libraries 
[mailto:adw3@umd.edu adw3@umd.edu] 
[https://www.lib.umd.edu/special lib.umd.edu/special]

Code4Lib 2018 Conference Committees

2017-04-12T19:21:36Z

AmyWickner: Volunteered

= Code4Lib 2018 Conference Committees =

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

We will assign a local contact (LPC) to each committee.

== Location and Dates ==

* Location: Washington, DC (more info coming soon)
* Dates: we're looking at early February 2018
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches
** Main meeting: Coming Soon but we're thinking a hotel downtown
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.

== Local Planning Committee ==
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.

* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact

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

[[2018 Website Working Group Documents|2018 Website Working Group Documents]]

* Your Name Here - Primary Contact aka Chair
* [[User:Phette23|Eric Phetteplace]] - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Planning Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them.

[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)
* Your Name Here - Documentarian
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host

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

[[2018 Keynote Documents|2018 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:adw3@umd.edu Amy Wickner], University of Maryland Libraries - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Pre-conference Documents|2018 Pre-conference Documents]]

* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Program Documents|2018 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Co-Chair of 2017 Program committee, Happy to help with carry over.
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - 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.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Brooke Johnson - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 T-Shirt Documents|2018 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:

[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:trey@koios.co Trey Gordner] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==
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).

[[2018 Social Activities Documents|2018 Social Activities Documents]]

Conference goers - The page you are looking for is at [[2018 Social Activities]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* 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 (?), and, of course, actually running the camera during the conference.

[[2018 Streaming Video Documents|2018 Streaming Video Documents]]

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Host Voting Documents|2018 Host Voting Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer
* Your Name Here - Volunteer

== Wifi and Electrical ==
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.

[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 (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).

[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== IRC and Slack Committee ==
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.

[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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 (physical and virtual).

[[2018 Accessibility Documents|2018 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - 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.

[[2018 Whatever Documents|2018 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer
* [[User:WayneGraham|Wayne Graham]] - Volunteer
* [[User:Phette23|Eric Phetteplace]] - Volunteer
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2018]]