https://wiki.code4lib.org/api.php?action=feedcontributions&user=Rtennant&feedformat=atomCode4Lib - User contributions [en]2024-03-19T10:22:06ZUser contributionsMediaWiki 1.26.2https://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46781Code4Lib2019 Lightning Talks2019-02-22T16:19:02Z<p>Rtennant: /* Day 3 - February 23, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# Mirador 3.0 Status Report - Shaun Ellis<br />
# What is Audio Description - Carli Spina<br />
# 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 />
# <br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46780Code4Lib2019 Lightning Talks2019-02-22T01:23:42Z<p>Rtennant: /* Day 3 - February 23, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46779Code4Lib2019 Lightning Talks2019-02-22T01:23:02Z<p>Rtennant: /* Day 2 - February 21, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46778Code4Lib2019 Lightning Talks2019-02-22T01:21:53Z<p>Rtennant: /* Day 2 - February 21, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - [https://osf.io/c2459 Slides] - 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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46777Code4Lib2019 Lightning Talks2019-02-22T01:20:59Z<p>Rtennant: /* Day 2 - February 21, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# [https://osf.io/c2459 Roots of Code4Lib] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)<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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46776Code4Lib2019 Lightning Talks2019-02-22T01:20:43Z<p>Rtennant: /* Day 2 - February 21, 2019 */</p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<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 />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# [ https://osf.io/c2459 Roots of Code4Lib] - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)<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://tinyurl.com/deibel-keyboard Keyboard Accessibility Testing]- Kate Deibel<br />
# Code4lib Continuity (everybody raise your hands and claps!) - Mike Giarlo<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46738Code4Lib2019 Lightning Talks2019-02-21T05:43:28Z<p>Rtennant: </p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<br />
# Does your catalog spark joy? - Sean Aery<br />
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# What a baby taught me about affordances - Dre<br />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and many thereafter)<br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
#<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46737Code4Lib2019 Lightning Talks2019-02-21T05:42:58Z<p>Rtennant: </p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<br />
# Does your catalog spark joy? - Sean Aery<br />
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# What a baby taught me about affordances - Dre<br />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference and several thereafter)<br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
#<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46736Code4Lib2019 Lightning Talks2019-02-21T05:42:36Z<p>Rtennant: </p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<br />
# Does your catalog spark joy? - Sean Aery<br />
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# What a baby taught me about affordances - Dre<br />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - Karen Coombs (participant of every conference), Ryan Wick (participant of every conference), and Roy Tennant (participant at first conference)<br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
#<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib2019_Lightning_Talks&diff=46735Code4Lib2019 Lightning Talks2019-02-21T05:41:10Z<p>Rtennant: </p>
<hr />
<div>== Day 1 - February 20, 2019 ==<br />
# Islandora for All: ISLE - community engagement and lowering barriers [[https://github.com/Islandora-Collaboration-Group/ISLE github]]<br />
# Does your catalog spark joy? - Sean Aery<br />
# [https://docs.google.com/presentation/d/1ZiaS4kNTl3iscn4NlCCce9K7T_zHm9T6ufERgKTzTvw/edit#slide=id.p Implementing a redesign from user feedback] - Nikitas Tampakis<br />
# What a baby taught me about affordances - Dre<br />
# Wait, what? Getting your bearings with server spec - Hardy<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 [[https://github.com/CCA-Public/dip-access-interface github]]<br />
# [http://bit.ly/c4l19-csv Whither CSV's?] - Mark Matienzo<br />
<br />
<br />
== Day 2 - February 21, 2019 ==<br />
# Roots of Code4Lib - Karen Coombs, Ryan Wick, and Roy Tennant<br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
# <br />
#<br />
<br />
== Day 3 - February 23, 2019 ==<br />
# <br />
# <br />
# <br />
# <br />
#<br />
# <br />
# <br />
#<br />
# <br />
#</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Logo_Design_Process&diff=46663Logo Design Process2019-02-13T22:38:36Z<p>Rtennant: /* History */ Fixed a broken URL</p>
<hr />
<div>__NOTOC__<br />
This page will document the process we are undertaking to create a logo for Code4Lib.<br />
<br />
== Working Group ==<br />
<br />
<br />
* Roy Tennant<br />
* Ranti Junus<br />
* Emily Molanphy<br />
<br />
== Process ==<br />
<br />
* We (the working group) will draft a logo requirements statement -- what Code4Lib is, who we are, and any kind of "messages" or "themes" we think should be considered in the design process.<br />
* When we're satisfied with the draft, we send it past David Cloutman, who has offered to review it.<br />
* We make any adjustments we want based on David's feedback.<br />
* We send it out the Code4Lib list for group comments.<br />
* We change it, if necessary, based on the feedback.<br />
* We submit it to Stephanie so she can get started, requesting a few draft concepts for review and feedback.<br />
* We request volunteers to help review the drafts who have familiarity with the process of selecting a logo.<br />
* When the draft designs are available, the working group and the volunteers select one design to further develop (if needed)<br />
* We forward to Stephanie collated suggestions for anything we'd like to see in a final version.<br />
<br />
== Requirements Document ==<br />
<br />
'''Code4Lib Logo Design Briefing and Requirements'''<br />
<br />
''About Code4Lib''<br />
<br />
Code4Lib is a loose collaboration of library software developers and technologists interested in learning, sharing their experiences, and having fun. There is no "membership", you simply participate. There is no "organization", you simply lead. Anyone who wishes to be involved with an activity (for example, the Code4Lib Journal) simply does it. <br />
<br />
There are many ways to participate. Code4Lib offers a web site, a wiki, a chatroom, a mailing list, an RSS aggregation service, a journal, and a conference. <br />
<br />
Key themes to consider include software, technology, libraries, librarians, participation, openness, and collaboration. The group is very technically-inclined and savvy about writing, debugging, and deploying software. At the same time, the group has a playful attitude and has fun while doing serious work.<br />
<br />
''Logo requirements:''<br />
* The organization name (Code4Lib) must be included in the final logo.<br />
* The logo must be identifiable.<br />
* The logo should be simple and clear in concept.<br />
* It must be distinctive in the quality and originality of its visual image and not offend any sensitivities.<br />
* The concept should have relevance to the organization.<br />
* It must adapt well to electronic and printed media, to reproduction on small surfaces, and to use in color, both in positive and in negative form.<br />
* It must be free of any copyright or other intellectual property claims.<br />
<br />
== History ==<br />
<br />
On September 19, 2008 Roy Tennant [http://serials.infomotions.com/code4lib/archive/2008/200809/1492.html posted a suggestion] on the Code4Lib mailing list that we create a logo for this group.<br />
<br />
There was enough interest expressed that Roy put up an online poll. The result of [http://serials.infomotions.com/code4lib/archive/2008/200809/1544.html that vote] indicated a strong interest in creating a logo, but the preferred process for doing so was not clear.<br />
<br />
A run-off vote was then held, and "Professional Option 1" [http://dilettantes.code4lib.org/voting_booth/election/results/6 won the vote], which was "We accept Stephanie Brinley's kind offer, request a few different ideas, vote on those ideas to settle on one, and the final version is created from the winning idea."<br />
<br />
A [http://serials.infomotions.com/code4lib/archive/2008/200811/1993.html call for volunteers] to draft a requirements document was then made, and Ranti Junus and Emily Molanphy volunteered.<br />
<br />
On January 5, 2009, Stephanie Brinley submitted a set of [http://roytennant.com/c4ldesigns.pdf draft concepts] and Roy Tennant called for volunteers with experience in a logo design process to view and comment on the concepts.<br />
<br />
The following Code4Lib participants volunteered to help review the designs and comment: Sean Hannan, Karen Schneider, Rob Styles, Steve Toub, Tito Sierra, and David Cloutman.<br />
<br />
On January 8, 2009, Roy Tennant [http://roytennant.com/1-8-09.txt replied to Stephanie] with the summarized response from the reviewers.<br />
<br />
On January 12, 2009, Stephanie Brinley replied with a set of [http://roytennant.com/c4l_finalvariations.pdf final variations] in response to our feedback.<br />
<br />
On January 16, 2009, the group decided to go with option #1, while checking with Stephanie that the colors were actual Pantone colors.<br />
<br />
On January 29, 2009, Roy Tennant created [https://code4lib.org/2009/01/29/code4lib-logo.html a page on the code4lib web site] for all of the files and instructions.</div>Rtennanthttps://wiki.code4lib.org/index.php?title=User:Rtennant&diff=46657User:Rtennant2019-02-13T05:34:55Z<p>Rtennant: </p>
<hr />
<div><br />
== Roy Tennant ==<br />
<br />
* royt in IRC<br />
* rtennant in Slack<br />
* roytennant at gmail<br />
* text or call 707-287-5580<br />
* [http://roytennant.com/ Website]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466352019 Conference Volunteers2019-02-08T04:56:25Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[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: [http://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: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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: [[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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466342019 Conference Volunteers2019-02-08T04:55:53Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[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: [http://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: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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: [[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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466332019 Conference Volunteers2019-02-08T04:54:59Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[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: [http://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: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [[User:rtennant|Roy Tennant]]<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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 />
== 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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466322019 Conference Volunteers2019-02-08T04:54:03Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[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: [http://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: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [User:rtennant|Roy Tennant]<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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 />
== 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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466312019 Conference Volunteers2019-02-08T04:52:53Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: [rtennant Roy Tennant]<br />
* PM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: [rtennant Roy Tennant]<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: [rtennant Roy Tennant]<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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 />
== 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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=User:Rtennant&diff=46630User:Rtennant2019-02-08T04:51:06Z<p>Rtennant: </p>
<hr />
<div><br />
== Roy Tennant ==<br />
<br />
* royt in channel<br />
* roytennant at gmail<br />
* text or call 707-287-5580<br />
* [http://roytennant.com/ Website]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=User:Rtennant&diff=46628User:Rtennant2019-02-08T04:50:25Z<p>Rtennant: </p>
<hr />
<div><br />
== Roy Tennant ==<br />
<br />
* royt in channel<br />
* roytennant at gmail<br />
* text or call 707-287-5580</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=466272019 Conference Volunteers2019-02-08T04:49:52Z<p>Rtennant: </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 />
* Hardy Pottinger<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 "LOCAL" 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 & 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: ''Your Name Here''<br />
* 8am - 10am: ''Your Name Here''<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:<br />
<br />
Wednesday, 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 />
Thursday, 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 />
Friday, Day Four:<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: [[User:Phette23|Eric Phetteplace]]<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: Cary Gordon<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: Roy Tennant<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: Roy Tennant<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: [http://mailto:fu@usna.edu Li Fu]<br />
* PM Volunteer: ''Your Name Here''<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: Roy Tennant<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 are Pacific Standard Time (PST).<br />
<br />
Onsite Volunteer Committee Coordinator: <br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday, Day Three:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday, Day Four:<br />
* AM Volunteer: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* PM volunteer: ''Your Name Here'' (East); ''Your Name Here'' (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]]<br />
* During the conference: ''Your Name Here'' & "Your Name Here" & [[User:Kimpham54|Kim Pham]]<br />
<br />
==MCs==<br />
<br />
Onsite Volunteer Committee Coordinator: Tammy Allgood Wolf<br />
<br />
Wednesday, Day Two:<br />
* AM Volunteer: ''Your Name Here''<br />
* PM Volunteer: ''Your Name Here''<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 />
== 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: ''Your Name Here''<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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Main_Page&diff=46625Main Page2019-02-08T04:48:49Z<p>Rtennant: </p>
<hr />
<div><!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"<br />
| style="width:54%; color:#000;" |<br />
<!-- "WELCOME TO WIKIPEDIA" AND ARTICLE COUNT --><br />
{| border:none; background:none;"<br />
| text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4Lib wiki</div><br />
|}<br />
<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
__NOTOC__<br />
| style="width:20%; font-size:95%;vertical-align:top; " |<br />
* [[#About Code4Lib|About Code4Lib]]<br />
* [[#Software Usage and Documentation|Software Usage and Documentation]]<br />
* [[#Current topics|Current topics]]<br />
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[#Code4Lib 2019 Conference|2019 Conference]]<br />
* [[#Local / Regional Groups|Local / Regional Groups]]<br />
* [[#Interest Groups|Interest Groups]]<br />
* [[#Earlier Conferences and events|Earlier Conferences and events]]<br />
|}<br />
<br />
<!-- ABOUT --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
|-<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.<br />
* [[Zoia or the Code4Lib IRC bot]]<br />
|-<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist<br />
|-<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Regional Meeting Streaming]]<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
* [[Libraries Sharing Code]]<br />
* [[Code4Lib Tagline brainstorm]]<br />
* [[Fiscal Continuity]]<br />
** [[Fiscal Sponsorship Working Group]]<br />
* [[Accessibility]]<br />
* [[Teaching beginners]] <br />
|-<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
|-<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
|}<br />
| style="border:1px solid transparent;" |<br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
<br />
==Code4Lib 2019 Conference==<br />
{{:Category:Code4Lib2019}}<br />
* [[2019_Keynote_Speakers_Nominations|2019 Keynote Nominations]]<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
* [[2019_Conference_Volunteers|ON-SITE CONFERENCE VOLUNTEERS]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
=== United States ===<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest<br />
* [[South_Central|Code4Lib South Central]] - Texas, Oklahoma, Louisiana, Arkansas, New Mexico<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[Western|Code4Lib West]] - California North and South <br />
<br />
=== Canada ===<br />
<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[North|code4lib North]] - Ontario and surrounding areas<br />
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<br />
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br />
<br />
=== Europe ===<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
<br />
=== Asia/Pacific ===<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
<br />
=== Middle East ===<br />
* [[Qatar|Code4Lib Qatar]] - Doha ''(new in 2018)''<br />
|-<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
* [[Fiscal_Continuity|Fiscal Continuity]] - A group that explored from 2016 to 2017 whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)<br />
* [[Fiscal_Sponsorship_Working_Group|Fiscal Sponsorship Working Group]] - A group formed to implement a fiscal sponsorship agreement per the results of the [[Fiscal_Continuity#Fiscal_Options_Vote|fiscal options vote]] in late 2017<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
== Earlier Conferences and events ==<br />
* [[:Category:Code4Lib2018|Code4Lib 2018]] Washington, DC<br />
* [[:Category:Code4Lib2017|Code4Lib 2017]] Los Angeles, CA<br />
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA<br />
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR<br />
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC<br />
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL<br />
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA<br />
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IN<br />
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC<br />
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI<br />
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR<br />
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA<br />
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR<br />
[[Conference Financial History At A Glance]]<br />
<br />
=== Older Conference T-Shirt Designs ===<br />
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]<br />
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]<br />
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Main_Page&diff=46624Main Page2019-02-08T04:48:25Z<p>Rtennant: </p>
<hr />
<div><!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"<br />
| style="width:54%; color:#000;" |<br />
<!-- "WELCOME TO WIKIPEDIA" AND ARTICLE COUNT --><br />
{| border:none; background:none;"<br />
| text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4Lib wiki</div><br />
|}<br />
<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
__NOTOC__<br />
| style="width:20%; font-size:95%;vertical-align:top; " |<br />
* [[#About Code4Lib|About Code4Lib]]<br />
* [[#Software Usage and Documentation|Software Usage and Documentation]]<br />
* [[#Current topics|Current topics]]<br />
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[#Code4Lib 2019 Conference|2019 Conference]]<br />
* [[#Local / Regional Groups|Local / Regional Groups]]<br />
* [[#Interest Groups|Interest Groups]]<br />
* [[#Earlier Conferences and events|Earlier Conferences and events]]<br />
|}<br />
<br />
<!-- ABOUT --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
|-<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.<br />
* [[Zoia or the Code4Lib IRC bot]]<br />
|-<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist<br />
|-<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Regional Meeting Streaming]]<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
* [[Libraries Sharing Code]]<br />
* [[Code4Lib Tagline brainstorm]]<br />
* [[Fiscal Continuity]]<br />
** [[Fiscal Sponsorship Working Group]]<br />
* [[Accessibility]]<br />
* [[Teaching beginners]] <br />
|-<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
|-<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
|}<br />
| style="border:1px solid transparent;" |<br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
<br />
==Code4Lib 2019 Conference==<br />
{{:Category:Code4Lib2019}}<br />
* [[2019_Keynote_Speakers_Nominations|2019 Keynote Nominations]]<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
* [[2019_Conference_Volunteers ON-SITE CONFERENCE VOLUNTEERS]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
=== United States ===<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest<br />
* [[South_Central|Code4Lib South Central]] - Texas, Oklahoma, Louisiana, Arkansas, New Mexico<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[Western|Code4Lib West]] - California North and South <br />
<br />
=== Canada ===<br />
<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[North|code4lib North]] - Ontario and surrounding areas<br />
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<br />
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br />
<br />
=== Europe ===<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
<br />
=== Asia/Pacific ===<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
<br />
=== Middle East ===<br />
* [[Qatar|Code4Lib Qatar]] - Doha ''(new in 2018)''<br />
|-<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
* [[Fiscal_Continuity|Fiscal Continuity]] - A group that explored from 2016 to 2017 whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)<br />
* [[Fiscal_Sponsorship_Working_Group|Fiscal Sponsorship Working Group]] - A group formed to implement a fiscal sponsorship agreement per the results of the [[Fiscal_Continuity#Fiscal_Options_Vote|fiscal options vote]] in late 2017<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
== Earlier Conferences and events ==<br />
* [[:Category:Code4Lib2018|Code4Lib 2018]] Washington, DC<br />
* [[:Category:Code4Lib2017|Code4Lib 2017]] Los Angeles, CA<br />
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA<br />
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR<br />
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC<br />
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL<br />
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA<br />
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IN<br />
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC<br />
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI<br />
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR<br />
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA<br />
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR<br />
[[Conference Financial History At A Glance]]<br />
<br />
=== Older Conference T-Shirt Designs ===<br />
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]<br />
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]<br />
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Conference_Volunteers&diff=465992019 Conference Volunteers2019-02-05T19:40:46Z<p>Rtennant: </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 />
== 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 "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br />
<br />
== Conference Logistics ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Day One:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Two:<br />
* 8a-12p: ''Your Name Here''<br />
<br />
== Duty Officers ==<br />
<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
== Preconference Setup & Sessions==<br />
Help manage preconference sessions, setting up projectors, etc.<br />
<br />
Preconference Setup Day One:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Preconference Sessions Day One:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
<br />
== Social Events ==<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc.<br />
<br />
Day Two:<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 />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Day Two:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Three:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Four:<br />
* Time TBD:''Your Name Here''<br />
<br />
Day Five:<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Day Three:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Four:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Five:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
Livestream assitants 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 />
Wednesday:<br />
* Time TBD: Cary Gordon<br />
* Time TBD: Roy Tennant<br />
<br />
Thursday:<br />
* Time TBD: Roy Tennant<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday:<br />
* Time TBD: Roy Tennant<br />
* Time TBD: ''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 are Pacific Standard Time (PST).<br />
<br />
Day Three:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Day Four:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Day Five:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (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.<br />
<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Day Three:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Four:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Day Five:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
Day Three:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
<br />
Day Four:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
<br />
Day Five:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''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 />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46598Code4Lib 2019 Conference Committees2019-02-05T19:38:29Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[http://doubletree3.hilton.com/en/hotels/california/doubletree-by-hilton-hotel-san-jose-JOSE-DT/index.html DoubleTree by Hilton]''' near the Airport, San José, CA<br />
* Dates: February 19 (pre-con) - 22, 2019<br />
** Pre-conferences: February 19, 2019<br />
** Main meeting: February 20-22, 2019<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:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - Chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair<br />
* [[User:WhitniWatkins|Whitni Watkins]], Analog Devices, Inc. - Secondary Contact aka Co-Chair (if you want to volunteer and you've not served on any Code4Lib committees before, let me know, I'll step aside) <br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* [http://mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Documentarian<br />
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer<br />
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer<br />
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer<br />
* Cody Whitby, Virginia Commonwealth University - Volunteer<br />
* Laura Chuang - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* Mark Matienzo - 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 />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<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 />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Primary Contact aka Chair<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol], Long Beach City College - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* [mailto:dicossio@crimson.ua.edu Diana Cossio]- Documentarian <br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<br />
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer<br />
* [mailto:cmathieu@jpl.nasa.gov Camille Mathieu], JPL Library - Volunteer<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam], Purdue - 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 />
[[2019 Keynote Documents|2019 Keynote Documents]]<br />
<br />
* [mailto:axm1195@case.edu Andrew Mancuso] - Primary Contact aka Chair<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact <br />
* [mailto:lconrad@cca.edu Lisa Conrad] - Documentarian<br />
* [mailto:ehenry124@gmail.com Elizabeth Henry] - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp] - Volunteer<br />
* [mailto:crh92@case.edu Charlie Harper] - 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 />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lydiaz@ualberta.ca Lydia Zvyagintseva] - Volunteer<br />
* [mailto:tod@uchicago.edu Tod Olson] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] - Volunteer<br />
* [[User:Kimpham54|Kim Pham]] - 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 />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer <br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [[User:DanielDraper|Dan Draper]] - Volunteer<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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 />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian <br />
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)<br />
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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 />
[[2019 T-Shirt Documents|2019 T-Shirt Documents]]<br />
<br />
* [mailto:ewahl@folger.edu Emily Wahl] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:matienzo@stanford.edu Mark Matienzo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - 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 [[2019 Conference Volunteers]]'''<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* [mailto:Kim.Pham60@du.edu Kim Pham] U Denver - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:hpottinger@library.ucla.edu Hardy Pottinger] UCLA Library - Volunteer<br />
* [mailto:Tammy.Allgood@asu.edu Tammy Wolf] Arizona St. - 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 at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair<br />
* [http://wiki.code4lib.org/User:NatashaAllen Natasha Allen] - Secondary Contact aka Co-Chair<br />
* [mailto:amcollie@stanford.edu Aaron Collier] - Local Planning Contact<br />
* Meredith Broadway - Documentarian<br />
* Ann S. - 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 />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - Chair<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 2020 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 />
[[2020 Host Voting Documents|2020 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Roy Tennant - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lillyho@gmail.com Lilly HS HO] - 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 />
[[2019 Book Giveaway Documents|2019 Book Giveaway 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 />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair <br />
* [[User:Anarchivist|Mark A. Matienzo]] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:JieChen|Jie Chen]], Univ. of WI-Milwaukee Libraries - 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 />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair<br />
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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 />
[[2019 Whatever Documents|2019 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:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46597Code4Lib 2019 Conference Committees2019-02-05T19:19:16Z<p>Rtennant: /* Local Planning Committee */</p>
<hr />
<div>= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[http://doubletree3.hilton.com/en/hotels/california/doubletree-by-hilton-hotel-san-jose-JOSE-DT/index.html DoubleTree by Hilton]''' near the Airport, San José, CA<br />
* Dates: February 19 (pre-con) - 22, 2019<br />
** Pre-conferences: February 19, 2019<br />
** Main meeting: February 20-22, 2019<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:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - Chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair<br />
* [[User:WhitniWatkins|Whitni Watkins]], Analog Devices, Inc. - Secondary Contact aka Co-Chair (if you want to volunteer and you've not served on any Code4Lib committees before, let me know, I'll step aside) <br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* [http://mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Documentarian<br />
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer<br />
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer<br />
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer<br />
* Cody Whitby, Virginia Commonwealth University - Volunteer<br />
* Laura Chuang - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* Mark Matienzo - 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 />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<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 />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Primary Contact aka Chair<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol], Long Beach City College - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* [mailto:dicossio@crimson.ua.edu Diana Cossio]- Documentarian <br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<br />
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer<br />
* [mailto:cmathieu@jpl.nasa.gov Camille Mathieu], JPL Library - Volunteer<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam], Purdue - 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 />
[[2019 Keynote Documents|2019 Keynote Documents]]<br />
<br />
* [mailto:axm1195@case.edu Andrew Mancuso] - Primary Contact aka Chair<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact <br />
* [mailto:lconrad@cca.edu Lisa Conrad] - Documentarian<br />
* [mailto:ehenry124@gmail.com Elizabeth Henry] - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp] - Volunteer<br />
* [mailto:crh92@case.edu Charlie Harper] - 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 />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lydiaz@ualberta.ca Lydia Zvyagintseva] - Volunteer<br />
* [mailto:tod@uchicago.edu Tod Olson] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] - Volunteer<br />
* [[User:Kimpham54|Kim Pham]] - 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 />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer <br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [[User:DanielDraper|Dan Draper]] - Volunteer<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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 />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian <br />
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)<br />
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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 />
[[2019 T-Shirt Documents|2019 T-Shirt Documents]]<br />
<br />
* [mailto:ewahl@folger.edu Emily Wahl] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:matienzo@stanford.edu Mark Matienzo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - 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 [[2019 Conference Volunteers]]'''<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* [mailto:Kim.Pham60@du.edu Kim Pham] U Denver - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jenn@concentra-cms.com Jennifer Cummings] & [mailto:kathy@concentra-cms.com Kathy Azevedo] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:hpottinger@library.ucla.edu Hardy Pottinger] UCLA Library - Volunteer<br />
* [mailto:Tammy.Allgood@asu.edu Tammy Wolf] Arizona St. - 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 at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair<br />
* [http://wiki.code4lib.org/User:NatashaAllen Natasha Allen] - Secondary Contact aka Co-Chair<br />
* [mailto:amcollie@stanford.edu Aaron Collier] - Local Planning Contact<br />
* Meredith Broadway - Documentarian<br />
* Ann S. - 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 />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - Chair<br />
* Your Name Here - 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 2020 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 />
[[2020 Host Voting Documents|2020 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Roy Tennant - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lillyho@gmail.com Lilly HS HO] - 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 />
[[2019 Book Giveaway Documents|2019 Book Giveaway 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 />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair <br />
* [[User:Anarchivist|Mark A. Matienzo]] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:JieChen|Jie Chen]], Univ. of WI-Milwaukee Libraries - 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 />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* [mailto:kndeibel@syr.edu Kate Deibel] - Primary Contact aka Chair<br />
* [mailto:jdandle@ucsd.edu Jenn Dandle] - Documentarian<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact<br />
* [https://libraries.towson.edu/staff/bill-helman Bill Helman] - 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 />
[[2019 Whatever Documents|2019 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:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Keynote_Speakers_Nominations&diff=464512019 Keynote Speakers Nominations2018-10-12T23:36:47Z<p>Rtennant: Added Mimi Fox Melton</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2019 in San José, CA will run until '''October 22, 2018'''.<br />
<br />
Please include a description and any relevant links and try to keep the list in alphabetical order.<br />
<br />
The criteria for nominating a candidate to act as keynote are below:<br />
*Speaker’s name (First Name, Last Name)<br />
*Brief description of individual (250-word max)<br />
*Pertinent links (Maximum of 3)<br />
*Contact information of candidate (email address)<br />
<br />
''We strongly encourage you to nominate speakers who are local to the San José area. If you would prefer to submit a nomination anonymously, please send your nominee(s) to Clara Turp at: [mailto:clara.turp@mcgill.ca clara.turp@mcgill.ca].'' <br />
<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><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 />
</pre><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 elucidates why Jane would be a good keynote speaker.<br />
<br />
==Tara Robertson ==<br />
<br />
Tara works at Mozilla as the Diversity & Inclusion Strategic Partner. She is tasked with ensuring one of the darlings of the technology industry to be more inclusive, diverse and open. Tara has been championing open communities, open source, open access, and open education prior to her affiliation with Mozilla for over a decade. As the Code4lib community continues to wrestle with these very issues, it is a timely opportunity to invite her to speak to us since we are on the left coast this year. <br />
<br />
More on [https://tararobertson.ca Tara].<br />
<br />
[https://tararobertson.ca/2016/lita-keynote/ Not all information wants to be free,] LITA Closing Keynote, 2016.<br />
<br />
==Mark Matienzo==<br />
<br />
Mark works at Stanford as the Collaboration & Interoperability Architect for Digital Library Systems and Services. <br />
<br />
Mark has worked at the intersection of technology, libraries, and systems for over a decade, serving as a technologist, advocate, and facilitator for cross-institutional projects. Prior to joining Stanford, Mark worked as an archivist, technologist, and strategist specializing in born-digital materials and metadata management, at institutions including the Digital Public Library of America, Yale University Library, The New York Public Library, and the American Institute of Physics. Mark would be an excellent keynote speaker because their long track record of involvement in cross-disciplinary and intra-institutional initiatives has given them a unique exposure to projects that touch on all aspects of library systems and tools. In addition, they are an outspoken advocate on a wide range of issues including labor, the environment, and leadership in libraries. <br />
<br />
More on [https://matienzo.org/ Mark].<br />
<br />
==Raj Jayadev==<br />
<br />
Raj Jayadev is the cofounder of [https://www.siliconvalleydebug.org/ Silicon Valley De-Bug], a community organizing, advocacy, and multimedia storytelling organization based in San José, California. Since its inception in 2001, Silicon Valley De-Bug has been a platform for Silicon Valley's diverse communities to impact the political, cultural, and social landscape of the region, while also becoming a nationally recognized model for community-based justice work. For nearly fifteen years, the organization has been a platform for the least heard of Silicon Valley — youth, immigrants, low-income workers, the incarcerated — to impact the the political, cultural, and social landscape of the region. Through De-Bug, Jayadev and is colleagues also started a family organizing model called the [https://acjusticeproject.org/ Albert Cobarrubias Justice Project] – a methodology for families and communities to impact the outcome of cases of their loved ones and change the landscape of power in the courts. They call the approach [https://www.participatorydefense.org/ "participatory defense"] and are now implementing the model nationally. Jayadev is a [https://www.macfound.org/fellows/1014/ 2018 MacArthur Foundation Fellow] and has been an [https://www.ashoka.org/en/fellow/raj-jayadev Ashoka Fellow] and a Rosenberg Foundation Leading Edge Fellow. All three recognitions are to support De-Bug’s innovative social justice work both locally and nationally. His writing and work has appeared and been profiled in media outlets such as the New York Times, Time.com, and National Public Radio.<br />
<br />
More about [https://aapip.org/our-stories/conversation-with-25-leaders-in-action-raj-jayadev Raj] ([https://acjusticeproject.org/about/contact-us/ contact info]).<br />
<br />
==Karla Monterroso==<br />
<br />
Karla Monterroso is the CEO of [http://www.code2040.org/ Code2040], a community of Black and Latinx technologists and their allies who are diversifying tech to create a more equitable, inclusive, and prosperous economy. Through high-impact direct service programs, robust in-person and online community engagement, and dynamic storytelling and knowledge sharing, Code2040 empowers and mobilizes diversity champions across the industry. She believes Code2040 sits in the perfect intersection of a skills- and network-building opportunity for Black and Latinx tech talent and a systems-change opportunity for a critical segment of the country's economy. Karla has focused much of her career growing the people and program functions of rapidly scaling social enterprises driving youth advocacy and leadership. Since joining Code2040 in 2014, she has grown the number of students served from 25 to 4,000, ushered in several new successful programs, and stewarded critical organizational development practices and policies around values and racial equity. Her success and insights on racial justice and equity have landed her in publications such as Fast Company, NPR, Bloomberg, and more.<br />
<br />
More about [https://twitter.com/karlitaliliana Karla].<br />
<br />
==Rick Prelinger==<br />
<br />
Rick Prelinger is an archivist, writer, filmmaker, and librarian. He is currently [http://film.ucsc.edu/faculty/rick_prelinger Professor of Film & Digital Media] at University of California, Santa Cruz. His archival work currently focuses on collecting, recontextualizing, and exhibiting home movies and amateur films, and is a renowned speaker on preservation, archives, and material culture in the anthropocene. In 1982, he founded [https://en.wikipedia.org/wiki/Prelinger_Archives Prelinger Archives], a collection of industrial, advertising, educational and amateur films that was acquired by the Library of Congress in 2002. With Megan Prelinger, he is the co-founder of [http://www.prelingerlibrary.org/home/ Prelinger Library], an appropriation-friendly private research library open to the public in downtown San Francisco. Prelinger has also partnered with the Internet Archive (of which he is a board member) to make 2,100 films available online for free viewing, downloading and reuse. His archival feature Panorama Ephemera (2004) played in venues around the world. Prelinger has recently made several film programs that he categorizes as “historical interventions,” called Lost Landscapes of San Francisco (7 annual parts) and Lost Landscapes of Detroit (3 annual parts).<br />
<br />
More about [http://prelinger.com/ Rick]. <br />
<br />
==Safiya U. Noble==<br />
<br />
From her website: "Dr. Safiya Umoja Noble is an Assistant Professor at the University of Southern California (USC) Annenberg School of Communication, and is the author of a best-selling book on racist and sexist algorithmic bias in commercial search engines, entitled Algorithms of Oppression: How Search Engines Reinforce Racism. [...] Previously, she was an assistant professor in the Department of Information Studies in the Graduate School of Education and Information Studies at UCLA where she held appointments in the Departments of African American Studies, Gender Studies, and Education."<br />
<br />
More about [https://safiyaunoble.com/ Safiya].<br />
<br />
==Sarah Mei==<br />
<br />
Sarah Mei is a Ruby and JavaScript developer and the Chief Consultant at DevMynd Software. With Sarah Allen, she founded [http://railsbridge.org/ RailsBridge], a community that provides free two-day workshops for members of under-represented groups in tech who want to learn Ruby on Rails. She also founded [http://bridgefoundry.org/ BridgeFoundry] to expand the RailsBridge model to other communities. Sarah is a renowned speaker and author on topics such as technical collaboration and pair programming, fostering inclusive communities, and Ruby development.<br />
<br />
More about [http://www.sarahmei.com/blog/ Sarah].<br />
<br />
==October Montoya ==<br />
<br />
October Montoya is a PhD student in the Communications and Science Studies Departments at UC San Diego. They hold a BA in Ethnic Studies, and a BA in Feminist Studies from University of California at Santa Cruz where their thesis, "Digital Activism in the Land of Abundant Failure: Silicon Valley and the Radical Re-Making of the Borders between Place and Space" explored the relationship between geography, technology, displacement, and change-making in their hometown of San Jose, California. Prior to attending graduate school, October engaged in various grassroots and coalitional forms of community organizing in the Bay Area, and this continues to influence their research interests, projects, and goals. They are also a contributing editor of San Jose-based literary journal Cheers from the Wasteland.<br />
<br />
More about October: [https://www.cheersfromthewasteland.com/october-montoya.html Cheersfromthewasteland] [http://communication.ucsd.edu/people/phd-students/october-montoya.html communication.ucsd.edu].<br />
<br />
== Isaac Schlueter ==<br />
<br />
Creator of npm, the JavaScript package manager, and CEO of npm, Inc. Isaac has been working in open source technology for decades and was instrumental in Node's early development, taking over from Node's creator Ryan Dahl and leading the project for a few years. While his contributions to open source software are notable, Isaac also leads by example with regards to diversity in the tech industry and creating a positive company atmosphere at npm. The company has [https://www.npmjs.com/jobs a code conduct] and emphasizes a healthy work/life balance. "We believe that the best way to iterate towards success is by taking care of ourselves, our families, our users, and one another." Isaac is local to Oakland, California.<br />
<br />
More about Isaac: [http://izs.me/resume.html izs.me] [https://twitter.com/izs @izs]<br />
<br />
== [http://www.code2040.org/mimi-fox-melton/ Mimi Fox Melton] ==<br />
<br />
Director, Community Mobilization for [http://www.code2040.org/ Code2040]. As a first generation Haitian-American, Mimi’s passion lives at the intersection of Black and Brown liberation and empowerment. In her role at CODE2040, she designs experiences to build and strengthen community while resourcing and connecting agents of equity and inclusion within the Black and Latinx tech community. Before CODE2040, Mimi co-founded and ran Code for Progress, a non-profit coding bootcamp that pays adults of color as they learn to code and start careers in social justice tech.<br />
<br />
[http://www.code2040.org/speaker-request/ Form for requesting her (or another Code2040 staffer) to speak]<br />
<br />
[[Category:Code4Lib2019]]<br />
<br />
[[Category:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46431Code4Lib 2019 Conference Committees2018-10-05T22:20:44Z<p>Rtennant: Added my name to the Precon committee</p>
<hr />
<div>= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: '''[http://doubletree3.hilton.com/en/hotels/california/doubletree-by-hilton-hotel-san-jose-JOSE-DT/index.html DoubleTree by Hilton]''' near the Airport, San José, CA<br />
* Dates: February 19 (pre-con) - 22, 2019<br />
** Pre-conferences: February 19, 2019<br />
** Main meeting: February 20-22, 2019<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:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact<br />
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair<br />
* [[User:WhitniWatkins|Whitni Watkins]], Analog Devices, Inc. - Secondary Contact aka Co-Chair (if you want to volunteer and you've not served on any Code4Lib committees before, let me know, I'll step aside) <br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* [http://mailto:kndeibel@syr.edu Kate Deibel], Syracuse University Libraries - Documentarian<br />
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer<br />
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer<br />
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer<br />
* Cody Whitby, Virginia Commonwealth University - Volunteer<br />
* Laura Chuang - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:swayh@oclc.org Hank Sway] - Primary Contact AKA Chair<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact and Co-Chair (veteran of 2017 and 2018)<br />
* Mark Matienzo - 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 />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<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 />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Primary Contact aka Chair<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol], Long Beach City College - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* [mailto:dicossio@crimson.ua.edu Diana Cossio]- Documentarian <br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<br />
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer<br />
* [mailto:cmathieu@jpl.nasa.gov Camille Mathieu], JPL Library - Volunteer<br />
* [mailto:subrama@purdue.edu Annapurni Subramaniam], Purdue - 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 />
[[2019 Keynote Documents|2019 Keynote Documents]]<br />
<br />
* [mailto:axm1195@case.edu Andrew Mancuso] - Primary Contact aka Chair<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]] - Local Planning Contact <br />
* [mailto:lconrad@cca.edu Lisa Conrad] - Documentarian<br />
* [mailto:ehenry124@gmail.com Elizabeth Henry] - Volunteer<br />
* [mailto:clara.turp@mcgill.ca Clara Turp] - Volunteer<br />
* [mailto:crh92@case.edu Charlie Harper] - 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 />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:lydiaz@ualberta.ca Lydia Zvyagintseva] - Volunteer<br />
* [mailto:tod@uchicago.edu Tod Olson] - Volunteer<br />
* [mailto:KHaley@mwa.org Kathleen Haley] - Volunteer<br />
* [[User:Kimpham54|Kim Pham]] - 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 />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer <br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman] - Volunteer<br />
* [[User:DanielDraper|Dan Draper]] - Volunteer<br />
* - 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 />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian <br />
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)<br />
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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 />
[[2019 T-Shirt Documents|2019 T-Shirt 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 />
== Onsite Volunteer Committee ==<br />
This committee wrangles <s>tributes</s> people to volunteer for the following duties:<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)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 />
== 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 />
[[2019 Social Activities Documents|2019 Social Activities Documents]]<br />
<br />
Conference goers - The page you are looking for is at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair<br />
* [http://wiki.code4lib.org/User:NatashaAllen Natasha Allen] - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact<br />
* Meredith Broadway - Documentarian<br />
* Ann S. - 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 />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
<br />
== Code4Lib 2020 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 />
[[2020 Host Voting Documents|2020 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 />
== Wifi and Electrical ==<br />
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.<br />
<br />
[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]<br />
<br />
* Your Name Here - Primary Contact <br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 />
[[2019 Book Giveaway Documents|2019 Book Giveaway 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 />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 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 />
* [[User:JieChen|Jie Chen]], Univ. of WI-Milwaukee Libraries - 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 />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<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 />
[[2019 Whatever Documents|2019 Whatever 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 />
[[Category:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46100Code4Lib 2019 Conference Committees2018-06-11T22:02:47Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Bay Area, California (more info coming soon)<br />
* Dates: we're looking at February-April, 2019<br />
** Pre-conferences: Coming Soon<br />
** Main meeting: Coming Soon<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:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact<br />
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
* Ray Pun, Fresno State - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Mark Matienzo - 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 />
* [mailto:swayh@oclc.org Hank Sway] - Volunteer<br />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<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 />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<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 />
[[2019 Keynote Documents|2019 Keynote 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 />
== 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 />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<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 />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer <br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - 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 />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian <br />
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)<br />
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (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 />
[[2019 T-Shirt Documents|2019 T-Shirt 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 />
== Onsite Volunteer Committee ==<br />
This committee wrangles <s>tributes</s> people to volunteer for the following duties:<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)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 />
== 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 />
[[2019 Social Activities Documents|2019 Social Activities Documents]]<br />
<br />
Conference goers - The page you are looking for is at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-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 />
== 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 />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - 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 />
== Code4Lib 2019 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 />
[[2019 Host Voting Documents|2019 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 />
== Wifi and Electrical ==<br />
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.<br />
<br />
[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]<br />
<br />
* Your Name Here - Primary Contact <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 />
[[2019 Book Giveaway Documents|2019 Book Giveaway 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 />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 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 />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<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 />
[[2019 Whatever Documents|2019 Whatever 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 />
[[Category:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2019_Conference_Committees&diff=46010Code4Lib 2019 Conference Committees2018-05-22T23:58:09Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2019 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 2019 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Bay Area, California (more info coming soon)<br />
* Dates: we're looking at February-April, 2019<br />
** Pre-conferences: Coming Soon<br />
** Main meeting: Coming Soon<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:nicole.esque@gmail.com Nicole Johnson], bepress - co-chair, Primary Contact<br />
* [mailto:ephetteplace@cca.edu Eric Phetteplace], California College of the Arts - co-chair, Primary Contact<br />
* [mailto:tennantr@oclc.org Roy Tennant], OCLC - Tertiary Contact<br />
* [mailto:matienzo@stanford.edu Mark Matienzo], Stanford University - Tertiary Contact<br />
* [mailto:aaron.collier@stanford.edu Aaron Collier], Stanford University - Tertiary Contact<br />
* Ray Pun, Fresno State - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2019 Website Working Group Documents|2019 Website Working Group Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Secondary Contact aka Co-Chair<br />
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Budget Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. <br />
<br />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* Mark Matienzo - 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 />
* [mailto:swayh@oclc.org Hank Sway] - Volunteer<br />
* [mailto:chennesy@berkeley.edu Cody Hennesy]- Volunteer (UC Berkeley)<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 />
[[2019 Budget and Sponsorship Documents|2019 Budget and Sponsorship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)<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 />
[[2019 Keynote Documents|2019 Keynote 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 />
== 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 />
[[2019 Pre-conference Documents|2019 Pre-conference Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<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 />
[[2019 Program Documents|2019 Program Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact <br />
* [https://lib.ncsu.edu/akorphan Dre] - Volunteer<br />
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer<br />
* Your Name Here - Volunteer <br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.<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 />
[[2019 Scholarship Documents|2019 Scholarship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact <br />
* Your Name Here - Documentarian <br />
* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] (Volunteer)<br />
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] (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 />
[[2019 T-Shirt Documents|2019 T-Shirt 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 />
== Onsite Volunteer Committee ==<br />
This committee wrangles <s>tributes</s> people to volunteer for the following duties:<br />
<br />
[[2019 Onsite Volunteer Documents|2019 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)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 />
== 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 />
[[2019 Social Activities Documents|2019 Social Activities Documents]]<br />
<br />
Conference goers - The page you are looking for is at [[2019 Social Activities]]<br />
<br />
* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-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 />
== 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 />
[[2019 Streaming Video Documents|2019 Streaming Video Documents]]<br />
<br />
* Your Name Here - 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 />
== Code4Lib 2019 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 />
[[2019 Host Voting Documents|2019 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 />
== Wifi and Electrical ==<br />
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.<br />
<br />
[[2019 Wifi and Electrical Documents|2019 Wifi and Electrical Documents]]<br />
<br />
* Your Name Here - Primary Contact <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 />
[[2019 Book Giveaway Documents|2019 Book Giveaway 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 />
== IRC and Slack Committee ==<br />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2019 IRC and Slack Documents|2019 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 />
[[2019 Accessibility Documents|2019 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact<br />
* Your Name Here - Documentarian<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 />
[[2019 Whatever Documents|2019 Whatever 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 />
[[Category:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Main_Page&diff=46009Main Page2018-05-22T23:57:37Z<p>Rtennant: </p>
<hr />
<div><!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"<br />
| style="width:54%; color:#000;" |<br />
<!-- "WELCOME TO WIKIPEDIA" AND ARTICLE COUNT --><br />
{| style="width:280px; border:none; background:none;"<br />
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4lib wiki</div><br />
|}<br />
<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
__NOTOC__<br />
| style="width:20%; font-size:95%;vertical-align:top; " |<br />
* [[#About Code4Lib|About Code4Lib]]<br />
* [[#Software Usage and Documentation|Software Usage and Documentation]]<br />
* [[#Current topics|Current topics]]<br />
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[#Code4Lib 2018 Conference|2018 Conference]]<br />
* [[#Local / Regional Groups|Local / Regional Groups]]<br />
* [[#Interest Groups|Interest Groups]]<br />
* [[#Earlier Conferences and events|Earlier Conferences and events]]<br />
|}<br />
<br />
<!-- ABOUT --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
|-<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.<br />
* [[Zoia or the Code4Lib IRC bot]]<br />
|-<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist<br />
|-<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Regional Meeting Streaming]]<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
* [[Libraries Sharing Code]]<br />
* [[Code4Lib Tagline brainstorm]]<br />
* [[Fiscal Continuity]]<br />
** [[Fiscal Sponsorship Working Group]]<br />
* [[Accessibility]]<br />
* [[Teaching beginners]] <br />
|-<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
|-<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
|}<br />
| style="border:1px solid transparent;" |<br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
<br />
==Code4Lib 2019 Conference==<br />
<br />
* [[Code4Lib_2019_Conference_Committees|Code4Lib 2019 Conference Committees]]<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
<br />
==Code4Lib 2018 Conference==<br />
{{:Category:Code4Lib2018}}<br />
<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
* [[2018_Conference_Volunteers|2018 Conference Volunteers]]<br />
* [[2018_Social_Activities|2018 Social Activities]]<br />
* [[Code4Lib2018_Posters|2018 Poster Presentations]]<br />
* [[Code4Lib2018_Breakout_Sessions|2018 Breakout Sessions]]<br />
* [[Code4Lib2018_Lightning_Talks|2018 Lightning Talks]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
=== United States ===<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest<br />
* [[South_Central|Code4Lib South Central]] - Texas, Oklahoma, Louisiana, Arkansas, New Mexico<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[Western|Code4Lib West]] - California North and South <br />
<br />
=== Canada ===<br />
<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[North|code4lib North]] - Ontario and surrounding areas<br />
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<br />
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br />
<br />
=== Europe ===<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
<br />
=== Asia/Pacific ===<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
<br />
=== Middle East ===<br />
* [[Qatar|Code4Lib Qatar]] - Doha ''(new in 2018)''<br />
|-<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
* [[Fiscal_Continuity|Fiscal Continuity]] - A group that explored from 2016 to 2017 whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)<br />
* [[Fiscal_Sponsorship_Working_Group|Fiscal Sponsorship Working Group]] - A group formed to implement a fiscal sponsorship agreement per the results of the [[Fiscal_Continuity#Fiscal_Options_Vote|fiscal options vote]] in late 2017<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
== Earlier Conferences and events ==<br />
* [[:Category:Code4Lib2017|Code4Lib 2017]] Los Angeles, CA<br />
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA<br />
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR<br />
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC<br />
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL<br />
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA<br />
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IN<br />
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC<br />
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI<br />
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR<br />
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA<br />
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR<br />
[[Conference Financial History At A Glance]]<br />
<br />
=== Older Conference T-Shirt Designs ===<br />
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]<br />
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]<br />
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Main_Page&diff=46008Main Page2018-05-22T23:57:20Z<p>Rtennant: </p>
<hr />
<div><!-- BANNER ACROSS TOP OF PAGE --><br />
{| id="mp-topbanner" style="width:100%; background:#f9f9f9; margin:1.2em 0 6px 0; border:1px solid #ddd;"<br />
| style="width:54%; color:#000;" |<br />
<!-- "WELCOME TO WIKIPEDIA" AND ARTICLE COUNT --><br />
{| style="width:280px; border:none; background:none;"<br />
| style="width:280px; text-align:center; white-space:nowrap; color:#000;" |<br />
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Welcome to the Code4lib wiki</div><br />
|}<br />
<br />
<!-- PORTAL LIST ON RIGHT-HAND SIDE --><br />
__NOTOC__<br />
| style="width:20%; font-size:95%;vertical-align:top; " |<br />
* [[#About Code4Lib|About Code4Lib]]<br />
* [[#Software Usage and Documentation|Software Usage and Documentation]]<br />
* [[#Current topics|Current topics]]<br />
* [[#Other Code4Lib Sites|Other Code4Lib Sites]]<br />
| style="width:13%; font-size:95%;" |<br />
* [[#Code4Lib 2018 Conference|2018 Conference]]<br />
* [[#Local / Regional Groups|Local / Regional Groups]]<br />
* [[#Interest Groups|Interest Groups]]<br />
* [[#Earlier Conferences and events|Earlier Conferences and events]]<br />
|}<br />
<br />
<!-- ABOUT --><br />
{| id="mp-upper" style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 0px;"<br />
<!-- TODAY'S FEATURED ARTICLE; DID YOU KNOW --><br />
| class="MainPageBG" style="width:55%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000;" |<br />
{| id="mp-left" style="width:100%; vertical-align:top; background:#f5fffa;"<br />
|-<br />
<br />
== About Code4Lib ==<br />
<br />
* [[About Code4Lib]] - Background and history of the community<br />
* [[A Guide for the Perplexed]] - Building skills for working with library technologies<br />
* [[How to hack code4lib]] - For those newer to the community<br />
* [https://docs.google.com/document/d/1m-9VtL7L_fUxl2hTF_YZSdFRfucaLtmHvLSzom6XPVM/edit?pli=1 Code4Lib Indoctrination] (This is a Google doc open to all including anonymous feedback.)<br />
**"How do we make code4lib a more inclusive place for newcomers? <br/> Or, how do we quickly indoctrinate newbies to our values and ways of doing things?" <br />
**Suggestions, ideas, and follow-up actions solicited.<br />
* [[One recommended tool/resource for n00bs]] - For new coding librarians/library Coders<br />
* [[Mentorship Program]]<br />
* [[Skill Sharing Clubs]] - Find people with similar interests in your field.<br />
* [[Zoia or the Code4Lib IRC bot]]<br />
|-<br />
<br />
== Software Usage and Documentation ==<br />
<br />
* [[Umlaut]] - OpenURL link resolving middleware<br />
* [[:Category:Patterns|Patterns for Collaborative Code]] - Patterns to make your open source 'more open', more amenable to distributed development and use at multiple institutions without forking. <br />
* [[ILS Documentation]]<br />
* [[OSS Directory]]<br />
* [[Working with MARC]]<br />
* [[Rogue]] - principles for standards creation<br />
* [[ProjectManagement]] - list of project management and issue tracking software that are frequently mentioned on the Code4Lib mailinglist<br />
|-<br />
<br />
== Current topics ==<br />
<br />
* [[Code4Lib Regional Meeting Streaming]]<br />
* [[Code4Lib Website Update]]<br />
* [[OCLC Policy Change]]<br />
* [[SirsiDynix: Integrated Library System Platforms on Open Source]]<br />
* [[Parsing Library Data]]<br />
* [[Robots Are Our Friends]]<br />
* [[Libraries Sharing Code]]<br />
* [[Code4Lib Tagline brainstorm]]<br />
* [[Fiscal Continuity]]<br />
** [[Fiscal Sponsorship Working Group]]<br />
* [[Accessibility]]<br />
* [[Teaching beginners]] <br />
|-<br />
<br />
== Other Code4Lib Sites ==<br />
<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://journal.code4lib.org journal.code4lib.org]<br />
|-<br />
<br />
== Code4Lib Journal ==<br />
<br />
* [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br />
<br />
|}<br />
| style="border:1px solid transparent;" |<br />
| class="MainPageBG" style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top;"|<br />
<br />
{| id="mp-right" style="width:100%; vertical-align:top; background:#f5faff;"<br />
<br />
==Code4Lib 2019 Conference==<br />
<br />
* [[Code4Lib_2019_Conference_Committees Code4Lib 2019 Conference Committees]]<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
<br />
==Code4Lib 2018 Conference==<br />
{{:Category:Code4Lib2018}}<br />
<br />
* [[How_To_Plan_A_Code4LibCon|How To Plan A Code4LibCon]]<br />
* [[2018_Conference_Volunteers|2018 Conference Volunteers]]<br />
* [[2018_Social_Activities|2018 Social Activities]]<br />
* [[Code4Lib2018_Posters|2018 Poster Presentations]]<br />
* [[Code4Lib2018_Breakout_Sessions|2018 Breakout Sessions]]<br />
* [[Code4Lib2018_Lightning_Talks|2018 Lightning Talks]]<br />
<br />
== Local / Regional Groups ==<br />
<br />
=== United States ===<br />
* [[NEC4L|New England Code4lib]] - New England<br />
* [[NYC|Code4LibNYC]] - NYC and surrounding areas<br />
* [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br />
* [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br />
* [[Southeast|Code4LibSE]] - North Carolina, South Carolina, Georgia, Virginia, Well, you get the idea<br />
* [[Midwest|Code4Lib Midwest]] - Wherever that is...<br />
* [[Code4Lib_Chicago|Chicago]] - Chicago is a city in the Midwest<br />
* [[South_Central|Code4Lib South Central]] - Texas, Oklahoma, Louisiana, Arkansas, New Mexico<br />
* [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br />
* [[Western|Code4Lib West]] - California North and South <br />
<br />
=== Canada ===<br />
<br />
* [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br />
* [[North|code4lib North]] - Ontario and surrounding areas<br />
* [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<br />
* [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br />
<br />
=== Europe ===<br />
* [[NL|Code4Bib]] - Dutch Code4Bib<br />
* [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<br />
<br />
=== Asia/Pacific ===<br />
* [http://www.code4lib.jp/ Code4Lib Japan] - ''(new in 2010!)'', see also [http://twitter.com/yesonline/statuses/28561046501 tweet from Jerry Lee]<br />
* [http://groups.google.com/group/code4glam Code4GLAM Australia] - coders, hackers, developers and technologists in the Australian GLAM (Galleries, Libraries, Archives & Museums) sector.<br />
<br />
=== Middle East ===<br />
* [[Qatar|Code4Lib Qatar]] - Doha ''(new in 2018)''<br />
|-<br />
<br />
== Interest Groups ==<br />
<br />
* [[ILS_Interop|ILS Interoperability]] - A group working to develop an infrastructure for interoperating between discovery layers and integrated library systems.<br />
* [[Open_Source_Book_Widgets|Open Source Book Widgets]] - A list of open source book widgets<br />
* [[Discovery|Open Source Discovery]] - Open Source application to enhance and support "discovery" in libraries<br />
* [[Mobile_Apps|Mobile Applications]] - A group interested in mobile web and native application development for libraries<br />
* [[Sources_Of_Metadata|Sources Of Metadata]] - list of api's and sources of interest to libraries<br />
* [[Fiscal_Continuity|Fiscal Continuity]] - A group that explored from 2016 to 2017 whether and how to make long-term fiscal arrangements for conferences (and perhaps other activities)<br />
* [[Fiscal_Sponsorship_Working_Group|Fiscal Sponsorship Working Group]] - A group formed to implement a fiscal sponsorship agreement per the results of the [[Fiscal_Continuity#Fiscal_Options_Vote|fiscal options vote]] in late 2017<br />
|-<br />
<br />
|}<br />
|}<br />
<br />
== Earlier Conferences and events ==<br />
* [[:Category:Code4Lib2017|Code4Lib 2017]] Los Angeles, CA<br />
* [[:Category:Code4Lib2016|Code4Lib 2016]] Philadelphia, PA<br />
* [[:Category:Code4Lib2015|Code4Lib 2015]] Portland, OR<br />
* [[:Category:Code4Lib2014|Code4Lib 2014]] Raleigh, NC<br />
* [[:Category:Code4Lib2013|Code4Lib 2013]] Chicago, IL<br />
* [[:Category:Code4Lib2012|Code4Lib 2012]] Seattle, WA<br />
* [[:Category:Code4Lib2011|Code4Lib 2011]] Bloomington, IN<br />
* [[:Category:Code4Lib2010|Code4Lib 2010]] Asheville, NC<br />
* [[:Category:Code4Lib2009|Code4Lib 2009]] Providence, RI<br />
* [[:Category:Code4Lib2008|Code4Lib 2008]] Portland, OR<br />
* [[:Category:Code4Lib2007|Code4Lib 2007]] Athens, GA<br />
* [[:Category:Code4Lib2006|Code4Lib 2006]] Corvallis, OR<br />
[[Conference Financial History At A Glance]]<br />
<br />
=== Older Conference T-Shirt Designs ===<br />
* [http://www.code4lib.org/node/235 2008 (Portland, Oregon)] - [http://code4lib.org/files/code4lib08.gif winning design]<br />
* [http://code4lib.org/node/146 2007 (Athens, Georgia)] - [http://code4lib.org/files/code4lib2007-7.jpg winning design]<br />
* [http://code4lib.org/tshirts 2006 (Corvalis, Oregon)] - [http://code4lib.org/files/t-shirt.png winning design]<br />
<br />
=== Other workshops ===<br />
* [http://barcamp.org/SearchCampDC SearchCampDC] - barcamp style event in DC with usual suspects from code4lib<br />
* [[code4lib/elag2010]] - 1-day code4lib preconference at elag2010<br />
<br />
== Archived topics ==<br />
<br />
* [[Logo Design Process]]<br />
<br />
<br />
[[AdminToDo]] - ideas and tasks for maintaining the Code4Lib sites</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2019_Hosting_Proposals&diff=458882019 Hosting Proposals2018-03-12T20:48:09Z<p>Rtennant: Adding a hosting proposal</p>
<hr />
<div>'''Schedule (First round)'''<br />
<br />
* Proposal period opens: November 14th, 2017<br />
<br />
* Proposal period ends: March 12th, 2018<br />
<br />
* Voting opens: TBD<br />
<br />
* Voting closes: TBD<br />
<br />
'''2019 Host Voting Committee'''<br />
<br />
* Peggy Griesinger, George Mason University<br />
* Craig Boman, Discovery Services Librarian, Miami University<br />
* Benjamin Florin<br />
<br />
'''Please list your proposal below.''' <br />
<br />
* [https://phette23.github.io/c4l19-norcal-proposal/ San Francisco Bay Area 2019 Hosting Proposal]<br />
<br />
See previous host proposals for examples: <br />
<br />
* [[2018 Hosting Proposals]]<br />
* [https://c4l-phl.github.io/ 2016 Hosting Proposal]<br />
* [http://osulp.github.io/code4lib-pdx/ 2015 Hosting Proposal]<br />
* [https://docs.google.com/document/d/1amxzn4xs26ILszZek5nIEEfd4qHNfLjp1BAc5CU5YKw/edit 2014 Hosting Proposal]<br />
* [http://web.archive.org/web/20131022165223/http://tigger.uic.edu/~kayiwa/code4lib.html 2013 Hosting Proposal]<br />
* [https://sites.google.com/site/code4lib2012seattle/ 2012 Hosting Proposal]<br />
<br />
==Code4Lib 2019 Location Proposals==<br />
<br />
<br />
<br />
===Welcome to ...!===<br />
<br />
<br />
<br />
===The Conference===<br />
<br />
Venue needs: February/March 2019 conference that can accommodate roughly 400(~450) attendees and meet Code4Lib's technical requirements.<br />
<br />
===The Cost===<br />
<br />
<br />
===Fiscal Sponsor===<br />
<br />
<br />
===Organizational Committee===<br />
<br />
<br />
[[Category:Code4Lib2019]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&diff=458082018 Conference Volunteers2018-02-13T20:25:56Z<p>Rtennant: /* Mic-minders */</p>
<hr />
<div>= Code4Lib 2018 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<br />
<br />
== Concierge/Local Guides ==<br />
Available after sessions to direct people to evening activities and local points of interest, etc.<br />
<br />
Special: One direction savvy local needed to help direct people to the preconference locations from the hotel lobby. <br />
Tuesday 2/13:<br />
* 8:00AM - 10:00AM: [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
<br />
If you're local to the DC area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br />
<br />
== Conference Logistics and Registration==<br />
Sets up and staffs registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Monday 2/12:<br />
* 9:30AM - 4:30PM (can be all or half of the day, please indicate): [mailto:carrano@mit.edu Joe Carrano] (all day)<br />
* 9:30AM - 4:30PM (can be all or half of the day, please indicate): [mailto:gerhardj@georgetown.edu Jeff Gerhard] (half day)<br />
<br />
Tuesday 2/13:<br />
* 8:00AM - 10:00AM: [mailto:mwaugh2@lsu.edu Mike Waugh]<br />
* 12:00PM - 2:30PM: [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
* 4:00PM - 6:00PM: [mailto:krevak@gmail.com Kelly Revak]<br />
<br />
Wednesday 2/14:<br />
* 7:45AM - 9:00AM: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
* 7:45AM - 9:00AM: [mailto:gerhardj@georgetown.edu Jeff Gerhard]<br />
<br />
Thursday 2/15:<br />
* 7:45AM - 9:00AM: [mailto:egonsalves@bishopoconnell.org Eva Gonsalves]<br />
<br />
Friday 2/16:<br />
* 7:45AM - 9:00AM: [mailto:durden@umd.edu David Durden]<br />
<br />
== Social Networking ==<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Tuesday 2/13:<br />
* am: ''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
* pm: ''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
<br />
Wednesday 2/14:<br />
* am: ''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
* pm: ''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
<br />
Thursday 2/15:<br />
* am:''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
<br />
Friday 2/16:<br />
* am: ''Your Name Here'' & [mailto:jkoivist@umd.edu Joseph Koivisto]<br />
<br />
== Mic-minders ==<br />
Pass mic for questions. Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Two people are needed for each shift. You are welcome to sign up for multiple shifts!<br />
<br />
Wednesday 2/14:<br />
* 9-12:15 (Opening Keynote and Group 1): [mailto:roytennant@gmail.com Roy Tennant] ; ''Your Name Here''<br />
* 1:30-5:00pm (Group 2, Breakout Sessions, and Lightning Talks): [mailto:jrees67@yahoo.com John Rees] ; Morgan McKeehan<br />
<br />
Thursday 2/15:<br />
* 9-12:00 (Announcements, FC Group, Group 3 Talks): [mailto:mwaugh2@lsu.edu Mike Waugh] ; ''Your Name Here'' ; [mailto:durden@umd.edu David Durden] ; ''Your Name Here'' <br />
* 1:00-5:00pm (Group 4 Talks, Lightning Talks 2, Group 4 Talks): [mailto:jrees67@yahoo.com John Rees] ; Morgan McKeehan<br />
<br />
Friday 2/16:<br />
* 9-10am (Closing Keynote): ''Your Name Here'' ; ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
Livestream assitants 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 />
Wednesday 2/14:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: [mailto:michael@dp.la Michael Della Bitta]<br />
* Time TBD: [[User:Khaley|Kathleen Haley]] (but will need to leave by 12:45 at latest)<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. <br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday 2/15:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (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.<br />
<br />
* Before the conference: [[User:Anarchivist|Mark Matienzo]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
* Wednesday 7:45AM - 9:00PM: [[User:DavidDurden|David Durden]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Wednesday 2/14:<br />
* Time TBD (AM?): Becky Yoose<br />
* Time TBD: (PM, not during my AM talk): [mailto:jswierc1@swarthmore.edu Julie Swierczek]<br />
<br />
Thursday 2/15:<br />
* Time TBD (AM, but not if that's when my talk is): Dre<br />
* Time TBD: Christina Harlow<br />
<br />
Friday 2/16:<br />
* AM Session: Mary Jinglewski<br />
<br />
== Session Timers ==<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
Wednesday 2/14:<br />
* 9-12:15 (Opening Keynote and Group 1): [mailto:liblna@emory.edu Laura Akerman] ; Backup: ''Your Name Here''<br />
* 1:30-5:00pm (Group 2, Breakout Sessions, and Lightning Talks): [mailto:eenglish@bpl.org Eben English] ; Backup: "Your Name Here"<br />
<br />
Thursday 2/15:<br />
* 9-12:00 (Announcements, FC Group, Group 3 Talks): ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
* 1:00-5:00pm (Group 4 Talks, Lightning Talks 2, Group 4 Talks): [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
9-11am (Closing Keynote, Lightning Talks 3): [mailto:mlibby@cfr.org Monique Libby] ; Backup: ''Your Name Here''<br />
<br />
== Reception assistance ==<br />
Help direct people who enter on the ground floor of the Library of Congress to the great hall. <br />
<br />
Wednesday 2/14:<br />
6:45-7:45pm: [mailto:trey@koios.co Trey Gordner]<br />
<br />
== The Whatever Crew ==<br />
Volunteers who are willing to help with various tasks as needed during the conference. <br />
<br />
* [mailto:bomanca@miamioh.edu Craig Boman]<br />
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580<br />
* [mailto:jswierc1@swarthmore.edu Julie Swierczek]<br />
* [mailto:jrees67@yahoo.com John Rees]<br />
* Morgan McKeehan<br />
* [mailto:mlibby@cfr.org Monique Libby] <br />
* [mailto:gerhardj@georgetown.edu Jeff Gerhard]<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2018]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&diff=457452018 Conference Volunteers2018-01-31T22:03:04Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2018 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<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 DC area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br />
<br />
== Conference Logistics ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Monday 2/12:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Tuesday 2/13:<br />
* Time TBD:''Your Name Here''<br />
<br />
Wednesday 2/14:<br />
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: [mailto:durden@umd.edu David Durden]<br />
<br />
== Preconference Setup & Sessions==<br />
Help manage preconference sessions, setting up projectors, etc.<br />
<br />
Preconference Setup and sessions Tuesday 2/13:<br />
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Tuesday 2/13:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
Livestream assitants 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 />
Wednesday 2/14:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''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 are Pacific Standard Time (PST).<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday 2/15:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (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.<br />
<br />
* Before the conference: [[User:Anarchivist|Mark Matienzo]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Wednesday 2/14:<br />
* Time TBD (AM?): Becky Yoose<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* AM Session: Mary Jinglewski<br />
<br />
== Session Timers ==<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
Wednesday 2/14:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]<br />
<br />
Thursday 2/15:<br />
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''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 />
* [mailto:bomanca@miamioh.edu Craig Boman]<br />
* [mailto:tennantr@oclc.org Roy Tennant] Can also text or call 707-287-5580<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2018]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2018_Conference_Volunteers&diff=457442018 Conference Volunteers2018-01-31T22:02:23Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2018 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<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 DC area (or know it very well), you can pick up a white "LOCAL" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br />
<br />
== Conference Logistics ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Monday 2/12:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Tuesday 2/13:<br />
* Time TBD:''Your Name Here''<br />
<br />
Wednesday 2/14:<br />
* Time TBD: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: [mailto:durden@umd.edu David Durden]<br />
<br />
== Preconference Setup & Sessions==<br />
Help manage preconference sessions, setting up projectors, etc.<br />
<br />
Preconference Setup and sessions Tuesday 2/13:<br />
* Time TBD: [mailto:mwaugh2@lsu.edu Mike Waugh] (I can help early morning Tuesday before sessions, or Monday afternoon/evening)<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Tuesday 2/13:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
Livestream assitants 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 />
Wednesday 2/14:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD: [[User:Khaley|Kathleen Haley]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''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 are Pacific Standard Time (PST).<br />
<br />
Wednesday 2/14:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Thursday 2/15:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
<br />
Friday 2/16:<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (West);<br />
* Time TBD: ''Your Name Here'' (East); ''Your Name Here'' (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.<br />
<br />
* Before the conference: [[User:Anarchivist|Mark Matienzo]]<br />
* Time TBD: ''Your Name Here''<br />
<br />
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
* Time TBD: ''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
==MCs==<br />
<br />
Wednesday 2/14:<br />
* Time TBD (AM?): Becky Yoose<br />
* Time TBD: ''Your Name Here''<br />
<br />
Thursday 2/15:<br />
* Time TBD:''Your Name Here''<br />
* Time TBD: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* AM Session: Mary Jinglewski<br />
<br />
== Session Timers ==<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
Wednesday 2/14:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: [mailto:durden@umd.edu David Durden]<br />
<br />
Thursday 2/15:<br />
* Time TBD: Primary: ''Whitni'' ; Backup: [mailto:mhughes@library.ucla.edu Maggie Hughes]<br />
* Time TBD: Primary: [mailto:durden@umd.edu David Durden] ; Backup: ''Your Name Here''<br />
<br />
Friday 2/16:<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''Your Name Here''<br />
* Time TBD: Primary: ''Your Name Here'' ; Backup: ''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 />
* [mailto:bomanca@miamioh.edu Craig Boman]<br />
* [mailto:tennantr@oclc.org Roy Tennant]<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2018]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45590About Code4Lib2017-11-10T19:52:49Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[Media:Code4lib-prelist.pdf|email thread (PDF)]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. Here is the [[Media:2006conf.pdf|official proposal]]. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45589About Code4Lib2017-11-10T19:51:53Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[Media:Code4lib-prelist.pdf|email thread (PDF)]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. Here is the message that made the official proposal [[Media:2006conf.pdf]]. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45588About Code4Lib2017-11-10T19:50:46Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[File:Code4lib-prelist.pdf||email thread (PDF)]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. Here is the message that made the official proposal [[Media:2006conf.pdf]]. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=File:2006conf.pdf&diff=45587File:2006conf.pdf2017-11-10T19:49:12Z<p>Rtennant: </p>
<hr />
<div></div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45586About Code4Lib2017-11-10T19:45:37Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[File:Code4lib-prelist.pdf||email thread (PDF)]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45585About Code4Lib2017-11-10T19:44:05Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[File:Code4lib-prelist.pdf|email thread (PDF)]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45584About Code4Lib2017-11-10T19:43:21Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [File:Code4lib-prelist.pdf email thread (PDF)]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45583About Code4Lib2017-11-10T19:40:12Z<p>Rtennant: </p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [Code4lib-prelist.pdf email thread (PDF)]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=About_Code4Lib&diff=45582About Code4Lib2017-11-10T19:39:23Z<p>Rtennant: Added a link to the prelist email discusion</p>
<hr />
<div>The Code4Lib community is a group of computer programmers and library technologists who largely work for and with libraries. It started as a [http://dewey.library.nd.edu/mailing-lists/code4lib/ mailing list] in the fall of 2003 when a group of library programmers decided to create an overarching community agnostic towards any particular language or technology. See this [[email thread|File:Code4lib-prelist.pdf]]. Soon after the mailing list was created the community decided to setup a channel on the Freenode network of [http://code4lib.org/irc IRC] named '''[irc://irc.freenode.net/code4lib #code4lib]''' on [http://freenode.net/ freenode].<br />
.<br />
<br />
===Code4Lib Conferences ===<br />
In February of 2006 the first Code4Lib conference was held in Corvallis, Oregon, hosted by Oregon State University. This initial Code4Lib conference was a hit, drawing over 80 attendees. The 2007 conference was held on the University of Georgia campus in Athens, GA attracting about 150 attendees. A list of Code4Lib conferences are available on the [http://code4lib.org/conference community website].<br />
<br />
'''Sources:'''<br />
* [http://www.code4lib.org/ code4lib.org]<br />
* [http://planet.code4lib.org planet.code4lib.org]<br />
* [http://eprints.rclis.org/11670/1/code4lib_journal_article_-_revised3.pdf 2007 Code4Lib Conference Report (PDF)]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=File:Code4lib-prelist.pdf&diff=45581File:Code4lib-prelist.pdf2017-11-10T19:37:52Z<p>Rtennant: </p>
<hr />
<div></div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2018_Conference_Committees&diff=45195Code4Lib 2018 Conference Committees2017-05-02T21:14:42Z<p>Rtennant: Added my name</p>
<hr />
<div>= Code4Lib 2018 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 2018 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
* We will assign a local contact (LPC) to each committee.<br />
<br />
* The chair/co-chair of each committee will be added to the private Code4Lib Slack channel, #c4l18-lpc, for direct communication with the LPC. If you cannot access the channel, please ping @bohyunkim either in slack or twitter. <br />
<br />
== Location and Dates ==<br />
<br />
* Location: Washington, DC (more info coming soon)<br />
* Dates: we're looking at early February 2018<br />
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches<br />
** Main meeting: Coming Soon but we're thinking a hotel downtown<br />
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.<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:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact<br />
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact<br />
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact<br />
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2018 Website Working Group Documents|2018 Website Working Group Documents]]<br />
<br />
* [[User:Phette23|Eric Phetteplace]] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* [[User:KaitlinNewson|Kaitlin Newson]], Ontario Council of University Libraries - Volunteer<br />
* [[User:WayneGraham|Wayne Graham]], CLIR - Volunteer<br />
* [[User:EkaGrguric|Eka Grguric]] - Volunteer<br />
* [[User:LukeAeschleman|Luke Aeschleman]] - Volunteer<br />
* [[User:MattCalsada|Matt Calsada]] - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Budget Planning Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them. <br />
<br />
[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]<br />
<br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact aka Chair<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Secondary Contact aka Co-Chair (v)<br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact <br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)<br />
* [Your name here] - Documentarian<br />
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Volunteer (v)<br />
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Volunteer (v)<br />
* Your Name Here - Volunteer<br />
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host<br />
<br />
== Sponsorship Committee ==<br />
This group will focus on fundraising and managing contacts with potential sponsors.<br />
<br />
* [mailto:mary.jinglewski@gmail.com Mary Jinglewski] - Primary Contact aka Chair<br />
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer<br />
* [mailto:liblna@emory.edu Laura Akerman] - Volunteer (v)<br />
* [mailto:tomeconqueror@gmail.com Kyle Breneman] - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host<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 />
[[2018 Keynote Documents|2018 Keynote Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* [mailto:epeele@emory.edu Elizabeth Peele Mumpower], Emory University - Volunteer<br />
* Your Name Here - 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 />
[[2018 Pre-conference Documents|2018 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact <br />
* Nick Kerelchuk - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer<br />
* Your Name Here - Volunteer<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 />
[[2018 Program Documents|2018 Program Documents]]<br />
<br />
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Primary Contact aka Chair <br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair <br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact <br />
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman], University of Bridgeport - Volunteer<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Volunteer<br />
* [mailto:juliakim@loc.gov Julia Kim], Library of Congress - Volunteer<br />
* [mailto:cng@nwpl.ca Cynthia Ng], New Westminster Public Library - Volunteer<br />
<!--'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.--><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 />
[[2018 Scholarship Documents|2018 Scholarship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact <br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <br />
* [[User:AmyWickner|Amy Wickner]] - Documentarian <br />
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer <br />
* Brooke Johnson - Volunteer <br />
* Your Name Here - Volunteer<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 />
[[2018 T-Shirt Documents|2018 T-Shirt Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Onsite Volunteer Committee ==<br />
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:<br />
<br />
[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact <br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger], George Mason University - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:trey@koios.co Trey Gordner] - Volunteer<br />
* [mailto:mwaugh2@lsu.edu Mike Waugh], LSU Libraries - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - 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 />
[[2018 Social Activities Documents|2018 Social Activities Documents]]<br />
<br />
Conference goers - The page you are looking for is at [[2018 Social Activities]]<br />
<br />
* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <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 (?), and, of course, actually running the camera during the conference.<br />
<br />
[[2018 Streaming Video Documents|2018 Streaming Video Documents]]<br />
<br />
* [[User:DataGazetteer|Peter Murray]] - Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Code4Lib 2019 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 />
[[2019 Host Voting Documents|2019 Host Voting Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Wifi and Electrical ==<br />
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.<br />
<br />
[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]<br />
<br />
* Your Name Here - Primary Contact/Local Planning Contact <br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 />
[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <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 />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair <br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact<br />
* Your Name Here - Documentarian<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 (physical and virtual).<br />
<br />
[[2018 Accessibility Documents|2018 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact <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 />
[[2018 Whatever Documents|2018 Whatever Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <br />
* [mailto:peggygriesinger@gmail.com Peggy Griesinger] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer<br />
* [[User:WayneGraham|Wayne Graham]] - Volunteer<br />
* [[User:Phette23|Eric Phetteplace]] - Volunteer<br />
* [mailto:khes@loc.gov Kirk Hess], Library of Congress - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2018]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=Code4Lib_2018_Conference_Committees&diff=45045Code4Lib 2018 Conference Committees2017-04-10T22:16:54Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2018 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 2018 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian (secretary). The role of the Documentarian is to transcribe key information to future conference committees, such as timelines, costs, process, etc. Feel free to improve the summary statements for each of the committees. When adding your name, please indicate 'v' if you are a veteran on the committee so that we ensure committees are not made up entirely of newbies.<br />
<br />
We will assign a local contact (LPC) to each committee.<br />
<br />
== Location and Dates ==<br />
<br />
* Location: Washington, DC (more info coming soon)<br />
* Dates: we're looking at early February 2018<br />
** Pre-conferences: Coming Soon but we're thinking they'll be at DCPL branches<br />
** Main meeting: Coming Soon but we're thinking a hotel downtown<br />
** Post conference activities: Coming Soon but we're thinking tours of LC, Smithsonian, etc.<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:jame@loc.gov Jaime Mears], Library of Congress - Primary Contact<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], University of Maryland, Baltimore, Health Sciences and Human Services Library - Secondary Contact<br />
* [mailto:nicholas.kerelchuk@dc.gov Nick Kerelchuk], DC Public Libraries - Tertiary Contact<br />
* [mailto:RichardJM@si.edu Joel Richard], Smithsonian Libraries - Tertiary Contact<br />
* [[User:BenWallberg|Ben Wallberg]], University of Maryland Libraries - Tertiary Contact<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Tertiary Contact<br />
<br />
== Website Working Group ==<br />
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br />
<br />
[[2018 Website Working Group Documents|2018 Website Working Group Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact<br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Budget and Sponsorship Planning Committee ==<br />
This group will focus on making sure we are appropriately planning for budgetary issues. This group will work involves working with the LPC to close budget gaps and talking to potential sponsors to find the level that is right for them. <br />
<br />
[[2018 Budget and Sponsorship Documents|2018 Budget and Sponsorship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact <br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact (Back-up)<br />
* Your Name Here - Documentarian<br />
* [mailto:gmcharlt@gmail.com Galen Charlton] - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* [mailto:bethany@clir.org Bethany Nowviskie], DLF - Ex Officio, Fiscal Host<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 />
[[2018 Keynote Documents|2018 Keynote Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - 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 />
[[2018 Pre-conference Documents|2018 Pre-conference Documents]]<br />
<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Primary Contact aka Chair<br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<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 />
[[2018 Program Documents|2018 Program Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* [mailto:jame@loc.gov Jaime Mears], Library of Congress - Local Planning Contact/Secondary Contact aka Co-Chair <br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim], UMB HS/HSL - Local Planning Contact <br />
* [mailto:chris@cbeer.info Chris Beer], Stanford University (v) - Volunteer<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer<br />
* [mailto:acollier@calstate.edu Aaron Collier], California State University - Co-Chair of 2017 Program committee, Happy to help with carry over. <br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<!--'''FULL''': Please consider volunteering for one or more of the other committees. Thank you.--><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 />
[[2018 Scholarship Documents|2018 Scholarship Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair <br />
* Your Name Here - Secondary Contact aka Co-Chair/Local Planning Contact <br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <br />
* Your Name Here - Documentarian <br />
* [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] - Volunteer <br />
* Your Name Here - Volunteer <br />
* Your Name Here - Volunteer<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 />
[[2018 T-Shirt Documents|2018 T-Shirt Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Onsite Volunteer Committee ==<br />
This committee wrangles <s>tributes</s> <s>minions</s> people to volunteer for the following duties:<br />
<br />
[[2018 Onsite Volunteer Documents|2018 Onsite Volunteer Documents]]<br />
<br />
* Your Name Here - Primary Contact aka (Co-)Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - 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 />
[[2018 Social Activities Documents|2018 Social Activities Documents]]<br />
<br />
Conference goers - The page you are looking for is at [[2018 Social Activities]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact<br />
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact <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 (?), and, of course, actually running the camera during the conference.<br />
<br />
[[2018 Streaming Video Documents|2018 Streaming Video Documents]]<br />
<br />
* Your Name Here - Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Code4Lib 2018 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 />
[[2018 Host Voting Documents|2018 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 - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:benjamin.florin@bc.edu Ben Florin] - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
== Wifi and Electrical ==<br />
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.<br />
<br />
[[2018 Wifi and Electrical Documents|2018 Wifi and Electrical Documents]]<br />
<br />
* Your Name Here - Primary Contact/Local Planning Contact <br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [[User:highermath|Cary Gordon]], Cherry Hill Company - 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 />
[[2018 Book Giveaway Documents|2018 Book Giveaway Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <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 />
Coordinate with freenode to ensure that the #code4lib IRC & Slack channels can handle the extra traffic during the conference. Also responsible for recruiting and advertising IRC helpers at the conference.<br />
<br />
[[2018 IRC and Slack Documents|2018 IRC and Slack Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<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 (physical and virtual).<br />
<br />
[[2018 Accessibility Documents|2018 Accessibility Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact <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 />
[[2018 Whatever Documents|2018 Whatever Documents]]<br />
<br />
* Your Name Here - Primary Contact aka Chair<br />
* Your Name Here - Secondary Contact aka Co-Chair<br />
* [mailto:bkim@hshsl.umaryland.edu Bohyun Kim] - Local Planning Contact <br />
* Your Name Here - Local Planning Contact <br />
* Your Name Here - Documentarian<br />
* [mailto:roytennant@gmail.com Roy Tennant] - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
* Your Name Here - Volunteer<br />
<br />
[[Category:Code4Lib2018]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2017_Conference_Volunteers&diff=448162017 Conference Volunteers2017-02-21T20:38:28Z<p>Rtennant: </p>
<hr />
<div>= Code4Lib 2017 Conference Volunteers =<br />
<br />
Call for volunteers during the actual conference, as opposed to the conference planning committees.<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 Los Angeles area (or know it very well), you can pick up a {insert color} "Local Guide" ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br />
<br />
== Conference Logistics ==<br />
Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br />
<br />
Monday 3/6:<br />
* 8a-12p: [mailto:bobbi_fox@harvard.edu Bobbi Fox]<br />
* 12p-4p: [mailto:lolliffe@getty.edu Lawrence Olliffe]<br />
<br />
Tuesday 3/7:<br />
* 8a-12p: ''Your Name Here'', ''Your Name Here''<br />
<br />
== Preconference Setup & Sessions==<br />
Help manage preconference sessions, setting up projectors, etc.<br />
<br />
Preconference Setup Monday 3/6:<br />
* 8a-9:30a: 6 UCLA<br />
* 12:30p-2p: 6 UCLA<br />
<br />
Preconference Sessions Monday 3/6:<br />
* 11:45a-12:15p at Powell: ''Your Name Here''<br />
* 11:45a-12:15p at Young: ''Your Name Here''<br />
* 11:45a-12:15p at Science & Engineering Library: ''Your Name Here''<br />
<br />
* 4:15p-4:45p at Powell: ''Your Name Here''<br />
* 4:15p-4:45p at Young: [mailto:kimpham54@gmail.com Kim Pham]<br />
* 4:15p-4:45p at Science & Engineering Library: ''Your Name Here'', ''Your Name Here''<br />
<br />
== Social Events ==<br />
Help manage the craft brew and game night, solve any problems that pop-up, have fun, etc.<br />
<br />
Wednesday 3/8:<br />
* 6p-9p: ''Your Name Here''<br />
* 8p-11p: ''Your Name Here''<br />
<br />
== Social Networking ==<br />
Answering general questions on Twitter, IRC, and Slack and passing questions to the Mic-minders.<br />
<br />
Tuesday 3/7:<br />
* 8a-12p: ''Your Name Here''<br />
* 1p-5p: ''Your Name Here''<br />
<br />
Wednesday 3/8:<br />
* 8a-12p: ''Your Name Here''<br />
* 1p-5p: ''Your Name Here''<br />
<br />
Thursday 3/9:<br />
* 8a-12p: ''Your Name Here''<br />
<br />
== Mic-minders ==<br />
Ask questions on mic on behalf of community (because of distance, mic aversion, etc)<br />
<br />
Tuesday 3/7:<br />
* 9a-12p: ''Your Name Here''<br />
* 1p-5p: [mailto:mheller1@luc.edu Margaret Heller]<br />
<br />
Wednesday 3/8:<br />
* 9a-12p: ''Your Name Here''<br />
* 1p-5p: ''Your Name Here''<br />
<br />
Thursday 3/9:<br />
* 9a-12p: ''Your Name Here''<br />
<br />
== Livestream Assistants (Onsite) ==<br />
Livestream assitants 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 />
Tuesday 3/7:<br />
* 8a-12p: [mailto:mlevy@ushmm.org Michael Levy]<br />
* 8a-12p: [[User:Khaley|Kathleen Haley]]<br />
<br />
* 12:30p-5p: ''Your Name Here''<br />
* 12:30p-5p: ''Your Name Here''<br />
<br />
Wednesday 3/8:<br />
* 8a-12p: [[User:Khaley|Kathleen Haley]]<br />
* 8a-12p: ''Your Name Here''<br />
<br />
* 12:30p-5p: ''Your Name Here''<br />
* 12:30p-5p: ''Your Name Here''<br />
<br />
Thursday 3/9:<br />
* 8a-12p: ''Your Name Here''<br />
* 8a-12p: ''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.<br />
<br />
Tuesday 3/7:<br />
* 9a-12p: [mailto:jswierc1@swarthmore.edu Julie Swierczek] (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)<br />
* 1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)<br />
<br />
Wednesday 3/8:<br />
* 9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); [mailto:jchutchi@uci.edu Josh Hutchinson] (West)<br />
* 1p-5p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (West)<br />
<br />
Thursday 3/9:<br />
* 9a-12p: ''Your Name Here'' (East); ''Your Name Here'' (Midwest); ''Your Name Here'' (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.<br />
<br />
* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]<br />
<br />
Helper: Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br />
<br />
* [mailto:mark.matienzo@gmail.com Mark A. Matienzo]<br />
* Your name here<br />
<br />
==MCs==<br />
<br />
Tuesday 3/7 <br />
* AM: [[User:Yoosebj|Becky]], who shall continue her reign as Destroyer of Names.<br />
* PM: [[User:rtennant|Roy Tennant]], who studies at the feet of the Destroyer of Names.<br />
<br />
Wednesday 3/8<br />
* AM: Dre, but feel free to boot me if someone desperately wants to MC and slots are full.<br />
* PM1: [[User:highermath|Cary Gordon]]<br />
* PM2: ''Your Name Here''<br />
<br />
Thursday 3/9 <br />
* AM: ''Your Name Here''<br />
<br />
== Session Timers ==<br />
People who volunteer to sit up front, keep time (and bring timer equipment - i.e. a laptop or tablet with a stopwatch program). It's good to have two people in each slot to back each other up in case of machinery failure.<br />
<br />
Tuesday AM<br />
* Primary: ''Your Name Here''<br />
* Backup: ''Your Name Here''<br />
<br />
Tuesday PM<br />
* Primary: [[User:Phette23|Eric Phetteplace]]<br />
* Backup: ''Your Name Here''<br />
<br />
Wednesday AM<br />
* Primary: [mailto:hsherid2@illinois.edu Helenmary Sheridan]<br />
* Backup: ''Your Name Here''<br />
<br />
Wednesday PM<br />
* Primary: [[User:Phette23|Eric Phetteplace]]<br />
* Backup: ''Your Name Here''<br />
<br />
Thursday AM<br />
* Primary: ''Your Name Here''<br />
* Backup: ''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 />
* Lawrence Olliffe<br />
* [mailto:bobbi_fox@harvard.edu Bobbi Fox]<br />
* [mailto:mheller1@luc.edu Margaret Heller]<br />
* [mailto:matt.r.sherman@gmail.com Matt Sherman]<br />
* ''Your Name Here''<br />
<br />
[[Category: Code4Lib2017]]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2017_Keynote_Speakers_Nominations&diff=444462017 Keynote Speakers Nominations2016-10-08T21:39:22Z<p>Rtennant: Removed Sumana, who has keynoted before</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2017 in Los Angeles. Please include a description and any relevant links and try to keep the list in alphabetical order.<br />
<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><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 />
</pre><br />
<br />
__TOC__<br />
<br />
==Jane Doe (example)==<br />
Jane works at ________, doing _______. <br />
<br />
Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.<br />
<br />
== Paul Ford ==<br />
<br />
Paul Ford is a Brooklyn-based writer and web technologist. He often writes about [https://medium.com/message/how-paper-magazines-web-engineers-scaled-kim-kardashians-back-end-sfw-6367f8d37688 the web], [http://www.npr.org/templates/story/story.php?storyId=6241967 archives] [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ programming], [http://www.ftrain.com/wwic.html the nature of information], and [https://medium.com/message/networks-without-networks-7644933a3100 living in the information age]. Past projects include [https://medium.com/message/tilde-club-i-had-a-couple-drinks-and-woke-up-with-1-000-nerds-a8904f0a2ebf tilde.club] and the [http://www.ftrain.com/AWebSiteForHarpers.html semantic web-ified harpers.org] (back in 2003). Ford's 30,000-word article [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ What Is Code?] was the entire June 11, 2015 issue of Bloomberg BusinessWeek. Learn more at his [http://ftrain.com website], on [http://twitter.com/ftrain Twitter], or on [https://medium.com/@ftrain Medium], or watch [https://www.youtube.com/watch?v=WSL5qVL3Mng his talk at XOXO 2014] or [http://www.bloomberg.com/news/videos/2015-06-12/-what-is-code-charlie-rose-06-12- his interview on Charlie Rose]. Paul was also interviewed at [http://www.inthelibrarywiththeleadpipe.org/2012/an-interview-with-paul-ford-and-gina-trapani/ at In the Library with the Lead Pipe, along with Gina Trapani].<br />
<br />
== David S. H. Rosenthal == <br />
Dr. David Rosenthal started the LOCKSS Program, which is aimed at long-term preservation of web published materials. <br />
[https://www.lockss.org/contact-us/dshr/ https://www.lockss.org/contact-us/dshr/]<br />
[http://blog.dshr.org/ http://blog.dshr.org/]<br />
<br />
== Greg Wilson ==<br />
<br />
[http://third-bit.com/about.html Greg Wilson] is the co-founder of [http://software-carpentry.org/about/ Software Carpentry], a volunteer organization that teaches basic computing skills to researchers in a wide range of disciplines. Greg has worked for 30 years in both industry and academia, and is the author or editor of several books on computing and two for children.<br />
<br />
Twitter: [https://twitter.com/gvwilson @gvwilson]<br />
<br />
== Gene Luen Yang ==<br />
Comic artist and author, Gene Yang has greatly broadened diversity representation in comics with successful titles such as '''American Born Chinese''', '''Boxers and Saints''', and '''The Shadow Hero'''. In 2016, the Library of Congress named him as an Ambassador for Young People’s Literature. In this capacity, Yang has pushed a mission of 'Reading Without Walls' to encourage literacies of all types. Additionally, he has recently started a graphic novel series, '''Secret Coders''' with artist Mike Holmes. This series aims to introduce kids to actual magic they can perform at home: computer programming. As several kids try to uncover the mysteries of their school, they face puzzles and challenges that teach readers about programming. <br />
<br />
[http://geneyang.com/ http://geneyang.com/]<br />
<br />
[http://geneyang.com/secret-coders http://geneyang.com/secret-coders]</div>Rtennanthttps://wiki.code4lib.org/index.php?title=2017_Keynote_Speakers_Nominations&diff=444432017 Keynote Speakers Nominations2016-10-06T18:14:52Z<p>Rtennant: Recovered Sumana's nomination</p>
<hr />
<div>Nominations for invited speakers/keynotes for Code4Lib 2017 in Los Angeles. Please include a description and any relevant links and try to keep the list in alphabetical order.<br />
<br />
<br />
Please follow the formatting guidelines:<br />
<br />
<pre><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 />
</pre><br />
<br />
__TOC__<br />
<br />
==Jane Doe (example)==<br />
Jane works at ________, doing _______. <br />
<br />
Some pertinent history/biography/hyperlinks that elucidates why Jane would be a good keynote speaker.<br />
<br />
== Greg Wilson ==<br />
<br />
[http://third-bit.com/about.html Greg Wilson] is the co-founder of [http://software-carpentry.org/about/ Software Carpentry], a volunteer organization that teaches basic computing skills to researchers in a wide range of disciplines. Greg has worked for 30 years in both industry and academia, and is the author or editor of several books on computing and two for children.<br />
<br />
Twitter: [https://twitter.com/gvwilson @gvwilson]<br />
<br />
== Paul Ford ==<br />
<br />
Paul Ford is a Brooklyn-based writer and web technologist. He often writes about [https://medium.com/message/how-paper-magazines-web-engineers-scaled-kim-kardashians-back-end-sfw-6367f8d37688 the web], [http://www.npr.org/templates/story/story.php?storyId=6241967 archives] [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ programming], [http://www.ftrain.com/wwic.html the nature of information], and [https://medium.com/message/networks-without-networks-7644933a3100 living in the information age]. Past projects include [https://medium.com/message/tilde-club-i-had-a-couple-drinks-and-woke-up-with-1-000-nerds-a8904f0a2ebf tilde.club] and the [http://www.ftrain.com/AWebSiteForHarpers.html semantic web-ified harpers.org] (back in 2003). Ford's 30,000-word article [http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/ What Is Code?] was the entire June 11, 2015 issue of Bloomberg BusinessWeek. Learn more at his [http://ftrain.com website], on [http://twitter.com/ftrain Twitter], or on [https://medium.com/@ftrain Medium], or watch [https://www.youtube.com/watch?v=WSL5qVL3Mng his talk at XOXO 2014] or [http://www.bloomberg.com/news/videos/2015-06-12/-what-is-code-charlie-rose-06-12- his interview on Charlie Rose]. Paul was also interviewed at [http://www.inthelibrarywiththeleadpipe.org/2012/an-interview-with-paul-ford-and-gina-trapani/ at In the Library with the Lead Pipe, along with Gina Trapani].<br />
<br />
== David S. H. Rosenthal == <br />
Dr. David Rosenthal started the LOCKSS Program, which is aimed at long-term preservation of web published materials. <br />
[https://www.lockss.org/contact-us/dshr/ https://www.lockss.org/contact-us/dshr/]<br />
[http://blog.dshr.org/ http://blog.dshr.org/]<br />
<br />
== Sumana Harihareswara ==<br />
Sumana is the founder of Changeset Consulting. She is a geek-suit interface, a programmer, and a teacher who likes to work on open source products, services, or sites that delight and help people.<br />
<br />
[https://www.harihareswara.net/ https://www.harihareswara.net/]</div>Rtennant