Code4Lib - User contributions [en]

2026 Book Giveaway Committee

2026-03-03T19:53:50Z

Ranti: /* Potential Donors to Contact */

== Potential Donors to Contact ==

{| class="wikitable"
|-
! Donor !! Email !! Contacted By !! Contacted On !! Response !! Notes
|-
| O'Reilly & Assoc. || support@oreilly.com || MBK || 2026-01-26 || 2026-02-10 || 5-10 physical titled selected by O'Reilly + Ebooks (winner's choice) + 30-day platform trial for all attendees
|-
| Pragmatic Bookshelf || support@pragprog.com || MBK || 2026-01-26 || 2026-01-26 || Offering DRM-free e-books as well as a conference-wide discount code
|-
| JetBrains || usergroups@jetbrains.com || MBK || 2026-01-26 || ||
|-
| Manning Publications || support@manning.com || MBK || 2026-01-26 || ||
|-
| No Starch Press || conferences@nostarch.com || MBK || 2026-01-26 || ||
|-
| Apress || editorial@apress.com || MBK || 2026-01-26 || ||
|-
| MIT Press || raldrich@mit.edu || MBK || 2026-01-26 || ||
|-
| Rosenfeld Media || info@rosenfeldmedia.com || Ranti || 2026-01-30 || 2026-02-05 || a discount on [https://rosenverse.rosenfeldmedia.com/ Rosenverse] Gold tier subscriptions
|-
| Facet publishing || || Crys || 2026-02-05 || 2026-02-05 || physical book : Lowagie’s AI-Powered Cataloguing (paperback)
|-
| University of Minnesoata Press || || Crys || 2026-02-05 || 2026-02-05 || About 7 physical books; information about [https://manifoldapp.org Manifold], a publishing platform for open access ebooks. Flyers + promotional materials (bookmarks, flyers, maybe a mug or two).
|-
| American Alliance of Museums Books || || Crys || 2026-02-05 || ||
|-
| Stanford University Press || || Crys || 2026-02-05 || ||
|-
| American Library Association || || Crys || 2026-02-05 || ||
|}

== At the Conference ==

=== Prizes ===

* In past years, we've seeded a randomizer with a list of attendees' names. At the end of each session break / lunch break, before resuming, we'd draw 2-3 names and let them choose from the available prizes. With 2 breaks + lunch per day (minus one break on the last day), that usually means 16-20 things given away.
* This year, we expect 13-18 physical prizes to arrive at the conference hotel, with a number of digital offerings as well, listed in the above grid.
* O'Reilly and Pragmatic haven't put a limit on the number of e-book prizes we can give away, but we should try to keep it within reason for each.
** Their offerings are limited to e-books actually ''published'' by each of them, which isn't necessarily everything they carry in their online stores.
** E-books are winner's choice. Winners' email addresses should be forwarded to me (MBK) so I can gather the selections and send them to the publishers so they can send out the codes.

=== Other Swag ===

* Some donors are also sending other "registration table swag" – buttons, stickers, bookmarks, etc. It's up to the organizers to decide how to distribute that stuff.
* O'Reilly is offering a 30-day platform trial to all code4lib attendees. I (MBK again) will send along the code as soon as I have it.
* Pragmatic has offered a 40% site-wide discount to all conference attendees.
** These are audio and e-books only, as PragProg does not actually sell print editions on their retail site.
** The code applies to the entire cart, not just a single item, and will be good for a few weeks following the conference.
** The only item not discounted is ''The Pragmatic Programmer, 20th Anniversary Edition'' which, ironically, is the one title Pragmatic Bookshelf doesn't have the rights to and therefore cannot discount.
** I (still MBK) will share that code soon as well so it can be conveyed to participants during the conference.

== Sample Request Email ==

Hello [Name / Team],

I’m writing on behalf of the book & resource giveaway committee for **code4lib**, an annual conference focused on libraries, technology, and open-source development. Our attendees are developers, librarians, system architects, and digital scholarship professionals working at the intersection of cultural heritage and modern infrastructure.

Each year, we host a free giveaway for attendees featuring technical books, professional resources, and software or service licenses. We’re reaching out to a small number of organizations whose work aligns closely with the interests of our community.

We would love to include a contribution from **[Organization Name]**, such as:

* print or digital books,
* access codes or licenses,
* training or certification vouchers,
* or other developer- or library-focused resources.

In return, donors are acknowledged on the conference website and signage at the giveaway table, and your contribution reaches a highly engaged audience of practitioners who actively recommend tools and resources within their institutions.

If this is something you’d consider, we’d be happy to share more details about the conference, audience demographics, or logistics. Thank you for your time—and for supporting the library and open-source community.

Best regards,
[Your Name]
Book & Resource Giveaway Committee
code4lib Conference
[contact email]

2026 Book Giveaway Committee

2026-02-10T00:58:15Z

Ranti:

== Potential Donors to Contact ==

{| class="wikitable"
|-
! Donor !! Email !! Contacted By !! Contacted On !! Response !! Notes
|-
| O'Reilly & Assoc. || support@oreilly.com || MBK || 2026-01-26 || 2026-01-30 || Zoom meeting on 2/2 to discuss what they can do for us
|-
| Pragmatic Bookshelf || support@pragprog.com || MBK || 2026-01-26 || 2026-01-26 || Offering DRM-free e-books as well as a conference-wide discount code
|-
| JetBrains || usergroups@jetbrains.com || MBK || 2026-01-26 || ||
|-
| Manning Publications || support@manning.com || MBK || 2026-01-26 || ||
|-
| No Starch Press || conferences@nostarch.com || MBK || 2026-01-26 || ||
|-
| Apress || editorial@apress.com || MBK || 2026-01-26 || ||
|-
| MIT Press || raldrich@mit.edu || MBK || 2026-01-26 || ||
|-
| Rosenfeld Media || info@rosenfeldmedia.com || Ranti || 2026-01-30 || 2026-02-05 || a discount on [https://rosenverse.rosenfeldmedia.com/ Rosenverse] Gold tier subscriptions
|-
| Facet publishing || || Crys || 2026-02-05 || 2026-02-05 || They’ll provide a book (asked for a shipping address)
|-
| Minnesota University Press || || Crys || 2026-02-05 || 2026-02-05 || Some books; information about [https://manifoldapp.org Manifold], a publishing platform for open access ebooks
|-
| American Alliance of Museums Books || || Crys || 2026-02-05 || ||
|-
| Stanford University Press || || Crys || 2026-02-05 || ||
|-
| American Library Association || || Crys || 2026-02-05 || ||
|}

== Sample Request Email ==

Hello [Name / Team],

I’m writing on behalf of the book & resource giveaway committee for **code4lib**, an annual conference focused on libraries, technology, and open-source development. Our attendees are developers, librarians, system architects, and digital scholarship professionals working at the intersection of cultural heritage and modern infrastructure.

Each year, we host a free giveaway for attendees featuring technical books, professional resources, and software or service licenses. We’re reaching out to a small number of organizations whose work aligns closely with the interests of our community.

We would love to include a contribution from **[Organization Name]**, such as:

* print or digital books,
* access codes or licenses,
* training or certification vouchers,
* or other developer- or library-focused resources.

In return, donors are acknowledged on the conference website and signage at the giveaway table, and your contribution reaches a highly engaged audience of practitioners who actively recommend tools and resources within their institutions.

If this is something you’d consider, we’d be happy to share more details about the conference, audience demographics, or logistics. Thank you for your time—and for supporting the library and open-source community.

Best regards,
[Your Name]
Book & Resource Giveaway Committee
code4lib Conference
[contact email]

2026 Book Giveaway Committee

2026-02-10T00:57:41Z

Ranti:

== Potential Donors to Contact ==

{| class="wikitable"
|-
! Donor !! Email !! Contacted By !! Contacted On !! Response !! Notes
|-
| O'Reilly & Assoc. || support@oreilly.com || MBK || 2026-01-26 || 2026-01-30 || Zoom meeting on 2/2 to discuss what they can do for us
|-
| Pragmatic Bookshelf || support@pragprog.com || MBK || 2026-01-26 || 2026-01-26 || Offering DRM-free e-books as well as a conference-wide discount code
|-
| JetBrains || usergroups@jetbrains.com || MBK || 2026-01-26 || ||
|-
| Manning Publications || support@manning.com || MBK || 2026-01-26 || ||
|-
| No Starch Press || conferences@nostarch.com || MBK || 2026-01-26 || ||
|-
| Apress || editorial@apress.com || MBK || 2026-01-26 || ||
|-
| MIT Press || raldrich@mit.edu || MBK || 2026-01-26 || ||
|-
| Rosenfeld Media || info@rosenfeldmedia.com || Ranti || 2026-01-30 || 2026-02-05 || a discount on Rosenverse Gold tier subscriptions
|-
| Facet publishing || || Crys || 2026-02-05 || 2026-02-05 || They’ll provide a book (asked for a shipping address)
|-
| Minnesota University Press || || Crys || 2026-02-05 || 2026-02-05 || Some books; information about [https://manifoldapp.org Manifold], a publishing platform for open access ebooks
|-
| American Alliance of Museums Books || || Crys || 2026-02-05 || ||
|-
| Stanford University Press || || Crys || 2026-02-05 || ||
|-
| American Library Association || || Crys || 2026-02-05 || ||
|}

== Sample Request Email ==

Hello [Name / Team],

I’m writing on behalf of the book & resource giveaway committee for **code4lib**, an annual conference focused on libraries, technology, and open-source development. Our attendees are developers, librarians, system architects, and digital scholarship professionals working at the intersection of cultural heritage and modern infrastructure.

Each year, we host a free giveaway for attendees featuring technical books, professional resources, and software or service licenses. We’re reaching out to a small number of organizations whose work aligns closely with the interests of our community.

We would love to include a contribution from **[Organization Name]**, such as:

* print or digital books,
* access codes or licenses,
* training or certification vouchers,
* or other developer- or library-focused resources.

In return, donors are acknowledged on the conference website and signage at the giveaway table, and your contribution reaches a highly engaged audience of practitioners who actively recommend tools and resources within their institutions.

If this is something you’d consider, we’d be happy to share more details about the conference, audience demographics, or logistics. Thank you for your time—and for supporting the library and open-source community.

Best regards,
[Your Name]
Book & Resource Giveaway Committee
code4lib Conference
[contact email]

2026 Book Giveaway Committee

2026-02-10T00:54:04Z

Ranti: /* Potential Donors to Contact */

== Potential Donors to Contact ==

{| class="wikitable"
|-
! Donor !! Email !! Contacted By !! Contacted On !! Response !! Notes
|-
| O'Reilly & Assoc. || support@oreilly.com || MBK || 2026-01-26 || 2026-01-30 || Zoom meeting on 2/2 to discuss what they can do for us
|-
| Pragmatic Bookshelf || support@pragprog.com || MBK || 2026-01-26 || 2026-01-26 || Offering DRM-free e-books as well as a conference-wide discount code
|-
| JetBrains || usergroups@jetbrains.com || MBK || 2026-01-26 || ||
|-
| Manning Publications || support@manning.com || MBK || 2026-01-26 || ||
|-
| No Starch Press || conferences@nostarch.com || MBK || 2026-01-26 || ||
|-
| Apress || editorial@apress.com || MBK || 2026-01-26 || ||
|-
| MIT Press || raldrich@mit.edu || MBK || 2026-01-26 || ||
|-
| Rosenfeld Media || info@rosenfeldmedia.com || Ranti || 2026-01-30 || 2026-02-05 || a discount on Rosenverse Gold tier subscriptions
|-
| Facet publishing || || Crys || 2026-02-05 || || They’ll provide a book (asked for a shipping address)
|-
| Minnesota University Press || || Crys || 2026-02-05 || 2026-02-05 || Some book; information about Manifold, a publishing platform for open access ebooks
|-
| American Alliance of Museums Books || || Crys || 2026-02-05 || ||
|-
| Stanford University Press || || Crys || 2026-02-05 || ||
|-
| American Library Association || || Crys || 2026-02-05 || ||
|}

== Sample Request Email ==

Hello [Name / Team],

I’m writing on behalf of the book & resource giveaway committee for **code4lib**, an annual conference focused on libraries, technology, and open-source development. Our attendees are developers, librarians, system architects, and digital scholarship professionals working at the intersection of cultural heritage and modern infrastructure.

Each year, we host a free giveaway for attendees featuring technical books, professional resources, and software or service licenses. We’re reaching out to a small number of organizations whose work aligns closely with the interests of our community.

We would love to include a contribution from **[Organization Name]**, such as:

* print or digital books,
* access codes or licenses,
* training or certification vouchers,
* or other developer- or library-focused resources.

In return, donors are acknowledged on the conference website and signage at the giveaway table, and your contribution reaches a highly engaged audience of practitioners who actively recommend tools and resources within their institutions.

If this is something you’d consider, we’d be happy to share more details about the conference, audience demographics, or logistics. Thank you for your time—and for supporting the library and open-source community.

Best regards,
[Your Name]
Book & Resource Giveaway Committee
code4lib Conference
[contact email]

2026 Book Giveaway Committee

2026-01-30T21:50:36Z

Ranti: /* Potential Donors to Contact */

== Potential Donors to Contact ==

{| class="wikitable"
|-
! Donor !! Email !! Contacted By !! Contacted On !! Response !! Notes
|-
| O'Reilly & Assoc. || support@oreilly.com || MBK || 2026-01-26 || ||
|-
| Pragmatic Bookshelf || support@pragprog.com || MBK || 2026-01-26 || 2026-01-26 || Offering DRM-free e-books as well as a conference-wide discount code
|-
| JetBrains || usergroups@jetbrains.com || MBK || 2026-01-26 || ||
|-
| Manning Publications || support@manning.com || MBK || 2026-01-26 || ||
|-
| No Starch Press || conferences@nostarch.com || MBK || 2026-01-26 || ||
|-
| Apress || editorial@apress.com || MBK || 2026-01-26 || ||
|-
| MIT Press || raldrich@mit.edu || MBK || 2026-01-26 || ||
|-
| Rosenfeld Media || info@rosenfeldmedia.com || Ranti || 2026-01-30 || ||
|}

== Sample Request Email ==

Hello [Name / Team],

I’m writing on behalf of the book & resource giveaway committee for **code4lib**, an annual conference focused on libraries, technology, and open-source development. Our attendees are developers, librarians, system architects, and digital scholarship professionals working at the intersection of cultural heritage and modern infrastructure.

Each year, we host a free giveaway for attendees featuring technical books, professional resources, and software or service licenses. We’re reaching out to a small number of organizations whose work aligns closely with the interests of our community.

We would love to include a contribution from **[Organization Name]**, such as:

* print or digital books,
* access codes or licenses,
* training or certification vouchers,
* or other developer- or library-focused resources.

In return, donors are acknowledged on the conference website and signage at the giveaway table, and your contribution reaches a highly engaged audience of practitioners who actively recommend tools and resources within their institutions.

If this is something you’d consider, we’d be happy to share more details about the conference, audience demographics, or logistics. Thank you for your time—and for supporting the library and open-source community.

Best regards,
[Your Name]
Book & Resource Giveaway Committee
code4lib Conference
[contact email]

2026 Keynote Speakers Nominations

2025-10-25T09:15:51Z

Ranti:

Keynote nominations are closed.

__TOC__

==Kate Deibel==

Katherine "Kate" Deibel has had a varied career in academia working within and across many disciplines, including computer science, education, disability, comics, digital literacies, and libraries. After transitioning in her first year of graduate school, she earned her PhD in computer science and engineering at the University of Washington in 2011 with a multidisciplinary study of the social and technological factors that hinder adoption of reading technologies among adults with dyslexia. As an ardent advocate for usable and accessible technologies, she works and educates to ensure that library technologies are effective tools for both library patrons and staff. Having worked in library technologies at the University of Washington and Syracuse University Libraries, she now is the systems librarian at Philadelphia College of Osteopathic Medicine, spearheading their adoption of open library systems such as FOLIO and VuFind.

[https://www.dropbox.com/scl/fi/xs3p6vfnjkx5h9gw2f4sz/deibel-cv.pdf?rlkey=5428wdpyauvmpvmtelqlqy89r&e=1&dl=0 CV]

Email contact information [mailto:katherine.deibel@gmail.com]

==Annalee Newitz==

Annalee Newitz is a science journalist who also writes science fiction. They are the author of several books, including Automatic Noodle, an instant USA Today bestseller, The Terraformers, which was nominated for the Nebula Award, and Four Lost Cities: A Secret History of the Urban Age. They have a monthly column in New Scientist magazine, and are the co-host of the Hugo-winning podcast Our Opinions Are Correct. (from Website)

Newitz was awarded a Knight Science Journalism Fellowship for 2002 to 2003, supporting them as a research fellow at Massachusetts Institute of Technology. From 2004 to 2005 Newitz was a policy analyst for the Electronic Frontier Foundation, and from 2007 to 2009 was on the board of Computer Professionals for Social Responsibility. (from Wikipedia)

[https://www.techsploitation.com/ Website]
[https://en.wikipedia.org/wiki/Annalee_Newitz Wikipedia]

Email contact information [mailto:annalee@gmail.com]

==Xe Iaso==
Xe Iaso is "a technical educator, conference speaker, twitch streamer, vtuber, and philosopher that focuses on ways to help make technology easier to understand and do cursed things in the process." They are best-known in the code4lib community for their work on [https://github.com/TecharoHQ/anubis Anubis], which "weighs the soul of incoming HTTP requests to stop AI crawlers" and is widely used by code4libbers defending cultural heritage web sites from bot onslaught. They are [https://xeiaso.net/talks/ an experienced and engaging conference speaker]. They have gotten pretty engaged with the code4lib community as they support our use of Anubis, and I think it would be neat if we all got to meet each other.

https://xeiaso.net/

[mailto:me@xeiaso.net email]

==Nate Matias==

[https://natematias.com/ Dr. J. Nathan Matias] is a social scientist and Cornell faculty member who "stud[ies] digital governance and behavior change in groups and networks shaped by AI systems" and "collaborate[s] with the public in citizen behavioral science, working for a world where digital power is guided by evidence and accountable to the public." His research includes concrete interventions to improve the quality of discourse and safety in online communities. These days, he's interested in speaking on AI governance, "community-led field experiments in computing, social-psychology, and technology governance", and independent, non-corporate research. He is an [https://natematias.com/speaking/ experienced public speaker] and also one of the nicest people you will ever meet.

[https://social.coop/@natematias mastodon]
[mailto:nathan.matias@cornell.edu email]

== Luis von Ahn ==

Luis von Ahn holds a PhD in Computer Science from Carnegie Mellon University. His thesis, completed in 2005, was the first publication to use the term "human computation", referring to methods that combine human brainpower with computers to solve problems that neither could solve alone. In 2007, von Ahn invented reCAPTCHA,[26] a new form of CAPTCHA that also helps digitize books. In 2009, von Ahn and his graduate student Severin Hacker started developing Duolingo, which now has 46.6 million daily active users worldwide.

von Ahn was awarded a MacArthur Fellowship in 2006, the David and Lucile Packard Foundation Fellowship in 2009, a Sloan Fellowship in 2009, and a Microsoft New Faculty Fellowship in 2007, and the Presidential Early Career Award for Scientists and Engineers in 2012.

Much of this information was taken from the Wikipedia article, [https://en.wikipedia.org/wiki/Luis_von_Ahn Luis von Ahn].

[mailto:press@duolingo.com Press Contact]

[http://linkedin.com/in/luis-von-ahn-duolingo LinkedIn]

== Lisa Nguyen ==

Lisa Nguyen is the digital archivist at the UC San Francisco Archives and Special Collections. With over 20 years of experience in archives, Lisa is constantly innovating ways to preserve and share historical collections from audiovisual to born-digital content for future access by researchers and the general public. Lisa is collaborating with others to harness and leverage AI to enhance discovery and access to historical collections in medicine and health sciences, especially from marginalized voices and experiences. At a time when government agencies censor or erase invaluable scientific research/documents/websites, it has become timely and more critical for digital archivists like Lisa to work collaboratively, collectively, and efficiently as a community to document the past in health sciences and to share how they are approaching it. As an archivist, Lisa has presented and participated in global projects in Asia. She brings an international perspective and vision on how technologies are evolving and changing to be utilized for digital archival and library work.

[https://www.library.ucsf.edu/news/welcome-lisa-nguyen-digital-archivist/ Welcome Lisa Nguyen, Digital Archivist]
[https://www.clir.org/2024/10/preserving-voices-saving-histories-meet-lisa-nguyen-clir-grantee-spotlight/ CLIR Preserving Voices, Saving History]
[https://www.library.ucsf.edu/news/celebrating-world-digital-preservation-day-2024/ Celebrating World Digital Preservation Day]

[mailto:Lisa.Nguyen2@ucsf.edu email]

== Brian Mathews ==

Dean and University Librarian of the Carol Grotnes Belk Library, Elon University

Brian Mathews is Library leader, administrator, and innovator whose career in academic libraries spans multiple decades. He maintains a driving interest in helping research libraries evolve — and the related structures & culture that enables successful transformation. Mathews explores professional interests in the way people engage with information: in his words, their “personal knowledge management.” Mathews also was the co-founder of the Carnegie Mellon University Library’s Robotics Project, and he served as the principal investigator on a grant from Sloan Foundation related to the formation of the Digital Robotics Archive.

[https://www.linkedin.com/in/brian-mathews-b156712/ LinkedIn]
[https://www.brianmathews.io/ Website]

[mailto:bmathews3@elon.edu email]

== Shoshana Zuboff ==

Shoshana Zuboff is a retired professor from the Harvard Business School, and is "a scholar, writer, and activist" and "is the author of three major books, each signaling a new epoch in technological society. Her most recent work, The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power (2019), synthesizes her decades of research and thinking to reveal a new economic era in which once private human experience is secretly invaded, extracted as data, and exploited for hidden processes of manufacturing, prediction, and sales." Her research is particularly important as libraries and technologists grapple with the emerging role of AI in the information landscape.

[https://shoshanazuboff.com/book/shoshana/ Website About]

[https://shoshanazuboff.com/book/contact/ Contact]

== Emily Laird ==

Emily Laird is the AI Integration Technologist at UW-Stout, where she collaborates in support of campus-wide efforts to integrate artificial intelligence into education, research, and industry collaboration. With expertise in AI foundations, generative AI, AI literacy, and industry integration, she works closely with faculty, staff, and students to advance AI adoption and support ethical, effective implementation of emerging AI technologies.

Emily is the host of Generative AI 101, a podcast dedicated to supporting AI literacy for all. She is also a national speaker [and an entertaining one!] on AI literacy and AI integration, engaging industry leaders, educators, and policymakers in discussions on the changing role of AI in business, education, and society. (from University Profile)

[https://www.uwstout.edu/directory/lairde University Profile]
[https://www.linkedin.com/in/meet-emily-laird/ LinkedIn]

[mailto:lairde@uwstout.edu email]

== Brandon Nightingale ==

Black Press Manager of the Moorland-Spingarn Research Center of Howard University

Brandon Nightingale is a highly experienced professional in the fields of project management and academia, currently serving as a Senior Project Manager at Howard University since May 2022. Previously, Brandon held multiple roles, including Professor, University Archivist, and Assistant Archivist at Bethune-Cookman University from April 2019 to December 2022, and worked as a Public History Contractor with the National Park Service focusing on African American history at Cumberland Island National Seashore from December 2020 to April 2022. Educational credentials include a Master of Arts in Public History and a Master of Science in Library and Information Science from the University of Central Florida and Florida State University, respectively, as well as a Bachelor of Arts in History from the University of Central Florida. Currently, Brandon is pursuing a PhD in History at Howard University, expected to conclude in December 2026.

[https://gs.howard.edu/sway/jun23_1 Bio]

[mailto:brandon.nightingale@howard.edu email]

== Speaker Name ==

Bio and other info (250 words)

Contact info

2026 Keynote Speakers Nominations

2025-10-21T17:38:16Z

Ranti:

Please add Keynote speaker nomination using the template below. See [https://wiki.code4lib.org/2025_Keynote_Speakers_Nominations 2025 Keynote Speakers Nominations] as example.

Keynote speaker nominations for the Code4Lib 2026 Conference will be accepted through October 24, 2025.

If you would like to nominate anonymously/without Code4Lib wiki account, you can send email to [mailto:msl321@lehigh.edu Maccabee Levine] and he will add the nominee to this page.

__TOC__

==Kate Deibel==

Katherine "Kate" Deibel has had a varied career in academia working within and across many disciplines, including computer science, education, disability, comics, digital literacies, and libraries. After transitioning in her first year of graduate school, she earned her PhD in computer science and engineering at the University of Washington in 2011 with a multidisciplinary study of the social and technological factors that hinder adoption of reading technologies among adults with dyslexia. As an ardent advocate for usable and accessible technologies, she works and educates to ensure that library technologies are effective tools for both library patrons and staff. Having worked in library technologies at the University of Washington and Syracuse University Libraries, she now is the systems librarian at Philadelphia College of Osteopathic Medicine, spearheading their adoption of open library systems such as FOLIO and VuFind.

[https://www.dropbox.com/scl/fi/xs3p6vfnjkx5h9gw2f4sz/deibel-cv.pdf?rlkey=5428wdpyauvmpvmtelqlqy89r&e=1&dl=0 CV]

Email contact information [mailto:katherine.deibel@gmail.com]

==Annalee Newitz==

Annalee Newitz is a science journalist who also writes science fiction. They are the author of several books, including Automatic Noodle, an instant USA Today bestseller, The Terraformers, which was nominated for the Nebula Award, and Four Lost Cities: A Secret History of the Urban Age. They have a monthly column in New Scientist magazine, and are the co-host of the Hugo-winning podcast Our Opinions Are Correct. (from Website)

Newitz was awarded a Knight Science Journalism Fellowship for 2002 to 2003, supporting them as a research fellow at Massachusetts Institute of Technology. From 2004 to 2005 Newitz was a policy analyst for the Electronic Frontier Foundation, and from 2007 to 2009 was on the board of Computer Professionals for Social Responsibility. (from Wikipedia)

[https://www.techsploitation.com/ Website]
[https://en.wikipedia.org/wiki/Annalee_Newitz Wikipedia]

Email contact information [mailto:annalee@gmail.com]

==Xe Iaso==
Xe Iaso is "a technical educator, conference speaker, twitch streamer, vtuber, and philosopher that focuses on ways to help make technology easier to understand and do cursed things in the process." They are best-known in the code4lib community for their work on [https://github.com/TecharoHQ/anubis Anubis], which "weighs the soul of incoming HTTP requests to stop AI crawlers" and is widely used by code4libbers defending cultural heritage web sites from bot onslaught. They are [https://xeiaso.net/talks/ an experienced and engaging conference speaker]. They have gotten pretty engaged with the code4lib community as they support our use of Anubis, and I think it would be neat if we all got to meet each other.

https://xeiaso.net/

[mailto:me@xeiaso.net email]

==Nate Matias==

[https://natematias.com/ Dr. J. Nathan Matias] is a social scientist and Cornell faculty member who "stud[ies] digital governance and behavior change in groups and networks shaped by AI systems" and "collaborate[s] with the public in citizen behavioral science, working for a world where digital power is guided by evidence and accountable to the public." His research includes concrete interventions to improve the quality of discourse and safety in online communities. These days, he's interested in speaking on AI governance, "community-led field experiments in computing, social-psychology, and technology governance", and independent, non-corporate research. He is an [https://natematias.com/speaking/ experienced public speaker] and also one of the nicest people you will ever meet.

[https://social.coop/@natematias mastodon]
[mailto:nathan.matias@cornell.edu email]

==FirstName LastName==

Description of the person (250 words or less)

[https://wiki.code4lib.org/2026_Keynote_Speakers_Nominations Relevant websites, if any]

Email contact information [mailto:someone@example.com someone@example.com]

2026 Keynote Speakers Nominations

2025-10-07T20:00:06Z

Ranti:

2026 Keynote Speakers Nominations

2025-10-07T19:59:41Z

Ranti:

2026 Keynote Speakers Nominations

2025-10-07T19:19:03Z

Ranti:

Please add Keynote speaker nomination using the template below. See [https://wiki.code4lib.org/2025_Keynote_Speakers_Nominations 2025 Keynote Speakers Nominations] as example.

If you would like to nominate anonymously, you can send email to [mailto:msl321@lehigh.edu Maccabee Levine] and he will add the nominee to this page.

__TOC__

==FirstName LastName==

Description of the person (100 words or less)

[https://wiki.code4lib.org/2026_Keynote_Speakers_Nominations Relevant websites, if any]

Email contact information [mailto:msl321@lehigh.edu msl321@lehigh.edu]

2026 Keynote Speakers Nominations

2025-10-07T19:18:17Z

Ranti:

Please add Keynote speaker nomination using the template below. See [https://wiki.code4lib.org/2025_Keynote_Speakers_Nominations 2025 Keynote Speakers Nominations] as example.

If you would like to nominate anonymously, you can send email to [mailto:msl321@lehigh.edu Maccabee Levine] and he will add the nominee to this page.

__TOC__

==FirstName LastName==

Description of the person (100 words or less)

[https://wiki.code4lib.org/2026_Keynote_Speakers_Nominations Relevant websites, if any]

Email contact information [mailto:doctorow@craphound.com doctorow@craphound.com]

2026 Keynote Speakers Nominations

2025-10-07T19:13:00Z

Ranti:

2026 Keynote Speakers Nominations

2025-10-06T16:55:00Z

Ranti: new page

Code4Lib 2026 Conference Committees

2025-08-21T20:32:56Z

Ranti: /* Book Giveaway Committee */

= Code4Lib Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2026 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact

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

[[2026 Planning Committee Documents|2026 Planning Committee Documents]]

* Ann Marie Mesco - Primary Contact, Chair
* Ken Rose - Secondary Contact, CoChair
* Esmé Cowles - Documentarian
* Erin Swift - Volunteer
* Joelen Pastva - Volunteer
* Lina Crowe - Volunteer
* Kelly Woessner - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2026 Website Working Group Documents|2026 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact, Chair
* Trip Kirkpatrick, CoChair
* Esmé Cowles - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[2026 Budget and Sponsorship Documents]

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

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Your Name Here - Andromeda Yelton, Chair ''if someone else really wants to chair hit me up; I've done this a few times and I'm happy to do it again but I'm also happy to share the opportunity''
* Your Name Here - Maccabee Levine, CoChair
* Your Name Here - Documentarian
* Andrew Battelini - Volunteer; abattel@emory.edu (and on Slack)
* Ranti Junus - Volunteer
* Your Name Here - Volunteer

== Workshop Committee (Pre / Post-Conference)==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2026 Pre-conference Documents|2026 Pre-conference Documents]]

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

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

[[2026 Program Documents|2026 Program Documents]]

* Your Name Here - Primary Contact, Chair
* Dre - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Matt Sherman - 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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:ChristineSalek|Christine Salek]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

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

[[2026 T-Shirt Documents|2026 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:ChristineSalek|Christine Salek]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2026 Online Volunteer Documents|2026 Online Volunteer Documents]]

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

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

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

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

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

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

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

[[2026 Host Voting Documents|2026 Host Voting Documents]]

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

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

* Michael B. Klein - Primary Contact, Chair
* Ranti Junus - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]

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

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

[[2026 Accessibility Documents|2026 Accessibility Documents]]

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

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

[[2026 Whatever Documents|2026 Whatever Documents]]

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

[[Category: Code4Lib2026]]
[[Category:Conference Committees]]

Code4Lib 2026 Conference Committees

2025-08-21T20:08:18Z

Ranti: add ranti

= Code4Lib Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2026 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact

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

[[2026 Planning Committee Documents|2026 Planning Committee Documents]]

* Ann Marie Mesco - Primary Contact, Chair
* Ken Rose - Secondary Contact, CoChair
* Esmé Cowles - Documentarian
* Erin Swift - Volunteer
* Joelen Pastva - Volunteer
* Lina Crowe - Volunteer
* Kelly Woessner - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2026 Website Working Group Documents|2026 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact, Chair
* Trip Kirkpatrick, CoChair
* Esmé Cowles - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[2026 Budget and Sponsorship Documents]

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

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Your Name Here - Andromeda Yelton, Chair ''if someone else really wants to chair hit me up; I've done this a few times and I'm happy to do it again but I'm also happy to share the opportunity''
* Your Name Here - Maccabee Levine, CoChair
* Your Name Here - Documentarian
* Andrew Battelini - Volunteer; abattel@emory.edu (and on Slack)
* Ranti Junus - Volunteer
* Your Name Here - Volunteer

== Workshop Committee (Pre / Post-Conference)==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2026 Pre-conference Documents|2026 Pre-conference Documents]]

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

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

[[2026 Program Documents|2026 Program Documents]]

* Your Name Here - Primary Contact, Chair
* Dre - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Matt Sherman - 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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:ChristineSalek|Christine Salek]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

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

[[2026 T-Shirt Documents|2026 T-Shirt Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:ChristineSalek|Christine Salek]] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2026 Online Volunteer Documents|2026 Online Volunteer Documents]]

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

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

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

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

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

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

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

[[2026 Host Voting Documents|2026 Host Voting Documents]]

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

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

* Michael B. Klein - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]

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

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

[[2026 Accessibility Documents|2026 Accessibility Documents]]

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

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

[[2026 Whatever Documents|2026 Whatever Documents]]

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

[[Category: Code4Lib2026]]
[[Category:Conference Committees]]

2025 Keynote Speakers Nominations

2024-11-15T17:46:23Z

Ranti: /* Ruth Kitchin Tillman */

Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.

'''Nominations will close after November 21, 2024.'''

When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:

1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?

2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?

3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?

Please include a description and any relevant links. Please try to keep the list in alphabetical order.

We require the following information in your nomination for a candidate to act as keynote:
*Speaker’s full name
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information for candidate (email address)

The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Hardy Pottinger at [mailto:hardy.pottinger@ucsf.edu?Subject=CODE4LIB%20KEYNOTE%20NOMINATION hardy.pottinger@ucsf.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

[mailto:email_link.foo nominee's email address]

</pre>

__TOC__

==Cory Doctorow==

Cory is a great speaker, and he is brilliant. He bridges the worlds of learning, technology, ethics, and sanity. He embraces the dystopian without being maudlin.
Doctorow married Alice Taylor in October 2008, and they have a daughter named Poesy Emmeline Fibonacci Nautilus Taylor Doctorow, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.

[https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]

[https://pluralistic.net pluralistic.net]

[https://craphound.com craphound.com]

[https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]
... and many more.

He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]

==Molly White==

From [https://www.mollywhite.net/ Molly's website]:

I research and write critically about the cryptocurrency industry and technology more broadly in the [https://www.citationneeded.news/ Citation Needed] newsletter. I also run the websites [https://www.web3isgoinggreat.com/ Web3 is Going Just Great], where I highlight examples of how cryptocurrencies, web3 projects, and the industry surrounding them are failing to live up to their promises, and [https://www.followthecrypto.org/ Follow the Crypto], where I track cryptocurrency industry spending in the 2024 election cycle. I spend a lot of time thinking about how to make a better, more human-centered web, and am a passionate advocate for free and open access, digital sovereignty, and ethical technology.

I regularly speak to journalists and do media appearances. I also have given talks and guest lectures, and have advised policymakers and regulators in and outside of the United States.

Before veering into spending so much of my time thinking about cryptocurrency and its implications for the web and society, I was a professional software engineer.

I have also been an active editor of the English Wikipedia for over fifteen years, where I edit under the username [https://en.wikipedia.org/wiki/User:GorillaWarfare GorillaWarfare]. I am an administrator and [https://en.wikipedia.org/wiki/Wikipedia:Functionaries functionary], and previously served three terms on the [https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee Arbitration Committee]. I care deeply about free and open access to high-quality information, and view projects like Wikipedia as critical infrastructure.

Not from Molly's website:

Molly has intelligent takes on issues of concern to Code4Lib. For example, here's her take on Controlled Digital Lending: [https://www.citationneeded.news/hachette-v-internet-archive/ Big publishers think libraries are the enemy]. She is likely to enjoy and learn from Code4Lib as we enjoy and learn from her.

She can be reached at [molly@mollywhite.net]

==Anne Washington==

Dr. Washington is a public interest technologist and professor of data policy at the NYU Steinhardt school. Her expertise on public sector information currently addresses the emerging governance needs of data science. She has an undergraduate degree in computer science, an MLIS, and a PhD in information systems. She's worked at the Library of Congress and is the Advisory Boards of the Electronic Privacy Information Center (EPIC) and the Open Government Foundation.

[https://annewashington.com/ web site]

[mailto:anne.washington@nyu.edu email address]

==Nikki Stevens==

Dr. Stevens is a faculty associate at Arizona State, maintainer of the [https://github.com/drnikki/open-demographics Open Demographics] project, and past postdoctoral researcher at MIT, in the [https://dataplusfeminism.mit.edu/ Data + Feminism Lab]. Formerly a software engineer, she studies how software engineering is situated in systems of power -- for instance, the ways that relational database architecture dovetails with carceral logics. She says "if you invite me for a talk (hint hint), I would give talks titled:

* “Abolitionist Data Practices: Applying political goals to data structures”
* “Is my database racist? How white supremacy structures our databases”
* “The history of data modeling” (this one is more exciting than it sounds, I swear!)
* “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”

[https://nikkistevens.com/ personal web site]

[mailto:nikki.stevens@asu.edu email]

==Cat Hicks==

Dr. Hicks is a psychologist studying developer thriving. Her social science research includes learning cultures, code review anxiety, and the psychological affordances of organizations. She says "I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity." I think we would be interested in her research, and she would also be interested in code4lib's overlap with and differences from industry tech culture.

[https://www.drcathicks.com/ web site]

[https://mastodon.social/@grimalkina mastodon]

[https://www.changetechnically.fyi/ podcast]

==Meredith Martin==

As Director of the Center for Digital Humanities at Princeton, she has pioneered interdisciplinary initiatives, fostering collaboration across departments and institutions worldwide. She co-chairs the Artificial Intelligence + Digital Humanities special interest group for the Association for Computers and the Humanities and is an editor of the Journal of Cultural Analytics. As Director of the Center for Digital Humanities at Princeton University, Professor Martin is a leading expert on the intersection of technology and the humanities. Her innovative work, including the Princeton Prosody Archive and forthcoming Poetry’s Data, explores how technologies like natural language processing and machine learning can transform humanities research. Professor Martin would provide a thought-provoking keynote, sparking meaningful discussions about the evolving role of technology in academia and beyond.

CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]

[mailto:mm4@princeton.edu Meredith Martin]

[https://www.dariah.eu/2024/10/17/meredith-martin-cdh-faculty-director-discusses-the-evolution-of-the-humanities-engagement-with-data-at-the-dariah-annual-event/ DARIAH EU]

== Ruth Kitchin Tillman ==

Ruth Kitchin Tillman works on discovery, the library catalog, and linked data projects at Penn State University Libraries. During her graduate school, she created [https://eadiva.com/ EADiva.com] for people who need to learn Encoded Archival Description (EAD) and still maintains the site. Her research primarily about working conditions of library staff. She was a co-PI in [https://laborforum.diglib.org/ Collective Responsibility], an IMLS-fund project that that investigated the labor conditions created by grants. She has written and presented on linked data, metadata encoding standards, library discovery, institutional repositories, and labor issues in libraries. Her current research focuses on the impacts of library systems migration and the staff who use and maintain them.

[https://ruthtillman.com/ Personal Website]

[https://github.com/ruthtillman Github]

[mailto:ruthtillman@gmail.com Email]

==Mukund Raghunath==
[https://www.linkedin.com/in/mukund-r-1158a31/ Mukund Raghunath], Founder & CEO of Acies Global, has several years of experience building organizations in the data and technology space and empowering Fortune 1000 clients in their digital transformation journey. Mukund is a passionate problem solver with a penchant for bringing together business fundamentals with first principles analytical thinking and cutting edge technology. He is an investor in and advisor to several startups in the technology and AI space. Mukund was previously part of the leadership team at Mu Sigma where he helped scale the organization from the ground up. His prior experiences also include stints at Motorola and ZS Associates. Outside of work, Mukund loves to travel the world and is on a constant endeavor to improve his golf handicap. Mukund has a Masters in Computer Science from the University of Illinois and an MBA with Honors from The University of Chicago, Booth School of Business.

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.

[mailto:jane@nowhere.foo janes_email_address]

2025 Keynote Speakers Nominations

2024-11-14T22:02:13Z

Ranti: /* Ruth Kitchin Tillman */

Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.

'''Nominations will close after November 21, 2024.'''

When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:

1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?

2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?

3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?

Please include a description and any relevant links. Please try to keep the list in alphabetical order.

We require the following information in your nomination for a candidate to act as keynote:
*Speaker’s full name
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information for candidate (email address)

The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Hardy Pottinger at [mailto:hardy.pottinger@ucsf.edu?Subject=CODE4LIB%20KEYNOTE%20NOMINATION hardy.pottinger@ucsf.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

[mailto:email_link.foo nominee's email address]

</pre>

__TOC__

==Cory Doctorow==

Cory is a great speaker, and he is brilliant. He bridges the worlds of learning, technology, ethics, and sanity. He embraces the dystopian without being maudlin.
Doctorow married Alice Taylor in October 2008, and they have a daughter named Poesy Emmeline Fibonacci Nautilus Taylor Doctorow, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.

[https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]

[https://pluralistic.net pluralistic.net]

[https://craphound.com craphound.com]

[https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]
... and many more.

He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]

==Molly White==

From [https://www.mollywhite.net/ Molly's website]:

I research and write critically about the cryptocurrency industry and technology more broadly in the [https://www.citationneeded.news/ Citation Needed] newsletter. I also run the websites [https://www.web3isgoinggreat.com/ Web3 is Going Just Great], where I highlight examples of how cryptocurrencies, web3 projects, and the industry surrounding them are failing to live up to their promises, and [https://www.followthecrypto.org/ Follow the Crypto], where I track cryptocurrency industry spending in the 2024 election cycle. I spend a lot of time thinking about how to make a better, more human-centered web, and am a passionate advocate for free and open access, digital sovereignty, and ethical technology.

I regularly speak to journalists and do media appearances. I also have given talks and guest lectures, and have advised policymakers and regulators in and outside of the United States.

Before veering into spending so much of my time thinking about cryptocurrency and its implications for the web and society, I was a professional software engineer.

I have also been an active editor of the English Wikipedia for over fifteen years, where I edit under the username [https://en.wikipedia.org/wiki/User:GorillaWarfare GorillaWarfare]. I am an administrator and [https://en.wikipedia.org/wiki/Wikipedia:Functionaries functionary], and previously served three terms on the [https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee Arbitration Committee]. I care deeply about free and open access to high-quality information, and view projects like Wikipedia as critical infrastructure.

Not from Molly's website:

Molly has intelligent takes on issues of concern to Code4Lib. For example, here's her take on Controlled Digital Lending: [https://www.citationneeded.news/hachette-v-internet-archive/ Big publishers think libraries are the enemy]. She is likely to enjoy and learn from Code4Lib as we enjoy and learn from her.

She can be reached at [molly@mollywhite.net]

==Anne Washington==

Dr. Washington is a public interest technologist and professor of data policy at the NYU Steinhardt school. Her expertise on public sector information currently addresses the emerging governance needs of data science. She has an undergraduate degree in computer science, an MLIS, and a PhD in information systems. She's worked at the Library of Congress and is the Advisory Boards of the Electronic Privacy Information Center (EPIC) and the Open Government Foundation.

[https://annewashington.com/ web site]

[mailto:anne.washington@nyu.edu email address]

==Nikki Stevens==

Dr. Stevens is a faculty associate at Arizona State, maintainer of the [https://github.com/drnikki/open-demographics Open Demographics] project, and past postdoctoral researcher at MIT, in the [https://dataplusfeminism.mit.edu/ Data + Feminism Lab]. Formerly a software engineer, she studies how software engineering is situated in systems of power -- for instance, the ways that relational database architecture dovetails with carceral logics. She says "if you invite me for a talk (hint hint), I would give talks titled:

* “Abolitionist Data Practices: Applying political goals to data structures”
* “Is my database racist? How white supremacy structures our databases”
* “The history of data modeling” (this one is more exciting than it sounds, I swear!)
* “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”

[https://nikkistevens.com/ personal web site]

[mailto:nikki.stevens@asu.edu email]

==Cat Hicks==

Dr. Hicks is a psychologist studying developer thriving. Her social science research includes learning cultures, code review anxiety, and the psychological affordances of organizations. She says "I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity." I think we would be interested in her research, and she would also be interested in code4lib's overlap with and differences from industry tech culture.

[https://www.drcathicks.com/ web site]

[https://mastodon.social/@grimalkina mastodon]

[https://www.changetechnically.fyi/ podcast]

==Meredith Martin==

As Director of the Center for Digital Humanities at Princeton, she has pioneered interdisciplinary initiatives, fostering collaboration across departments and institutions worldwide. She co-chairs the Artificial Intelligence + Digital Humanities special interest group for the Association for Computers and the Humanities and is an editor of the Journal of Cultural Analytics. As Director of the Center for Digital Humanities at Princeton University, Professor Martin is a leading expert on the intersection of technology and the humanities. Her innovative work, including the Princeton Prosody Archive and forthcoming Poetry’s Data, explores how technologies like natural language processing and machine learning can transform humanities research. Professor Martin would provide a thought-provoking keynote, sparking meaningful discussions about the evolving role of technology in academia and beyond.

CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]

[mailto:mm4@princeton.edu Meredith Martin]

[https://www.dariah.eu/2024/10/17/meredith-martin-cdh-faculty-director-discusses-the-evolution-of-the-humanities-engagement-with-data-at-the-dariah-annual-event/ DARIAH EU]

== Ruth Kitchin Tillman ==

Ruth Kitchin Tillman works on discovery, the library catalog, and linked data projects at Penn State University Libraries. During her graduate school, she created [https://eadiva.com/ EADiva.com] for people who need to learn Encoded Archival Description (EAD) and still maintains the site. Her research primarily about working conditions of library staff. She was a co-PI in [https://laborforum.diglib.org/ Collective Responsibility], an IMLS-fund project that that investigated the labor conditions created by grants. She has written and presented on linked data, metadata encoding standards, library discovery, institutional repositories, and labor issues in libraries. Her current research focuses on the impacts of library systems migration and the staff who use and maintain them.

[https://ruthtillman.com/ Personal Website]

[https://github.com/ruthtillman Github]

[mailto:ruth.tillman@gmail.com Email]

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.

[mailto:jane@nowhere.foo janes_email_address]

2025 Keynote Speakers Nominations

2024-11-14T21:58:28Z

Ranti:

Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.

'''Nominations will close after November 21, 2024.'''

When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:

1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?

2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?

3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?

Please include a description and any relevant links. Please try to keep the list in alphabetical order.

We require the following information in your nomination for a candidate to act as keynote:
*Speaker’s full name
*Brief description of individual (250-word max)
*Pertinent links (Maximum of 3)
*Contact information for candidate (email address)

The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.

''If you would prefer to submit a nomination anonymously, please send your nominee(s) to Hardy Pottinger at [mailto:hardy.pottinger@ucsf.edu?Subject=CODE4LIB%20KEYNOTE%20NOMINATION hardy.pottinger@ucsf.edu].''

Please follow the formatting guidelines:

<pre>

== Nominee's Name ==

Description of no more than 250 words.

[[Link(s) with contact information for nominee]]

[mailto:email_link.foo nominee's email address]

</pre>

__TOC__

==Cory Doctorow==

Cory is a great speaker, and he is brilliant. He bridges the worlds of learning, technology, ethics, and sanity. He embraces the dystopian without being maudlin.
Doctorow married Alice Taylor in October 2008, and they have a daughter named Poesy Emmeline Fibonacci Nautilus Taylor Doctorow, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.

[https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]

[https://pluralistic.net pluralistic.net]

[https://craphound.com craphound.com]

[https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]
... and many more.

He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]

==Molly White==

From [https://www.mollywhite.net/ Molly's website]:

I research and write critically about the cryptocurrency industry and technology more broadly in the [https://www.citationneeded.news/ Citation Needed] newsletter. I also run the websites [https://www.web3isgoinggreat.com/ Web3 is Going Just Great], where I highlight examples of how cryptocurrencies, web3 projects, and the industry surrounding them are failing to live up to their promises, and [https://www.followthecrypto.org/ Follow the Crypto], where I track cryptocurrency industry spending in the 2024 election cycle. I spend a lot of time thinking about how to make a better, more human-centered web, and am a passionate advocate for free and open access, digital sovereignty, and ethical technology.

I regularly speak to journalists and do media appearances. I also have given talks and guest lectures, and have advised policymakers and regulators in and outside of the United States.

Before veering into spending so much of my time thinking about cryptocurrency and its implications for the web and society, I was a professional software engineer.

I have also been an active editor of the English Wikipedia for over fifteen years, where I edit under the username [https://en.wikipedia.org/wiki/User:GorillaWarfare GorillaWarfare]. I am an administrator and [https://en.wikipedia.org/wiki/Wikipedia:Functionaries functionary], and previously served three terms on the [https://en.wikipedia.org/wiki/Wikipedia:Arbitration_Committee Arbitration Committee]. I care deeply about free and open access to high-quality information, and view projects like Wikipedia as critical infrastructure.

Not from Molly's website:

Molly has intelligent takes on issues of concern to Code4Lib. For example, here's her take on Controlled Digital Lending: [https://www.citationneeded.news/hachette-v-internet-archive/ Big publishers think libraries are the enemy]. She is likely to enjoy and learn from Code4Lib as we enjoy and learn from her.

She can be reached at [molly@mollywhite.net]

==Anne Washington==

Dr. Washington is a public interest technologist and professor of data policy at the NYU Steinhardt school. Her expertise on public sector information currently addresses the emerging governance needs of data science. She has an undergraduate degree in computer science, an MLIS, and a PhD in information systems. She's worked at the Library of Congress and is the Advisory Boards of the Electronic Privacy Information Center (EPIC) and the Open Government Foundation.

[https://annewashington.com/ web site]

[mailto:anne.washington@nyu.edu email address]

==Nikki Stevens==

Dr. Stevens is a faculty associate at Arizona State, maintainer of the [https://github.com/drnikki/open-demographics Open Demographics] project, and past postdoctoral researcher at MIT, in the [https://dataplusfeminism.mit.edu/ Data + Feminism Lab]. Formerly a software engineer, she studies how software engineering is situated in systems of power -- for instance, the ways that relational database architecture dovetails with carceral logics. She says "if you invite me for a talk (hint hint), I would give talks titled:

* “Abolitionist Data Practices: Applying political goals to data structures”
* “Is my database racist? How white supremacy structures our databases”
* “The history of data modeling” (this one is more exciting than it sounds, I swear!)
* “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”

[https://nikkistevens.com/ personal web site]

[mailto:nikki.stevens@asu.edu email]

==Cat Hicks==

Dr. Hicks is a psychologist studying developer thriving. Her social science research includes learning cultures, code review anxiety, and the psychological affordances of organizations. She says "I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity." I think we would be interested in her research, and she would also be interested in code4lib's overlap with and differences from industry tech culture.

[https://www.drcathicks.com/ web site]

[https://mastodon.social/@grimalkina mastodon]

[https://www.changetechnically.fyi/ podcast]

==Meredith Martin==

As Director of the Center for Digital Humanities at Princeton, she has pioneered interdisciplinary initiatives, fostering collaboration across departments and institutions worldwide. She co-chairs the Artificial Intelligence + Digital Humanities special interest group for the Association for Computers and the Humanities and is an editor of the Journal of Cultural Analytics. As Director of the Center for Digital Humanities at Princeton University, Professor Martin is a leading expert on the intersection of technology and the humanities. Her innovative work, including the Princeton Prosody Archive and forthcoming Poetry’s Data, explores how technologies like natural language processing and machine learning can transform humanities research. Professor Martin would provide a thought-provoking keynote, sparking meaningful discussions about the evolving role of technology in academia and beyond.

CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]

[mailto:mm4@princeton.edu Meredith Martin]

[https://www.dariah.eu/2024/10/17/meredith-martin-cdh-faculty-director-discusses-the-evolution-of-the-humanities-engagement-with-data-at-the-dariah-annual-event/ DARIAH EU]

== Ruth Kitchin Tillman ==

Ruth Kitchin Tillman works on discovery, the library catalog, and linked data projects at Penn State University Libraries. During her graduate school, she created [https://eadiva.com/ EADiva.com] for people who need to learn Encoded Archival Description (EAD) and still maintains the site. Her research primarily about working conditions of library staff. She was a co-PI in [https://laborforum.diglib.org/ Collective Responsibility], an IMLS-fund project that that investigated the labor conditions created by grants. Her current research focuses on the impacts of library systems migration and the staff who use and maintain them. She has written and presented on linked data, metadata encoding standards, library discovery, institutional repositories, and labor issues in libraries.

[https://ruthtillman.com/ Personal Website]

[https://github.com/ruthtillman Github]

[mailto:ruth.tillman@gmail.com Email]

==Jane Doe (example)==

Jane works at ________, doing _______.

Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.

[mailto:jane@nowhere.foo janes_email_address]

Code4Lib 2025 Conference Committees

2024-09-13T23:40:47Z

Ranti: /* Keynote Committee */

= Code4Lib Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2025 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact

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

[[2025 Planning Committee Documents|2025 Planning Committee Documents]]

* Esmé Cowles (Princeton) - Primary Contact, Chair
* Kate Lynch (Princeton) - Secondary Contact, Co-chair, documentarian
* Tracy Hall (Princeton) - Tertiary Contact
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2025 Website Working Group Documents|2025 Website Working Group Documents]]

* Esmé Cowles - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Trip Kirkpatrick - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2025 Budget and Sponsorship Documents]

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

== Keynote Committee ==
This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.

From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.

* Andromeda Yelton - Primary Contact, Chair
* Maccabee Levine - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Hardy Pottinger - Volunteer
* Ranti Junus - Volunteer
* Esmé Cowles - LPC Liaison

== Pre-conference Committee ==
This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2025 Pre-conference Documents|2025 Pre-conference Documents]]

* Your Name Here - Primary Contact, CoChair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* 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.

[[2025 Program Documents|2025 Program Documents]]

* Matt Sherman - Primary Contact, Chair
* Dre - Secondary Contact, CoChair
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* [[User:highermath|Cary Gordon]] - Volunteer
* Ken Varnum - Volunteer
* Steph Gritz (sgritz@lmu.edu) - 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.

* Your Name Here - Primary Contact, Chair
* Your Name Here - Secondary Contact, CoChair
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] (Brown University) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2025.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.

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

[[2025 T-Shirt Documents|2025 T-Shirt Documents]]

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

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2025 Online Volunteer Documents|2025 Online Volunteer Documents]]

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

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

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

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

== Streaming Video Committee ==
With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.

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

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

[[2026 Host Voting Documents|2026 Host Voting Documents]]

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

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

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

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

[[2025 IRC and Slack Documents|2025 IRC and Slack Documents]]

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

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

[[2025 Accessibility Documents|2025 Accessibility Documents]]

* Your Name Here - Primary Contact, Chair
* Your Name Here - Kate Deibel <[mailto:katheride@pcom.edu katheride@pcom.edu]>, Co-Chair
* 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.

[[2025 Whatever Documents|2025 Whatever Documents]]

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

[[Category: Code4Lib2025]]

Code4Lib2024 Lightning Talks

2024-05-16T00:10:34Z

Ranti: /* Wednesday, May 15, 1:35 - 2:35pm */

== Tuesday, May 14, 10:20-11:05am ==

1. Jonathan Rochkind: "A local page viewer for digitized historical material”

2. Jenn Colt: [https://osf.io/cnpve/ "FOLIO: It's not just..."]

3. Vera Kahn: "Progamming Protest"

4. Shinwoo Kim: "Lambda fixity process"

5. Eric Lease Morgan: "Free GSU!"

6. Cary Gordon: "Let find a host for 2025 Code4Lib"

7. Barbara Cormack: [https://osf.io/ry7vt/ "Metadata Analysis in Zephir and HathiTrust"]

8. Natasha Allen: "A Brief History of Fowling"

== Wednesday, May 15, 10:15-11:15am ==

1. Micah Walter: [https://osf.io/fepqc/ "Smith Inventory System: How it works and lessons learned"]

2. Maccabee Levine: [https://docs.google.com/presentation/d/1dxnGKLbSbM05JptxTm-1nKz_6UVqM9EE4rZmGwLogAA/edit "Bound-with Titles in FOLIO and VuFind"]

3. Eric Hellman: Browser Extension Rant

4. Michael Klein: “Things my grandfather told me [30 years later, with the help of AI audio transcription]”

5. Dee Dee Crema: [https://osf.io/m83t5/ ETDs@Harvard]

6. Patrick Galligan: [https://osf.io/h4ud3/ On Not choosing Kubernetes OR it's OK to fail]

7. Angela Zoss: [https://osf.io/tqhye Three(ish) Tips for Better Data Visualization]

8. Steve Bischof: Learning from Poggio Civitate: Data Verification

9. Thomas Dowling: [https://oatd.org Open Access Theses and Dissertations]

== Wednesday, May 15, 1:35 - 2:35pm ==

1. Emily Frazier: [https://osf.io/p6vyr/ Sometimes You Can't Automate It!]

2. Ray Schwartz: [https://detroitography.com/ What about Detroit?]

3. Kate Deibel: [https://osf.io/j8k69/ New US Federal A11y Laws Ready to Pounce]

4. Corey Halpin: How I hope the history of computing in chess predicts AI in libraries.

5. Susan Hoover: [https://osf.io/v4egb/ Ten Thousand]

6. Harpo Harbert: [https://osf.io/ve6ut/ Battle of the Bots]

7. Ange Zaytsev: [https://osf.io/z4jen/ Making Your Slides More Accessible]

8. Roger Espinosa: [https://osf.io/6av2f/ Digital Collections: 25 years in 5 minutes]

9. Anne Slaughter: [https://www.benton.org/visions-digital-equity/state-vision Digital Equity and Libraries]

10. Chad Nelson: Are we just hallucinating AI?

Code4Lib2024 Lightning Talks

2024-05-16T00:09:20Z

Ranti: /* Wednesday, May 15, 1:35 - 2:35pm */

== Tuesday, May 14, 10:20-11:05am ==

1. Jonathan Rochkind: "A local page viewer for digitized historical material”

2. Jenn Colt: [https://osf.io/cnpve/ "FOLIO: It's not just..."]

3. Vera Kahn: "Progamming Protest"

4. Shinwoo Kim: "Lambda fixity process"

5. Eric Lease Morgan: "Free GSU!"

6. Cary Gordon: "Let find a host for 2025 Code4Lib"

7. Barbara Cormack: [https://osf.io/ry7vt/ "Metadata Analysis in Zephir and HathiTrust"]

8. Natasha Allen: "A Brief History of Fowling"

== Wednesday, May 15, 10:15-11:15am ==

1. Micah Walter: [https://osf.io/fepqc/ "Smith Inventory System: How it works and lessons learned"]

2. Maccabee Levine: [https://docs.google.com/presentation/d/1dxnGKLbSbM05JptxTm-1nKz_6UVqM9EE4rZmGwLogAA/edit "Bound-with Titles in FOLIO and VuFind"]

3. Eric Hellman: Browser Extension Rant

4. Michael Klein: “Things my grandfather told me [30 years later, with the help of AI audio transcription]”

5. Dee Dee Crema: [https://osf.io/m83t5/ ETDs@Harvard]

6. Patrick Galligan: [https://osf.io/h4ud3/ On Not choosing Kubernetes OR it's OK to fail]

7. Angela Zoss: [https://osf.io/tqhye Three(ish) Tips for Better Data Visualization]

8. Steve Bischof: Learning from Poggio Civitate: Data Verification

9. Thomas Dowling: [https://oatd.org Open Access Theses and Dissertations]

== Wednesday, May 15, 1:35 - 2:35pm ==

1. Emily Frazier: [https://osf.io/p6vyr/ Sometimes You Can't Automate It!]

2. Ray Schwartz: [https://detroitography.com/ What about Detroit?]

3. Kate Deibel: [https://osf.io/j8k69/ New US Federal A11y Laws Ready to Pounce]

4. Corey Halpin: How I hope the history of computing in chess predicts AI in libraries.

5. Susan Hoover: [https://osf.io/v4egb/ Ten Thousand]

6. Harpo Harbert: [https://osf.io/ve6ut/ Battle of the Bots]

7. Ange Zaytsev: Making Your Slides More Accessible

8. Roger Espinosa: [https://osf.io/6av2f/ Digital Collections: 25 years in 5 minutes]

9. Anne Slaughter: [https://www.benton.org/visions-digital-equity/state-vision Digital Equity and Libraries]

10. Chad Nelson: Are we just hallucinating AI?

Code4Lib2024 Lightning Talks

2024-05-15T20:05:41Z

Ranti: Afternon list

== Tuesday, May 14, 10:20-11:05am ==

1. Jonathan Rochkind: "A local page viewer for digitized historical material”

2. Jenn Colt: [https://osf.io/cnpve/ "FOLIO: It's not just..."]

3. Vera Kahn: "Progamming Protest"

4. Shinwoo Kim: "Lambda fixity process"

5. Eric Lease Morgan: "Free GSU!"

6. Cary Gordon: "Let find a host for 2025 Code4Lib"

7. Barbara Cormack: [https://osf.io/ry7vt/ "Metadata Analysis in Zephir and HathiTrust"]

8. Natasha Allen: "A Brief History of Fowling"

== Wednesday, May 15, 10:15-11:15am ==

1. Micah Walter: [https://osf.io/fepqc/ "Smith Inventory System: How it works and lessons learned"]

2. Maccabee Levine: [https://docs.google.com/presentation/d/1dxnGKLbSbM05JptxTm-1nKz_6UVqM9EE4rZmGwLogAA/edit "Bound-with Titles in FOLIO and VuFind"]

3. Eric Hellman: Browser Extension Rant

4. Michael Klein: “Things my grandfather told me [30 years later, with the help of AI audio transcription]”

5. Dee Dee Crema: [https://osf.io/m83t5/ ETDs@Harvard]

6. Patrick Galligan: [https://osf.io/h4ud3/ On Not choosing Kubernetes OR it's OK to fail]

7. Angela Zoss: [https://osf.io/tqhye Three(ish) Tips for Better Data Visualization]

8. Steve Bischof: Learning from Poggio Civitate: Data Verification

9. Thomas Dowling: [https://oatd.org Open Access Theses and Dissertations]

== Wednesday, May 15, 1:35 - 2:35pm ==

1. Emily Frazier: [https://osf.io/p6vyr/ Sometimes You Can't Automate It!]

2. Ray Schwartz: [https://detroitography.com/ What about Detroit?]

3. Kate Deibel: [https://osf.io/j8k69/ New US Federal A11y Laws Ready to Pounce]

4. Corey Halpin: On Things

5. Susan Hoover: [https://osf.io/v4egb/ Ten Thousand]

6. Harpo Harbert: [https://osf.io/ve6ut/ Battle of the Bots]

7. Ange Zaytsev: Making Your Slides More Accessible

8. Roger Espinosa: [https://osf.io/6av2f/ Digital Collections: 25 years in 5 minutes]

9. Anne Slaughter: [https://www.benton.org/visions-digital-equity/state-vision Digital Equity and Libraries]

10. Chad Nelson: Are we just hallucinating AI?

Code4Lib2024 Breakout Sessions

2024-05-15T18:38:14Z

Ranti: Refine list

== Tuesday, May 14, 2:15-3:15pm ==

1. ArchivesSpace tech update & community chat

2. Patron and Data Privacy

3. Transcriptions (video, audio, image) using Whisper OpenAI, google AI, etc.

4. Advocacy & Retrenchment: How do we continue our work in this world?

== Wednesday, May 15, 2:35-3:20pm ==

1. Let’s Talk C4L2025!

2. FOLIO meet and greet: interested and adopters

3. Digitization Project Management

4. Centralized IT… how do you function? Gripe session.

5. Did you bring a fountain pen? Let’s Chat!

6. Stupid GPT Tricks and other AI research tool experience

7. Shape-note singing

Code4Lib2024 Breakout Sessions

2024-05-15T18:37:40Z

Ranti: Add more breakouts

== Tuesday, May 14, 2:15-3:15pm ==

1. ArchivesSpace tech update & community chat

2. Patron and Data Privacy

3. Transcriptions (video, audio, image) using Whisper OpenAI, google AI, etc.

4. Advocacy & Retrenchment: How do we continue our work in this world?

== Wednesday, May 15, 2:35-3:20pm ==

1. Let’s Talk C4L2025!

2. FOLIO meet and greet: interested and adopters

3. Digitization Project Management

4. Centralized IT… how do you function? Gripe session.

5: Did you bring a fountain pen? Let’s Chat!

6: Stupid GPT Tricks and other AI research tool experience

7: Shape-note singing

2.

3.

Code4Lib 2023 Conference Committees

2022-09-29T19:35:13Z

Ranti: /* Program Committee */

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Location: Princeton University
* Dates: TBD

== Local Planning Committee ==
The LPC is charged with running the show such as overall timeline, budgeting, coordinating of locations and logistics, wrangler of committees, and communicating with the community.

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* NAME - (EMAIL) - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* 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.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* 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.

[[2023 Program Documents|2023 Program Documents]]

* Matt Sherman - (matt.r.sherman@gmail.com) - Primary Contact, Chair
* Dre (akorphan) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus (junus-at-msu-edu) - Volunteer
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]] - 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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator:

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

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

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

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - 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 possibly running the camera during the conference.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

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

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

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (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).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - 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.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib 2023 Conference Committees

2022-09-07T22:12:44Z

Ranti: /* Keynote Committee */

= Code4Lib 2023 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2023 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Location: Princeton University
* Dates: TBD

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

* Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact
* Esmé Cowles - (escowles@princeton.edu) - Documentarian & Secondary Contact
* NAME - (EMAIL) - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2023 Website Working Group Documents|2023 Website Working Group Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* 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.

[[2023 Keynote Documents|2023 Keynote Documents]]

[[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Ranti Junus - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2023 Pre-conference Documents|2023 Pre-conference Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* 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.

[[2023 Program Documents|2023 Program Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Dre (akorphan) - Volunteer
* Matt Sherman - 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.

[[2023 Scholarship Documents|2023 Scholarship Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers

* Coordinator:

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

[[2023 T-Shirt Documents|2023 T-Shirt Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Social Activities Committee ==

This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences.

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

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - 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.

[[2023 Streaming Video Documents|2023 Streaming Video Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (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).

[[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 Accessibility Documents|2023 Accessibility Documents]]

* Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - 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.

[[2023 Whatever Documents|2023 Whatever Documents]]

* NAME - (EMAIL) - Primary Contact, Chair
* NAME - (EMAIL) - Secondary Contact, CoChair
* NAME - (EMAIL) - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2023]]

Code4Lib 2022 Conference Committees

2021-09-15T21:33:33Z

Ranti: /* Website Working Group */

= Code4Lib 2022 Conference Committees =

Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2022 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Your Name Here -conferences:

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

* Omar Brown - (omarbrow@buffalo.edu) - Tertiary Contact
* Blake Carver - (blake.carver@lyrasis.org) - Tertiary Contact
* Karlen Chase - (klchase@buffalo.edu) - Chair, Primary Contact
* Sarah Cogley - (smpinard@buffalo.edu) - Documentarian & Secondary Contact
* Francis Kayiwa - (kayiwa@princeton.edu) - Tertiary Contact
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Tertiary Contact
* Molly Maloney - (mkm9@buffalo.edu) - Tertiary Contact
* Amanda McCormick - (afm33@buffalo.edu) - Tertiary Contact
* Rose Orcutt - (rmorcutt@buffalo.edu) - Tertiary Contact

== Website Working Group ==
This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

[[2022 Website Working Group Documents|2022 Website Working Group Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Blake Carver - (blake.carver@lyrasis.org) - Planning Committee Contact
* Your Name Here - Documentarian
* Ranti Junus (Michigan State University) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget and Sponsorship Committee ==
This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2022 Budget and Sponsorship Documents|2022 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Sarah Cogley - (smpinard@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* - ex officio, fiscal host (CLIR/DLF)

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

[[2022 Keynote Documents|2022 Keynote Documents]]

[[2022 Keynote Speakers Nominations|2022 Keynote Speakers Nominations]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Francis Kayiwa - (kayiwa@princeton.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer
* Your Name Here - Volunteer

== Pre-conference Committee ==
This committee plans the post-conference day. It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.

[[2022 Pre-conference Documents|2022 Pre-conference Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Documentarian/Planning Committee Contact
* 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.

[[2022 Program Documents|2022 Program Documents]]

* Your Name Here - Primary Contact AKA Chair
* Daricus Larry (dlarry@arizona.edu) - Secondary Contact AKA CoChair
* Karlen Chase - (klchase@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Matt Sherman (matt.r.sherman@gmail.com) - Volunteer
* Dre (akorphan@ncsu.edu) - Volunteer
* Jingjing Wu(jingjing.wu@ttu.edu) - 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.

[[2022 Scholarship Documents|2022 Scholarship Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Amanda McCormick - (afm33@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer
* Your Name Here - Volunteer

== Community Support Squad (CSS) ==
This group enforces [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees.

'''Community Support Volunteers'''

[[2022 Community Support Documents|2022 Community Support Documents]]

* Your Name Here - Co-Coordinator
* Your Name Here - Co-Coordinator

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

[[2022 T-Shirt Documents|2022 T-Shirt Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Molly Maloney - (mkm9@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Online Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2022 Online Volunteer Documents|2022 Online Volunteer Documents]]

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

== Social Activities Committee ==

This committee organizes virtual social activities.

2022 Social Activities Documents - Contact [[User:Yoosebj|Becky]] for access to the Google Drive folder

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Rose Orcutt - (rmorcutt@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* 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.

[[2022 Streaming Video Documents|2022 Streaming Video Documents]]

* [[User:DataGazetteer|Peter Murray]] - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Omar Brown - (omarbrow@buffalo.edu) - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2023 Host Voting Documents|2023 Host Voting Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* 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).

[[2022 Book Giveaway Documents|2022 Book Giveaway Documents]]

* Your Name Here - Primary Contact AKA Chair
* Your Name Here - Secondary Contact AKA CoChair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2022 IRC and Slack Documents|2022 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Planning Committee Contact
* Your Name Here - Documentarian
* Daricus Larry (dlarry@arizona.edu) - Volunteer

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

[[2022 Accessibility Documents|2022 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Carolyn Klotzbach-Russell - (cmklotzb@buffalo.edu) - Planning Committee Contact
* 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.

[[2022 Whatever Documents|2022 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Documentarian
* Your Name Here - Planning Committee Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

[[Category:Code4Lib2022]]

Code4Lib 2020 Conference Committees

2019-06-10T14:25:28Z

Ranti: /* Website Working Group */

= Code4Lib 2020 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 2020 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA
* Dates: March 08 (pre-con) - 22, 2020
** Pre-conferences: March 08, 2020
** Main meeting: March 09-11, 2020
** Post conference activities: Coming Soon

== 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:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact
* [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact
* [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact
* [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact
* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact
* [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact
* [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact
* [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact
* [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact
* [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2020 Website Working Group Documents|2020 Website Working Group Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Julia Caffrey (newbie) - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [[User:KaitlinNewson|Kaitlin Newson]] (veteran) - Volunteer/Program committee contact
* [[User:Ranti|Ranti Junus]] (v) - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]

* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)
* Your Name Here - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* [mailto:kerchner@gwu.edu Dan Kerchner] - Volunteer

== Sponsorship Committee ==
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship 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 - Documentarian
* Your Name Here - 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.

[[2020 Keynote Documents|2020 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - 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.

[[2020 Pre-conference Documents|2020 Pre-conference Documents]]

* Your Name Here - Primary Contact aka Chair
* 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

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

[[2020 Program Documents|2020 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact
* [mailto:lillyho@gmail.com Lilly Ho] - Volunteer
* [[User:KaitlinNewson|Kaitlin Newson]] - Volunteer/Web committee contact
* [mailto:mardenj@carnegielibrary.org Julia Marden] Carnegie Library of Pittsburgh - Documentarian? (new!)
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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.

[[2020 Scholarship Documents|2020 Scholarship Documents]]

* Your Name Here - Primary Contact aka Co-Chair
* Your Name Here - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2020 T-Shirt Documents|2020 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Onsite Volunteer Committee ==

This committee wrangles people to volunteer for the following duties:

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

[[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact
* Your Name Here - Documentarian
* 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).

[https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]

Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]

* [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair
* [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2020 Streaming Video Documents|2020 Streaming Video Documents]]

* [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )
* [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair
* [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)
* [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer

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

[[2021 Host Voting Documents|2021 Host Voting Documents]]

* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Roy Tennant - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:lillyho@gmail.com Lilly HS HO] - 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).

[[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]

* [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2020 IRC and Slack Documents|2020 IRC and Slack 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 - Documentarian
* Your Name Here - Volunteer

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

[[2020 Accessibility Documents|2020 Accessibility Documents]]

* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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.

[[2020 Whatever Documents|2020 Whatever Documents]]

* [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2020]]

Code4Lib2019 Lightning Talks

2019-02-22T23:13:30Z

Ranti: Add link to Spina's talk /* Day 3 - February 22, 2019 */

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface - Stefana Breitwieser, Canadian Centre for Architecture - [[https://github.com/CCA-Public/dip-access-interface github]] [[https://journal.code4lib.org/articles/14283 more info]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo

== Day 3 - February 22, 2019 ==
# [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis
# [https://osf.io/x75bk/ What is Audio Description] - Carli Spina
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark
# Web-based AR. Simple! - Dan Lou
# We Are Family - Code4Lib Local Chapters - Thomas Guignard
# Making a staff calendar: an intro to automation - Zach Pell
# Speed mentoring/skill share
#

Code4Lib2019 Lightning Talks

2019-02-22T23:12:34Z

Ranti: Fix link to Deibel's talk

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface - Stefana Breitwieser, Canadian Centre for Architecture - [[https://github.com/CCA-Public/dip-access-interface github]] [[https://journal.code4lib.org/articles/14283 more info]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo

== Day 3 - February 22, 2019 ==
# [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis
# What is Audio Description - Carli Spina
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark
# Web-based AR. Simple! - Dan Lou
# We Are Family - Code4Lib Local Chapters - Thomas Guignard
# Making a staff calendar: an intro to automation - Zach Pell
# Speed mentoring/skill share
#

Code4Lib2019 Lightning Talks

2019-02-22T20:19:08Z

Ranti: link to mirador talk

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface - Stefana Breitwieser, Canadian Centre for Architecture - [[https://github.com/CCA-Public/dip-access-interface github]] [[https://journal.code4lib.org/articles/14283 more info]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo

== Day 3 - February 22, 2019 ==
# [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis
# What is Audio Description - Carli Spina
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark
# Web-based AR. Simple! - Dan Lou
# We Are Family - Code4Lib Local Chapters - Thomas Guignard
# Making a staff calendar: an intro to automation - Zach Pell
# Speed mentoring/skill share
#

Code4Lib2019 Lightning Talks

2019-02-22T19:32:27Z

Ranti: link to jaclark talk

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - [https://osf.io/c2459 Slides] and [https://docs.google.com/document/d/1yu6bH5KDqg81oGwKujRAXOeGfkkrQtY7Fsmhn8wbaPk/edit?usp=sharing Notes] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo

== Day 3 - February 22, 2019 ==
# Mirador 3.0 Status Report - Shaun Ellis
# What is Audio Description - Carli Spina
# [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark
# Web-based AR. Simple! - Dan Lou
# We Are Family - Code4Lib Local Chapters - Thomas Guignard
# Making a staff calendar: an intro to automation - Zach Pell
# Speed mentoring/skill share
#

Code4Lib2019 Breakout Sessions

2019-02-21T23:25:42Z

Ranti: link to LUX

Keep an eye on this page for the full list of Code4Lib 2019 Breakout Sessions.

For directions to rooms, see the [https://doubletree3.hilton.com/resources/media/dt/JOSE-DT/en_US/pdf/JOSE.Floorplans.May04.pdf San Jose DoubleTree floor map]. We are in the Bayshore Ballroom (Sierra, Cascade, Siskiyou, Donner) on the lower level.

== Day One Breakouts 3:00pm ==

* '''Code4Lib conference budgeting and sustainability'''
** San Martin room (1st floor to the left of the elevators in the city foyer)
** [https://meet.google.com/pmx-csog-gvc Google Hangout] for remote participation
** [https://docs.google.com/presentation/d/1jAqnEoz92tWmoWRF1LShYSuf8_s08xKrjllHryDLvAU/edit?usp=sharing Slides: #Money4Code4Lib: Code4Lib Annual Conference Finances 2017-2019]
** [https://docs.google.com/document/d/1xk2OFy8GsuTeLCjXd3naieRj36y1nWI42gBnpgVvPrc/edit?usp=sharing Shared notes]

* '''Code4Lib Website Feedback'''
** San Jose room (1st floor to the left of the elevators in the pool foyer)
** Come learn about the website group that maintains the conference website and help us make it better!

* '''What's New with Archivematica?'''
** Santa Clara (1st floor to the left of the elevators in the pool foyer)

* '''Post-Makerspaces: What's next? What's working? What Flopped?'''
** Monterey (1st floor to the left of the elevators in the pool foyer)

* '''Islandora'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)

* '''Mentoring Program for C4L Community'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)

* '''Inclusive Metadata'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)

* '''Thinking of ditching Fedora or already have? Let's talk?'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)

* '''Decentralized Web Primer and Q&A'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)
** Interactive session introducing and demystifying the concepts, technologies and motivations of the decentralized web (ie. peer to peer protocols, content-addressing, etc), with an opportunity to ask questions.

* '''Datapipeline 4 Lib'''
** 2nd Floor Lunch space (Oak, Fir, Pine, Cedar)

== Day Two Breakouts 2:15pm ==

* Code4Lib 2020 Host Proposals - join the 2019 LPC, Concentra, and the 2020 Host Voting committee to learn about creating a hosting proposal and running the conference. (San Jose)
** [https://docs.google.com/document/d/17_kNihDQu9Pce1uqSmIHf2y6zLgiLDMalvWqNZP0HNo/edit Shared notes]
* Regional Code4lib Groups (San Martin)
* Working with ArchivesSpace (Monterey)
* Achieving Privacy in the Age of Analytics (Santa Clara)
* We Here Group Meeting (Lunch Room)
* Speed 2: The Mentoring (Lunch Room)
* Front End Design Systems (Lunch Room)
** LUX Design System: [https://github.com/pulibrary/lux github], [https://pulibrary.github.io/lux/docs/ documentation], [https://codepen.io/axamei/pen/exKWaO codepen]

Code4Lib2019 Lightning Talks

2019-02-21T23:08:27Z

Ranti: /* Day 2 - February 21, 2019 */

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T22:54:35Z

Ranti:

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity - Mike Giarlo

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T22:52:49Z

Ranti:

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity - Mike Giarlo

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

2019 Conference Volunteers

2019-02-21T22:49:08Z

Ranti:

= Code4Lib 2019 Conference Volunteers =

Call for volunteers during the actual conference, as opposed to the conference planning committees.

== Community Support Volunteers ==

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

Onsite Volunteer Committee Coordinator: N/A

* Karen Coyle
* Justin Coyne
* Shaun Ellis
* Erin Fahy
* Bobbi Fox
* Wayne Graham
* Francis Kayiwa
* Megan Kudzia
* Anne Slaughter

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

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

Onsite Volunteer Committee Coordinator:

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

Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]

Monday, day before:
* 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]
* 3pm - 6pm: [[User:Kimpham54|Kim Pham]]
* 3pm - 6pm: [[User:rtennant|Roy Tennant]]
* 3pm - 6pm: [[User:Anarchivist|Mark Matienzo]]

Tuesday, preconference day:
* 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]
* 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]
* 1pm - 3pm: ''Your Name Here''

Wednesday, day one:
* 8am - 9:30am: [[User:KaitlinNewson|Kaitlin Newson]]

== Social Events ==

Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc. Game Night is in the Hotel this year.

Onsite Volunteer Committee Coordinator:

Wednesday, Day One:
* 6:30-7:30pm Reception: [[User:tallgood|Tammy Allgood Wolf]] (need to be at venue at 6:30pm so on the first bus or arrive on their own)
* 6:30-7:30pm Reception: ''Your Name Here'' (ditto)
* 7:30-8:30pm Reception: ''Your Name Here''
* https://www.thetech.org/floor-maps Floor Map. Lower Level

Thursday, Day Two:
* 9:30-10pm Game Night Cleanup: [[User:Phette23|Eric Phetteplace]]
* 9:30-10pm Game Night Cleanup: [[User:hardyoyo|Hardy Pottinger]]

== Social Networking ==

Answering general questions on Twitter (#c4l19), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)

Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]

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

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

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

Friday, Day Three:
* AM volunteer: ''Your Name Here''

== Mic-minders ==

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

Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]

Wednesday, Day Two:
* AM volunteer: [[User:Kimpham54|Kim Pham]]
* AM volunteer: Thomas Guignard
* PM volunteer: Lydia Zvyagintseva
* PM volunteer: Nathan W

Thursday, Day Three:
* AM volunteer: ''Whitni''
* AM volunteer: Thomas Guignard
* PM volunteer: [[User:ChrisDay|Chris Day]]
* PM volunteer: Lydia Zvyagintseva

Friday, Day Four:
* AM volunteer: [[User:ChrisDay|Chris Day]]
* AM volunteer: [[User:Gmcharlt|Galen Charlton]]

== Livestream Assistants (Onsite) ==

Livestream assistants will help the livestream technicians in the presentation room, troubleshooting video and audio connections at the podium, and monitoring the encoding computer. Two people are needed for each shift. You are welcome to sign up for multiple shifts!

Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]

Wednesday, Day Two:
* AM Volunteer: Cary Gordon
* AM Volunteer: [[User:rtennant|Roy Tennant]]
* PM Volunteer: [[User:JerryWaller|Jerry Waller]]
* PM Volunteer: [mailto:fu@usna.edu Li Fu]

Thursday, Day Three:
* AM Volunteer: [[User:rtennant|Roy Tennant]]
* AM Volunteer: ''Your Name Here''
* PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]
* PM Volunteer: ''Your Name Here''

Friday, Day Four:
* AM Volunteer: [[User:rtennant|Roy Tennant]]
* AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]

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

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

Onsite Volunteer Committee Coordinator: Hardy Pottinger

Wednesday, Day Two:
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)

Thursday, Day Three:
* AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);
* PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)

Friday, Day Four:
* AM Volunteer: Ranti Junus (East); Kevin Clair (West); Melissa Johnson (West)

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

Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]

* Before the conference: [[User:Kimpham54|Kim Pham]] & [[User:Anarchivist|Mark Matienzo]]
* During the conference: [[User:Anarchivist|Mark Matienzo]] & [[User:Kimpham54|Kim Pham]]

==MCs==

Onsite Volunteer Committee Coordinator: [[User:tallgood|Tammy Allgood Wolf]]

Wednesday, Day One:
* AM Volunteer: Dre
* PM Volunteer: Whitni

Thursday, Day Two:
* AM Volunteer: [http://mailto:phette23@gmail.com Eric Phetteplace]
* PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]

Friday, Day Three:
* AM Volunteer: [[User:rtennant|Roy Tennant]]

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

Onsite Volunteer Committee Coordinator:

Wednesday, Day Two:
* AM Volunteer: Kim Pham
* PM Volunteer: Whitni

Thursday, Day Three:
* AM Volunteer: Kim Pham
* PM Volunteer: Whitni

Friday, Day Four:
* AM Volunteer: [[User:msuranofsky|Michelle Suranofsky]]

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

* [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail
* [[User:rtennant|Roy Tennant]]
* [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu
* [[User:JerryWaller|Jerry Waller]] - jerrywaller on slack
* ''Your Name Here''
* ''Your Name Here''

future potential volunteers:

podium tech help

[[Category: Code4Lib2019]]

Code4Lib2019 Lightning Talks

2019-02-21T19:34:01Z

Ranti:

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# Preserve this Podcast - Sarah Nguyen [[http://preservethispodcast.org/ website]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel
# Code4lib Continuity - Mike Giarlo

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T19:25:48Z

Ranti: link to kate's presentation

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# Preserve this Podcast - Sarah Nagen [[http://preservethispodcast.org/ website]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# [https://www.dropbox.com/s/xkhokvtawzm3mji/deibel-keyboard-accessibility.pptx?dl=0 Keyboard Accessibility Testing] - Kate Deibel
#
#
#

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T19:19:14Z

Ranti: link to hyku github

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# Preserve this Podcast - Sarah Nagen [[http://preservethispodcast.org/ website]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]
# Profiles Core - Karen Coyle
# Kate Deibel
#
#
#

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T19:10:12Z

Ranti: link to preserve this podcast website

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface [[https://github.com/CCA-Public/dip-access-interface github]]
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

== Day 2 - February 21, 2019 ==
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)
# The Patron Data Firehose - David Lacy
# Preserve this Podcast - Sarah Nagen [[http://preservethispodcast.org/ website]]
# The Real World of Technology - Ashley Blewer
# Hyku - Samvera in a Box
# Profiles Core - Karen Coyle
#
#
#
#

== Day 3 - February 23, 2019 ==
#
#
#
#
#
#
#
#
#
#

Code4Lib2019 Lightning Talks

2019-02-21T01:12:15Z

Ranti: Links for Day 1

Code4Lib2019 Lightning Talks

2019-02-21T00:59:41Z

Ranti: add link to Matienzo talk

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM (Review, Appraisal and Triage of Emails)- Cal Lee
# Cataloging Interface for Linked Data - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo

Code4Lib2019 Lightning Talks

2019-02-21T00:47:27Z

Ranti: expand RATOM acronym

Code4Lib2019 Lightning Talks

2019-02-21T00:42:30Z

Ranti: Add Ethan Gates

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization - Ethan Gates
# RATOM - Cal Lee
# Cataloging Interface for Linked Data - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface
# Whither CSV's? - Mark Matienzo

Code4Lib2019 Lightning Talks

2019-02-21T00:32:36Z

Ranti: Link to Tampakis presentation

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers
# Does your catalog spark joy? - Sean Aery
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization
# RATOM - Cal Lee
# Cataloging Interface for Linked Data - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface
# Whither CSV's? - Mark Matienzo

Code4Lib2019 Lightning Talks

2019-02-21T00:22:59Z

Ranti: add Matienzo talk

== Day 1 - February 20, 2019 ==
# Islandora for All: ISLE - community engagement and lowering barriers
# Does your catalog spark joy? - Sean Aery
# Implementing a redesign from user feedback - Nikitas Tampakis
# What a baby taught me about affordances - Dre
# Wait, what? Getting your bearings with server spec - Hardy
# EaaSI project update: Call for community feedback on software prioritization
# RATOM - Cal Lee
# Cataloging Interface for Linked Data - Jeremy Nelson + Naomi D.
# SCOPE: a born digital access interface
# Whither CSV's? - Mark Matienzo

Code4Lib2019 Lightning Talks

2019-02-20T23:11:51Z

Ranti: add day-1 talks

Code4Lib 2019 Conference Committees

2018-06-06T07:55:00Z

Ranti: /* Website Working Group */

= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Location: Bay Area, California (more info coming soon)
* Dates: we're looking at February-April, 2019
** Pre-conferences: Coming Soon
** Main meeting: Coming Soon
** Post conference activities: Coming Soon

== 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:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact
* Ray Pun, Fresno State - 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).

[[2019 Website Working Group Documents|2019 Website Working Group Documents]]

* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact
* Your Name Here - Documentarian
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Mark Matienzo - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* [mailto:swayh@oclc.org Hank Sway] - Volunteer
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)

== Sponsorship Committee ==
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)
* 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.

[[2019 Keynote Documents|2019 Keynote 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 - Documentarian
* 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.

[[2019 Pre-conference Documents|2019 Pre-conference Documents]]

* Your Name Here - Primary Contact aka Chair
* 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

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

[[2019 Program Documents|2019 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.

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

[[2019 Scholarship Documents|2019 Scholarship Documents]]

* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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.

[[2019 T-Shirt Documents|2019 T-Shirt 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 - Documentarian
* Your Name Here - Volunteer

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

[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]

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

[[2019 Social Activities Documents|2019 Social Activities Documents]]

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

* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Streaming Video Documents|2019 Streaming Video Documents]]

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]

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

[[2019 Book Giveaway Documents|2019 Book Giveaway 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 - Documentarian
* 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.

[[2019 IRC and Slack Documents|2019 IRC and Slack 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 - Documentarian
* Your Name Here - Volunteer

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

[[2019 Accessibility Documents|2019 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Whatever Documents|2019 Whatever 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 - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2019]]

Code4Lib 2019 Conference Committees

2018-06-06T07:54:42Z

Ranti: /* Website Working Group */

= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.

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

== Location and Dates ==

* Location: Bay Area, California (more info coming soon)
* Dates: we're looking at February-April, 2019
** Pre-conferences: Coming Soon
** Main meeting: Coming Soon
** Post conference activities: Coming Soon

== 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:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact
* Ray Pun, Fresno State - 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).

[[2019 Website Working Group Documents|2019 Website Working Group Documents]]

* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact
* Your Name Here - Documentarian
* [[User:Ranti|Ranti Junus]].Michigan State University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Budget Committee ==
This group will focus on making sure we are appropriately planning for budgetary issues.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Mark Matienzo - Local Planning Contact
* [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)
* [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)
* [mailto:swayh@oclc.org Hank Sway] - Volunteer
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)

== Sponsorship Committee ==
This group involves working with the LPC and budget committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.

[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)
* 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.

[[2019 Keynote Documents|2019 Keynote 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 - Documentarian
* 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.

[[2019 Pre-conference Documents|2019 Pre-conference Documents]]

* Your Name Here - Primary Contact aka Chair
* 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

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

[[2019 Program Documents|2019 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.

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

[[2019 Scholarship Documents|2019 Scholarship Documents]]

* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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.

[[2019 T-Shirt Documents|2019 T-Shirt 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 - Documentarian
* Your Name Here - Volunteer

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

[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]

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

[[2019 Social Activities Documents|2019 Social Activities Documents]]

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

* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Streaming Video Documents|2019 Streaming Video Documents]]

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]

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

[[2019 Book Giveaway Documents|2019 Book Giveaway 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 - Documentarian
* 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.

[[2019 IRC and Slack Documents|2019 IRC and Slack 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 - Documentarian
* Your Name Here - Volunteer

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

[[2019 Accessibility Documents|2019 Accessibility Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* 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.

[[2019 Whatever Documents|2019 Whatever 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 - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2019]]