Code4Lib - User contributions [en]

One recommended tool/resource for n00bs

2018-08-30T18:53:44Z

SarahGreen:

===One recommended tool/resource for n00bs===

These resources/tools were recommended by the Code4Lib community in Nov. 2012, specifically for new coding librarians and library coders. The whole thread of discussion is available at [http://www.mail-archive.com/code4lib@listserv.nd.edu/msg15762.html the C4L listserv archive].

Please fill out a [https://docs.google.com/spreadsheet/viewform?formkey=dHNPVWgyX0E2a20xWHBHS1dJV05Pb0E6MQ#gid=0 mini-survey] if this was helpful to you. Thank you!

====Tools/Resources====

=====Books or Things to read=====
* O'Reilly Head first series
* Visual QuickStart Guides http://www.peachpit.com/imprint/series_detail.aspx?ser=335245
* [https://docs.google.com/spreadsheet/ccc?key=0AlVSWa90m8umdGg3U0h4bjdMT0ttVUJBU3RCaUc0WGc#gid=0 QA Collection Purchases for Code4Lib]
* [http://www.worldcat.org/title/pragmatic-programmer-from-journeyman-to-master/oclc/42038638 "The Pragmatic Programmer"] by Andrew Hunt and David Thomas. A book that teaches beginners how think like a programmer, and reminds experts of good practices.
* The top 9 in a hacker's bookshelf: http://grokcode.com/11/the-top-9-in-a-hackers-bookshelf/
* "How to Design Programs" http://www.ccs.neu.edu/home/matthias/HtDP2e/. Good for newbie coders.
* Kernighan and Ritchie's [http://www.worldcat.org/title/c-programming-language/oclc/17650642 "The C Programming Language."] A keeper for life, and surprisingly readable and directed to the newbie.
* [http://www.worldcat.org/title/agile-web-development-with-rails-4/oclc/852808602&referer=brief_results Agile Web Development with Rails 4] is a well-paced introduction to Rails and Ruby. Covers a lot of core concepts (MVC, agile development, testing, AJAX).
** To dive further into Ruby, there's [http://www.worldcat.org/title/programming-ruby-19-20-the-pragmatic-programmers-guide/oclc/855706057&referer=brief_results Programming Ruby] (aka The PickAxe Book)
* http://www.w3.org/International
* Guide for the Perplexed on the code4lib wiki: http://wiki.code4lib.org/index.php/A_Guide_for_the_Perplexed
* Video series on command line basics from Lullabot: http://drupalize.me/series/command-line-basics-series

=====Software=====

* Vi- because it keeps me (you?) focused.
* [http://www.activestate.com/komodo-edit Komodo Edit]
* [http://notepad-plus-plus.org/ Notepad++ IMO best open source lightweight editor on Windows]
*AMP (LAMP, WAMP, MAMP) stacks for an easy install of Apache, mySQL + perl/ python / php.
*A @rdio subscription. :) And a text editor with syntax highlighting.
* Git (Version Control)
* Github, Bitbucket and Other Remote Git Services
* Emmet, http://docs.emmet.io/ (supersedes Zen Coding, http://code.google.com/p/zen-coding/ ) The idea is that it lets you use CSS-like selectors as tags that can be expanded into full HTML snippets.
* [http://sass-lang.com/ SASS Syntactically Awesome Stylesheets]
* LESS http://lesscss.org/
* Compass http://compass-style.org/ - extends SASS with reusable patterns
* BareBones's [http://www.barebones.com/products/bbedit/index.html BBEdit]
* Sublime Text & Zen Coding (recently reborn as [http://docs.emmet.io Emmet]). Saves a lot of keystrokes when writing web content.
* The best one IMHO is [http://www.sublimetext.com Sublime Text 2]. Oh, okay, I can't resist - I'm going to cheat and list a second: everyone needs to stop writing just CSS and complement it with SASS (syntactically awesome stylesheets) & Compass - http://sass-lang.com/. Totally invaluable for any front-end work. It makes CSS fun.
* [http://www.virtualbox.org VirtualBox] to make new VM setup and deployment easier we use [http://vagrantup.com/ Vagrant]
* Version control. My own strong preference is for git (either managed locally or through github.com), but really, just pick a version control solution and use it. If you value your work at all, it should be in version control. Smart use of version control can make finding and fixing problems in code much, much easier - but even fairly naive use of it leaves you with much, much better tools for fixing screw ups than you have without it.

=====Websites=====
* Code4Lib listserv, IRC, [http://journal.code4lib.org journal] (duh)
* Google is more useful than any reference book to find answers to programming problems.
* [http://stackexchange.com/ StackExchange] (by extension, [http://stackoverflow.com StackOverflow]) is a great site for questions.
* [http://lynda.com lynda.com]
* [http://www.pluralsight.com/ PluralSight.com]
* JS Fiddle http://jsfiddle.net/
* CodePen http://codepen.io/
* [http://css-tricks.com CSS Tricks ]
* [http://openhatch.org/ Open Hatch] - to learn tools you need to participate in open source development and find friendly projects to be a part of
* [http://drupalladder.org/ Drupal Ladder], which teaches you what you need to know to participate in developing Drupal
* [http://rubykoans.com/ Ruby Koans] - learn Ruby by fixing failing tests
* [https://librarycarpentry.org/ Library Carpentry] - Free, open-source lessons for non-techy librarians on coding, data analysis, and related topics. They also give in-person workshops upon request.

=====Meetups and User Groups=====

* Perl Mongers http://www.pm.org/groups/
* Python Local User Groups http://wiki.python.org/moin/LocalUserGroups
** Look for user groups running an incarnation of the [http://bostonpythonworkshop.com/ Boston Python Workshop], a women-and-their-friends day-and-a-half introduction to Python which assumes no prior knowledge.
* R Users Group Meetups http://r-users-group.meetup.com/
* Drupal Groups http://groups.drupal.org/
* Ruby User Groups http://www.ruby-lang.org/en/community/user-groups/
** Look for groups running an incarnation of [http://workshops.railsbridge.org/ RailsBridge] (like Boston Python Workshop except it came first, and covers Ruby)
* Haskell User Groups http://www.haskell.org/haskellwiki/User_groups
* ColdFusion Meetups http://coldfusion.meetup.com/

=====Other=====

* Resources for lots of languages: [http://pear.ly/8ohL pear.ly/8ohL]
* [http://catcode.pbworks.com/w/page/49680175/Resources Catcode]
* [http://foss4lib.org/ FOSS4lib]
* I can already feel the collective rolling of eyes for this, but what about Twitter? It's not a guide or manual, but start following and engaging talented developers and library geeks on Twitter and you'll soon have more help than you know what to do with. Plus, no Zoia ;)
* Practice! No matter the learning material, nothing will really sink in unless you apply it in the wild (like a small project).
* It's still useful to learn a little something about configuring a webserver / database / etc.
* The [http://connect.ala.org/node/167971 Library Code Year Interest Group], an ALA group (joint between LITA and ALCTS) for librarians who want to learn and apply code

=====Advice on what to do=====
*Building things that help people matters, and for that you need empathy.
* Reusing people's [http://dotfiles.github.com/ public dotfiles],my favorite being [https://github.com/mathiasbynens/dotfiles Mathias Bynens']. Using a mature dotfiles collection can help bootstrap you to use the command line more and start grabbing vital tools from package managers like Homebrew or npm that you might not think of otherwise. I'm still a newbie coder but reusing dotfiles gives me the confidence to tweak things here and there without building a ton from scratch.
* I'm taking "tool" to mean a piece of hardware. I'd recommend some old laptop with your favorite linux distro less desktop. Why? Well the main thing is that it puts them into a position where they're not learning to be a google copy/paste coder given the lack of the desktop, mouse and distractions like email. They can also learn to setup the server environment on their new dev box and eventually do all sorts of cool stuff.
* A cheapie online webhosting account - like a $10 a month one - and multiple URLs. Multiple URLs will make them point a URL at a nameserver at least once ideally, and to understand that the two are separate and what you can do with domains and subdomains. The cheapie webhosting account will let them play with installing popular content management systems manually and with one-click installs. The most important thing is to break things and then rebuild them. The worst possible thing would be to build a website, leave it up as their public face or personal website, and be nervous to wreck it so notchange or play with different CMSes (another reason multiple URLs might psychologically be better - they encourage experimentation on one and the person can make the other a static goal oriented publishing area).The more the cheapie hosting account experience I have, the more I know what's cheap and easy to do, and the more I see very specific benefits to adedicated server. It makes me more intentional and able to better assess the value of services vendors provide. That's more web4lib ish, but ultimately if someone experiments enough they have to get comfortable with php. Scripting is the gateway drug.
* +1 to web-hosting as it gives the ability install one's own software on one's domain (which feels great) *and* easy access to shell. And when web-hosting feels like too much of a barrier to access, sites like jsfiddle where you can immediately start adding *and* sharing code is key. IMHO the initial appeal of [http://www.codecademy.com/ Codecademy] was that it removed all barriers to getting started. Getting a laptop's localhost set up is too daunting for a first step, I think.

Code4Lib 2019 Conference Committees

2018-07-05T18:28:49Z

SarahGreen: I added myself as a volunteer.

= Code4Lib 2019 Conference Committees =

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

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

== Location and Dates ==

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

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

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

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

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

* [[User:KaitlinNewson|Kaitlin Newson]], Scholars Portal - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:Phette23|Eric Phetteplace]], California College of the Arts - Local Planning Contact
* Your Name Here - Documentarian
* [[User:Ranti|Ranti Junus]], Michigan State University - Volunteer
* [[User:jcoyne|Justin Coyne]], Stanford - Volunteer
* [[User:AshleyBrewer|Ashley Brewer]], Virginia Commonwealth University - Volunteer
* Cody Whitby, Virginia Commonwealth University - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

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

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

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

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

* Your Name Here - Primary Contact aka Chair
* [mailto:jeffreystephensabol@gmail.com Jeffrey Sabol] - Secondary Contact aka Co-Chair
* [mailto:nicole.esque@gmail.com Nicole Johnson] - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:mprice@calpoly.edu Mike Price] - Volunteer (Cal Poly)
* [mailto:selizabethgreen@gmail.com Sarah Green] - Volunteer

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

[[2019 Keynote Documents|2019 Keynote Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

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

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

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2019 Program Documents|2019 Program Documents]]

* Your Name Here - Primary Contact aka Chair
* [http://roytennant.com/ Roy Tennant] - Local Planning Contact
* [https://lib.ncsu.edu/staff/akorphan Dre] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Volunteer
* [http://about.me/cynthiang Arty (Cynthia Ng)] - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Scholarship Committee ==
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

[[2019 Scholarship Documents|2019 Scholarship Documents]]

* [mailto:elvia.ar@uci.edu Elvia Arroyo-Ramirez - UC Irvine] - Primary Contact aka Co-Chair
* [mailto:mlemusro@iupui.edu Mairelys Lemus-Rojas - IUPUI] - Primary Contact aka Co-Chair
* [mailto:phette23@gmail.com Eric Phetteplace] - Local Planning Contact
* [mailto:mandellr@usc.edu Rachel Mandell] - Documentarian
* [mailto:avloera@cpp.edu Alyssa V. Loera - Cal Poly Pomona] - (Volunteer)
* [mailto:yooyoung.lee@uottawa.ca Yoo Young Lee - uOttawa] - (Volunteer)

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

[[2019 T-Shirt Documents|2019 T-Shirt Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact aka (Co-)Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

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

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

* Becky Yoose - Primary (or secondary if there's someone who wants to step up this year!) Contact aka Co-Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

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

* Your Name Here - Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

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

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Wifi and Electrical ==
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.

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

* Your Name Here - Primary Contact
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

[[2019 Book Giveaway Documents|2019 Book Giveaway Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

[[2019 IRC and Slack Documents|2019 IRC and Slack Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

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

[[2019 Accessibility Documents|2019 Accessibility Documents]]

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

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

[[2019 Whatever Documents|2019 Whatever Documents]]

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Secondary Contact aka Co-Chair
* Your Name Here - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer

[[Category:Code4Lib2019]]

Code4Lib 2018 Conference Committees

2017-07-18T19:55:31Z

SarahGreen: I added myself as a volunteer to the sponsorship committee.

= Code4Lib 2018 Conference Committees =

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[2018 Keynote Documents|2018 Keynote Documents]]

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

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

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

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

== Program Committee ==
This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.

[[2018 Program Documents|2018 Program Documents]]

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


== Scholarship Committee ==
This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements.

[[2018 Scholarship Documents|2018 Scholarship Documents]]

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

== T-Shirt Committee ==
This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.

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

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

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

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

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

== Social Activities Committee ==
This committee works closely with the local programming committee in organizing events outside of conference hours. This committee is in charge of organizing the Newcomer Dinner (traditionally held the night before the first day of the main conference) as well as ensuring that there is a variety of different events to cater to different interests (alcoholic/non-alcoholic, carnivore/vegan, mainstream/niche, and everything in between).

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

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

* [mailto:b.yoose@gmail.com Becky Yoose] - Primary Contact aka Chair
* [[User:ranti|Ranti Junus]] - Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* [mailto:katedohe@umd.edu Kate Dohe], University of Maryland Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [mailto:DaleLoreNY@gmail.com Lorena Ramirez-Lopez] - Volunteer
* [mailto:bomanca@miamioh.edu Craig Boman] - Miami University Libraries - Volunteer
* Your Name Here - Volunteer

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

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

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

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

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

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

== Wifi and Electrical ==
Arguably the most important committee. Coordinates with the local programming committee and the conference venue to ensure that wifi will be functioning for 450 people x 3 to 4 wifi enabled devices per person... as well as ensuring that there is ample power for folks to plug said devices in at the conference. Note that this will largely be handled by the conference management company.

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

* Your Name Here - Primary Contact/Local Planning Contact
* Your Name Here - Secondary Contact aka Co-Chair
* [[User:BenWallberg|Ben Wallberg]], UMD Libraries - Local Planning Contact
* Your Name Here - Documentarian
* [[User:highermath|Cary Gordon]], Cherry Hill Company - Volunteer
* Your Name Here - Volunteer
* Your Name Here - Volunteer

== Book Giveaway Committee ==
This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies (for example, free private repo from Github or license for oXygen). They also handle the raffle at the conference (with a randomizer to do the drawing of names).

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

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

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

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

* Your Name Here - Primary Contact aka Chair
* Your Name Here - Local Planning Contact/Secondary Contact aka Co-Chair
* [mailto:richardjm@si.edu Joel Richard], Smithsonian Libraries - Local Planning Contact
* Your Name Here - Documentarian
* Your Name Here - Volunteer
* Your Name Here - Volunteer

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

[[2018 Accessibility Documents|2018 Accessibility Documents]]

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

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

[[2018 Whatever Documents|2018 Whatever Documents]]

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

[[Category:Code4Lib2018]]