https://wiki.code4lib.org/api.php?action=feedcontributions&feedformat=atom&user=Hardyoyo 2026-05-18T20:22:49Z User contributions MediaWiki 1.26.2 https://wiki.code4lib.org/index.php?title=2025_Keynote_Speakers_Nominations&diff=48537 2024-11-21T22:03:29Z

<p>Hardyoyo: /* Timnit Gebru */</p> <hr /> <div>Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.<br /> <br /> '''Nominations will close after November 21, 2024.'''<br /> <br /> When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:<br /> <br /> 1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?<br /> <br /> 2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?<br /> <br /> 3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?<br /> <br /> Please include a description and any relevant links. Please try to keep the list in alphabetical order.<br /> <br /> We require the following information in your nomination for a candidate to act as keynote:<br /> *Speaker’s full name<br /> *Brief description of individual (250-word max)<br /> *Pertinent links (Maximum of 3)<br /> *Contact information for candidate (email address)<br /> <br /> The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.<br /> <br /> ''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].'' <br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Nominee's Name ==<br /> <br /> Description of no more than 250 words.<br /> <br /> [[Link(s) with contact information for nominee]]<br /> <br /> [mailto:email_link.foo nominee's email address]<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> __TOC__<br /> <br /> ==Cory Doctorow==<br /> <br /> 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.<br /> Doctorow married Alice Taylor in October 2008, and they have a daughter named &lt;i&gt;Poesy Emmeline Fibonacci Nautilus Taylor Doctorow&lt;/i&gt;, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.<br /> <br /> [https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]<br /> <br /> [https://pluralistic.net pluralistic.net]<br /> <br /> [https://craphound.com craphound.com]<br /> <br /> [https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]<br /> ... and many more.<br /> <br /> He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]<br /> <br /> ==Molly White==<br /> <br /> From [https://www.mollywhite.net/ Molly's website]:<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Not from Molly's website:<br /> <br /> 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.<br /> <br /> She can be reached at [molly@mollywhite.net]<br /> <br /> ==Anne Washington==<br /> <br /> 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.<br /> <br /> [https://annewashington.com/ web site]<br /> <br /> [mailto:anne.washington@nyu.edu email address]<br /> <br /> ==Nikki Stevens==<br /> <br /> 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 &quot;if you invite me for a talk (hint hint), I would give talks titled:<br /> <br /> * “Abolitionist Data Practices: Applying political goals to data structures”<br /> * “Is my database racist? How white supremacy structures our databases”<br /> * “The history of data modeling” (this one is more exciting than it sounds, I swear!)<br /> * “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”<br /> <br /> [https://nikkistevens.com/ personal web site]<br /> <br /> [mailto:nikki.stevens@asu.edu email]<br /> <br /> ==Cat Hicks==<br /> <br /> 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 &quot;I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity.&quot; 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.<br /> <br /> [https://www.drcathicks.com/ web site]<br /> <br /> [https://mastodon.social/@grimalkina mastodon]<br /> <br /> [https://www.changetechnically.fyi/ podcast]<br /> <br /> <br /> ==Meredith Martin==<br /> <br /> 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. <br /> <br /> CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]<br /> <br /> [mailto:mm4@princeton.edu Meredith Martin]<br /> <br /> [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]<br /> <br /> <br /> == Ruth Kitchin Tillman ==<br /> <br /> 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.<br /> <br /> [https://ruthtillman.com/ Personal Website]<br /> <br /> [https://github.com/ruthtillman Github] <br /> <br /> [mailto:ruthtillman@gmail.com Email]<br /> <br /> ==Mukund Raghunath==<br /> [https://www.linkedin.com/in/mukund-r-1158a31/ Mukund Raghunath], Founder &amp; 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.<br /> <br /> ==Fobazi Ettarh==<br /> <br /> [https://fobaziettarh.com Fobazi] is a former librarian, now a second-year PhD student at University of Illinois-Champaign. An excerpt from her bio reads &quot;Fobazi Ettarh’s research is concerned with the relationships and tensions between the espoused values of librarianship and the realities present in the experiences of marginalized librarians and library users. In 2018, she coined the term and defined the concept of 'vocational awe,' which describe, 'the set of ideas, values, and assumptions librarians have about themselves and the profession that result in beliefs that libraries as institutions are inherently good and sacred, and therefore beyond critique.' In her article [https://www.inthelibrarywiththeleadpipe.org/2018/vocational-awe/ 'Vocational Awe: The Lies We Tell Ourselves,'] she describes how vocational awe can lead to burnout and a sense that one’s own self-care is less important than the work being done. Although written before the start of the COVID-19 pandemic, Ettarh’s words have resonated with many library workers throughout the nation in the current moment, as we strive to serve our patrons and our profession as best we can amidst the competing demands of home, work, and health. Her research has been covered in numerous outlets and she consults in library and corporate contexts on labor, identity, and diversity. She is also the creator of the open-access video game Killing Me Softly: A Game About Microaggressions.&quot; <br /> <br /> [mailto:fobettarh@gmail.com Fobazi's Email Address]<br /> <br /> ==John Kunze==<br /> <br /> John Kunze is a pioneer in the theory and practice of digital libraries. With a background in computer science and mathematics, he wrote open source BSD Unix tools that come pre-installed with Mac and Linux systems. For the past 25 years he has been working on cross-domain issues with libraries, archives, museums, and data centers.<br /> <br /> He created the ARK (Archival Resource Key) persistent identifier scheme (a non-paywalled alternative to the DOI and Handle systems) and the N2T.net scheme-agnostic resolver (a global ARK resolver, that also resolves hundreds of identifier schemes). Since 2001, 8.2 billion ARKs have been created by over 1400 organizations, including 10 national libraries, 185 universities, 209 archives, 104 museums, and 101 journals.<br /> <br /> He also contributed heavily to the first standards for URLs (RFC1736, RFC1625, RFC2056), library search and retrieval (Z39.50), archival transfer (BagIt - RFC8493), web archiving (WARC), and Dublin Core metadata (RFC2413, RFC2731, ANSI/NISO Z39.85).<br /> <br /> His specs and tools for repository microservices -- Pairtree, Namaste, ReDD, oxum, ERC/ANVL, TEMPER, THUMP -- may be found in such places as the HathiTrust and OCFL. Follow-on work in metadata includes creation of the Dublin Kernel and yamz.net. His current professional focus is with the ARK Alliance (arks.org).<br /> <br /> * [https://jkunze.net jkunze.net]<br /> * [https://arks.org arks.org]<br /> * [https://yamz.net yamz.net]<br /> * [https://orcid.org/0000-0001-7604-8041 ORCID]<br /> * [mailto:jakkbl@gmail.com email]<br /> <br /> ==Timnit Gebru==<br /> <br /> Gebru is the founder and executive director of the Distributed Artificial Intelligence Research Institute (DAIR). She previously co-led Google’s Ethical AI research team and received her PhD from the Stanford Artificial Intelligence Laboratory. With artificial general intelligence’s (AGI’s) recent rapid expansion in libraries as noted by this year’s many AI-focused conference talk proposals, Gebru’s research on AI ethics and her illuminating exploration (with Émile Torres) of AGI through the lens of the TESCREAL bundle of ideologies will hopefully be of interest to all who are motivated to support core library values while engaging with emerging technology.<br /> <br /> * [https://www.dair-institute.org/team/ Bio]<br /> * [https://en.wikipedia.org/wiki/Timnit_Gebru Wikipedia]<br /> * [https://scholar.google.com/citations?hl=en&amp;user=lemnAcwAAAAJ&amp;view_op=list_works&amp;sortby=pubdate Google Scholar bibliography]<br /> * [mailto:contact@dair-institute.org email]<br /> <br /> ==Jane Doe (example)==<br /> <br /> Jane works at ________, doing _______. <br /> <br /> Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.<br /> <br /> [mailto:jane@nowhere.foo janes_email_address]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2025_Keynote_Speakers_Nominations&diff=48536 2024-11-21T22:02:57Z

<p>Hardyoyo: Add anonymous nomination for Timnit Gebru, add ORCID for John Kunze</p> <hr /> <div>Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.<br /> <br /> '''Nominations will close after November 21, 2024.'''<br /> <br /> When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:<br /> <br /> 1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?<br /> <br /> 2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?<br /> <br /> 3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?<br /> <br /> Please include a description and any relevant links. Please try to keep the list in alphabetical order.<br /> <br /> We require the following information in your nomination for a candidate to act as keynote:<br /> *Speaker’s full name<br /> *Brief description of individual (250-word max)<br /> *Pertinent links (Maximum of 3)<br /> *Contact information for candidate (email address)<br /> <br /> The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.<br /> <br /> ''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].'' <br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Nominee's Name ==<br /> <br /> Description of no more than 250 words.<br /> <br /> [[Link(s) with contact information for nominee]]<br /> <br /> [mailto:email_link.foo nominee's email address]<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> __TOC__<br /> <br /> ==Cory Doctorow==<br /> <br /> 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.<br /> Doctorow married Alice Taylor in October 2008, and they have a daughter named &lt;i&gt;Poesy Emmeline Fibonacci Nautilus Taylor Doctorow&lt;/i&gt;, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.<br /> <br /> [https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]<br /> <br /> [https://pluralistic.net pluralistic.net]<br /> <br /> [https://craphound.com craphound.com]<br /> <br /> [https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]<br /> ... and many more.<br /> <br /> He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]<br /> <br /> ==Molly White==<br /> <br /> From [https://www.mollywhite.net/ Molly's website]:<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Not from Molly's website:<br /> <br /> 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.<br /> <br /> She can be reached at [molly@mollywhite.net]<br /> <br /> ==Anne Washington==<br /> <br /> 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.<br /> <br /> [https://annewashington.com/ web site]<br /> <br /> [mailto:anne.washington@nyu.edu email address]<br /> <br /> ==Nikki Stevens==<br /> <br /> 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 &quot;if you invite me for a talk (hint hint), I would give talks titled:<br /> <br /> * “Abolitionist Data Practices: Applying political goals to data structures”<br /> * “Is my database racist? How white supremacy structures our databases”<br /> * “The history of data modeling” (this one is more exciting than it sounds, I swear!)<br /> * “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”<br /> <br /> [https://nikkistevens.com/ personal web site]<br /> <br /> [mailto:nikki.stevens@asu.edu email]<br /> <br /> ==Cat Hicks==<br /> <br /> 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 &quot;I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity.&quot; 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.<br /> <br /> [https://www.drcathicks.com/ web site]<br /> <br /> [https://mastodon.social/@grimalkina mastodon]<br /> <br /> [https://www.changetechnically.fyi/ podcast]<br /> <br /> <br /> ==Meredith Martin==<br /> <br /> 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. <br /> <br /> CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]<br /> <br /> [mailto:mm4@princeton.edu Meredith Martin]<br /> <br /> [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]<br /> <br /> <br /> == Ruth Kitchin Tillman ==<br /> <br /> 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.<br /> <br /> [https://ruthtillman.com/ Personal Website]<br /> <br /> [https://github.com/ruthtillman Github] <br /> <br /> [mailto:ruthtillman@gmail.com Email]<br /> <br /> ==Mukund Raghunath==<br /> [https://www.linkedin.com/in/mukund-r-1158a31/ Mukund Raghunath], Founder &amp; 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.<br /> <br /> ==Fobazi Ettarh==<br /> <br /> [https://fobaziettarh.com Fobazi] is a former librarian, now a second-year PhD student at University of Illinois-Champaign. An excerpt from her bio reads &quot;Fobazi Ettarh’s research is concerned with the relationships and tensions between the espoused values of librarianship and the realities present in the experiences of marginalized librarians and library users. In 2018, she coined the term and defined the concept of 'vocational awe,' which describe, 'the set of ideas, values, and assumptions librarians have about themselves and the profession that result in beliefs that libraries as institutions are inherently good and sacred, and therefore beyond critique.' In her article [https://www.inthelibrarywiththeleadpipe.org/2018/vocational-awe/ 'Vocational Awe: The Lies We Tell Ourselves,'] she describes how vocational awe can lead to burnout and a sense that one’s own self-care is less important than the work being done. Although written before the start of the COVID-19 pandemic, Ettarh’s words have resonated with many library workers throughout the nation in the current moment, as we strive to serve our patrons and our profession as best we can amidst the competing demands of home, work, and health. Her research has been covered in numerous outlets and she consults in library and corporate contexts on labor, identity, and diversity. She is also the creator of the open-access video game Killing Me Softly: A Game About Microaggressions.&quot; <br /> <br /> [mailto:fobettarh@gmail.com Fobazi's Email Address]<br /> <br /> ==John Kunze==<br /> <br /> John Kunze is a pioneer in the theory and practice of digital libraries. With a background in computer science and mathematics, he wrote open source BSD Unix tools that come pre-installed with Mac and Linux systems. For the past 25 years he has been working on cross-domain issues with libraries, archives, museums, and data centers.<br /> <br /> He created the ARK (Archival Resource Key) persistent identifier scheme (a non-paywalled alternative to the DOI and Handle systems) and the N2T.net scheme-agnostic resolver (a global ARK resolver, that also resolves hundreds of identifier schemes). Since 2001, 8.2 billion ARKs have been created by over 1400 organizations, including 10 national libraries, 185 universities, 209 archives, 104 museums, and 101 journals.<br /> <br /> He also contributed heavily to the first standards for URLs (RFC1736, RFC1625, RFC2056), library search and retrieval (Z39.50), archival transfer (BagIt - RFC8493), web archiving (WARC), and Dublin Core metadata (RFC2413, RFC2731, ANSI/NISO Z39.85).<br /> <br /> His specs and tools for repository microservices -- Pairtree, Namaste, ReDD, oxum, ERC/ANVL, TEMPER, THUMP -- may be found in such places as the HathiTrust and OCFL. Follow-on work in metadata includes creation of the Dublin Kernel and yamz.net. His current professional focus is with the ARK Alliance (arks.org).<br /> <br /> * [https://jkunze.net jkunze.net]<br /> * [https://arks.org arks.org]<br /> * [https://yamz.net yamz.net]<br /> * [https://orcid.org/0000-0001-7604-8041 ORCID]<br /> * [mailto:jakkbl@gmail.com email]<br /> <br /> ==Timnit Gebru==<br /> <br /> Gebru is the founder and executive director of the Distributed Artificial Intelligence Research Institute (DAIR). She previously co-led Google’s Ethical AI research team and received her PhD from the Stanford Artificial Intelligence Laboratory. With artificial general intelligence’s (AGI’s) recent rapid expansion in libraries as noted by this year’s many AI-focused conference talk proposals, Gebru’s research on AI ethics and her illuminating exploration (with Émile Torres) of AGI through the lens of the TESCREAL bundle of ideologies will hopefully be of interest to all who are motivated to support core library values while engaging with emerging technology.<br /> <br /> * [https://www.dair-institute.org/team/ Bio]<br /> * [https://en.wikipedia.org/wiki/Timnit_Gebru Wikipedia]<br /> * [https://scholar.google.com/citations?hl=en&amp;user=lemnAcwAAAAJ&amp;view_op=list_works&amp;sortby=pubdate Google Scholar bibliography]<br /> * [mailto:contact@dair-institute.org email} <br /> <br /> <br /> ==Jane Doe (example)==<br /> <br /> Jane works at ________, doing _______. <br /> <br /> Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.<br /> <br /> [mailto:jane@nowhere.foo janes_email_address]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2025_Keynote_Speakers_Nominations&diff=48535 2024-11-21T21:20:38Z

<p>Hardyoyo: Add nomination for John Kunze (via anonymous e-mail suggestion)</p> <hr /> <div>Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.<br /> <br /> '''Nominations will close after November 21, 2024.'''<br /> <br /> When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:<br /> <br /> 1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?<br /> <br /> 2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?<br /> <br /> 3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?<br /> <br /> Please include a description and any relevant links. Please try to keep the list in alphabetical order.<br /> <br /> We require the following information in your nomination for a candidate to act as keynote:<br /> *Speaker’s full name<br /> *Brief description of individual (250-word max)<br /> *Pertinent links (Maximum of 3)<br /> *Contact information for candidate (email address)<br /> <br /> The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.<br /> <br /> ''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].'' <br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Nominee's Name ==<br /> <br /> Description of no more than 250 words.<br /> <br /> [[Link(s) with contact information for nominee]]<br /> <br /> [mailto:email_link.foo nominee's email address]<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> __TOC__<br /> <br /> ==Cory Doctorow==<br /> <br /> 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.<br /> Doctorow married Alice Taylor in October 2008, and they have a daughter named &lt;i&gt;Poesy Emmeline Fibonacci Nautilus Taylor Doctorow&lt;/i&gt;, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.<br /> <br /> [https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]<br /> <br /> [https://pluralistic.net pluralistic.net]<br /> <br /> [https://craphound.com craphound.com]<br /> <br /> [https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]<br /> ... and many more.<br /> <br /> He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]<br /> <br /> ==Molly White==<br /> <br /> From [https://www.mollywhite.net/ Molly's website]:<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Not from Molly's website:<br /> <br /> 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.<br /> <br /> She can be reached at [molly@mollywhite.net]<br /> <br /> ==Anne Washington==<br /> <br /> 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.<br /> <br /> [https://annewashington.com/ web site]<br /> <br /> [mailto:anne.washington@nyu.edu email address]<br /> <br /> ==Nikki Stevens==<br /> <br /> 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 &quot;if you invite me for a talk (hint hint), I would give talks titled:<br /> <br /> * “Abolitionist Data Practices: Applying political goals to data structures”<br /> * “Is my database racist? How white supremacy structures our databases”<br /> * “The history of data modeling” (this one is more exciting than it sounds, I swear!)<br /> * “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”<br /> <br /> [https://nikkistevens.com/ personal web site]<br /> <br /> [mailto:nikki.stevens@asu.edu email]<br /> <br /> ==Cat Hicks==<br /> <br /> 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 &quot;I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity.&quot; 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.<br /> <br /> [https://www.drcathicks.com/ web site]<br /> <br /> [https://mastodon.social/@grimalkina mastodon]<br /> <br /> [https://www.changetechnically.fyi/ podcast]<br /> <br /> <br /> ==Meredith Martin==<br /> <br /> 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. <br /> <br /> CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]<br /> <br /> [mailto:mm4@princeton.edu Meredith Martin]<br /> <br /> [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]<br /> <br /> <br /> == Ruth Kitchin Tillman ==<br /> <br /> 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.<br /> <br /> [https://ruthtillman.com/ Personal Website]<br /> <br /> [https://github.com/ruthtillman Github] <br /> <br /> [mailto:ruthtillman@gmail.com Email]<br /> <br /> ==Mukund Raghunath==<br /> [https://www.linkedin.com/in/mukund-r-1158a31/ Mukund Raghunath], Founder &amp; 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.<br /> <br /> ==Fobazi Ettarh==<br /> <br /> [https://fobaziettarh.com Fobazi] is a former librarian, now a second-year PhD student at University of Illinois-Champaign. An excerpt from her bio reads &quot;Fobazi Ettarh’s research is concerned with the relationships and tensions between the espoused values of librarianship and the realities present in the experiences of marginalized librarians and library users. In 2018, she coined the term and defined the concept of 'vocational awe,' which describe, 'the set of ideas, values, and assumptions librarians have about themselves and the profession that result in beliefs that libraries as institutions are inherently good and sacred, and therefore beyond critique.' In her article [https://www.inthelibrarywiththeleadpipe.org/2018/vocational-awe/ 'Vocational Awe: The Lies We Tell Ourselves,'] she describes how vocational awe can lead to burnout and a sense that one’s own self-care is less important than the work being done. Although written before the start of the COVID-19 pandemic, Ettarh’s words have resonated with many library workers throughout the nation in the current moment, as we strive to serve our patrons and our profession as best we can amidst the competing demands of home, work, and health. Her research has been covered in numerous outlets and she consults in library and corporate contexts on labor, identity, and diversity. She is also the creator of the open-access video game Killing Me Softly: A Game About Microaggressions.&quot; <br /> <br /> <br /> [mailto:fobettarh@gmail.com Fobazi's Email Address]<br /> <br /> ==John Kunze==<br /> <br /> John Kunze is a pioneer in the theory and practice of digital libraries. With a background in computer science and mathematics, he wrote open source BSD Unix tools that come pre-installed with Mac and Linux systems. For the past 25 years he has been working on cross-domain issues with libraries, archives, museums, and data centers.<br /> <br /> He created the ARK (Archival Resource Key) persistent identifier scheme (a non-paywalled alternative to the DOI and Handle systems) and the N2T.net scheme-agnostic resolver (a global ARK resolver, that also resolves hundreds of identifier schemes). Since 2001, 8.2 billion ARKs have been created by over 1400 organizations, including 10 national libraries, 185 universities, 209 archives, 104 museums, and 101 journals.<br /> <br /> He also contributed heavily to the first standards for URLs (RFC1736, RFC1625, RFC2056), library search and retrieval (Z39.50), archival transfer (BagIt - RFC8493), web archiving (WARC), and Dublin Core metadata (RFC2413, RFC2731, ANSI/NISO Z39.85).<br /> <br /> His specs and tools for repository microservices -- Pairtree, Namaste, ReDD, oxum, ERC/ANVL, TEMPER, THUMP -- may be found in such places as the HathiTrust and OCFL. Follow-on work in metadata includes creation of the Dublin Kernel and yamz.net. His current professional focus is with the ARK Alliance (arks.org).<br /> <br /> * [https://jkunze.net jkunze.net]<br /> * [https://arks.org arks.org]<br /> * [https://yamz.net yamz.net]<br /> * [mailto:jakkbl@gmail.com email]<br /> <br /> <br /> <br /> ==Jane Doe (example)==<br /> <br /> Jane works at ________, doing _______. <br /> <br /> Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.<br /> <br /> [mailto:jane@nowhere.foo janes_email_address]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2025_Keynote_Speakers_Nominations&diff=48530 2024-11-15T17:35:38Z

<p>Hardyoyo: facilitating an anonymous nomination for Mukund Raghunath as keynote speaker</p> <hr /> <div>Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.<br /> <br /> '''Nominations will close after November 21, 2024.'''<br /> <br /> When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:<br /> <br /> 1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?<br /> <br /> 2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?<br /> <br /> 3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through uncommon experience or background?<br /> <br /> Please include a description and any relevant links. Please try to keep the list in alphabetical order.<br /> <br /> We require the following information in your nomination for a candidate to act as keynote:<br /> *Speaker’s full name<br /> *Brief description of individual (250-word max)<br /> *Pertinent links (Maximum of 3)<br /> *Contact information for candidate (email address)<br /> <br /> The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.<br /> <br /> ''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].'' <br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Nominee's Name ==<br /> <br /> Description of no more than 250 words.<br /> <br /> [[Link(s) with contact information for nominee]]<br /> <br /> [mailto:email_link.foo nominee's email address]<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> __TOC__<br /> <br /> ==Cory Doctorow==<br /> <br /> 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.<br /> Doctorow married Alice Taylor in October 2008, and they have a daughter named &lt;i&gt;Poesy Emmeline Fibonacci Nautilus Taylor Doctorow&lt;/i&gt;, who was born in 2008. (fromBoing Boing via WikiPedia) What more do you really need to know.<br /> <br /> [https://en.wikipedia.org/wiki/Cory_Doctorow Wikipedia]<br /> <br /> [https://pluralistic.net pluralistic.net]<br /> <br /> [https://craphound.com craphound.com]<br /> <br /> [https://www.latimes.com/books/la-ca-jc-fob-cory-doctorow-interview-radicalized-20190411-story.html LA Times interview]<br /> ... and many more.<br /> <br /> He can be reached at [mailto:doctorow@craphound.com doctorow@craphound.com]<br /> <br /> ==Molly White==<br /> <br /> From [https://www.mollywhite.net/ Molly's website]:<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> Not from Molly's website:<br /> <br /> 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.<br /> <br /> She can be reached at [molly@mollywhite.net]<br /> <br /> ==Anne Washington==<br /> <br /> 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.<br /> <br /> [https://annewashington.com/ web site]<br /> <br /> [mailto:anne.washington@nyu.edu email address]<br /> <br /> ==Nikki Stevens==<br /> <br /> 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 &quot;if you invite me for a talk (hint hint), I would give talks titled:<br /> <br /> * “Abolitionist Data Practices: Applying political goals to data structures”<br /> * “Is my database racist? How white supremacy structures our databases”<br /> * “The history of data modeling” (this one is more exciting than it sounds, I swear!)<br /> * “Beyond ‘anti-racist’ engineering: why anti-racism does not make better software”<br /> <br /> [https://nikkistevens.com/ personal web site]<br /> <br /> [mailto:nikki.stevens@asu.edu email]<br /> <br /> ==Cat Hicks==<br /> <br /> 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 &quot;I'm passionate about learning equity, access to opportunity, and how we make visible the invisible effort of people operating under extraordinary adversity.&quot; 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.<br /> <br /> [https://www.drcathicks.com/ web site]<br /> <br /> [https://mastodon.social/@grimalkina mastodon]<br /> <br /> [https://www.changetechnically.fyi/ podcast]<br /> <br /> <br /> ==Meredith Martin==<br /> <br /> 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. <br /> <br /> CDH Link [https://cdh.princeton.edu/people/meredith-martin/ ]<br /> <br /> [mailto:mm4@princeton.edu Meredith Martin]<br /> <br /> [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]<br /> <br /> <br /> == Ruth Kitchin Tillman ==<br /> <br /> 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.<br /> <br /> [https://ruthtillman.com/ Personal Website]<br /> <br /> [https://github.com/ruthtillman Github] <br /> <br /> [mailto:ruth.tillman@gmail.com Email]<br /> <br /> ==Mukund Raghunath==<br /> [https://www.linkedin.com/in/mukund-r-1158a31/ Mukund Raghunath], Founder &amp; 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.<br /> <br /> ==Jane Doe (example)==<br /> <br /> Jane works at ________, doing _______. <br /> <br /> Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.<br /> <br /> [mailto:jane@nowhere.foo janes_email_address]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2025_Keynote_Speakers_Nominations&diff=48510 2024-10-22T22:29:08Z

<p>Hardyoyo: all-caps-mode for the e-mail subject line</p> <hr /> <div>'''This is a preliminary draft of the Keynote nominations page for 2025. Please do not submit nominations yet--we are still finalizing some details.'''<br /> <br /> Code4Lib 2025 will take place March 10-13, 2025 at Princeton University.<br /> <br /> '''Nominations will close after November 25, 2024.'''<br /> <br /> When making a nomination, please consider whether the nominee is likely to be an excellent contributor in each of the following areas:<br /> <br /> 1) '''Appropriateness'''. Is this speaker likely to convey information that is useful to many members of our community?<br /> <br /> 2) '''Uniqueness'''. Is this speaker likely to cover themes that may not commonly appear in the rest of the program?<br /> <br /> 3) '''Contribution to diversity'''. Will this person bring something rare, notable, or unique to our community, through unusual experience or background?<br /> <br /> Please include a description and any relevant links. Please try to keep the list in alphabetical order.<br /> <br /> We require the following information in your nomination for a candidate to act as keynote:<br /> *Speaker’s full name<br /> *Brief description of individual (250-word max)<br /> *Pertinent links (Maximum of 3)<br /> *Contact information for candidate (email address)<br /> <br /> The Keynote Committee will attempt to contact all nominees and will only include on the ballot those who consent to be nominated.<br /> <br /> ''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].'' <br /> <br /> Please follow the formatting guidelines:<br /> <br /> &lt;pre&gt;<br /> <br /> == Nominee's Name ==<br /> <br /> Description of no more than 250 words.<br /> <br /> [[Link(s) with contact information for nominee]]<br /> <br /> [mailto:email_link.foo nominee's email address]<br /> <br /> <br /> &lt;/pre&gt;<br /> <br /> __TOC__<br /> <br /> <br /> ==Jane Doe (example)==<br /> <br /> Jane works at ________, doing _______. <br /> <br /> Some pertinent history/biography/[https://example.com hyperlinks] that illustrates why Jane would be a good keynote speaker.<br /> <br /> [mailto:jane@nowhere.foo janes_email_address]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2025_Conference_Committees&diff=48471 2024-09-12T00:51:54Z

<p>Hardyoyo: /* Keynote Committee */Volunteered for the Keynote committee</p> <hr /> <div>= Code4Lib Conference Committees =<br /> <br /> 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<br /> <br /> ==Planning Committee==<br /> Also known as the Local Planning Committee, although there is no requirement for the members to be local.<br /> <br /> [[2025 Planning Committee Documents|2025 Planning Committee Documents]]<br /> <br /> * Esmé Cowles (Princeton) - Primary Contact, Chair<br /> * Kate Lynch (Princeton) - Secondary Contact, Co-chair, documentarian<br /> * Tracy Hall (Princeton) - Tertiary Contact<br /> * Your Name Here - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2025 Website Working Group Documents|2025 Website Working Group Documents]]<br /> <br /> * Esmé Cowles - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Trip Kirkpatrick - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2025 Budget and Sponsorship Documents]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> From the chair: This committee's timeline is TBD, pending scheduling info from the LPC. I expect it will start imminently (September, or October at the latest) and wrap up several months before the conference, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.<br /> <br /> * Andromeda Yelton - Primary Contact, Chair<br /> * Maccabee Levine - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Hardy Pottinger - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - LPC Liaison<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2025 Pre-conference Documents|2025 Pre-conference Documents]]<br /> <br /> * Your Name Here - Primary Contact, CoChair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer <br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2025 Program Documents|2025 Program Documents]]<br /> <br /> * Matt Sherman - Primary Contact, Chair<br /> * Dre - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Daricus Larry (dlarry@arizona.edu) - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Ken Varnum - Volunteer<br /> * Steph Gritz (sgritz@lmu.edu) - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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. <br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] (Brown University) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> 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.<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2025 T-Shirt Documents|2025 T-Shirt Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2025 Conference Volunteers]]'''<br /> <br /> [[2025 Online Volunteer Documents|2025 Online Volunteer Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2025 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - LPC Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Code4Lib 2026 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2026 Host Voting Documents|2026 Host Voting Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2025 IRC and Slack Documents|2025 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2025 Accessibility Documents|2025 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2025 Whatever Documents|2025 Whatever Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Remote Volunteer<br /> <br /> [[Category: Code4Lib2025]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48389 2024-05-13T01:03:41Z

<p>Hardyoyo: /* Livestream QA (Remote) */Add Merit Ibekeme to Livestream QA</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * [[User:Hardyoyo|Hardy Pottinger]]<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> * Backup volunteer (all day): Merit Ibekeme (West Africa)<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> * Backup volunteer (all day): Merit Ibekeme (West Africa)<br /> <br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> * Backup volunteer (all day): Merit Ibekeme (West Africa)<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48388 2024-05-10T16:05:20Z

<p>Hardyoyo: /* Livestream QA (Remote) */ add Michael Andrec and Umar Faruk Yunus as backup volunteers for all days</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * [[User:Hardyoyo|Hardy Pottinger]]<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> * Backup volunteer (all day): Michael Andrec (East Coast)<br /> * Backup volunteer (all day): Umar Faruk Yunus (West Africa)<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2024_Conference_Committees&diff=48387 2024-05-09T22:28:21Z

<p>Hardyoyo: </p> <hr /> <div>= Code4Lib 2024 Conference Committees =<br /> <br /> Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2024 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact<br /> <br /> ==Planning Committee==<br /> Also known as the Local Planning Committee, although there is no requirement for the members to be local.<br /> <br /> [[2024 Planning Committee Documents|2024 Planning Committee Documents]]<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M) - Primary Contact, Chair<br /> * Jesse Johnston (U Michigan) - Secondary Contact, Co-chair, documentarian<br /> * Jennifer Cummings (Concentra) - Tertiary Contact<br /> * Kathy Azevedo (Concentra) - Volunteer<br /> * [[User:varnum|Ken Varnum]] (U-M) - Volunteer<br /> * [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2024 Website Working Group Documents|2024 Website Working Group Documents]]<br /> <br /> * Esmé Cowles - Primary Contact, Chair<br /> * [[User:Phette23|Eric Phetteplace]] phette23@gmail.com - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Andy Pederson (apederson@unl.edu) - Accessibility Committee Contact<br /> * Trip Kirkpatrick trip.kirkpatrick@yale.edu - Volunteer<br /> * Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br /> * Christine Salek (cmsalek@wisc.edu) - Volunteer<br /> * [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - LPC liaison<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2024 Budget and Sponsorship Documents]<br /> <br /> * Jesse Johnston (UMich) - Primary Contact, Chair, and liaison to LPC<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Bohyun Kim - Volunteer<br /> * Mary Jinglewski - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> From the chair: This committee will start work in late September. The work will wrap up in January, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.<br /> <br /> * Andromeda Yelton - Primary Contact, Chair<br /> * Mike Taylor (mike.taylor@nau.edu) - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Lillian Hogendoorn (lillian.hogendoorn@utoronto.ca) - Volunteer<br /> * Maccabee Levine (@maccabeelevine on slack) - Volunteer<br /> * [[User:NatashaAllen|Natasha Allen]] - LPC Liaison<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2024 Pre-conference Documents|2024 Pre-conference Documents]]<br /> <br /> * Ann Marie Mesco - Primary Contact, CoChair<br /> * Ken Rose - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:SheriseKimura|Sherise Kimura]] - Volunteer<br /> * Jason Glenn - Volunteer <br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2024 Program Documents|2024 Program Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * [[User:MegoFranks|Mego Franks]] - Secondary Contact, CoChair - megofranks@gmail.com<br /> * [[User:BrandonPatterson|Brandon Patterson]] - Documentarian<br /> * Matt Sherman - Volunteer<br /> * Dre - Volunteer<br /> * [[User:varnum|Ken Varnum]] - LPC liaison<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * [[User:MoniqueRio|Monique Rio]] - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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. <br /> <br /> Work will start in early October<br /> <br /> * Chad Nelson - chad.nelson at ucop.edu, @bibliotechy on Slack - Primary Contact, Chair<br /> * Michelle Speed - Secondary Contact, CoChair<br /> * Andrew Battelini - abattel@emory.edu, Documentarian<br /> * [[User:MaxEckard|Max Eckard]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> 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://2024.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.<br /> <br /> '''Currently seeking a co-coordinator.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Soojeong Herring on Slack or via email (soojeong_herring@brown.edu).<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2024 T-Shirt Documents|2024 T-Shirt Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''<br /> <br /> [[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Coral Sheldon-Hess - Volunteer, virtual-only<br /> * [[User:Hardyoyo|Hardy Pottinger]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * Brandon Patterson - Primary Contact, Chair<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:Hardyoyo|Hardy Pottinger]] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> * [[User:DataGazetteer|Peter Murray]] - Primary Contact, Chair<br /> * [[User:highermath|Cary Gordon]] - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - LPC Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Code4Lib 2025 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2025 Host Voting Documents|2025 Host Voting Documents]]<br /> <br /> *[[User:NatashaAllen|Natasha Allen]] (University of Michigan) - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * [[User:DavidFulmer|David Fulmer]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2024 Accessibility Documents|2024 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Christine Salek (cmsalek@wisc.edu) - Volunteer<br /> * Zhaneille Green (zbg@duke.edu) - Volunteer<br /> * Andy Pederson (apederson@unl.edu) - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2024 Whatever Documents|2024 Whatever Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * [[User:SamHansen|Sam Hansen]] - Volunteer<br /> * [[User:coral|Coral Sheldon-Hess]] - Remote Volunteer<br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2024_Conference_Committees&diff=48386 2024-05-09T22:26:55Z

<p>Hardyoyo: </p> <hr /> <div>= Code4Lib 2024 Conference Committees =<br /> <br /> Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2024 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact<br /> <br /> ==Planning Committee==<br /> Also known as the Local Planning Committee, although there is no requirement for the members to be local.<br /> <br /> [[2024 Planning Committee Documents|2024 Planning Committee Documents]]<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M) - Primary Contact, Chair<br /> * Jesse Johnston (U Michigan) - Secondary Contact, Co-chair, documentarian<br /> * Jennifer Cummings (Concentra) - Tertiary Contact<br /> * Kathy Azevedo (Concentra) - Volunteer<br /> * [[User:varnum|Ken Varnum]] (U-M) - Volunteer<br /> * [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2024 Website Working Group Documents|2024 Website Working Group Documents]]<br /> <br /> * Esmé Cowles - Primary Contact, Chair<br /> * [[User:Phette23|Eric Phetteplace]] phette23@gmail.com - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Andy Pederson (apederson@unl.edu) - Accessibility Committee Contact<br /> * Trip Kirkpatrick trip.kirkpatrick@yale.edu - Volunteer<br /> * Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br /> * Christine Salek (cmsalek@wisc.edu) - Volunteer<br /> * [[User:HeidiBurkhardt|Heidi Burkhardt]] (U-M) - LPC liaison<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2024 Budget and Sponsorship Documents]<br /> <br /> * Jesse Johnston (UMich) - Primary Contact, Chair, and liaison to LPC<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Bohyun Kim - Volunteer<br /> * Mary Jinglewski - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> From the chair: This committee will start work in late September. The work will wrap up in January, when we hand off our selected keynoters to Concentra for further logistics. Please DM me (@thatandromeda) in Slack if you have questions about serving on this committee.<br /> <br /> * Andromeda Yelton - Primary Contact, Chair<br /> * Mike Taylor (mike.taylor@nau.edu) - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Lillian Hogendoorn (lillian.hogendoorn@utoronto.ca) - Volunteer<br /> * Maccabee Levine (@maccabeelevine on slack) - Volunteer<br /> * [[User:NatashaAllen|Natasha Allen]] - LPC Liaison<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2024 Pre-conference Documents|2024 Pre-conference Documents]]<br /> <br /> * Ann Marie Mesco - Primary Contact, CoChair<br /> * Ken Rose - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:SheriseKimura|Sherise Kimura]] - Volunteer<br /> * Jason Glenn - Volunteer <br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2024 Program Documents|2024 Program Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * [[User:MegoFranks|Mego Franks]] - Secondary Contact, CoChair - megofranks@gmail.com<br /> * [[User:BrandonPatterson|Brandon Patterson]] - Documentarian<br /> * Matt Sherman - Volunteer<br /> * Dre - Volunteer<br /> * [[User:varnum|Ken Varnum]] - LPC liaison<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * [[User:MoniqueRio|Monique Rio]] - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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. <br /> <br /> Work will start in early October<br /> <br /> * Chad Nelson - chad.nelson at ucop.edu, @bibliotechy on Slack - Primary Contact, Chair<br /> * Michelle Speed - Secondary Contact, CoChair<br /> * Andrew Battelini - abattel@emory.edu, Documentarian<br /> * [[User:MaxEckard|Max Eckard]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> 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://2024.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.<br /> <br /> '''Currently seeking a co-coordinator.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Soojeong Herring on Slack or via email (soojeong_herring@brown.edu).<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2024 T-Shirt Documents|2024 T-Shirt Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2024 Conference Volunteers]]'''<br /> <br /> [[2024 Online Volunteer Documents|2024 Online Volunteer Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Coral Sheldon-Hess - Volunteer, virtual-only<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2024 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * Brandon Patterson - Primary Contact, Chair<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (JHU) - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:Hardyoyo|Hardy Pottinger]] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> * [[User:DataGazetteer|Peter Murray]] - Primary Contact, Chair<br /> * [[User:highermath|Cary Gordon]] - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - LPC Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Code4Lib 2025 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2025 Host Voting Documents|2025 Host Voting Documents]]<br /> <br /> *[[User:NatashaAllen|Natasha Allen]] (University of Michigan) - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * [[User:DavidFulmer|David Fulmer]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2024 IRC and Slack Documents|2024 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2024 Accessibility Documents|2024 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Christine Salek (cmsalek@wisc.edu) - Volunteer<br /> * Zhaneille Green (zbg@duke.edu) - Volunteer<br /> * Andy Pederson (apederson@unl.edu) - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2024 Whatever Documents|2024 Whatever Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Elaine Kong (elainekong@pitt.edu) - Volunteer<br /> * [[User:SamHansen|Sam Hansen]] - Volunteer<br /> * [[User:coral|Coral Sheldon-Hess]] - Remote Volunteer<br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48385 2024-05-09T16:48:42Z

<p>Hardyoyo: Hardy volunteers for Game Night</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * [[User:Hardyoyo|Hardy Pottinger]]<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48383 2024-05-09T14:18:43Z

<p>Hardyoyo: use a wiki link for Michelle Janowiecki</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * [[User:MichelleJanowiecki|Michelle Janowiecki]] (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48382 2024-05-09T14:16:43Z

<p>Hardyoyo: Add Michelle Janowiecki as the volunteer for the morning run (with permission)</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * Michelle Janowiecki (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48379 2024-05-07T16:39:59Z

<p>Hardyoyo: </p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * ''Your Name Here'' (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48378 2024-05-07T16:39:06Z

<p>Hardyoyo: add link to reception</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], [https://2024.code4lib.org/general-info/venues/#reception Reception]):<br /> * ''Your Name Here'' (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48377 2024-05-07T16:37:51Z

<p>Hardyoyo: /* Social Events */ add links to each event</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One ([https://2024.code4lib.org/general-info/social/#tours Tours]):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2024.code4lib.org/general-info/social/#morning-run Morning Run], Reception):<br /> * ''Your Name Here'' (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three ([https://2024.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48376 2024-05-07T15:41:15Z

<p>Hardyoyo: add more details to the Social Events volunteer slots</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2024 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] (U-M)<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * Heidi Burkhardt<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Heidi Burkhardt<br /> * Elena Colon-Marrero<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One (Tours):<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two (Morning Run, Reception):<br /> * ''Your Name Here'' (morning run)<br /> * ''Your Name Here'' (reception)<br /> <br /> Wednesday, Day Three (Game Night):<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: [[User:TripKirkpatrick|Trip Kirkpatrick]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Ange Zaytsev<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''[http://mailto:liblna@emory.edu Laura Akerman]''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Michelle Navarro<br /> * PM volunteer: Michelle Navarro<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: Cary Gordon<br /> * PM Volunteer: Barbara Cormack<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * [[User:Phette23|Eric Phetteplace]] — I will be able to volunteer for specific tasks once I know my Community Support schedule<br /> * Ange Zaytsev<br /> * Elena Colon-Marrero<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48340 2024-03-05T00:14:56Z

<p>Hardyoyo: Hardy volunteers for the Whatever Crew</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: Dre<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: Eric Hellman<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48324 2024-02-02T14:47:03Z

<p>Hardyoyo: /* Session Timers */</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48323 2024-02-02T00:26:22Z

<p>Hardyoyo: modernizing the social media names and hashtags</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l24), X ( aka Twitter) (#c4l24), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48322 2024-02-01T19:56:41Z

<p>Hardyoyo: Add MC slot to Wed PM</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48321 2024-02-01T19:44:36Z

<p>Hardyoyo: revised to match the 2024 schedule (starting on an afternoon, and a full last day)</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 12 Noon - 1pm Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2024_Conference_Volunteers&diff=48320 2024-02-01T18:53:49Z

<p>Hardyoyo: first draft of 2024 Conference Volunteers page</p> <hr /> <div>= Code4Lib 2024 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2024_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2024.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 8am - 9am Monday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, day two:<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2024]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48087 2023-03-10T15:31:00Z

<p>Hardyoyo: /* Mic-minders */ added Michael Andrec to Thursday AM mic minder slot as per request via Jennifer Cummings</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * Bobbi Fox<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * Hector Correa<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 7am Run/Walk organizer: Eric Hellman<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: Benjamin Riesenberg<br /> * PM volunteer: Hector Correa<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: Michael Andrec<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Heather Greer Klein<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: Vickie Karasic<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: Dre<br /> * PM Volunteer: Eric Hellman<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: Trey Pendragon<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: Heather Greer Klein<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Craig Rosenbeck<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48081 2023-03-08T23:18:45Z

<p>Hardyoyo: /* Livestream Assistants (Onsite) */ removing section, livestream assistance not required this year</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * Hector Correa<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 7am Run/Walk organizer: Eric Hellman<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Hector Correa<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Heather Greer Klein<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: Dre<br /> * PM Volunteer: Eric Hellman<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: Trey Pendragon<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Craig Rosenbeck<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48074 2023-03-07T17:41:08Z

<p>Hardyoyo: volunteer to be the onsite volunteer committee coordinator for registration</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Hector Correa<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: Maccabee Levine<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48071 2023-03-07T14:37:56Z

<p>Hardyoyo: remove DRAFT stamp, this is as real as it gets</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l23), Twitter (#c4l23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48063 2023-02-07T17:49:21Z

<p>Hardyoyo: add link to the conference planning committees page</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2023_Conference_Committees|conference planning committees]].<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48062 2023-02-07T17:43:55Z

<p>Hardyoyo: Update days</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48061 2023-02-07T17:42:33Z

<p>Hardyoyo: /* Livestream Assistants (Onsite) */ update days</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48060 2023-02-07T17:41:59Z

<p>Hardyoyo: /* Livestream QA (Remote) */</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48059 2023-02-07T17:41:28Z

<p>Hardyoyo: /* Session Timers */ update days</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48058 2023-02-07T17:40:49Z

<p>Hardyoyo: /* MCs */ fix days for MC slots, and volunteered for one of 'em, whee!</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Hardy Pottinger<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48057 2023-02-06T22:38:40Z

<p>Hardyoyo: /* Conference Logistics &amp; Registration */Fixed registration dates</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Thursday, day two:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48056 2023-02-06T22:26:50Z

<p>Hardyoyo: /* Conference Logistics &amp; Registration */ volunteer for registration</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, preconference day:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * Hardy Pottinger<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48055 2023-02-06T22:23:26Z

<p>Hardyoyo: add times for registration</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Tuesday, preconference day:<br /> * ''Your Name Here''<br /> <br /> 8am - 9am Wednesday, day one:<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48052 2023-02-03T20:53:13Z

<p>Hardyoyo: hashtag for social stuff</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Tuesday, preconference day:<br /> * ''Your Name Here''<br /> <br /> Wednesday, day one:<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#cfl23), Twitter (#cfl23), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48051 2023-02-03T20:38:07Z

<p>Hardyoyo: proper bolding of DRAFT label</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> '''DRAFT/Work in Progress'''<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Tuesday, preconference day:<br /> * ''Your Name Here''<br /> <br /> Wednesday, day one:<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon, IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2023_Conference_Volunteers&diff=48050 2023-02-03T20:36:33Z

<p>Hardyoyo: copy-pasta with light edits, from 2020 to 2023</p> <hr /> <div>= Code4Lib 2023 Conference Volunteers =<br /> <br /> ** DRAFT/Work in Progress **<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2023.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Tuesday, preconference day:<br /> * ''Your Name Here''<br /> <br /> Wednesday, day one:<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> * 11pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon, IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * ''Your Name Here''<br /> <br /> <br /> [[Category: Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=48041 2023-01-10T23:37:20Z

<p>Hardyoyo: Volunteering for the Social Activities Committee</p> <hr /> <div>= Code4Lib 2023 Conference Committees =<br /> <br /> 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.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: Princeton University<br /> * Pre-conferences: March 14, 2023 (Rabinowitz Building)<br /> * Main conference: March 15-17, 2023 (Frist Campus Center)<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br /> * Esmé Cowles - (escowles@princeton.edu) - Documentarian &amp; Secondary Contact<br /> * Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br /> * Hillel Arnold - (harnold@rockarch.org) - Volunteer<br /> * Chulin Meng - (chm213@lehigh.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br /> <br /> * Yinlin Chen - (ylchen@vt.edu) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Kate Deibel (kndeibel@metageekery.org) - Accessibility Committee Contact<br /> * Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br /> * Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br /> * John DeLooper - (john.delooper@lehman.cuny.edu) - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br /> <br /> * Jenn Cummings &amp; Kathy Azevedo - (code4lib@concentra-cms.com) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> [[2023 Keynote Documents|2023 Keynote Documents]]<br /> <br /> [[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br /> <br /> * [[User:Khaley|Kathleen Haley]] - Primary Contact, Chair<br /> * Kathryn Michaelis - (kmicha3@emory.edu) - Secondary Contact, CoChair<br /> * [[User:Thatandromeda|Andromeda Yelton]] - Documentarian<br /> * Ranti Junus - Volunteer<br /> * Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br /> <br /> * Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br /> * Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br /> * Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br /> * Eric Morgan &lt;emorgan@nd.edu&gt; - Volunteer, grip, and all-around lackey <br /> * Tod Olson &lt;tod@uchicago.edu&gt; - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2023 Program Documents|2023 Program Documents]]<br /> <br /> * Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br /> * Dre (akorphan) - Secondary Contact, CoChair<br /> * Andrew Battelini - (abattel@emory.edu)- Documentarian<br /> * Ranti Junus (junus-at-msu-edu) - Volunteer<br /> * Emily Boss (eboss-at-unr-edu) - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> <br /> [[2023 Scholarship Documents|2023 Scholarship Documents]]<br /> <br /> * Yongming Wang - (wangyo@tcnj.edu) - Primary Contact, Chair<br /> * - Secondary Contact, CoChair<br /> * Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br /> * Junior Tidal - (jtidal-at-citytech-dot-cuny-dot-edu)- Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2022.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2022_national_conference_annual_report.md.<br /> <br /> '''Currently seeking one or two coordinators.''' Because all coordinators and volunteers for the CSS need to pass a community vetting procedure, the process of filling these roles is different from the other committees. Rather than signing up here, please reach out to Anne Slaughter on Slack or via email (anne dot slaughter at railslibraries dot info).<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br /> <br /> * Kate Lynch - (katelynch@princeton.edu) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Margaret Heller - (mheller1@luc.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br /> <br /> [[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Hardy Pottinger - hardy.pottinger@ucop.edu - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> [[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Kate Lynch - (katelynch@princeton.edu) - LPC Volunteer<br /> * [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Code4Lib 2023 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2023 Host Voting Documents|2023 Host Voting Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> 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).<br /> <br /> [[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2023 Accessibility Documents|2023 Accessibility Documents]]<br /> <br /> * Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br /> * Caitlin Bakker - (caitlin.bakker@uregina.ca) - Secondary Contact, CoChair<br /> * Ed Hill - (edhill@duck.com) - Documentarian<br /> * Hilary Shiue (hilaryszuyinshiue@nypl.org) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2023 Whatever Documents|2023 Whatever Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> [[Category:Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=47909 2022-10-19T20:06:11Z

<p>Hardyoyo: add &quot;pre or post&quot; to preconference day, to keep our options open</p> <hr /> <div>= Code4Lib 2023 Conference Committees =<br /> <br /> 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.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: Princeton University<br /> * Dates: March 14-17, 2023<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br /> * Esmé Cowles - (escowles@princeton.edu) - Documentarian &amp; Secondary Contact<br /> * Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br /> * Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br /> * Your Name Here - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> [[2023 Keynote Documents|2023 Keynote Documents]]<br /> <br /> [[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Ranti Junus - Volunteer<br /> * Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br /> <br /> * Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br /> * Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br /> * Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2023 Program Documents|2023 Program Documents]]<br /> <br /> * Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br /> * Dre (akorphan) - Secondary Contact, CoChair<br /> * Andrew Battelini - (abattel@emory.edu)- Documentarian<br /> * Ranti Junus (junus-at-msu-edu) - Volunteer<br /> * Emily Boss (eboss-at-unr-edu) - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> <br /> [[2023 Scholarship Documents|2023 Scholarship Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair<br /> * Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br /> * Yongming Wang - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> 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<br /> <br /> * Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br /> <br /> [[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> [[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Code4Lib 2023 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2023 Host Voting Documents|2023 Host Voting Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> 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).<br /> <br /> [[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2023 Accessibility Documents|2023 Accessibility Documents]]<br /> <br /> * Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2023 Whatever Documents|2023 Whatever Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> [[Category:Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2023_Conference_Committees&diff=47908 2022-10-19T20:03:52Z

<p>Hardyoyo: volunteering for the Pre-conference Documentarian position</p> <hr /> <div>= Code4Lib 2023 Conference Committees =<br /> <br /> 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.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: Princeton University<br /> * Dates: March 14-17, 2023<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * Kate Lynch - (katelynch@princeton.edu) - Chair, Primary Contact<br /> * Esmé Cowles - (escowles@princeton.edu) - Documentarian &amp; Secondary Contact<br /> * Greg Murray - (gregory.murray@ptsem.edu) - Tertiary Contact<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2023 Website Working Group Documents|2023 Website Working Group Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Craig Rosenbeck (rosenbeck_craig@roberts.edu) - Volunteer<br /> * Robert-Anthony Lee-Faison (rl3667-at-princeton-dot-edu) - Volunteer <br /> * Your Name Here - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> 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.<br /> <br /> [[2023 Budget and Sponsorship Documents|2023 Budget and Sponsorship Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Linda Salvesen - (salvesenl@wpunj.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> [[2023 Keynote Documents|2023 Keynote Documents]]<br /> <br /> [[2023 Keynote Speakers Nominations|2023 Keynote Speakers Nominations]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Ranti Junus - Volunteer<br /> * Tyler N Wade-(tw8766@princeton.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2023 Pre-conference Documents|2023 Pre-conference Documents]]<br /> <br /> * Ann Marie Mesco - (mesco@andrew.cmu.edu) - Primary Contact, Chair<br /> * Andrea Schurr - (Andrea-Schurr@utc.edu) - Secondary Contact, CoChair<br /> * Hardy Pottinger - (hardy.pottinger@ucop.edu) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2023 Program Documents|2023 Program Documents]]<br /> <br /> * Matt Sherman - (matt.r.sherman-at-gmail-com) - Primary Contact, Chair<br /> * Dre (akorphan) - Secondary Contact, CoChair<br /> * Andrew Battelini - (abattel@emory.edu)- Documentarian<br /> * Ranti Junus (junus-at-msu-edu) - Volunteer<br /> * Emily Boss (eboss-at-unr-edu) - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> <br /> [[2023 Scholarship Documents|2023 Scholarship Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * Bess Sadler - (bess-dot-sadler-at-princeton-dot-edu) - Secondary Contact, CoChair<br /> * Soojeong Herring - (soojeong-dot-herring-at-colostate-dot-edu) - Documentarian<br /> * Yongming Wang - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> 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<br /> <br /> * Coordinator: Bess Sadler - bess-dot-sadler-at-princeton-dot-edu<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2023 T-Shirt Documents|2023 T-Shirt Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2023 Conference Volunteers]]'''<br /> <br /> [[2023 Online Volunteer Documents|2023 Online Volunteer Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> 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. <br /> <br /> 2023 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> [[2023 Streaming Video Documents|2023 Streaming Video Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * [[User:ksclarke|Kevin S. Clarke]] - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> <br /> == Code4Lib 2023 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2023 Host Voting Documents|2023 Host Voting Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> 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).<br /> <br /> [[2023 Book Giveaway Documents|2023 Book Giveaway Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2023 IRC and Slack Documents|2023 IRC and Slack Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2023 Accessibility Documents|2023 Accessibility Documents]]<br /> <br /> * Kate Deibel - (kndeibel@metageekery.org) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2023 Whatever Documents|2023 Whatever Documents]]<br /> <br /> * NAME - (EMAIL) - Primary Contact, Chair<br /> * NAME - (EMAIL) - Secondary Contact, CoChair<br /> * NAME - (EMAIL) - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> [[Category:Code4Lib2023]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&diff=47260 2019-11-25T15:48:59Z

<p>Hardyoyo: /* Book Giveaway Committee */</p> <hr /> <div>= Code4Lib 2020 Conference Committees =<br /> <br /> 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.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA<br /> * Dates: March 08 (pre-con) - 22, 2020<br /> ** Pre-conferences: March 08, 2020<br /> ** Main meeting: March 09-11, 2020<br /> ** Post conference activities: Coming Soon<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact<br /> * [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact<br /> * [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact<br /> * [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact<br /> * [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact<br /> * [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact<br /> * [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer<br /> * [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2020 Website Working Group Documents|2020 Website Working Group Documents]]<br /> <br /> * [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair<br /> * [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * Julia Caffrey (newbie) - Volunteer <br /> * [[User:Ranti|Ranti Junus]] (v) - Volunteer<br /> * [[User:Tomkeays|Tom Keays]] - Volunteer<br /> * [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer<br /> * [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer <br /> * [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer<br /> <br /> == Budget Committee ==<br /> This group will focus on making sure we are appropriately planning for budgetary issues. <br /> <br /> [[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br /> <br /> * [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)<br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br /> * [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact <br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)<br /> * [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)<br /> <br /> == Sponsorship Committee ==<br /> 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.<br /> <br /> [[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br /> <br /> * Mary Jinglewski - Primary Contact aka Chair<br /> * Scott Carlson - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact <br /> * Janna Avon - Documentarian <br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer<br /> * [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> [[2020 Keynote Documents|2020 Keynote Documents]]<br /> <br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair<br /> * [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)<br /> * [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact <br /> * [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian<br /> * [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer<br /> * [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer<br /> * [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2020 Pre-conference Documents|2020 Pre-conference Documents]]<br /> <br /> * [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact <br /> * [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian<br /> * [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer<br /> * [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer<br /> * [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2020 Program Documents|2020 Program Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair <br /> * [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact <br /> * [mailto:lillyho@gmail.com Lilly Ho] - Volunteer<br /> * [mailto:akorphan@ncsu.edu Dre] - Volunteer<br /> * [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br /> * [mailto:bomanc@oclc.org Craig Boman] - Volunteer<br /> * [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br /> * [[User:RichardHiggins|Richard Higgins]], Indiana University - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> <br /> [[2020 Scholarship Documents|2020 Scholarship Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Co-Chair<br /> * Your Name Here - Primary Contact aka Co-Chair <br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian <br /> * [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer<br /> * [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer<br /> * Your Name Here - (Volunteer)<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2020 T-Shirt Documents|2020 T-Shirt Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair<br /> * [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''<br /> <br /> [[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * [mailto:jenn@concentra-cms.com Jennifer Cummings] &amp; [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer<br /> * [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer<br /> <br /> == Social Activities Committee ==<br /> 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). <br /> <br /> [https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]<br /> <br /> Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]<br /> <br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair<br /> * [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian<br /> * [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br /> * [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> [[2020 Streaming Video Documents|2020 Streaming Video Documents]]<br /> <br /> * [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )<br /> * [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair<br /> * [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)<br /> * [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer<br /> <br /> == Code4Lib 2021 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2021 Host Voting Documents|2021 Host Voting Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> 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).<br /> <br /> [[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]<br /> <br /> * [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * [[User:Hardyoyo|Hardy Pottinger]] - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> Coordinate with freenode to ensure that the #code4lib IRC &amp; Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br /> <br /> [[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair <br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).<br /> <br /> [[2020 Accessibility Documents|2020 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2020 Whatever Documents|2020 Whatever Documents]]<br /> <br /> * [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> [[Category:Code4Lib2020]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib_2020_Conference_Committees&diff=47259 2019-11-25T15:48:18Z

<p>Hardyoyo: officially volunteering for the book giveaway committee</p> <hr /> <div>= Code4Lib 2020 Conference Committees =<br /> <br /> 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.<br /> <br /> We will assign a local contact (LPC) to each committee.<br /> <br /> == Location and Dates ==<br /> <br /> * Location: '''[https://www.marriott.com/hotels/travel/pitwi-the-westin-pittsburgh/ The Westin Pittsburgh]''' Downtown, Pittsburgh, PA<br /> * Dates: March 08 (pre-con) - 22, 2020<br /> ** Pre-conferences: March 08, 2020<br /> ** Main meeting: March 09-11, 2020<br /> ** Post conference activities: Coming Soon<br /> <br /> == Local Planning Committee ==<br /> 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.<br /> <br /> * [mailto:kr2e@andrew.cmu.edu Ken Rose], Carnegie Mellon University - Chair, Primary Contact<br /> * [mailto:jglenn@andrew.cmu.edu Jason Glenn], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:jcorrin@andrew.cmu.edu Julia Corrin], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Tertiary Contact<br /> * [mailto:gesina.a.phillips@gmail.com Gesina Phillips], University of Pittsburgh - Tertiary Contact<br /> * [mailto:sriffe@andrew.cmu.edu Shannon Riffe], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:rashid@andrew.cmu.edu Rashid Siddiqui], Carnegie Mellon University - Tertiary Contact<br /> * [mailto:MStrauss@heinzhistorycenter.org Matthew Strauss], Heinz History Center - Tertiary Contact<br /> * [mailto:MTighe1@Chatham.edu Molly Tighe], Chatham University - Tertiary Contact<br /> * [mailto:tyt3@pitt.edu Tyrica Terry Kapral], University of Pittsburgh - Tertiary Contact<br /> * [mailto:rspotts@andrew.cmu.edu Angelina R Spotts], Carnegie Mellon University - Volunteer<br /> * [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Volunteer<br /> <br /> == Website Working Group ==<br /> 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). <br /> <br /> [[2020 Website Working Group Documents|2020 Website Working Group Documents]]<br /> <br /> * [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair<br /> * [[User:KaitlinNewson|Kaitlin Newson]] (v) - Secondary Contact aka Co-Chair<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco], Carnegie Mellon University - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * Julia Caffrey (newbie) - Volunteer <br /> * [[User:Ranti|Ranti Junus]] (v) - Volunteer<br /> * [[User:Tomkeays|Tom Keays]] - Volunteer<br /> * [[User:KellyHiser|Kelly Hiser]] (newbie) - Volunteer<br /> * [mailto:qum@miamioh.edu Meng Qu] (newbie) - Volunteer <br /> * [[User:Derekz| Derek Zoladz]] (newbie) - Volunteer<br /> <br /> == Budget Committee ==<br /> This group will focus on making sure we are appropriately planning for budgetary issues. <br /> <br /> [[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br /> <br /> * [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair (veteran of 2018)<br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br /> * [mailto:nbharti@andrew.cmu.edu Neelam Bharti] - Local Planning Contact <br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Documentarian (veteran of 2017 and 2018)<br /> * [mailto:bethany@clir.org Bethany Nowviskie] - ex officio, fiscal host (CLIR/DLF)<br /> <br /> == Sponsorship Committee ==<br /> 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.<br /> <br /> [[2020 Budget and Sponsorship Documents|2020 Budget and Sponsorship Documents]]<br /> <br /> * Mary Jinglewski - Primary Contact aka Chair<br /> * Scott Carlson - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact <br /> * Janna Avon - Documentarian <br /> * [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer<br /> * [mailto:Andrea-Schurr@utc.edu Andrea Schurr] - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> 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.<br /> <br /> [[2020 Keynote Documents|2020 Keynote Documents]]<br /> <br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Primary Contact aka Chair<br /> * [mailto:wladimir.labeikovsky@ucdenver.edu Wladimir Labeikovsky], University of Colorado Anschutz Medical Campus - Secondary Contact aka Co-Chair (newbie)<br /> * [mailto:hickss1@duq.edu Sarah Hicks], Duquesne University - Local Planning Contact <br /> * [mailto:sxb891@case.edu Stephanie Becker], Case Western Reserve University - Documentarian<br /> * [mailto:subrama@purdue.edu Annapurni Subramaniam],Purdue University - Volunteer<br /> * [mailto:clara.turp@mcgill.ca Clara Turp], McGill University - Volunteer<br /> * [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br /> <br /> == Pre-conference Committee ==<br /> 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.<br /> <br /> [[2020 Pre-conference Documents|2020 Pre-conference Documents]]<br /> <br /> * [mailto:jglenn@andrew.cmu.edu Jason Glenn] - Primary Contact aka Chair<br /> * [mailto:mesco@andrew.cmu.edu Ann Marie Mesco] - Local Planning Contact <br /> * [mailto:rspotts@andrew.cmu.edu Angelina R Spotts] - Documentarian<br /> * [mailto:tod@uchicago.edu Tod Olson] (v) - Volunteer<br /> * [mailto:mike.taylor@nau.edu Mike Taylor] - Volunteer<br /> * [mailto:KHaley@mwa.org Kathleen Haley] (v) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Program Committee == <br /> 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.<br /> <br /> [[2020 Program Documents|2020 Program Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair <br /> * [mailto:gesina.a.phillips@gmail.com Gesina Phillips] University of Pittsburgh - Local Planning Contact <br /> * [mailto:lillyho@gmail.com Lilly Ho] - Volunteer<br /> * [mailto:akorphan@ncsu.edu Dre] - Volunteer<br /> * [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br /> * [mailto:bomanc@oclc.org Craig Boman] - Volunteer<br /> * [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br /> * [[User:RichardHiggins|Richard Higgins]], Indiana University - Volunteer<br /> <br /> == Scholarship Committee ==<br /> 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.<br /> <br /> [[2020 Scholarship Documents|2020 Scholarship Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Co-Chair<br /> * Your Name Here - Primary Contact aka Co-Chair <br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian <br /> * [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas] - Volunteer<br /> * [mailto:ylee4@uottawa.ca Yoo Young Lee] - Volunteer<br /> * Your Name Here - (Volunteer)<br /> <br /> == T-Shirt Committee ==<br /> 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.<br /> <br /> [[2020 T-Shirt Documents|2020 T-Shirt Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * [mailto:tfluhr@iit.edu Tim Fluhr] Illinois Institute of Technology - Secondary Contact aka Co-Chair<br /> * [mailto:rashid@andrew.edu Rashid Siddiqui] Carnegie Mellon University - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [mailto:mnarlock@nd.edu Mikala Narlock] University of Notre Dame - Volunteer<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2020 Conference Volunteers]]'''<br /> <br /> [[2020 Onsite Volunteer Documents|2020 Onsite Volunteer Documents]]<br /> <br /> * [[User:NatashaAllen|Natasha Allen]] - Primary Contact aka (Co-)Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * [mailto:jenn@concentra-cms.com Jennifer Cummings] &amp; [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [mailto:kbehrman@andrew.cmu.edu Katie Behrman] - Volunteer<br /> * [mailto:rloomis@sclibnj.org Rich Loomis], Somerset County Library System of New Jersey - Volunteer<br /> <br /> == Social Activities Committee ==<br /> 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). <br /> <br /> [https://drive.google.com/drive/folders/1NX5H8G7oRW6-xLi47tnQOoOSNy2Ps2Bu?usp=sharing Social Activities Documents (Members Only)]<br /> <br /> Conference goers - The page you are looking for is coming soon... [[2020 Social Activities]]<br /> <br /> * [mailto:LusterD@Cmoa.Org Dominique Luster], Carnegie Museum of Art - Co-Chair<br /> * [[User:Yoosebj|Becky Yoose]] - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * meredith.c.broadway@vanderbilt.edu Meredith Broadway, Vanderbilt University - Documentarian<br /> * [mailto:eslayton@andrew.cmu.edu Emma Slayton], Carnegie Mellon University - Volunteer<br /> * [mailto:kbehrman@andrew.cmu.edu Katie Behrman], Carnegie Mellon University - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> 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.<br /> <br /> [[2020 Streaming Video Documents|2020 Streaming Video Documents]]<br /> <br /> * [mailto:jester@dltj.org Peter Murray] - Chair (note: what Cary doesn't have, I have.... ;-) )<br /> * [mailto:roytennant@gmail.com Roy Tennant] - Secondary Contact aka Co-Chair<br /> * [mailto:jenn@concentra-cms.com Jennifer Cummings] - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer (note: I have most needed equipment.)<br /> * [mailto:fu@usna.edu Li Fu], U.S. Naval Academy - Volunteer<br /> <br /> == Code4Lib 2021 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2021 Host Voting Documents|2021 Host Voting Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> 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).<br /> <br /> [[2020 Book Giveaway Documents|2020 Book Giveaway Documents]]<br /> <br /> * [[User:JulieSwierczek|Julie C. Swierczek]] - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * [[User:Hardyoyo]] Hardy Pottinger - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> Coordinate with freenode to ensure that the #code4lib IRC &amp; Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br /> <br /> [[2020 IRC and Slack Documents|2020 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair <br /> * Your Name Here - Local Planning Contact <br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees (physical and virtual).<br /> <br /> [[2020 Accessibility Documents|2020 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact aka Chair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2020 Whatever Documents|2020 Whatever Documents]]<br /> <br /> * [mailto:rebecca@califa.org Rebecca Holloway] - Primary Contact aka Chair<br /> * Your Name Here - Secondary Contact aka Co-Chair<br /> * Your Name Here - Local Planning Contact<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> <br /> [[Category:Code4Lib2020]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=One_recommended_tool/resource_for_n00bs&diff=46848 2019-03-30T17:22:25Z

<p>Hardyoyo: added link to Jenn Riley's Seeing Standards site</p> <hr /> <div>===One recommended tool/resource for n00bs===<br /> <br /> These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive]. <br /> <br /> Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!<br /> <br /> ====Tools/Resources====<br /> <br /> =====Books or Things to read=====<br /> * O'Reilly Head first series<br /> * Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245<br /> * [https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]<br /> * [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 &quot;The Pragmatic Programmer&quot;] by Andrew Hunt and David Thomas. A book that teaches beginners how think like a programmer, and reminds experts of good practices.<br /> * The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/<br /> * &quot;How to Design Programs&quot; http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.<br /> * Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 &quot;The C Programming Language.&quot;] A keeper for life, and surprisingly readable and directed to the newbie.<br /> * [http://www.worldcat.org/title/agile-web-development-with-rails-4/oclc/852808602&amp;referer=brief_results Agile Web Development with Rails 4] is a well-paced introduction to Rails and Ruby. Covers a lot of core concepts (MVC, agile development, testing, AJAX).<br /> ** To dive further into Ruby, there's [http://www.worldcat.org/title/programming-ruby-19-20-the-pragmatic-programmers-guide/oclc/855706057&amp;referer=brief_results Programming Ruby] (aka The PickAxe Book)<br /> * http://www.w3.org/International<br /> * Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed<br /> * Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series<br /> <br /> =====Software=====<br /> <br /> * Vi- because it keeps me (you?) focused.<br /> * [http://www.activestate.com/komodo-edit Komodo Edit]<br /> * [http://notepad-plus-plus.org/ Notepad++ IMO best open source lightweight editor on Windows]<br /> *AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.<br /> *A @rdio subscription. :) And a text editor with syntax highlighting.<br /> * Git (Version Control)<br /> * Github, Bitbucket and Other Remote Git Services<br /> * Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets. <br /> * [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]<br /> * LESS http://lesscss.org/ <br /> * Compass http://compass-style.org/ - extends SASS with reusable patterns<br /> * BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]<br /> * Sublime Text &amp; Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.<br /> * The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) &amp; Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.<br /> * [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]<br /> * Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.<br /> <br /> =====Websites=====<br /> * Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)<br /> * Google is more useful than any reference book to find answers to programming problems.<br /> * [http://stackexchange.com/ StackExchange] (by extension, [http://stackoverflow.com StackOverflow]) is a great site for questions.<br /> * [http://lynda.com lynda.com]<br /> * [http://www.pluralsight.com/ PluralSight.com]<br /> * JS Fiddle http://jsfiddle.net/<br /> * CodePen http://codepen.io/<br /> * [http://css-tricks.com CSS Tricks ]<br /> * [http://openhatch.org/ Open Hatch] - to learn tools you need to participate in open source development and find friendly projects to be a part of<br /> * [http://drupalladder.org/ Drupal Ladder], which teaches you what you need to know to participate in developing Drupal<br /> * [http://rubykoans.com/ Ruby Koans] - learn Ruby by fixing failing tests<br /> * [https://librarycarpentry.org/ Library Carpentry] - Free, open-source lessons for non-techy librarians on coding, data analysis, and related topics. They also give in-person workshops upon request.<br /> * [http://jennriley.com/metadatamap/ Seeing Standards] - Let's be frank, there is a giant pile of metadata standards awaiting any newbie to this field. Jenn Riley's map of these standards, and the accompanying glossary, is an invaluable resource. It may be tempting to try to print the PDF of this visualization, just be aware that it is absolutely gigantic. You will need access to a poster printer to do it justice. Don't let that frighten you, feel free to explore it on your computer, save it, keep it as a reference. This poster will help you, you need it.<br /> <br /> =====Meetups and User Groups=====<br /> <br /> * Perl Mongers http://www.pm.org/groups/<br /> * Python Local User Groups http://wiki.python.org/moin/LocalUserGroups<br /> ** Look for user groups running an incarnation of the [http://bostonpythonworkshop.com/ Boston Python Workshop], a women-and-their-friends day-and-a-half introduction to Python which assumes no prior knowledge.<br /> * R Users Group Meetups http://r-users-group.meetup.com/<br /> * Drupal Groups http://groups.drupal.org/<br /> * Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/<br /> ** Look for groups running an incarnation of [http://workshops.railsbridge.org/ RailsBridge] (like Boston Python Workshop except it came first, and covers Ruby)<br /> * Haskell User Groups http://www.haskell.org/haskellwiki/User_groups<br /> * ColdFusion Meetups http://coldfusion.meetup.com/<br /> <br /> =====Other=====<br /> <br /> * Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]<br /> * [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]<br /> * [http://foss4lib.org/ FOSS4lib]<br /> * I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)<br /> * Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).<br /> * It's still useful to learn a little something about configuring a webserver / database / etc.<br /> * The [http://connect.ala.org/node/167971 Library Code Year Interest Group], an ALA group (joint between LITA and ALCTS) for librarians who want to learn and apply code<br /> <br /> =====Advice on what to do=====<br /> *Building things that help people matters, and for that you need empathy.<br /> * Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.<br /> * I'm taking &quot;tool&quot; to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.<br /> * A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.<br /> * +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46840 2019-03-21T18:45:59Z

<p>Hardyoyo: </p> <hr /> <div>== Day 1 - February 20, 2019 ==<br /> # [https://osf.io/fby9s/ Islandora for All: ISLE + LASIR + Community Engagement] - David Keiser-Clark<br /> # [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery<br /> # [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis<br /> # [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre<br /> # [https://github.com/hardyoyo/code4lib19-serverspec-talk Wait, what? Getting your bearings with ServerSpec] - Hardy Pottinger<br /> # EaaSI project update: Call for community feedback on software prioritization - Ethan Gates<br /> # RATOM (Review, Appraisal and Triage of Emails)- Cal Lee<br /> # [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.<br /> # 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]]<br /> # [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br /> <br /> == Day 2 - February 21, 2019 ==<br /> # 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)<br /> # The Patron Data Firehose - David Lacy<br /> # [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]<br /> # The Real World of Technology - Ashley Blewer<br /> # Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]<br /> # Profiles Core - Karen Coyle<br /> # [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel<br /> # Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br /> <br /> == Day 3 - February 22, 2019 ==<br /> # [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis<br /> # [https://osf.io/x75bk/ What is Audio Description] - Carli Spina<br /> # [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark<br /> # Web-based AR. Simple! - Dan Lou<br /> # We Are Family - Code4Lib Local Chapters - Thomas Guignard<br /> # Making a staff calendar: an intro to automation - Zach Pell<br /> # Speed mentoring/skill share<br /> #</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46839 2019-03-21T18:45:02Z

<p>Hardyoyo: added link to my lightning talk slides</p> <hr /> <div>== Day 1 - February 20, 2019 ==<br /> # [https://osf.io/fby9s/ Islandora for All: ISLE + LASIR + Community Engagement] - David Keiser-Clark<br /> # [https://osf.io/jwcg4/ Does your catalog spark joy?] - Sean Aery<br /> # [https://osf.io/mpqdh/ Implementing a redesign from user feedback] - Nikitas Tampakis<br /> # [https://osf.io/unwbc/ What a baby taught me about affordances] - Dre<br /> # [https://github.com/hardyoyo/code4lib19-serverspec-talk Wait, what? Getting your bearings with server spec] - Hardy Pottinger<br /> # EaaSI project update: Call for community feedback on software prioritization - Ethan Gates<br /> # RATOM (Review, Appraisal and Triage of Emails)- Cal Lee<br /> # [https://ld4p.github.io/code4lib_2019/cataloging-interface Cataloging Interface for Linked Data] - Jeremy Nelson + Naomi D.<br /> # 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]]<br /> # [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br /> <br /> == Day 2 - February 21, 2019 ==<br /> # 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)<br /> # The Patron Data Firehose - David Lacy<br /> # [http://preservethispodcast.org/ Preserve this Podcast] - Sarah Nguyen [[https://github.com/mnylc/preservethispodcast github]]<br /> # The Real World of Technology - Ashley Blewer<br /> # Hyku - Samvera in a Box [[https://github.com/samvera/hyku github]]<br /> # Profiles Core - Karen Coyle<br /> # [https://osf.io/8ncbf/ Keyboard Accessibility Testing]- Kate Deibel<br /> # Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br /> <br /> == Day 3 - February 22, 2019 ==<br /> # [https://osf.io/7sba2/ Mirador 3.0 Status Report] - Shaun Ellis<br /> # [https://osf.io/x75bk/ What is Audio Description] - Carli Spina<br /> # [https://t.co/ERUhQcFiff Can't Get This Thing to .WARC (or linked BioScience)] - Jason Clark<br /> # Web-based AR. Simple! - Dan Lou<br /> # We Are Family - Code4Lib Local Chapters - Thomas Guignard<br /> # Making a staff calendar: an intro to automation - Zach Pell<br /> # Speed mentoring/skill share<br /> #</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=46694 2019-02-15T18:17:52Z

<p>Hardyoyo: add slack channel info to the Livestream QA (Remote) volunteer info</p> <hr /> <div>= Code4Lib 2019 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br /> <br /> Onsite Volunteer Committee Coordinator: N/A<br /> <br /> * Karen Coyle<br /> * Justin Coyne<br /> * Shaun Ellis<br /> * Erin Fahy<br /> * Bobbi Fox<br /> * Wayne Graham<br /> * Francis Kayiwa<br /> * Megan Kudzia<br /> * Anne Slaughter<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br /> <br /> Monday, day before:<br /> * 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br /> * 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br /> * 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br /> * 3pm - 6pm: [[User:Anarchivist|Mark Matienzo]]<br /> <br /> Tuesday, preconference day:<br /> * 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br /> * 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]<br /> * 1pm - 3pm: ''Your Name Here''<br /> <br /> Wednesday, day one:<br /> * 8am - 9:30am: ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * 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)<br /> * 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br /> * 7:30-8:30pm Reception: ''Your Name Here''<br /> * https://www.thetech.org/floor-maps Floor Map. Lower Level<br /> <br /> <br /> <br /> Thursday, Day Two:<br /> * 9:30-10pm Game Night Cleanup: [[User:Phette23|Eric Phetteplace]]<br /> * 9:30-10pm Game Night Cleanup: [[User:hardyoyo|Hardy Pottinger]]<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Twitter (#c4l19), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> 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<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> Wednesday, Day Two:<br /> * AM volunteer: [[User:Kimpham54|Kim Pham]]<br /> * AM volunteer: Thomas Guignard<br /> * PM volunteer: Lydia Zvyagintseva<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Three:<br /> * AM volunteer: ''Whitni''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: [[User:ChrisDay|Chris Day]]<br /> * PM volunteer: Lydia Zvyagintseva<br /> <br /> Friday, Day Four:<br /> * AM volunteer: [[User:ChrisDay|Chris Day]]<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: Cary Gordon<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: [mailto:fu@usna.edu Li Fu]<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: [mailto:fu@usna.edu Li Fu]<br /> * PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br /> <br /> == Livestream QA (Remote) ==<br /> 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).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #livestream-qa channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);<br /> * PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);<br /> * PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: ''Your Name Here'' (East); Kevin Clair (West)<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> * Before the conference: [[User:Kimpham54|Kim Pham]] &amp; [[User:Anarchivist|Mark Matienzo]]<br /> * During the conference: [[User:Anarchivist|Mark Matienzo]] &amp; &quot;Your Name Here&quot; &amp; [[User:Kimpham54|Kim Pham]]<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:tallgood|Tammy Allgood Wolf]]<br /> <br /> Wednesday, Day One:<br /> * AM Volunteer: Dre<br /> * PM Volunteer: Whitni<br /> <br /> Thursday, Day Two:<br /> * AM Volunteer: [http://mailto:phette23@gmail.com Eric Phetteplace]<br /> * PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]<br /> <br /> Friday, Day Three:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: 'Your Name Here''<br /> * PM Volunteer: Whitni<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: Whitni<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br /> * [[User:rtennant|Roy Tennant]]<br /> * [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> [[Category: Code4Lib2019]]</div>

Hardyoyo https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=46673 2019-02-15T16:17:41Z

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

Hardyoyo https://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=46664 2019-02-14T00:17:36Z

<p>Hardyoyo: signing up for MC duty, Thursday afternoon</p> <hr /> <div>= Code4Lib 2019 Conference Volunteers =<br /> <br /> Call for volunteers during the actual conference, as opposed to the conference planning committees.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2019.code4lib.org/conduct/#officers for more details, including contact information.<br /> <br /> Onsite Volunteer Committee Coordinator: N/A<br /> <br /> * Karen Coyle<br /> * Justin Coyne<br /> * Shaun Ellis<br /> * Erin Fahy<br /> * Bobbi Fox<br /> * Wayne Graham<br /> * Francis Kayiwa<br /> * Megan Kudzia<br /> * Anne Slaughter<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br /> <br /> Monday, day before:<br /> * 3pm - 6pm: [[User:Phette23|Eric Phetteplace]]<br /> * 3pm - 6pm: [[User:Kimpham54|Kim Pham]]<br /> * 3pm - 6pm: [[User:rtennant|Roy Tennant]]<br /> * 3pm - 6pm: ''Your Name Here''<br /> <br /> Tuesday, preconference day:<br /> * 8am - 10am: [[User:Hardyoyo|Hardy Pottinger]]<br /> * 8am - 10am: [[User:KaitlinNewson|Kaitlin Newson]]<br /> * 1pm - 3pm: ''Your Name Here''<br /> <br /> Wednesday, day one:<br /> * 8am - 9:30am: ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day One:<br /> * 6:30-7:30pm Reception: ''Your Name Here'' (need to be at venue at 6:30pm so on the first bus or arrive on their own)<br /> * 6:30-7:30pm Reception: ''Your Name Here'' (ditto)<br /> * 7:30-8:30pm Reception: ''Your Name Here''<br /> * 9:30-10pm Game Night Cleanup: ''Your Name Here''<br /> * 9:30-10pm Game Night Cleanup: ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> Tuesday, Preconference Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Friday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> Wednesday, Day Two:<br /> * AM volunteer: [[User:Kimpham54|Kim Pham]]<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: Lydia Zvyagintseva<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Three:<br /> * AM volunteer: ''Whitni''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: [[User:ChrisDay|Chris Day]]<br /> * PM volunteer: 'Lydia Zvyagintseva<br /> <br /> Friday, Day Four:<br /> * AM volunteer: [[User:ChrisDay|Chris Day]]<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream Assistants (Onsite) ==<br /> <br /> 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!<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Phette23|Eric Phetteplace]]<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: Cary Gordon<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * PM Volunteer: ''Your Name Here''<br /> * PM Volunteer: [mailto:fu@usna.edu Li Fu]<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: [mailto:fu@usna.edu Li Fu]<br /> * PM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> * AM Volunteer: [mailto:ethan.t.gates@gmail.com Ethan Gates]<br /> <br /> == Livestream QA (Remote) ==<br /> 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).<br /> <br /> Onsite Volunteer Committee Coordinator: Hardy Pottinger<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); [[User:ElissaThomas|Elissa Thomas]] (West);<br /> * PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); ''Your Name Here'' (West)<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West);<br /> * PM volunteer: [[User:DataGazetteer|Peter Murray]] (East); Jeff Rynhart (West)<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: ''Your Name Here'' (East); Kevin Clair (West)<br /> <br /> == IRC/Slack (Technical) ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator: [[User:Kimpham54|Kim Pham]]<br /> <br /> * Before the conference: [[User:Kimpham54|Kim Pham]] &amp; [[User:Anarchivist|Mark Matienzo]]<br /> * During the conference: [[User:Anarchivist|Mark Matienzo]] &amp; &quot;Your Name Here&quot; &amp; [[User:Kimpham54|Kim Pham]]<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: Dre<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: [[User:hardyoyo|Hardy Pottinger]]<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: [[User:rtennant|Roy Tennant]]<br /> <br /> == Session Timers ==<br /> 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.<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Wednesday, Day Two:<br /> * AM Volunteer: 'Your Name Here''<br /> * PM Volunteer: ''Whitni''<br /> <br /> Thursday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Friday, Day Four:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * [[User:Phette23|Eric Phetteplace]] phette23 on slack or gmail<br /> * [[User:rtennant|Roy Tennant]]<br /> * [[User:Hardyoyo|Hardy Pottinger]] hpottinger on slack or -at-library-dot-ucla-dot-edu<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> [[Category: Code4Lib2019]]</div>

Hardyoyo