https://wiki.code4lib.org/api.php?action=feedcontributions&feedformat=atom&user=Ejlynema 2026-05-28T07:27:49Z User contributions MediaWiki 1.26.2 https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Volunteers&diff=49108 2026-02-18T14:47:37Z

<p>Ejlynema: </p> <hr /> <div>Call for volunteers during the actual conference, as opposed to the [[Code4Lib_2026_Conference_Committees|conference planning committees]].<br /> <br /> If you are interested in helping out during the Code4Lib 2026 conference, create an account on this wiki and then edit the page to sign-up for one or more slots.<br /> <br /> == Community Support Volunteers ==<br /> <br /> See https://2026.code4lib.org/conduct/#volunteers for more details, including contact information.<br /> <br /> == Concierge/Local Guides ==<br /> Available after sessions to direct people to evening activities and local points of interest, etc.<br /> <br /> If you're local to the area (or know it very well), you can pick up a white &quot;LOCAL&quot; ribbon at check-in. Conference hosts will direct attendees to seek out Local Guides for directions, restaurant recommendations, etc.<br /> <br /> * ''Your Name Here''<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here'' and anyone else with a &quot;LOCAL&quot; tag<br /> <br /> == Conference Logistics &amp; Registration ==<br /> Sets up registration table, signage and welcome packets, ensures proper power availability to conference attendees, etc.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> 8am - 9am Monday, day one:<br /> * Amy Rodriguez<br /> * Doreen Chen<br /> <br /> 8am - 9am Tuesday, day two:<br /> * Emily Lynema<br /> * ''Your Name Here''<br /> <br /> == Social Events ==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One ([https://2026.code4lib.org/general-info/social/#newcomer-dinner Newcomer Dinner]):<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> Tuesday, Day Two ([https://2026.code4lib.org/general-info/social/#game-night Game Night]):<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> Wednesday, Day Three ([https://2026.code4lib.org/general-info/social/ Social Activities TBD]):<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> == Social Networking ==<br /> <br /> Answering general questions on Mastodon (#c4l26), IRC, and Slack (#general) and passing questions to the Mic-minders on Slack (#code4libcon)<br /> <br /> Onsite Volunteer Committee Coordinator:<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Thursday, Workshop Day:<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> == Mic-minders ==<br /> <br /> Ask questions on mic on behalf of community (because of distance, mic aversion, etc). Asking questions on behalf of remote attendees passed to the slack channel: #code4libcon<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM volunteer: ''Your Name Here''<br /> * AM volunteer: ''Your Name Here''<br /> <br /> == Livestream QA (Remote) ==<br /> Volunteers for livestream QA will be remotely watching the conference and can notify us if there are any issues with the feed. We'd prefer two or three volunteers per shift, located in different parts of the US/world. All times below (if any are listed) are Eastern Standard Time (EST).<br /> <br /> To report a problem (even if you're not an &quot;official&quot; volunteer), you can send a message in the #code4libcon channel of the Code4Lib Slack.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> <br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM volunteer: ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> * Backup volunteer (all day): ''Your Name Here''<br /> <br /> == IRC/Slack (Technical) ==<br /> Access: Look into technology/procedures to make connecting to, and maintaining a connection to, IRC/Slack less painful. i.e. make sure wifi will allow connection, and someone needs to contact freenode about the sudden influx of people. Demonstrate how to get onto #code4lib during Registration. Offer support for newcomers in #code4lib during the conference.<br /> <br /> Onsite Volunteer Committee Coordinator: <br /> <br /> * Before the conference: ''Your Name Here''<br /> * During the conference: ''Your Name Here''<br /> <br /> ==MCs==<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: Dre<br /> * PM Volunteer: Matt Sherman<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == Session Timers ==<br /> Assist the AV crew with running the talk timer. They will have a digital sign so this volunteer functions mostly as a backup who is prepared in case the system fails or someone goes over time without noticing the signage.<br /> <br /> Onsite Volunteer Committee Coordinator: ''Your Name Here''<br /> <br /> Monday, Day One:<br /> * AM Volunteer: ''Your Name Here''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Tuesday, Day Two:<br /> * AM Volunteer: ''Baowei''<br /> * PM Volunteer: ''Your Name Here''<br /> <br /> Wednesday, Day Three:<br /> * AM Volunteer: ''Your Name Here''<br /> <br /> == The Whatever Crew ==<br /> Volunteers who are willing to help with various tasks as needed during the conference. <br /> <br /> * Matt Sherman<br /> * ''Your Name Here''<br /> * ''Your Name Here''<br /> <br /> <br /> future potential volunteers:<br /> <br /> * ''Your Name Here''<br /> <br /> podium tech help:<br /> <br /> * [[User:highermath|Cary Gordon]]<br /> * ''Your Name Here''<br /> <br /> [[Category: Code4Lib2026]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2026_Conference_Committees&diff=49054 2026-01-07T19:42:54Z

<p>Ejlynema: add Emily Lynema to workshop committee</p> <hr /> <div>= Code4Lib Conference Committees =<br /> <br /> Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2026 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact<br /> <br /> ==Planning Committee==<br /> Also known as the Local Planning Committee, although there is no requirement for the members to be local.<br /> <br /> [[2026 Planning Committe|2026 Planning Committee Documents]]<br /> <br /> * Ann Marie Mesco - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Esmé Cowles - Documentarian<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Jason Glenn - Volunteer<br /> * Alfredo Gonzalez Espinoza - Volunteer<br /> * Ken Rose - Volunteer<br /> <br /> == Website Working Group ==<br /> This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br /> <br /> [[2026 Website Working Group Documents|2026 Website Working Group Documents]]<br /> <br /> * [[User:Phette23|Eric Phetteplace]] - Primary Contact, Chair<br /> * [[User:TripKirkpatrick|Trip Kirkpatrick]], CoChair<br /> * Esmé Cowles - Documentarian, LPC liaison<br /> * Mike Paulmeno - Volunteer<br /> * [[User:RickyLee|Ricky Lee]] - Volunteer<br /> * Kim Shepherd - Volunteer<br /> * [[User:CoriHutchinson|Cori Hutchinson]] - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br /> <br /> [2026 Budget and Sponsorship Documents]<br /> <br /> * [http://mailto:code4lib@concentra-cms.com CONCENTRA-CMS] - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [http://mailto:riddle2@clemson.edu Kelly Riddle] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br /> <br /> From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.<br /> <br /> * Andromeda Yelton, Chair<br /> * Maccabee Levine, CoChair<br /> * Your Name Here - Documentarian<br /> * Andrew Battelini - Volunteer; abattel@emory.edu (and on Slack)<br /> * Ranti Junus - Volunteer<br /> * Carl Haynes-Magyar - Volunteer - cchmagyar@pitt.edu<br /> * Kathy Azevedo - LPC contact<br /> <br /> == Workshop Committee (Pre / Post-Conference)==<br /> This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br /> <br /> [[2026 Pre-conference Documents|2026 Pre-conference Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Ann Marie Mesco (mesco@andrew.cmu.edu) - Secondary Contact, CoChair, LPC Contact<br /> * Brian Maass (brian.maass@unmc.edu) - Documentarian<br /> * Sarah Smulligan (smm5878@psu.edu) - Volunteer<br /> * Emily Lynema (elynema@umich.edu) - 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 /> [[2026 Program Documents|2026 Program Documents]]<br /> <br /> * Jessica McMillen - Primary Contact, Chair<br /> * Dre - Secondary Contact, CoChair<br /> * Clara Turp - Documentarian<br /> * Matt Sherman - Volunteer<br /> * Caleb Derven - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer - LPC Liaison<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 via CONCENTRA. <br /> <br /> [[2026 Scholarship Documents|2026 Scholarship Committee Documents]]<br /> <br /> * [[User:MichelleSpeed|Michelle Speed]] (michelle_speed@baylor.edu) - Primary Contact, Chair<br /> * [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] (mairelys.lemus-rojas@ucf.edu)- Secondary Contact, CoChair<br /> * Kristen Scotti (kscotti@andrew.cmu.edu) - Documentarian<br /> * [[User:ChristineSalek|Christine Salek]] (christine.salek@wisc.edu)- Volunteer<br /> * Yingxue Li (yingxuel@andrew.cmu.edu) - Local Planning Committee Liaison<br /> <br /> == Community Support Squad (CSS) ==<br /> This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2026.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.<br /> <br /> == T-Shirt Committee ==<br /> This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br /> <br /> [[2026 T-Shirt Documents|2026 T-Shirt Documents]]<br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:ChristineSalek|Christine Salek]] - Volunteer<br /> * Sarah Smulligan (smm5878@psu.edu) - Volunteer<br /> * Ruiling Zhang - Volunteer (ruz152@pitt.edu)<br /> <br /> == Social Activities Committee ==<br /> <br /> This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences. <br /> <br /> 2026 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:ElaineKong|Elaine Kong]] - Volunteer; elainekong@pitt.edu<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * [[User:RichardHiggins|Richard Higgins]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Code4Lib 2027 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2026 Host Voting Documents|2026 Host Voting Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies.<br /> <br /> [[2026 Book Giveaway Committee|2026 Book Giveaway Committee]]<br /> <br /> * Michael B. Klein - Primary Contact, Chair<br /> * Ranti Junus - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [http://mailto:caroldinh@tuta.io Caroline Dinh] - Volunteer<br /> * [http://mailto:c.miette.ferrer@gmail.com Crystal Ferrer] - Volunteer<br /> * Gabby Amorelli (Gabriella.Amorelli@lsus.edu)- Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2026 IRC and Slack Documents|2026 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Baowei Wei (baowei@upenn.edu) - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2026 Accessibility Documents|2026 Accessibility Documents]]<br /> <br /> * Kate Deibel (@metageeky / katheride@pcom.edu), Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Karen Schifferdecker (karen.schifferdecker@wku.edu) - Volunteer<br /> * Alfred J Lin (ajrlin@umd.edu) - Volunteer<br /> * [[User:SusanHoover|Susan Hoover]] - 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 /> [[2026 Whatever Documents|2026 Whatever Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:ElaineKong|Elaine Kong]] - Volunteer; elainekong@pitt.edu<br /> * Karen Okamoto - Volunteer (kokamoto@jjay.cuny.edu)<br /> * Joe Mesco - Volunteer (jmesco@andrew.cmu.edu)<br /> <br /> [[Category: Code4Lib2026]]<br /> [[Category:Conference Committees]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2025_Conference_Committees&diff=48503 2024-10-10T16:11:25Z

<p>Ejlynema: </p> <hr /> <div>= Code4Lib Conference Committees =<br /> <br /> Hosting a conference is complex, and it cannot be done without the help of the entire community. If you are interested in being an awesome person and applying your skills to a particular part of the Code4Lib 2025 conference, create an account on this wiki and sign-up for one or more of the groups below (please provide a contact). Each committee must have a Primary Contact (chair), Secondary Contact (co-chair), and Documentarian Chair, Primary Contact<br /> <br /> ==Planning Committee==<br /> Also known as the Local Planning Committee, although there is no requirement for the members to be local.<br /> <br /> [[2025 Planning Committee Documents|2025 Planning Committee Documents]]<br /> <br /> * Esmé Cowles (Princeton) - Primary Contact, Chair<br /> * Kate Lynch (Princeton) - Secondary Contact, Co-chair, documentarian<br /> * Tracy Hall (Princeton) - Tertiary Contact<br /> * Your Name Here - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Website Working Group ==<br /> This group will focus on content strategy and feature implementations for the conference website to improve the overall experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users). <br /> <br /> [[2025 Website Working Group Documents|2025 Website Working Group Documents]]<br /> <br /> * Esmé Cowles - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Trip Kirkpatrick - Documentarian<br /> * Emily Lynema - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Budget and Sponsorship Committee ==<br /> This group involves working with the Planning Committee to close any budget gaps and talking to potential sponsors to find the level that is right for them.<br /> <br /> [https://drive.google.com/drive/u/0/folders/1nEZU5Hlca-qf_x2eXN2RJQgU8TUjgFlT 2025 Budget and Sponsorship Documents]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Keynote Committee ==<br /> This group will: gather nominations from Code4Lib community; contact nominees to confirm their willingness and availability; collect bios from the available nominees and add them to the Diebold-o-Tron; support the voting process; work with the community's top nominees to schedule their keynotes; and collaborate with other committees and the community to ensure everything is communicated appropriately and logistical matters are given suitable attention.<br /> <br /> From the chair: This committee will start meeting around mid-October and wrap up in mid-January, when we hand off our selected keynoters to Concentra for further logistics. Please ask me (@thatandromeda) in Slack if you have questions about serving on this committee.<br /> <br /> * Andromeda Yelton - Primary Contact, Chair<br /> * Maccabee Levine - Secondary Contact, CoChair<br /> * Andrew Battelini (abattel@emory.edu) - Documentarian<br /> * Hardy Pottinger - Volunteer<br /> * Ranti Junus - Volunteer<br /> * Esmé Cowles - LPC Liaison<br /> <br /> == Pre-conference Committee ==<br /> This committee plans the pre or post-conference day (TBD). It keeps strong lines of communications open with the Program Committee. It also helps shepherd events on the day itself.<br /> <br /> [[2025 Pre-conference Documents|2025 Pre-conference Documents]]<br /> <br /> * Your Name Here - Primary Contact, CoChair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Ann Marie Mesco - Volunteer<br /> * Minhao Jiang ([[minhao.jiang@wayne.edu]]) - Volunteer<br /> * Kenneth Rose - Volunteer <br /> * Kate Lynch - LPC Liaison<br /> <br /> == Program Committee == <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC. Committee membership will be capped at 10 members.<br /> <br /> [[2025 Program Documents|2025 Program Documents]]<br /> <br /> * Matt Sherman - Primary Contact, Chair<br /> * Dre - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Daricus Larry (dlarry@arizona.edu) - Volunteer<br /> * [[User:highermath|Cary Gordon]] - Volunteer<br /> * Ken Varnum - Volunteer<br /> * Steph Gritz (sgritz@lmu.edu) - Volunteer<br /> * Kate Lynch - LPC Liaison<br /> <br /> == Scholarship Committee ==<br /> This committee works with funding institutions to arrange the scholarships offered. They solicit submissions and select winners of the scholarship(s). They also work with the winners to plan their travel and arrangements. <br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * [[User:MairelysLemus-Rojas|Mairelys Lemus-Rojas]] (Brown University) - Volunteer<br /> * [[User:ChristineSalek|Christine Salek]] (christinesalek@gmail.com) - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Community Support Squad (CSS) ==<br /> This group responds to violations and concerns regarding [https://github.com/code4lib/code-of-conduct/blob/main/code_of_conduct.md the Code4Lib code of conduct] and ensures that the event is safe and enjoyable for all attendees. More details here: https://2025.code4lib.org/conduct/#volunteers and here: https://github.com/code4lib/code-of-conduct/blob/main/transparency_reports/2023_national_conference_annual_report.md.<br /> <br /> == T-Shirt Committee ==<br /> This committee organizes the t-shirt contest, collecting submissions, and putting out the call for votes. This committee is also responsible for helping the local planning committee identify a vendor that will fit within the budget constraints for the conference. User sizes and preferences will be obtained as part of the registration process.<br /> <br /> [[2025 T-Shirt Documents|2025 T-Shirt Documents]]<br /> <br /> * Kate Lynch - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Jessica Hayden (haydenj@berea.edu) - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Online Volunteer Committee ==<br /> <br /> This committee wrangles people to volunteer for the following duties:<br /> <br /> '''Looking for opportunities to help out at the conference? See [[2025 Conference Volunteers]]'''<br /> <br /> [[2025 Online Volunteer Documents|2025 Online Volunteer Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Social Activities Committee ==<br /> <br /> This committee organizes social activities for the conference, including the Newcomer Dinner (for in-person conferences) and other after/before conference hours activities (for in-person and virtual conferences). This committee also facilitates the process for attendee-planned social activities for virtual and in-person conferences. <br /> <br /> 2025 Social Activities Documents - Contact the Primary Contact/Chair for access to the Google Drive folder<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Streaming Video Committee ==<br /> With the local program committee(as appropriate), organize the streaming and archiving of presentations at the conference. This could include securing A/V equipment, working with the conference venue w/r/t AV needs, choosing streaming and archiving providers, post-production editing and posting of videos, securing speaker releases for recording talks.<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - LPC Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Code4Lib 2026 Host Voting Committee ==<br /> This committee organizes the call for hosts for the next annual code4lib conference as well as the voting process. <br /> <br /> [[2026 Host Voting Documents|2026 Host Voting Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Book Giveaway Committee ==<br /> This committee solicits free copies of books from various publishers or free keys/copies of programs from various companies,<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == IRC and Slack Committee ==<br /> This committee will assist attendees with IRC and Slack.<br /> <br /> [[2025 IRC and Slack Documents|2025 IRC and Slack Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Accessibility Committee ==<br /> Document and address major points of the conference that are not accessible for conference attendees.<br /> <br /> [[2025 Accessibility Documents|2025 Accessibility Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Kate Deibel &lt;[mailto:katheride@pcom.edu katheride@pcom.edu]&gt;, Co-Chair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> <br /> == Whatever Committee ==<br /> Not a committee per se. This is a list of people who are willing to help the above committees with various tasks.<br /> <br /> [[2025 Whatever Documents|2025 Whatever Documents]]<br /> <br /> * Your Name Here - Primary Contact, Chair<br /> * Your Name Here - Secondary Contact, CoChair<br /> * Your Name Here - Documentarian<br /> * Your Name Here - Volunteer<br /> * Your Name Here - Volunteer<br /> * Jessica Hayden (haydenj@berea.edu) - Remote Volunteer<br /> <br /> [[Category: Code4Lib2025]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=42852 2015-03-02T18:39:26Z

<p>Ejlynema: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Also consider using conference planning services from other entities. In 2013, Chicago used DLF services to handle registration. In 2014, NC used CONCENTRA services for all contract negotiation, fiscal activities, registration, and other conference planning and management services.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> *[[Useful information from 2012]]<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> * [http://code4lib.org/content/template-code4lib-20xx Template for the conference page on the main Code4Lib website] - This page is only visible to those who have a code4lib.org account. Once a host has been selected, please copy the template to a new page for that conference year.<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> The process works something like this:<br /> <br /> # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.<br /> # People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)<br /> #* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)<br /> # After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.<br /> # After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.<br /> <br /> ===Program Voting===<br /> Pre-conf voting may need to take place if there are more proposals than spaces.<br /> <br /> Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly<br /> explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.<br /> <br /> There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.<br /> <br /> If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.<br /> <br /> ===Guidelines===<br /> For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:<br /> * Max 2 presenters per talk (this should be checked at the proposal stage)<br /> * Max 1 talk per person<br /> * (at least) 15% talks to be decided by the program committee with &quot;diversity&quot; in mind. Diversity may be any of these (not an exhaustive list):<br /> ** first-time presenter (should be major consideration)<br /> ** gender<br /> ** visible minority<br /> ** technology/tool<br /> <br /> Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].<br /> <br /> Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.<br /> <br /> ===Schedule===<br /> While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.<br /> <br /> ===Keynoter logistics===<br /> <br /> See [[Keynote Committee Duties]].<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Book Giveaway Committee ==<br /> Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.<br /> <br /> Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).<br /> <br /> Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.<br /> <br /> == T-shirt Committee ==<br /> Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.<br /> <br /> Example: [[2013 t-shirt design proposals]]<br /> <br /> Propose to add additional restrictions:<br /> * should not be a designed used previously (do we have an archive of previous designs somewhere?)<br /> * unique (cannot be bought online already)<br /> * design should include &quot;code4lib&quot; and conference year in design, city optional<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Hotels ==<br /> You will likely have to convince the conference hotel of the conference size and past room uptake as part of negotiating your contract. They may want to contact past conference hotels to get more info about actual uptake.<br /> * 2014 -- Raleigh Downtown Sheraton<br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc<br /> <br /> <br /> === Emails to send out ===<br /> <br /> ==== Quick orientation email for newer folks ====<br /> <br /> Send out at least a week in advance before conference...<br /> <br /> <br /> We're in the last few days before the conference begins, and for a good number of you, <br /> this will be your first code4lib. Here is some information to help you navigate through <br /> the conference craziness next week:<br /> <br /> - Social Activities&lt;insert link to SA page&gt;: There's a lot going on outside of the sessions, <br /> and this page has information about various gatherings, events, meals, etc. One activity I <br /> want to highlight is the Newcomer dinner&lt;insert link to SA page&gt; that will be on <br /> &lt;insert date of dinner&gt;. There are still a lot of great restaurants left on the list, and this <br /> is your chance to meet folks you might otherwise not get a chance to talk to at the conference. <br /> Read the guidelines on the wiki, and pick your restaurant.<br /> <br /> (Public service announcement: for those of you who have signed up for the dinner already, make <br /> sure that there's a designated leader for organizing reservations and people herding.)<br /> <br /> - Hospitality Suite: For some of the events listed on the Social Activities page, you will see <br /> the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside <br /> of sessions (or taking a break from sessions). The location of the Suite is usually announced <br /> through various means, including the wiki, IRC and Twitter.<br /> <br /> - IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag <br /> for conference related stuff. The IRC channel&lt;insert link to IRC page&gt; is #code4lib, and there <br /> will be volunteers at the conference who would be more than happy to help you with IRC.<br /> <br /> - For my last item, give the following a read:&lt;insert links to appropriate pages&gt;<br /> <br /> -- How to hack code4lib<br /> -- CodeofConduct4lib<br /> -- Zoia, #code4lib's IRC bot<br /> <br /> If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify <br /> themselves as first timers and &quot;old timers&quot; as well, if you're into classification and stuff. ;-)<br /> <br /> <br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> # IRC Monitor for podium during speaker changes?<br /> <br /> ===Photography===<br /> <br /> * Consider different colored lanyards to articulate personal photography preferences.<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> # YouTube Live, youtube.com/code4lib<br /> <br /> === Live Blogging ===<br /> Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.<br /> <br /> === Ask Anything===<br /> * Add to volunteer page to have a moderator or do a general call out<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit Code4Lib 2014 planning schedule] planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.<br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> ===Calls for Hosting===<br /> No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.<br /> <br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013: Jan 22, 2012<br /> * 2014: January 27, 2013<br /> * 2015: January 29, 2014<br /> * 2016: <br /> <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> [[Category: Code4Lib2012]]<br /> [[Category: Code4Lib2013]]<br /> [[Category: Code4LibCon Planning]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=42851 2015-03-02T18:37:32Z

<p>Ejlynema: /* Suggested Timeline */</p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Also consider using conference planning services from other entities. In 2013, Chicago used DLF services to handle registration. In 2014, NC used CONCENTRA services for all contract negotiation, fiscal activities, registration, and other conference planning and management services.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> *[[Useful information from 2012]]<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> * [http://code4lib.org/content/template-code4lib-20xx Template for the conference page on the main Code4Lib website] - This page is only visible to those who have a code4lib.org account. Once a host has been selected, please copy the template to a new page for that conference year.<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> The process works something like this:<br /> <br /> # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.<br /> # People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)<br /> #* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)<br /> # After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.<br /> # After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.<br /> <br /> ===Program Voting===<br /> Pre-conf voting may need to take place if there are more proposals than spaces.<br /> <br /> Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly<br /> explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.<br /> <br /> There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.<br /> <br /> If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.<br /> <br /> ===Guidelines===<br /> For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:<br /> * Max 2 presenters per talk (this should be checked at the proposal stage)<br /> * Max 1 talk per person<br /> * (at least) 15% talks to be decided by the program committee with &quot;diversity&quot; in mind. Diversity may be any of these (not an exhaustive list):<br /> ** first-time presenter (should be major consideration)<br /> ** gender<br /> ** visible minority<br /> ** technology/tool<br /> <br /> Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].<br /> <br /> Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.<br /> <br /> ===Schedule===<br /> While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.<br /> <br /> ===Keynoter logistics===<br /> <br /> See [[Keynote Committee Duties]].<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Book Giveaway Committee ==<br /> Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.<br /> <br /> Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).<br /> <br /> Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.<br /> <br /> == T-shirt Committee ==<br /> Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.<br /> <br /> Example: [[2013 t-shirt design proposals]]<br /> <br /> Propose to add additional restrictions:<br /> * should not be a designed used previously (do we have an archive of previous designs somewhere?)<br /> * unique (cannot be bought online already)<br /> * design should include &quot;code4lib&quot; and conference year in design, city optional<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Hotels ==<br /> You will likely have to convince the conference hotel of the conference size and past room uptake as part of negotiating your contract. They may want to contact past conference hotels to get more info about actual uptake.<br /> * 2014 -- Raleigh Downtown Sheraton<br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc<br /> <br /> <br /> === Emails to send out ===<br /> <br /> ==== Quick orientation email for newer folks ====<br /> <br /> Send out at least a week in advance before conference...<br /> <br /> <br /> We're in the last few days before the conference begins, and for a good number of you, <br /> this will be your first code4lib. Here is some information to help you navigate through <br /> the conference craziness next week:<br /> <br /> - Social Activities&lt;insert link to SA page&gt;: There's a lot going on outside of the sessions, <br /> and this page has information about various gatherings, events, meals, etc. One activity I <br /> want to highlight is the Newcomer dinner&lt;insert link to SA page&gt; that will be on <br /> &lt;insert date of dinner&gt;. There are still a lot of great restaurants left on the list, and this <br /> is your chance to meet folks you might otherwise not get a chance to talk to at the conference. <br /> Read the guidelines on the wiki, and pick your restaurant.<br /> <br /> (Public service announcement: for those of you who have signed up for the dinner already, make <br /> sure that there's a designated leader for organizing reservations and people herding.)<br /> <br /> - Hospitality Suite: For some of the events listed on the Social Activities page, you will see <br /> the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside <br /> of sessions (or taking a break from sessions). The location of the Suite is usually announced <br /> through various means, including the wiki, IRC and Twitter.<br /> <br /> - IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag <br /> for conference related stuff. The IRC channel&lt;insert link to IRC page&gt; is #code4lib, and there <br /> will be volunteers at the conference who would be more than happy to help you with IRC.<br /> <br /> - For my last item, give the following a read:&lt;insert links to appropriate pages&gt;<br /> <br /> -- How to hack code4lib<br /> -- CodeofConduct4lib<br /> -- Zoia, #code4lib's IRC bot<br /> <br /> If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify <br /> themselves as first timers and &quot;old timers&quot; as well, if you're into classification and stuff. ;-)<br /> <br /> <br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> # IRC Monitor for podium during speaker changes?<br /> <br /> ===Photography===<br /> <br /> * Consider different colored lanyards to articulate personal photography preferences.<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> # YouTube Live, youtube.com/code4lib<br /> <br /> === Live Blogging ===<br /> Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.<br /> <br /> === Ask Anything===<br /> * Add to volunteer page to have a moderator or do a general call out<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit|Code4Lib 2014] planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.<br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> ===Calls for Hosting===<br /> No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.<br /> <br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013: Jan 22, 2012<br /> * 2014: January 27, 2013<br /> * 2015: January 29, 2014<br /> * 2016: <br /> <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> [[Category: Code4Lib2012]]<br /> [[Category: Code4Lib2013]]<br /> [[Category: Code4LibCon Planning]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42345 2014-12-19T03:30:03Z

<p>Ejlynema: </p> <hr /> <div>== Preconference Schedule (draft) ==<br /> <br /> Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.<br /> <br /> This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br /> |-<br /> | '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp; possibly beyond (Needs: projector/screen)<br /> |-<br /> | '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) <br /> |-<br /> | '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp<br /> |-<br /> | '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)<br /> |-<br /> | '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)<br /> |-<br /> | '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br /> |-<br /> | '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)<br /> |-<br /> | '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker<br /> |-<br /> | '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)<br /> |-<br /> | '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)<br /> |-<br /> | '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)<br /> |}<br /> <br /> == Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conferences ==<br /> <br /> ===MORNING:===<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> # Padraic Stack<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> # Padraic Stack<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Laney McGlohon, Stanford University, laneymcg@stanford.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Bojana Skarich<br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Chris Sharp<br /> # Heidi Frank<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Matt Critchlow<br /> # Ray Henry<br /> # Eric Frierson<br /> # Sara Amato<br /> # David Lacy<br /> # David Uspal<br /> # Matt Bernhardt<br /> # Brendan Quinn<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> # Barbara Hui<br /> # Carol Bean<br /> # Matt Connolly<br /> # James Van Mil<br /> # Glen Horton<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> # David Bass<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> # Whitni Watkins<br /> # Jason Raitz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> # Chris Sharp<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> # Mark Mounts<br /> # Heather Pitts<br /> # Andrew Woods<br /> # Carol Bean<br /> # Naomi Dushay (probably)<br /> # David Lacy<br /> # David Uspal<br /> # David Bass<br /> # Brendan Quinn<br /> # Chrissy Rissmeyer<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> # Ryan Rotter<br /> # Matt LaChance<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> # Emily Lynema<br /> # Bret Davidson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> # Josh Wilson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CANCELLED: ''UXtravaganza'' ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> # Whitni Watkins (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> # Laurie Reeves<br /> # Bojana Skarich<br /> # Heidi Frank<br /> # Jason Raitz<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Mounts<br /> # Kathryn Stine<br /> # Steve Meyer<br /> # Matt Critchlow<br /> # Andrew Pasterfield<br /> # Ray Henry<br /> # Bret Davidson<br /> # Naomi Dushay (maybe)<br /> # Eric Frierson<br /> # Matt Bernhardt<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Terry Brady<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Jarrell<br /> # Heather Pitts<br /> # Kathryn Stine<br /> # Andrew Woods<br /> <br /> [[Category:Code4Lib2015]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42342 2014-12-18T21:01:11Z

<p>Ejlynema: </p> <hr /> <div>== Preconference Schedule (draft) ==<br /> <br /> Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.<br /> <br /> This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br /> |-<br /> | '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp; possibly beyond (Needs: projector/screen)<br /> |-<br /> | '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) <br /> |-<br /> | '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp<br /> |-<br /> | '''Grand Ballroom''' I (320) || CANCELLED: [UXtravaganza] || Presentations workshop (Needs: projector/screen)<br /> |-<br /> | '''Grand Ballroom''' II (200) || Visualizing Library Data (Needs: projector) || DPLA API Workshop (Bringing their own projector)<br /> |-<br /> | '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br /> |-<br /> | '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || CollectionSpace: Getting it up and running at your museum (Needs: Projector)<br /> |-<br /> | '''Galleria III (35)''' || Replace yourself with a painfully complex bash script...or try Ansible (Confirmed with Chad; No given setup needs yet) || Intro to Docker<br /> |-<br /> | '''Studio (35)''' || Linked Data Workshop (Bringing their own projector) || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)<br /> |-<br /> | '''Directors (35)''' || Code4Arc (Needs: projector) || Code4Arc (Needs: projector)<br /> |-<br /> | '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || A hands-on introduction to GeoBlacklight (Needs: projector, outlets; Requests: list of attendees)<br /> |}<br /> <br /> == Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conferences ==<br /> <br /> ===MORNING:===<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> # Padraic Stack<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> # Padraic Stack<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Laney McGlohon, Stanford University, laneymcg@stanford.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Bojana Skarich<br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Chris Sharp<br /> # Heidi Frank<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Matt Critchlow<br /> # Ray Henry<br /> # Eric Frierson<br /> # Sara Amato<br /> # David Lacy<br /> # David Uspal<br /> # Matt Bernhardt<br /> # Brendan Quinn<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> # Barbara Hui<br /> # Carol Bean<br /> # Matt Connolly<br /> # James Van Mil<br /> # Glen Horton<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> # David Bass<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> # Whitni Watkins<br /> # Jason Raitz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> # Chris Sharp<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> # Mark Mounts<br /> # Heather Pitts<br /> # Andrew Woods<br /> # Carol Bean<br /> # Naomi Dushay (probably)<br /> # David Lacy<br /> # David Uspal<br /> # David Bass<br /> # Brendan Quinn<br /> # Chrissy Rissmeyer<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> # Ryan Rotter<br /> # Matt LaChance<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> # Emily Lynema<br /> # Bret Davidson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> # Josh Wilson<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === CANCELLED: ''UXtravaganza'' ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> # Whitni Watkins (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> # Laurie Reeves<br /> # Bojana Skarich<br /> # Heidi Frank<br /> # Jason Raitz<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Mounts<br /> # Kathryn Stine<br /> # Steve Meyer<br /> # Matt Critchlow<br /> # Andrew Pasterfield<br /> # Ray Henry<br /> # Bret Davidson<br /> # Naomi Dushay (maybe)<br /> # Eric Frierson<br /> # Matt Bernhardt<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * Becky Escamilla, Oakland Museum of California, rescamilla@museumca.org<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Terry Brady<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Jarrell<br /> # Heather Pitts<br /> # Kathryn Stine<br /> # Andrew Woods<br /> <br /> [[Category:Code4Lib2015]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42252 2014-12-05T03:54:34Z

<p>Ejlynema: </p> <hr /> <div>== Preconference Schedule (draft) ==<br /> <br /> Session titles in Italics means they have not been confirmed yet by presenters/workshop leaders.<br /> <br /> This is a draft, and there may be some room switching when registration opens. Rooms will be confirmed the week before Code4Lib.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Room (capacity) !! Morning (9 AM - Noon) !! Afternoon (1:30 PM - 4:30 PM)<br /> |-<br /> | '''Parlor A (30''') || Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable (Needs: projector, internet connection, and power strips) || Intro to Git &amp; possibly beyond (Needs: projector/screen)<br /> |-<br /> | '''Parlor B (30)''' || Code Retreat (Needs whiteboard, dry-erase markers, projector) || Code Retreat (Needs whiteboard, dry-erase markers, projector) <br /> |-<br /> | '''Parlor C (30)''' || code4lib/Write The Docs barcamp (Needs: projector/screen, flipboard/whiteboard, power sources for laptops) || code4lib/Write The Docs barcamp<br /> |-<br /> | '''Grand Ballroom''' I (320) || ''UXtravaganza'' || Presentations workshop (Needs: projector/screen)<br /> |-<br /> | '''Grand Ballroom''' II (200) || ''Visualizing Library Data'' || DPLA API Workshop<br /> |-<br /> | '''Galleria I (35)''' || Coding Custom Solutions for Every Department in the Library with File Analyzer (Needs PC laptop projection, monitor, internet access/wifi, attendees bring laptops) || Fail4Lib 2015 (Needs: projector/screen; Requested: Conference table seating, limit 20 attendants)<br /> |-<br /> | '''Galleria II (60)''' || RailsBridge: Intro to programming in Ruby on Rails (Needs: internet/wifi, overhead projection) || ''CollectionSpace: Getting it up and running at your museum''<br /> |-<br /> | '''Galleria III (35)''' || ''Replace yourself with a painfully complex bash script...or try Ansible'' || Intro to Docker<br /> |-<br /> | '''Studio (35)''' || ''Linked Data Workshop'' || Dive into Hydra (Needs: projector/screen; Requests: classroom style seating)<br /> |-<br /> | '''Directors (35)''' || Code4Arc || Code4Arc (Needs: projector)<br /> |-<br /> | '''Council (45)''' || Delivering and Preserving GIS Data (Projector, Video connector for MacBook Pro, wifi, power outlets) || ''A hands-on introduction to GeoBlacklight''<br /> |}<br /> <br /> == Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conferences ==<br /> <br /> ===MORNING:===<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Laney McGlohon, Stanford University, laneymcg@stanford.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> # Mark Mounts<br /> # Chris Sharp<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> # Mark Mounts<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> # Barbara Hui<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> # Whitni Watkins<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> # Chris Sharp<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> # Mark Mounts<br /> # Heather Pitts<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> # Whitni Watkins (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Mark Jarrell<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Mounts<br /> # Kathryn Stine<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> # Mark Jarrell<br /> # Heather Pitts<br /> # Kathryn Stine<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2015_Preconference_Proposals&diff=42205 2014-12-01T21:46:36Z

<p>Ejlynema: </p> <hr /> <div>== Instructions ==<br /> Thank you for considering proposing a pre-conference! Here are a few details:<br /> <br /> * We will be taking pre-conference proposals until '''November 7, 2014'''<br /> * If you cannot or do not want to edit this wiki directly, you can email your proposals to cmh2166@columbia.edu or collie@msu.edu<br /> * Examples from the 2014 pre-conference proposals can be found at [[2014 preconference proposals|http://wiki.code4lib.org/2014_preconference_proposals]]<br /> * If you are interested in ''attending'' a particular pre-conference, please append your name below that proposal (indicating interest in more than one proposal is fine!)<br /> * If you have an idea for a pre-conference, but cannot facilitate yourself please post the idea below and email cmh2116@columbia.edu or collie@msu.edu<br /> * '''NOTE:''' Pre-conferences are NOT included in the Code4Lib Conference price and will be held on Monday, February 9, 2015 as either full day or half day sessions<br /> * Please use the template for proposals provided in the pre-formatted block below<br /> <br /> == Pre-conference Proposals ==<br /> <br /> === Delivering and Preserving GIS Data ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> We will discuss how to set up a spatial data infrastructure (SDI) to deliver GIS data, to manage GIS content in a Fedora repository for preservation, and to establish metadata requirements for good spatial discovery. By the end of the workshop you will have a working SDI! This workshop is a compliment to the GeoBlacklight workshop in the afternoon.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === A hands-on introduction to GeoBlacklight ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Darren Hardy, Stanford University, drh@stanford.edu<br /> * Jack Reed, Stanford University, pjreed@stanford.edu<br /> <br /> GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many libraries have collections of GIS data that aren’t easily discoverable. This will be a hands-on workshop, focused on installing and running GeoBlacklight which builds on the morning workshop &quot;Delivering and Preserving GIS Data&quot;.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # [[User:Ssimpkin|Sarah Simpkin]]<br /> # Vicky Steeves<br /> # Andrew Battista<br /> # Peggy Griesinger<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> ===RailsBridge: Intro to programming in Ruby on Rails===<br /> <br /> '''&quot;Half-Day&quot; [morning]'''<br /> <br /> * Contact Carolyn Cole, Penn State University, carolyn@psu.edu<br /> * Additional instructors welcome<br /> <br /> Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! [http://www.railsbridge.org/ RailsBridge] is a friendly place to get together and learn how to write some code.<br /> <br /> RailsBridge is a great workshop that opens the doors to projects like [http://projectblacklight.org/ Blacklight] and [http://projecthydra.org/ Hydra] and [https://github.com/traject-project/traject Traject].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> #Vicky Steeves<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Coral Sheldon-Hess<br /> # Margaret Heller<br /> # Bohyun Kim<br /> #<br /> #<br /> <br /> === Replace yourself with a painfully complex bash script...or try Ansible ===<br /> <br /> '''Half Day [Morning]'''<br /> <br /> * Chad Nelson, chad dot nelson @ lyrasis dot org<br /> * Blake Carver, Blake dot carver @lyrasis dot org<br /> <br /> Abstract: <br /> <br /> [http://www.ansible.com Ansible] is an open source automation and [http://en.wikipedia.org/wiki/Configuration_management configuration management] tool that focuses on simplicity to help make your life as a developer, or a sysadmin, or even a full on devops-er, easier. This workshop will cover the basic building blocks used in Ansible as well as some best practices for maintaining your Ansible code. We will start by working through a simple example together, and then participants will be given time to work on their own projects with instructors providing guidance and troubleshooting along the way. By the end of the session, participants will have a working knowledge of Ansible and be able to write a working [http://docs.ansible.com/playbooks.html playbook] to meet local needs.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> # Ray Schwartz<br /> # Coral Sheldon-Hess<br /> # Kevin S. Clarke<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Anna Headley<br /> # Chelsea Lobdell<br /> # Shaun Ellis<br /> #<br /> #<br /> <br /> === Intro to Docker ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * John Fink, McMaster University, john dot fink at gmail dot com<br /> * Francis Kayiwa, University of Maryland Libraries , francis dot kayiwa at gmail dot com<br /> <br /> Abstract:<br /> <br /> [http://docker.io Docker] ([http://journal.code4lib.org/articles/9669 jbfink code4lib journal article]) is an open source Linux operating system-level virtualization framework that has seen great uptake over the past year. This workshop will take you through the basic features of Docker, including setup, importing of containers, development workflows and deploying. Knowing when Docker is useful and when it isn't will also be covered. Ideally, every attendee will have ample experience creating and running their own Docker instances by the end.<br /> <br /> ''Interested in Attending''<br /> <br /> # Jim Hahn<br /> # Joshua Gomez<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Megan Kudzia<br /> # Coral Sheldon-Hess (pleeeeaaase put this in a different slot from Ansible!)<br /> # Cary Gordon (uses Docker in production on AWS)<br /> # Eric Phetteplace<br /> # Esther Verreau<br /> # Charlie Morris<br /> # Anna Headley (voting for afternoon, compliments ansible)<br /> # Shaun Ellis<br /> <br /> === Code Retreat ===<br /> <br /> '''Full Day'''<br /> <br /> * Jeremy Friesen, University of Notre Dame, jfriesen at nd dot edu<br /> * Additional facilitators welcome; Especially if you have CodeRetreat experience.<br /> <br /> Abstract:<br /> <br /> &quot;Coderetreat is a day-long, intensive practice event, focusing on the fundamentals of software development and design.<br /> By providing developers the opportunity to take part in focused practice, away from the pressures of 'getting things done', the coderetreat format has proven itself to be a highly effective means of skill improvement.<br /> Practicing the basic principles of modular and object-oriented design, developers can improve their ability to write code that minimizes the cost of change over time.&quot; [http://coderetreat.org/about About Code Retreat]<br /> <br /> ''Interested in Attending''<br /> <br /> # Mike Giarlo<br /> # Charlie Morris<br /> # Devon Smith<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Presentations workshop ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' (but could be expanded based on interest)<br /> <br /> * Chris Beer, Stanford University, cabeer@stanford.edu<br /> * Additional facilitators welcome.<br /> <br /> This is a preconference session intended for first time Code4Lib speakers, habitual procrastinators, experienced speakers, those thinking about offering lightning talks, etc. If you're preparing a talk for this year's Code4Lib, this workshop is an opportunity to rehearse your presentation, get feedback from peers, get familiar with the presentation technology, etc.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #Vicky Steeves<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Dive into Hydra ===<br /> <br /> '''&quot;Half Day [Afternoon]&quot;''' <br /> <br /> * Justin Coyne, Data Curation Experts, justin@curationexperts.com<br /> * Bess Sadler, Stanford University, bess@stanford.edu<br /> <br /> Hydra is a collaboration of over 30 educational institutions who work together to solve their repository needs by building open-source software. Dive into Hydra is a course that bootstraps you into the Hydra software framework. We'll start at the basics and walk you through the various layers of the Hydra stack. We'll conclude by installing the Worthwhile gem, enabling every participant to walk away with their own Institutional Repository. Participants who have prior exposure to web programming will get the most out of this course. It's recommended (but not required) that you attend &quot;RailsBridge&quot; prior to this workshop.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Maura Carbone<br /> # Peggy Griesinger<br /> # Mike Price<br /> # Jean Rainwater<br /> # Sara Amato<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === code4lib/Write The Docs barcamp ===<br /> <br /> '''&quot;Full Day&quot;''', with options for jumping in for half a day<br /> <br /> * code4lib wrangler: Becky Yoose, yoosebec at grinnell dot edu<br /> * Write the Docs contacts: TBA<br /> <br /> Abstract<br /> <br /> Documentation. We all know that we need it for things we develop, but most of us either keep putting it off or write documentation that is not maintained, clear, concise, and so on. We're all guilty! So what's stopping us from doing better docs? Luckily, Portland is also the home to the NA Write the Docs conference, and is home for many folks who live and breathe documentation. This barcamp is open to both code4lib and non-code4lib conference attendees and is intended to provide a space where code4libbers can find practices and tools in creating better documentation for all as well as documentation wonks can find out ways in which the library wonks can help with better documentation access and organization. <br /> <br /> Remember, like metadata, documentation is a love note to the future.<br /> <br /> More information about Write the Docs at http://conf.writethedocs.org/<br /> <br /> There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval). <br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> '''Full day'''<br /> # Emily Lynema<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Morning'''<br /> # Ranti Junus<br /> # Mita Williams<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> '''Afternoon'''<br /> # Francis Kayiwa (if my Pre-Conf is in the AM) Otherwise with Ranti if my Pre-Conf is in the afternoon. <br /> # Kevin S. Clarke<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Linked Data Workshop ===<br /> <br /> '''&quot;Half Day [morning]&quot;''' <br /> <br /> * Karen Estlund, University of Oregon, kestlund@uoregon.edu<br /> * Tom Johnson, DPLA, tom@dp.la<br /> <br /> Abstract:<br /> <br /> Developer and metadata experts-focused linked data workshop. Topics covered will include: linked open data principles, converting existing data, and modeling linked data in DAMS.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Logan Cox<br /> # Ray Schwartz<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Steven Anderson<br /> # Eben English<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Code4Arc ===<br /> <br /> '''&quot;Full Day&quot;''' (with options for half day participation)<br /> <br /> * Sarah Romkey, Artefactual Systems, sromkey@artefactual.com<br /> * Justin Simpson, Artefactual Systems, jsimpson@artefactual.com<br /> * Chris Fitzpatrick, ArchivesSpace, chris.fitzpatrick@lyrasis.org<br /> * Alexandra Chassanoff, BitCurator Access, bitcurator@gmail.com<br /> <br /> Abstract:<br /> <br /> What does it mean to Code for Archives? Is it different than coding for libraries, and if so, how? <br /> <br /> Code4Lib is a wonderful and successful model (you must agree or you wouldn't be reading this). This workshop is an attempt to create a space to replicate the model in an Archival context. A space to talk about development for archives, and the particular challenges of developing archival systems. Topics to discuss include Integration between different Archival software tools, and between Archival tools/workflows and larger institutional tools like institutional repositories, discovery and access systems.<br /> <br /> The schedule may include the following:<br /> <br /> * Panel type conversations about the State of Art in Archives <br /> * Case Studies - discussion of workflows at specific institutions, including gaps in tools and how those are being addressed or could be addressed <br /> * Tool Demos - access to demos of some of the open source tools used in an Archival Context (examples include ArchivesSpace, Archivematica, BitCurator, AtoM)<br /> <br /> Artefactual will provide demos running Archivematica and AtoM, Lyrasis will do so for ArchivesSpace, BitCurator will for BitCurator. We encourage others to chime in here to expand the list of tools available to touch and play with. <br /> <br /> When signing up, please indicate if you are an end-user or a developer.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Laney McGlohon - developer<br /> # Shaun Ellis<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Fail4Lib 2015 ===<br /> <br /> '''Half Day [TBD, probably afternoon]'''<br /> <br /> * Andreas Orphanides, akorphan (at) ncsu.edu<br /> * Jason Casden, jmcasden (at) ncsu.edu<br /> <br /> Abstract:<br /> <br /> Failure. Failure never changes. Since failure is an inescapable part of our professional work, it's important to be familiar with it, to acknowledge it, and to grow from it -- and, in contravention to longstanding tradition, to accept it as a fact of development life. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be shunned. Let's train ourselves to understand and embrace failure, encourage enlightened risk-taking, and seek out opportunities to fail and learn. This way, when we do what we do -- and fail at what we do -- we'll do so with grace and without fear.<br /> <br /> This year's preconference will include new case studies and an improved discussion format. Repeat customers are welcome! (Fail early, fail often.)<br /> <br /> The schedule may include the following:<br /> <br /> * Case studies. Avoid our own mistakes by bearing witness to the failures of others.<br /> * Confessionals, for those willing to share. Let's learn from our own (and each others') failures.<br /> * Group therapy. Vent about your own experiences in a judgment-free setting. Explore how we can make our organizations less risk-averse and more failure-tolerant.<br /> <br /> ''Interested in attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Charlie Morris<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Coding Custom Solutions for Every Department in the Library with File Analyzer ===<br /> <br /> '''&quot;Half Day [Morning]&quot;''' <br /> <br /> * Terry Brady, Georgetown University Library, twb27@georgetown.edu<br /> <br /> Abstract<br /> <br /> The Georgetown University Library has shared an application called the [http://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer] that has allowed us to build custom solutions for nearly every department in the library.<br /> <br /> * Analyzing Marc Records for the Cataloging department<br /> * Transferring ILS invoices for the University Account System for the Acquisitions department <br /> * Delivering patron fines to the Bursar’s office for the Access Service department<br /> * Summarizing student worker timesheet data for the Finance department<br /> * Validating counter compliant reports for the Electronic Resources department<br /> * Preparing ingest packages for the Digital Services department<br /> * Validating checksums for the Preservation department<br /> <br /> This hands on workshop will step through the components of the application framework. Workshop participants will install and develop custom File Analyzer tasks in this session.<br /> <br /> The workshop agenda will loosely follow the [https://github.com/Georgetown-University-Libraries/File-Analyzer/wiki/File-Analyzer-Training----Code4Lib-2014 pre-conference agenda from Code4Lib 2014].<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Megan Kudzia<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Confessions of the (Accidental) Code Hoarder: How to make your Code Sharable: ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Karen A. Coombs, OCLC, coombsk@oclc.org<br /> <br /> Abstract<br /> Have you built something cool and useful that you want to share with others? This preconference session will discuss techniques and tools for sharing code. Using our own OCLC Developer Network PHP authentication code libraries as an example, we will discuss a set of recommended best practices for how to share your code.<br /> <br /> We’ll start with coding standards and test writing so you can be confident of the quality of your code. Next we'll discuss inline documentation as a tool for developers and how auto-generating documentation will save you time and effort. Lastly we'll provide an overview of the tricky areas of dependency and package management, and distribution tools. Along the way, we'll cover PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manage distribution, updates and community feedback.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Peggy Griesinger<br /> # Ray Schwartz<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> <br /> === UXtravaganza ===<br /> '''&quot;Half or Full Day [Based on Interest?, Morning/Afternoon Doesn’t Matter]&quot;'''<br /> <br /> * William Hicks, University of North Texas, William.hicks@unt.edu<br /> * Volunteers?<br /> <br /> Abstract<br /> <br /> I’m envisioning a 1/2 of full day for front-end developers, content strategy people, and other misfits with an interest in user experience, where we can talk about our shared problems, use cases, the state of current research, and play with each other’s sites. A half day seems doable, but if there’s significant enough interest we could push for a full? Here are a few of the things I think might be interesting to see happen:<br /> <br /> * '''Analytics Share-fest:''' A few volunteers demonstrate data about their websites, catalogs, archival/digital collections. Most of us know our own sites but it would be interesting/validating to share this data with others so we can start to see commonalities between institutions, in certain kinds of systems, etc. For anyone using event tracking, or using click- or heat-maps, this would be a great opportunity to show off what people are seeing.<br /> <br /> * '''UX Best Practices Catch Up:''' This spring I had the opportunity to attend a few days worth of usability workshops from the Nielsen-Norman Group, most of which was focused on mobile. I could distill down a lot of the information into an short presentation. Since this is a constantly moving area of research it would be nice to see a few people do other similar short presentations on some current trends/findings relevant to libraries, search, etc.<br /> <br /> * '''Mobile Dev Lab:''' The UNT Libraries has been collecting a small set of smartphones and tablets for testing and development. Basically an [http://labup.org Open Device Lab]. We have about a dozen devices now of varying sizes, OS, OS Versions, + Google Glass. I’ll bring the devices, you can bring yours, and assuming we can get the wifi up and running we can test our sites/services with our big sausage fingers rather than pretending to do so through emulators and the one or two devices we each usually have on hand. If anyone is game they can do a tutorial on Browser-based Inspector Tools, Browser-Cams, or other testing services.<br /> <br /> * '''The Eye’s Have It.''' The UNT Libraries is also in the process of acquiring an eye tracker and software for usability and other gaze-based research studies. We’ll take possession of it shortly after this pre-conference proposal is due and will have a couple of months to play with them before the conference. Assuming we can get our act together learning the device and can get past the technical hurdles of setting it up at the pre-conference, we could try to do some live demos on each other’s sites; i.e. You nominate a site/service, someone in the audience volunteers to wear the device, and we all watch them struggle do the tasks you request on a projector. Rinse. Lather. Repeat. It would hardly be scientific, but it sure would be fun. As a backup, if we have some sites nominated beforehand, I can run a few students at my library through some tasks here and we can show off the results to the crowd.<br /> <br /> For those of you wanting to attend and help out, I’d really like to see some discussion on typography, writing for the web, “dealing with business/administrative requirements from on-high&quot;, maybe do some prototyping exercises, etc. Similarly if anyone is interested in doing some tutorials on bootstrap or how-to’s on running a usability test, that would be rad. But we need you to step up and steer part of the time for most of this to work, so if you are interested in some aspect, and especially if you want to volunteer to lead a bit of the time, contact me.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your<br /> name (but not email address, etc.) here<br /> <br /> # Ray Schwartz<br /> # Andy Mardesich<br /> # Chelsea Lobdell<br /> # Eben English (1/2 day)<br /> # Shaun Ellis (as attendee or volunteer)<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Intro to Git &amp; possibly beyond ===<br /> <br /> '''Half Day [Whenever]'''<br /> <br /> * Erin Fahy, Stanford University, efahy@stanford.edu<br /> * Shaun Trujillo, Mount Holyoke College, strujill@mtholyoke.edu<br /> <br /> We can start with the basics of Git and discuss ways in which it can help you version control just about any file, not just code. Points we can go over:<br /> <br /> * What is a Distributed Version Control System?<br /> * What's the difference between Git and Github.com?<br /> * How to initialize new Git projects locally and on a remote server/Github<br /> * Cloning/Forking existing projects and keeping up to date<br /> * The wonderful world of Git branches<br /> * Interactive rebasing<br /> * Contributing code to existing projects &amp; what pull requests are<br /> * How to handle merge conflicts<br /> * Overview of workflows and branch best practices<br /> * (time allowing) Advanced git: pre/post hooks, submodules, anything else?<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Jeannie Graham<br /> # Derek Merleaux<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === Visualizing Library Data ===<br /> <br /> '''&quot;Half Day [Morning||Afternoon]&quot;''' <br /> <br /> * Matt Miller, matthewmiller@nypl.org, New York Public Library, NYPL Labs<br /> <br /> Visualizing your institution’s data can give new insight about your holding’s strengths, weaknesses and outliers. They can also provide potential new avenues for discovery and access. This half day session will focus on programmatically visualizing library metadata. Emphasis will be on creating web-based visualizations utilizing libraries such as d3.js but attention paid towards visualizing large datasets while keeping them web accessible. By then end of the session participants will have template, sample code and methodologies enabling them to start producing visualization with their own data.<br /> <br /> ''Interested in Attending''<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ashley Blewer!<br /> # Bobbi Fox<br /> # Ray Schwartz<br /> # Ranti Junus<br /> # Eric Phetteplace<br /> # Joshua Gomez<br /> # Charlie Morris<br /> # Andy Mardesich<br /> # Tao Zhao<br /> # Chris Hallberg<br /> # Derek Merleaux<br /> # Bohyun Kim<br /> # Eben English<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> <br /> === CollectionSpace: Getting it up and running at your museum ===<br /> <br /> '''Half Day [Afternoon]'''<br /> <br /> * Richard Millet, CollectionSpace.org, richard.millet@lyrasis.org<br /> * TBD<br /> <br /> This workshop is designed for anyone interested in or tasked with the technical setup and configuration of CollectionSpace for use in any collections environment (museum, library, special collection, gallery, etc. For more information about CollectionSpace, visit http://www.collectionspace.org<br /> <br /> Participants will be walked through the process of installing the software and performing basic configuration work on a stand-alone instance of CollectionSpace. Participants will learn how to create user accounts, set up basic roles and permissions, and may then catalog or otherwise document sample objects from their collections. Materials distributed prior to the workshop will cover hardware and system requirements for participants.<br /> <br /> ''Interested in Attending''<br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> #<br /> <br /> === DPLA API Workshop: ===<br /> <br /> '''Half Day [Afternoon]''' <br /> <br /> * Audrey Altman, DPLA<br /> * Mark Breedlove, DPLA<br /> * Mark Matienzo, DPLA<br /> * Tom Johnson, DPLA<br /> <br /> The Digital Public Library of America API workshop guides attendees through the process of creating an app based on DPLA's free, public API. The API provides access to over 8 million [http://creativecommons.org/publicdomain/zero/1.0/ CC0] licensed metadata records from America’s libraries, archives, and museums in a common metadata format. This workshop is designed for people of all technical skill levels and will cover API basics, the capabilities of the DPLA API, available toolsets, and tips for using records from the API effectively. Members of DPLA's technology team will be on hand to help the group build their first application, and answer questions about tools and content.<br /> <br /> If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here<br /> <br /> # Ranti Junus<br /> # Jean Rainwater<br /> # Mita Williams<br /> # Margaret Heller<br /> # Bohyun Kim<br /> # Steven Anderson<br /> # Shaun Ellis<br /> # Sarah Simpkin<br /> #<br /> #<br /> <br /> [[Category:Code4Lib2015]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=41025 2014-03-28T18:48:37Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br /> <br /> '''Venue planning and negotiation'''<br /> * A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br /> * Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br /> * Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br /> * When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br /> * Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br /> * Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br /> <br /> '''Registration'''<br /> * The venue of C4L2014 could hold 350 people<br /> * To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br /> * Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br /> * Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br /> * CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br /> * Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br /> <br /> '''Sponsorships'''<br /> * 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br /> * To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br /> * The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> ** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> * When putting out a call for any graphics, ensure that the formats submitted are usable in production (e.g. vector formats).<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> * Using negotiation to buy &quot;off menu&quot; will save money.<br /> * Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Diebold-o-Tron)<br /> <br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> * Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br /> * Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br /> <br /> * Communicate early and often with organizers and have a plan for '''getting a solid schedule''' as early as possible (this can help some organizers provide the needed justification to their institutions for travel support). Consider this in light of your winnowing process.<br /> * (Also applies to the A/V section) find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, and wifi, power availability, etc. up front.<br /> <br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> * Provide A/V info to speakers in advance (availability of computer, network availability, any additional software installs needed, etc.).<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br /> * A Google Calendar worked well this year in establishing all deadlines across all committees.<br /> * A regularly occurring meeting of some planning group helps keep things moving.<br /> * See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br /> <br /> '''IRC'''<br /> *Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br /> *Start the process to get the freenode limit raised a month before to plan for any kinks!<br /> *Announce channel logging a month or more ahead of time <br /> <br /> '''Scholarships'''<br /> <br /> * forthcoming!<br /> <br /> '''Keynotes'''<br /> * It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br /> <br /> '''Ideas'''<br /> * Lanyards for whether it is OK to take photographs<br /> * Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br /> * Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br /> ** Another possibility could be to have the room next to the hospitality room be reserved for a &quot;suite steward&quot; or &quot;host&quot; volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br /> * Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br /> * Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br /> * Consider precombining lightning talks into a single slide deck to keep the flow going.<br /> * Consider live closed captioning software for talks and streaming<br /> * IRC channel shown on screens when no presenter is up<br /> * Consider switches at the tables<br /> * Add a Code4Lib logo to the podium<br /> * Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=41023 2014-03-28T18:29:18Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br /> <br /> '''Venue planning and negotiation'''<br /> * A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br /> * Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br /> * Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br /> * When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br /> * Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br /> * Overall, the 2014 group began working on venue negotiation and sponsorships in June 2013 for a conference taking place in March 2014.<br /> <br /> '''Registration'''<br /> * The venue of C4L2014 could hold 350 people<br /> * To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br /> * Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br /> * Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br /> * CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br /> * Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br /> <br /> '''Sponsorships'''<br /> * 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br /> * To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br /> * The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> ** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> * When putting out a call for any graphics, ensure that the formats submitted are usable in production.<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> * Using negotiation to buy &quot;off menu&quot; will save money.<br /> * Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Debold-o-Tron)<br /> <br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> * Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br /> * Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br /> <br /> * Communicate early and often with organizers and have a plan for *having a solid plan* as early as possible (this can help some organizers provide the needed justification to their instituitions for travel support).<br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> * While you're at that, find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, *and* wifi and power availability up front.<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br /> * A Google Calendar worked well this year in establishing all deadlines across all committees.<br /> * A regularly occurring meeting of some planning group helps keep things moving.<br /> * See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br /> <br /> '''IRC'''<br /> *Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br /> *Start the process to get the freenode limit raised a month before to plan for any kinks!<br /> *Announce channel logging a month or more ahead of time <br /> <br /> '''Scholarships'''<br /> <br /> * forthcoming!<br /> <br /> '''Keynotes'''<br /> * It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br /> <br /> '''Ideas'''<br /> * Lanyards for whether it is OK to take photographs<br /> * Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br /> * Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br /> ** Another possibility could be to have the room next to the hospitality room be reserved for a &quot;suite steward&quot; or &quot;host&quot; volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br /> * Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br /> * Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br /> * Consider precombining lightning talks into a single slide deck to keep the flow going.<br /> * Consider live closed captioning software for talks and streaming<br /> * IRC channel shown on screens when no presenter is up<br /> * Consider switches at the tables<br /> * Add a Code4Lib logo to the podium<br /> * Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=41022 2014-03-28T18:27:21Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br /> <br /> '''Venue planning and negotiation'''<br /> * A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br /> * Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br /> * Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br /> * When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br /> * Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br /> <br /> '''Registration'''<br /> * The venue of C4L2014 could hold 350 people<br /> * To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br /> * Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br /> * Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br /> * CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br /> * Waitlist was well-handled by a Google Form, as the registration system didn't have built-in waitlist functionality.<br /> <br /> '''Sponsorships'''<br /> * 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br /> * To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br /> * The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> ** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> * When putting out a call for any graphics, ensure that the formats submitted are usable in production.<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> * Using negotiation to buy &quot;off menu&quot; will save money.<br /> * Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Debold-o-Tron)<br /> <br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> * Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br /> * Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br /> <br /> * Communicate early and often with organizers and have a plan for *having a solid plan* as early as possible (this can help some organizers provide the needed justification to their instituitions for travel support).<br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> * While you're at that, find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, *and* wifi and power availability up front.<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br /> * A Google Calendar worked well this year in establishing all deadlines across all committees.<br /> * A regularly occurring meeting of some planning group helps keep things moving.<br /> * See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br /> <br /> '''IRC'''<br /> *Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br /> *Start the process to get the freenode limit raised a month before to plan for any kinks!<br /> *Announce channel logging a month or more ahead of time <br /> <br /> '''Scholarships'''<br /> <br /> * forthcoming!<br /> <br /> '''Keynotes'''<br /> * It's useful to ask nominees about their availability and willingness to attend before voting so that the community is only voting on real candidates (as opposed to wishful thinking).<br /> <br /> '''Ideas'''<br /> * Lanyards for whether it is OK to take photographs<br /> * Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br /> * Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br /> ** Another possibility could be to have the room next to the hospitality room be reserved for a &quot;suite steward&quot; or &quot;host&quot; volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br /> * Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br /> * Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br /> * Consider precombining lightning talks into a single slide deck to keep the flow going.<br /> * Consider live closed captioning software for talks and streaming<br /> * IRC channel shown on screens when no presenter is up<br /> * Consider switches at the tables<br /> * Add a Code4Lib logo to the podium<br /> * Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=41021 2014-03-28T18:24:04Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br /> <br /> '''Venue planning and negotiation'''<br /> * A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br /> * Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br /> * Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br /> * When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br /> * Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br /> <br /> '''Registration'''<br /> * The venue of C4L2014 could hold 350 people<br /> * To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br /> * Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br /> * Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br /> * CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br /> <br /> '''Sponsorships'''<br /> * 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br /> * To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br /> * The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> ** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> * When putting out a call for any graphics, ensure that the formats submitted are usable in production.<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> * Using negotiation to buy &quot;off menu&quot; will save money.<br /> * Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Debold-o-Tron)<br /> <br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> * Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br /> * Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br /> <br /> * Communicate early and often with organizers and have a plan for *having a solid plan* as early as possible (this can help some organizers provide the needed justification to their instituitions for travel support).<br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> * While you're at that, find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, *and* wifi and power availability up front.<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br /> * A Google Calendar worked well this year in establishing all deadlines across all committees.<br /> * A regularly occurring meeting of some planning group helps keep things moving.<br /> * See [http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.<br /> <br /> '''IRC'''<br /> *Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br /> *Start the process to get the freenode limit raised a month before to plan for any kinks!<br /> *Announce channel logging a month or more ahead of time <br /> <br /> '''Scholarships'''<br /> <br /> * forthcoming!<br /> <br /> '''Ideas'''<br /> * Lanyards for whether it is OK to take photographs<br /> * Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br /> * Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br /> ** Another possibility could be to have the room next to the hospitality room be reserved for a &quot;suite steward&quot; or &quot;host&quot; volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br /> * Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br /> * Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br /> * Consider precombining lightning talks into a single slide deck to keep the flow going.<br /> * Consider live closed captioning software for talks and streaming<br /> * IRC channel shown on screens when no presenter is up<br /> * Consider switches at the tables<br /> * Add a Code4Lib logo to the podium<br /> * Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=41020 2014-03-28T18:23:02Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned (and Ideas)<br /> <br /> '''Venue planning and negotiation'''<br /> * A conference services planning organization, like CONCENTRA, has significant experience in contract details that volunteer planners would unlikely have. <br /> * Venue negotiation takes a significant amount of time. Total of nearly four (5) months of visits, informational calls, and negotiations.<br /> * Hotel block negotiations are valuable, especially in the fine print of cancellation clauses, re-selling of unsold rooms, penalties of underselling, and scheduled kickbacks at certain increments.<br /> * When looking at space capacities, make sure you find out how many attendees can REALLY fit in a given space. The advertised numbers seem to be artificially inflated; ask to see a room layout graphic with A/V in place (we lost 15% of stated capacity at least to A/V).<br /> * Regardless of how strongly we communicate to the venue the pressures we'll be placing on their wifi, they almost always have trouble keeping up with our connection weight (especially hotels).<br /> <br /> '''Registration'''<br /> * The venue of C4L2014 could hold 350 people<br /> * To ensure registration Presenters, Preconference Organizers, and Sponsors (Platinum, Gold, and Table), initial registration was capped at 325. This filled in approximately 48 hours.<br /> * Demand for Code4Lib 2014 was 420 based on registrations and wait list. <br /> * Local registrations by the hosting libraries (Duke, NCSU, UNC) was 41 registrations.<br /> * CONCENTRA's registration system had some technical limitations as to data input and flow, but CONCENTRA handled all processing with little assistance by volunteers.<br /> <br /> '''Sponsorships'''<br /> * 46.8% of the estimated cost of C4L2014 was provided by sponsorships. The registration cost of $165 per person covered another 46.8%. The remaining balance of C4L2013 covered the remaining 6-7%. <br /> * To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year.<br /> * The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money this year.<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> ** Nevertheless, there is value in providing as diverse a selection of sizes and cuts as is practicable.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> * When putting out a call for any graphics, ensure that the formats submitted are usable in production.<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> * Using negotiation to buy &quot;off menu&quot; will save money.<br /> * Make sure that you ask about dietary requirements during registration so that you can accommodate vegan / vegetarian / gluten-free, etc.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful. (Adam Constabaris [first dot last, lowercased at gmail] from the 2014 committee has a working database schema and a vague idea about incorporating voting on preconferences into the Debold-o-Tron)<br /> <br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> * Some preconferences work a lot better with special seating arrangements, enrollment caps, etc. Some support for allowing preconf presenters to request/implement such arrangements would be worth considering.<br /> * Pre-conference organizers will likely want to know before registration opens whether or not their pre-conference is actually going to happen (relevant if there are two many proposed for the space to support).<br /> <br /> * Communicate early and often with organizers and have a plan for *having a solid plan* as early as possible (this can help some organizers provide the needed justification to their instituitions for travel support).<br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> * While you're at that, find out as much as possible about the rooms at the venue, including the layout and suitability to different session styles, *and* wifi and power availability up front.<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.<br /> * A Google Calendar worked well this year in establishing all deadlines across all committees.<br /> * A regularly occurring meeting of some planning group helps keep things moving.<br /> * See [documentation and timelines|http://wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers] for 2014 volunteer committees.<br /> <br /> '''IRC'''<br /> *Pay attention to the IPs you are assigned, make sure they are not PRIVATE (eg. 10,172.4-31,192.168) <br /> *Start the process to get the freenode limit raised a month before to plan for any kinks!<br /> *Announce channel logging a month or more ahead of time <br /> <br /> '''Scholarships'''<br /> <br /> * forthcoming!<br /> <br /> '''Ideas'''<br /> * Lanyards for whether it is OK to take photographs<br /> * Add chairs to the front of the room so that lightning talk presenters can sit before they talk<br /> * Do not place a conference goer near the hospitality suite! Maybe make the hang out place a different area in the hotel or conference.<br /> ** Another possibility could be to have the room next to the hospitality room be reserved for a &quot;suite steward&quot; or &quot;host&quot; volunteer - aka a person that can look after the room in terms of cleanliness, drink/food stock, etc. <br /> * Make the podium laptop desktop background a plain color with good contrast. After every group of presenters clean off the desktop to keep it quicker and easier for presenters to find their slides.<br /> * Put someone at the front of the room who is responsible for helping presenters with the presenter computer. <br /> * Consider precombining lightning talks into a single slide deck to keep the flow going.<br /> * Consider live closed captioning software for talks and streaming<br /> * IRC channel shown on screens when no presenter is up<br /> * Consider switches at the tables<br /> * Add a Code4Lib logo to the podium<br /> * Have someone whose job it is to collect questions during a presentation and that can then ask them. Allowing for anonymous questions may lead to more folks asking.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=40762 2014-03-20T19:01:44Z

<p>Ejlynema: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Also consider using conference planning services from other entities. In 2013, Chicago used DLF services to handle registration. In 2014, NC used CONCENTRA services for all contract negotiation, fiscal activities, registration, and other conference planning and management services.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> *[[Useful information from 2012]]<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> The process works something like this:<br /> <br /> # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.<br /> # People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)<br /> #* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)<br /> # After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.<br /> # After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.<br /> <br /> ===Program Voting===<br /> Pre-conf voting may need to take place if there are more proposals than spaces.<br /> <br /> Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly<br /> explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.<br /> <br /> There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.<br /> <br /> If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.<br /> <br /> ===Guidelines===<br /> For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:<br /> * Max 2 presenters per talk (this should be checked at the proposal stage)<br /> * Max 1 talk per person<br /> * (at least) 15% talks to be decided by the program committee with &quot;diversity&quot; in mind. Diversity may be any of these (not an exhaustive list):<br /> ** first-time presenter (should be major consideration)<br /> ** gender<br /> ** visible minority<br /> ** technology/tool<br /> <br /> Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].<br /> <br /> Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.<br /> <br /> ===Schedule===<br /> While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Book Giveaway Committee ==<br /> Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.<br /> <br /> Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).<br /> <br /> Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.<br /> <br /> == T-shirt Committee ==<br /> Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.<br /> <br /> Example: [[2013 t-shirt design proposals]]<br /> <br /> Propose to add additional restrictions:<br /> * should not be a designed used previously (do we have an archive of previous designs somewhere?)<br /> * unique (cannot be bought online already)<br /> * design should include &quot;code4lib&quot; and conference year in design, city optional<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Hotels ==<br /> You will likely have to convince the conference hotel of the conference size and past room uptake as part of negotiating your contract. They may want to contact past conference hotels to get more info about actual uptake.<br /> * 2014 -- Raleigh Downtown Sheraton<br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc<br /> <br /> <br /> === Emails to send out ===<br /> <br /> ==== Quick orientation email for newer folks ====<br /> <br /> Send out at least a week in advance before conference...<br /> <br /> <br /> We're in the last few days before the conference begins, and for a good number of you, <br /> this will be your first code4lib. Here is some information to help you navigate through <br /> the conference craziness next week:<br /> <br /> - Social Activities&lt;insert link to SA page&gt;: There's a lot going on outside of the sessions, <br /> and this page has information about various gatherings, events, meals, etc. One activity I <br /> want to highlight is the Newcomer dinner&lt;insert link to SA page&gt; that will be on <br /> &lt;insert date of dinner&gt;. There are still a lot of great restaurants left on the list, and this <br /> is your chance to meet folks you might otherwise not get a chance to talk to at the conference. <br /> Read the guidelines on the wiki, and pick your restaurant.<br /> <br /> (Public service announcement: for those of you who have signed up for the dinner already, make <br /> sure that there's a designated leader for organizing reservations and people herding.)<br /> <br /> - Hospitality Suite: For some of the events listed on the Social Activities page, you will see <br /> the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside <br /> of sessions (or taking a break from sessions). The location of the Suite is usually announced <br /> through various means, including the wiki, IRC and Twitter.<br /> <br /> - IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag <br /> for conference related stuff. The IRC channel&lt;insert link to IRC page&gt; is #code4lib, and there <br /> will be volunteers at the conference who would be more than happy to help you with IRC.<br /> <br /> - For my last item, give the following a read:&lt;insert links to appropriate pages&gt;<br /> <br /> -- How to hack code4lib<br /> -- CodeofConduct4lib<br /> -- Zoia, #code4lib's IRC bot<br /> <br /> If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify <br /> themselves as first timers and &quot;old timers&quot; as well, if you're into classification and stuff. ;-)<br /> <br /> <br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Live Blogging ===<br /> Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.<br /> <br /> === Ask Anything===<br /> * Add to volunteer page to have a moderator or do a general call out<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit|Code4Lib 2014 planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.<br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> ===Calls for Hosting===<br /> No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.<br /> <br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013: Jan 22, 2012<br /> * 2014: January 27, 2013<br /> * 2015: <br /> <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> [[Category: Code4Lib2012]]<br /> [[Category: Code4Lib2013]]<br /> [[Category: Code4LibCon Planning]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=40761 2014-03-20T18:59:26Z

<p>Ejlynema: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Also consider using conference planning services from other entities. In 2013, Chicago used DLF services to handle registration. In 2014, NC used CONCENTRA services for all contract negotiation, fiscal activities, registration, and other conference planning and management services.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> *[[Useful information from 2012]]<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> The process works something like this:<br /> <br /> # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.<br /> # People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)<br /> #* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)<br /> # After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.<br /> # After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.<br /> <br /> ===Program Voting===<br /> Pre-conf voting may need to take place if there are more proposals than spaces.<br /> <br /> Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly<br /> explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.<br /> <br /> There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.<br /> <br /> If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.<br /> <br /> ===Guidelines===<br /> For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:<br /> * Max 2 presenters per talk (this should be checked at the proposal stage)<br /> * Max 1 talk per person<br /> * (at least) 15% talks to be decided by the program committee with &quot;diversity&quot; in mind. Diversity may be any of these (not an exhaustive list):<br /> ** first-time presenter (should be major consideration)<br /> ** gender<br /> ** visible minority<br /> ** technology/tool<br /> <br /> Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].<br /> <br /> Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.<br /> <br /> ===Schedule===<br /> While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Book Giveaway Committee ==<br /> Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.<br /> <br /> Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).<br /> <br /> Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.<br /> <br /> == T-shirt Committee ==<br /> Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.<br /> <br /> Example: [[2013 t-shirt design proposals]]<br /> <br /> Propose to add additional restrictions:<br /> * should not be a designed used previously (do we have an archive of previous designs somewhere?)<br /> * unique (cannot be bought online already)<br /> * design should include &quot;code4lib&quot; and conference year in design, city optional<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc<br /> <br /> <br /> === Emails to send out ===<br /> <br /> ==== Quick orientation email for newer folks ====<br /> <br /> Send out at least a week in advance before conference...<br /> <br /> <br /> We're in the last few days before the conference begins, and for a good number of you, <br /> this will be your first code4lib. Here is some information to help you navigate through <br /> the conference craziness next week:<br /> <br /> - Social Activities&lt;insert link to SA page&gt;: There's a lot going on outside of the sessions, <br /> and this page has information about various gatherings, events, meals, etc. One activity I <br /> want to highlight is the Newcomer dinner&lt;insert link to SA page&gt; that will be on <br /> &lt;insert date of dinner&gt;. There are still a lot of great restaurants left on the list, and this <br /> is your chance to meet folks you might otherwise not get a chance to talk to at the conference. <br /> Read the guidelines on the wiki, and pick your restaurant.<br /> <br /> (Public service announcement: for those of you who have signed up for the dinner already, make <br /> sure that there's a designated leader for organizing reservations and people herding.)<br /> <br /> - Hospitality Suite: For some of the events listed on the Social Activities page, you will see <br /> the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside <br /> of sessions (or taking a break from sessions). The location of the Suite is usually announced <br /> through various means, including the wiki, IRC and Twitter.<br /> <br /> - IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag <br /> for conference related stuff. The IRC channel&lt;insert link to IRC page&gt; is #code4lib, and there <br /> will be volunteers at the conference who would be more than happy to help you with IRC.<br /> <br /> - For my last item, give the following a read:&lt;insert links to appropriate pages&gt;<br /> <br /> -- How to hack code4lib<br /> -- CodeofConduct4lib<br /> -- Zoia, #code4lib's IRC bot<br /> <br /> If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify <br /> themselves as first timers and &quot;old timers&quot; as well, if you're into classification and stuff. ;-)<br /> <br /> <br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Live Blogging ===<br /> Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.<br /> <br /> === Ask Anything===<br /> * Add to volunteer page to have a moderator or do a general call out<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit|Code4Lib 2014 planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.<br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> ===Calls for Hosting===<br /> No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.<br /> <br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013: Jan 22, 2012<br /> * 2014: January 27, 2013<br /> * 2015: <br /> <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> [[Category: Code4Lib2012]]<br /> [[Category: Code4Lib2013]]<br /> [[Category: Code4LibCon Planning]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&diff=40760 2014-03-20T18:55:59Z

<p>Ejlynema: </p> <hr /> <div>* Apply to be a host<br /> <br /> * Consider your action plan<br /> ** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.<br /> ** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.<br /> ** Also, when you get cost estimates, don't forget to include food costs.<br /> ** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.<br /> *** make sure VPN is allowed<br /> ** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.<br /> ** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.<br /> *** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012<br /> ** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.<br /> <br /> <br /> * Get approved by the community<br /> * Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]<br /> * Invite the community to help with <br /> * Have a timeline<br /> *[[Useful information from 2012]]<br /> <br /> <br /> == Important Public Resources ==<br /> * Past calls for host sites: [http://code4lib.org/node/275 2010] - <br /> * [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]<br /> * [http://groups.google.com/group/code4libcon Code4LibCon listserv]<br /> * Sponsorship info (public)<br /> * [http://code4lib.org/logo/ Logos]<br /> <br /> == Important Private Resources ==<br /> * Code4LibCon-hostsite listserv<br /> * Budgets from previous years<br /> * Sponsorship info (private)<br /> <br /> <br /> ==Gender Diversity &amp; Minority Scholarship Committee==<br /> The scholarship committee is a self-selected group that manages the gender diversity &amp; minority scholarships. Separate groups handle AngelFund and Code4LibJapan scholarships.<br /> <br /> ===Suggestions received===<br /> * Send to a wider bunch of listservs, including for national orgs (ALA/SLA/MLA/CLA) &amp; relevant sections? &amp; student chapter<br /> <br /> ===Process===<br /> # Put out a call<br /> # Receive and coordinate applications<br /> # Distribute applications to the committee<br /> # Select awardees<br /> # Inform selected candidates<br /> # Notify unsuccessful candidates<br /> # Announce to Code4Lib main listserv and post on code4lib.org (e.g. http://code4lib.org/node/274 )<br /> # Hosts work with awardees on reimbursement, registration, etc.<br /> # Follow up with awardees after the conference -- receive report, ask for suggestions, etc.<br /> <br /> == Program Committtee==<br /> The program committee is a self-selected group that manages talk proposals and other aspects of the program.<br /> The process works something like this:<br /> <br /> # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.<br /> # People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)<br /> #* One idea that's been thrown around to help diversity is for people to self-identify as female/minority/first-timer/first-time presenter, etc. (see the Guidelines below)<br /> # After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.<br /> # After the voting closes, we talk about where to place the dividing line between accepted and declined proposals. There is a bit of negotiation between us and the host committee on scheduling depending on how many talks we want to accept and any scheduling juggling that is required.<br /> <br /> ===Program Voting===<br /> Pre-conf voting may need to take place if there are more proposals than spaces.<br /> <br /> Based on past discussions (such as the [http://serials.infomotions.com/code4lib/archive/2011/201111/thread.html pandering votes thread]), for next year, consider a notification for voters 'briefly<br /> explaining how the ballot works and to reiterate the voting criteria that's on the proposal page.<br /> <br /> There has also been discussions about whether voting should be done without names, but it was inconclusive as there are pros and cons to each.<br /> <br /> If possible, it has been suggested that talks be grouped by topic so there is more consideration by people on giving too many votes to a single topic.<br /> <br /> ===Guidelines===<br /> For 2014, you may want to make this a bit more clear on the talk proposals page, but this is what the community agreed on through mailing list discussion:<br /> * Max 2 presenters per talk (this should be checked at the proposal stage)<br /> * Max 1 talk per person<br /> * (at least) 15% talks to be decided by the program committee with &quot;diversity&quot; in mind. Diversity may be any of these (not an exhaustive list):<br /> ** first-time presenter (should be major consideration)<br /> ** gender<br /> ** visible minority<br /> ** technology/tool<br /> <br /> Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread].<br /> <br /> Based on the comments from the 2013 feedback, the program committee may also consider proposing limiting the number of talks on a particular topic or technology used (e.g. Hydra, Solr) unless the next conference host proposes to turn the conference into a multi-track conference.<br /> <br /> ===Schedule===<br /> While always posted on the website, consider putting it on lanyrd like in 2013. Worked great of adding links to sessions, which can then be copied to the website if needed.<br /> <br /> ===Talk Acceptance Letter (samples)===<br /> <br /> &lt;pre&gt;<br /> Dear &lt;&lt;first name last name&gt;&gt;,<br /> <br /> On behalf of the Code4Lib Program Planning Committee, I am pleased to <br /> notify you that your proposal, &lt;&lt;proposal title&gt;&gt; has been accepted for <br /> the Code4Lib &lt;&lt;year&gt;&gt; in &lt;&lt;location&gt;&gt;. Please reply to this message to <br /> confirm your intention to present the approved session at the Conference. <br /> If at any time in the future you need to bow out or have any program <br /> changes, please notify us immediately. You will be sent a letter of <br /> agreement soon.<br /> <br /> The schedule for the conference is here:<br /> <br /> http://code4lib.org/conference/2011/schedule<br /> <br /> You will have 20 minutes for your talk, including questions and answers.<br /> A quick transition between speakers will be necessary.<br /> <br /> It is very important that you focus your presentation on the more unique <br /> and technical aspects of your topic whenever possible. Although Code4Lib<br /> attendees come from many different work environments, they attend Code4Lib <br /> events for information technology education.<br /> <br /> Experts like you are the heart of Code4Lib. We really appreciate your contribution <br /> and look forward to working with you.<br /> <br /> Sincerely,<br /> <br /> &lt;/pre&gt;<br /> <br /> ===Talk Rejection Letter (sample)===<br /> &lt;pre&gt;<br /> I'm sorry, but your prepared talk proposal for the 2010 Code4Lib Conference in Asheville, NC did not receive enough votes to make it into the program. But here are a couple things you should know:<br /> <br /> - The field of presentations was very large (probably the largest we have had so far) and very strong, so you should not take it too hard.<br /> - Please remember that there are many additional opportunities for participating, including lightning talks (open to anyone), breakout sessions (open to anyone to suggest and/or participate), and a special &quot;Ask Anything&quot; (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event.<br /> <br /> Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.<br /> Roy<br /> &lt;/pre&gt;<br /> <br /> == Sponsorship Committee ==<br /> ===Sample Sponsorship Request Letter===<br /> As you know, Code4Lib is a group of library technologists, programmers, system administrators, web designers, and librarians. Started in 2003, the group continues to grow--with a journal, a mailing list, and an active IRC channel. Since 2005, Code4Lib has sponsored an annual conference, which has attracted programmers and librarians from around the world.<br /> <br /> Topics at past conferences have included library information systems, new directions in library research, semantic web applications, and<br /> information technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found from<br /> http://www.code4lib.org/conference/<br /> <br /> Our &lt;&gt; conference will be held in &lt;&gt; from &lt;&gt;. Be a part of this library success story by underwriting the conference!<br /> <br /> We have several sponsorship levels:<br /> <br /> &lt;&gt;<br /> I look forward to hearing from you, and can be reached at &lt;&gt;.<br /> <br /> Best,<br /> <br /> &lt;&gt;<br /> http://code4lib.org/<br /> <br /> == Book Giveaway Committee ==<br /> Responsible for contacting publishers to see if they will donate books to the conference so we can raffle them off. Take a look at [[BookRaffle]] for ideas.<br /> <br /> Please coordinate with Program committee as to when book raffle is to happen during the conference (as in part it depends on how many things there are to give away).<br /> <br /> Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary.<br /> <br /> == T-shirt Committee ==<br /> Responsible for organizing the call, vote, print, etc. for conference t-shirts. Need to coordinate with sponsorship committee for what goes on the back of the shirt.<br /> <br /> Example: [[2013 t-shirt design proposals]]<br /> <br /> Propose to add additional restrictions:<br /> * should not be a designed used previously (do we have an archive of previous designs somewhere?)<br /> * unique (cannot be bought online already)<br /> * design should include &quot;code4lib&quot; and conference year in design, city optional<br /> <br /> == Money==<br /> * [[Conference_Financial_History_At_A_Glance]]<br /> * private conlist has budget info <br /> <br /> == Shortly before the Conference ==<br /> <br /> === Keynotes ===<br /> # Contact speakers in advance to get a speaker bio, plus to ask if they need anything, arrange airport pickup, etc<br /> <br /> <br /> === Emails to send out ===<br /> <br /> ==== Quick orientation email for newer folks ====<br /> <br /> Send out at least a week in advance before conference...<br /> <br /> <br /> We're in the last few days before the conference begins, and for a good number of you, <br /> this will be your first code4lib. Here is some information to help you navigate through <br /> the conference craziness next week:<br /> <br /> - Social Activities&lt;insert link to SA page&gt;: There's a lot going on outside of the sessions, <br /> and this page has information about various gatherings, events, meals, etc. One activity I <br /> want to highlight is the Newcomer dinner&lt;insert link to SA page&gt; that will be on <br /> &lt;insert date of dinner&gt;. There are still a lot of great restaurants left on the list, and this <br /> is your chance to meet folks you might otherwise not get a chance to talk to at the conference. <br /> Read the guidelines on the wiki, and pick your restaurant.<br /> <br /> (Public service announcement: for those of you who have signed up for the dinner already, make <br /> sure that there's a designated leader for organizing reservations and people herding.)<br /> <br /> - Hospitality Suite: For some of the events listed on the Social Activities page, you will see <br /> the Hospitality Suite listed as a location. This is a place where attendees usually hang out outside <br /> of sessions (or taking a break from sessions). The location of the Suite is usually announced <br /> through various means, including the wiki, IRC and Twitter.<br /> <br /> - IRC/Twitter/etc.: Speaking of those channels, you'll find many folks using the #c4lXX hashtag <br /> for conference related stuff. The IRC channel&lt;insert link to IRC page&gt; is #code4lib, and there <br /> will be volunteers at the conference who would be more than happy to help you with IRC.<br /> <br /> - For my last item, give the following a read:&lt;insert links to appropriate pages&gt;<br /> <br /> -- How to hack code4lib<br /> -- CodeofConduct4lib<br /> -- Zoia, #code4lib's IRC bot<br /> <br /> If you have a question, ask! I'll be bringing in some badge ribbons for everyone to self-identify <br /> themselves as first timers and &quot;old timers&quot; as well, if you're into classification and stuff. ;-)<br /> <br /> <br /> <br /> === Freenode IRC connection ===<br /> Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.<br /> <br /> Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &quot;private&quot; IP ranges used for connection sharing.)<br /> <br /> Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:<br /> <br /> To: ilines@freenode.net<br /> <br /> Hello,<br /> <br /> I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. <br /> Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead <br /> to avoid running up against the connection limit. Would it be possible to raise the cap <br /> for us during the conference? Details follow.<br /> <br /> Conference: code4lib 2010 &lt; http://code4lib.org/conference/2010/ &gt;<br /> Dates: February 22-26, 2010<br /> Attendees: 250<br /> Location: Renaissance Asheville Hotel, Asheville, NC<br /> IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block<br /> <br /> We encourage in-channel participation, so we expect a high percentage of attendees to <br /> be connected at once. We'll also have two or three channel bots connected from the <br /> conference for the lobby monitors.<br /> <br /> Please let me know if you need any further information, and thanks very much for <br /> your help!<br /> <br /> Michael<br /> <br /> I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of. (Follow-up, one year later: Same experience. Immediate automated reply, but with a need to follow up with Freenode staff in the #freenode channel to get the ticket resolved.)<br /> <br /> Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.<br /> <br /> == At the Conference ==<br /> <br /> ===Keynotes===<br /> # Water at the podium<br /> # Speaker gifts<br /> # Dinner plans<br /> <br /> === Timers ===<br /> * Sit in the front of the room<br /> * Have several people<br /> * You may want to use an extra machine<br /> * Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)<br /> * Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/<br /> <br /> === Lightning Talks ===<br /> * Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )<br /> <br /> ===PreConf===<br /> # make sure projector avail for each session<br /> # whiteboards or reasonable facsimile thereof<br /> # everyone wants a power outlet<br /> <br /> === Conference ===<br /> # power - everyone would like to plug in their laptop<br /> <br /> === Video ===<br /> # live stream is awesome<br /> # join.me ??<br /> <br /> === Live Blogging ===<br /> Consider doing live blogging for 2014. You will have two people so they can switch off during each section of day.<br /> <br /> === Ask Anything===<br /> * Add to volunteer page to have a moderator or do a general call out<br /> * Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )<br /> <br /> ===Book Raffle===<br /> * (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table<br /> <br /> === Flipcharts ===<br /> Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:<br /> images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/<br /> <br /> === Hospitality Suite ===<br /> # having a few people with room keys, any of whom might need to be available to open up or close down the room at the beginning or end of the evening<br /> # making sure the mess left for cleaning staff is an appropriate mess<br /> # making sure the noise made near other hotel guests is an appropriate noise<br /> # having someone act as a point person to gather a gratuity for the housekeeping staff maintaining the suite<br /> <br /> == Suggested Timeline ==<br /> * See [[C4L2010planning]] for an example <br /> * See [https://docs.google.com/a/ncsu.edu/document/d/1Ci_aeXlUOW_1XZ9isvwXfyt-FFyO7zsBxesenbFvCPI/edit|Code4Lib 2014 planning schedule] for example, including dates for responsibilities for each volunteer committee. Note that we established schedule at the outset by counting weeks backwards from the desired conference dates.<br /> * Ideal to have program set before registration, including pre-conf<br /> ** also allows clarity for how many spots are avail for non-presenters<br /> <br /> ===Calls for Hosting===<br /> No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider having this task as the host committee, the voting committee, or perhaps the whatever committee.<br /> <br /> * 2008:<br /> * 2009:<br /> * 2010:<br /> * 2011: March 5, 2010<br /> * 2012:<br /> * 2013: Jan 22, 2012<br /> * 2014: January 27, 2013<br /> * 2015: <br /> <br /> <br /> [[Category: Code4Lib2010]]<br /> [[Category: Code4Lib2011]]<br /> [[Category: Code4Lib2012]]<br /> [[Category: Code4Lib2013]]<br /> [[Category: Code4LibCon Planning]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=40270 2014-01-27T19:35:05Z

<p>Ejlynema: </p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.<br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> <br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).<br /> <br /> '''Organizing Volunteers'''<br /> * It's helpful to have a local representative on all volunteer committees to help grease the wheels.</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_Lessons_Learned&diff=40269 2014-01-27T19:34:28Z

<p>Ejlynema: Created page with &quot;Code4Lib 2014 Conference Planning -- Lessons Learned '''T-shirts''' * Getting sizing that works for everyone is hard. * There may be some design fatigue in the community. * Cons...&quot;</p> <hr /> <div>Code4Lib 2014 Conference Planning -- Lessons Learned<br /> <br /> '''T-shirts'''<br /> * Getting sizing that works for everyone is hard.<br /> * There may be some design fatigue in the community.<br /> * Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)<br /> <br /> '''Food and Beverage'''<br /> * Coffee in unlimited quantities is valued more highly than food at breaks.<br /> <br /> '''Pre-Conferences'''<br /> * Consider a winnowing process for pre-conferences to limit them in advance of registration to the number of rooms that you have. Could either do advance voting like with talks, or say that you have x number of rooms and take the top x pre-conferences, etc. We set a 5-person registration minimum for A/V support this year, and found that all the pre-conferences met that limit (all 19 of them!) so it was not particularly useful.<br /> * Ask ahead of time to find out if pre-conf organizers are planning to open their pre-confs to non-conference attendees.<br /> <br /> '''A/V'''<br /> * When talking to sales folks, get the REAL numbers on how many attendees will fit in a space (this means WITH A/V included, which could be 15% less or more than advertised capacities).</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Main_Page&diff=40268 2014-01-27T19:29:21Z

<p>Ejlynema: /* Code4Lib 2014 Conference */</p> <hr /> <div>{|align=right<br /> |__TOC__<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 /> **&quot;How do we make code4lib a more inclusive place for newcomers? &lt;br/&gt; Or, how do we quickly indoctrinate newbies to our values and ways of doing things?&quot; <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 /> * [[Zoia or the Code4Lib IRC bot]]<br /> <br /> ==Code4Lib 2014 Conference==<br /> See also the ''[[:Category:Code4Lib2014]] category''<br /> *[http://code4lib.org/conference/2014 Summary Information]<br /> *[[Code4Lib 2014 Conference Planning Volunteers]]<br /> *[[2014 Proposals]]<br /> *[[2014 Prepared Talk Proposals]]<br /> *[[2014 preconference proposals]]<br /> *[[2014 Invited Speakers Nominations]]<br /> *[[Sponsor Logos for T-Shirt]]<br /> *[[2014 t-shirt design proposals]]<br /> *[[2014 Room and Ride Share]]<br /> *[[2014 Lessons Learned]]<br /> <br /> == Local / Regional Groups ==<br /> <br /> * [[NYC|Code4LibNYC]] - NYC and surrounding areas<br /> * [[NEC4L|New England Code4lib]] - New England<br /> * [[NL|Code4Bib]] - Dutch Code4Bib<br /> * [[MDC|Code4libMDC]] - Maryland, Washington D.C, Virginia, and surrounding areas<br /> * [http://groups.google.com/group/pnwcode4lib?hl=en PNWCode4Lib] - Pacific Northwest<br /> * [[North|code4lib North]] - Ontario and surrounding areas ''(new for Jan 2010!)''<br /> * [[Midwest|Code4Lib Midwest]] - Wherever that is...<br /> * [http://groups.google.com/group/ikr-fejlesztok/ Code4lib.hu] - Group of Hungarian library developers<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 &amp; Museums) sector.<br /> * [[GreatEastern|Code4Lib Great Eastern]] - Atlantic Provinces<br /> * [[Code4lib_Mid-Atlantic|Code4Lib Mid-Atlantic]] - Philadelphia and the Greater Tri-State Area<br /> * [[BC|Code4Lib BC]] - British Columbia ''(new in 2013)''<br /> * [[Edmonton|Code4LibYEG]] - Edmonton, Alberta ''(also new in 2013)''<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 &quot;discovery&quot; 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 /> <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 /> == Code4Lib Journal ==<br /> <br /> * [[:Category:Code4Lib Journal|Code4Lib Journal]] - information and working documents<br /> <br /> == Current topics ==<br /> <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 /> <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 /> == Earlier Conferences and events ==<br /> [[Conference Financial History At A Glance]]<br /> <br /> ===Code4Lib 2013 Conference===<br /> See also the ''[[:Category:Code4Lib2013]] category''<br /> *[http://code4lib.org/conference/2013/schedule 2013 Schedule]<br /> *[[2013 Lightning Talks Signup]]<br /> *[https://docs.google.com/document/d/1TahfqabnchZLD1opq6ILs8XCYdXkgJDsj8-WyVLNzI4/edit Breakout Session Signups] | [[2013_breakout_sessions_reports|2013 Breakout Sessions Reports]]<br /> *[[2013_committees_sign-up_page|Volunteer to help plan 2013 conference]]<br /> *[[2013_During_the_Conference_Volunteers|During the conference volunteer signup]]<br /> *[[2013 Invited Speakers Nominations]] -- nominations close Aug. 31, 2012.<br /> *[[2013 preconference proposals|2013 preconference sessions]] - try to sign up by Jan 15th<br /> *[[2013 talks proposals]] - due Friday, Nov 9<br /> *[[2013 t-shirt design proposals]] - due Monday, Dec. 31<br /> <br /> *[[2013_social_activities|Social Activities for 2013 Conference]]<br /> *[[2013_travel|Travel Advice and Getting To and From the 2013 Conference]]<br /> *[[2013_room_ride_share|2013 Conference Room and Ride Share]]<br /> *[[2013_Guide_To_Wireless| Connecting to the UIC's Wifi]]<br /> *[[2013 Twitter List| 2013 Twitter Attendee List]]<br /> <br /> * Conference hashtag: #c4l13 -- [https://docs.google.com/spreadsheet/ccc?key=0AsyivMoYhk87dFljMUZURWZMYzNzT2lwcEduUUJ6d1E#gid=113 Archive of tweets] | [http://www.flickr.com/search/?q=c4l13 Flickr photos]<br /> <br /> ===Code4Lib 2012 Conference===<br /> ''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2012 Code4lib2012 category]''<br /> <br /> * [http://code4lib.org/conference/2012/ 2012 home]<br /> * [[During_the_Conference_Volunteers|Volunteer to help at code4lib 2012]]<br /> * [[2012_committees_sign-up_page|Volunteer to help plan 2012 conference]]<br /> * [[2012_preconference_proposals|2012 Preconference Proposals]]--due Sunday, November 20<br /> * [[2012_talks_proposals|2012 Talk Proposals]]--due Sunday, November 20<br /> * [[2012_c4l2012_social_activities|Social Activities]] - ideas and sign-up<br /> * [[c4l2012_rideshare|Rideshare-Roomshare]]<br /> * [[c4l2012_t-shirtcontest|T-shirt contest]]<br /> * [[ideas_for_2012|Put your ideas for 2012 here!]]<br /> * [[C4L2012_Call_For_Host|2012 Call For Host]]<br /> * [[How To Plan A Code4LibCon]]<br /> * [http://linkd.in/unhJsR LinkedIn Event]<br /> * [[2012_twitter_list|List your Twitter handle here]]<br /> * [[2012_Lightning_Talks_Signup|Lightning Talks Signup]]<br /> * [http://irc.code4lib.org/ IRC Channel Timeline &amp; Log]<br /> * [http://www.livestream.com/code4lib Conference Livestream] (non-attendees only, please!)<br /> <br /> === Code4Lib 2011 Conference ===<br /> ''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2011 Code4lib2011 category]''<br /> <br /> * [http://code4lib.org/conference/2011 C4L2011 Home]<br /> * [[C4L2011_registration | Registration Information!]]<br /> * [[2011_committees_sign-up_page | 2011 Committees Sign-Up]] - '''Volunteer to help'''<br /> * [[How To Plan A Code4LibCon]]<br /> * [[C4L2011_social_activities|Social Activities]] - ideas &amp; sign-up<br /> * [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br /> * [http://www.facebook.com/event.php?eid=161853827200024 Facebook Event Page]<br /> * [http://events.linkedin.com/Code4Lib-2011/pub/448897 LinkedIn Event Page]<br /> &lt;!-- commenting out until later * '''[[2011 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff''' --&gt;<br /> * [[C4L2011_rideshare|Airport Ride Share and Carpooling]]<br /> * [[C4L2011_roomshare | Hotel room share]]<br /> <br /> === Code4Lib 2010 Conference ===<br /> <br /> ''See also the [http://wiki.code4lib.org/index.php/Category:Code4Lib2010 Code4lib2010 category]''<br /> * [http://code4lib.org/conference/2010/schedule Finalized schedule]<br /> * [[2010 Lightning Talks Signup]] - sign up to give a lightning talk<br /> * [[2010 Breakout Sessions]] - suggest a breakout here<br /> * '''[[2010 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff'''<br /> * [[C4L2010_social_activities|Social Activities]] - ideas &amp; sign-up<br /> * [[Committees sign-up page]] - '''Volunteer to help'''<br /> * [[C4L2011_planning_wishlist|'''Put your ideas for 2011 here!''']]<br /> * [[Asheville Airport to Hotel Van Manifest]] <br /> * [[C4L2010rideshare|General shared travel/transportation planning]]<br /> * [[C4L2010planning:RoommatesRidesEtc|Roommates, Rides, Etc]]<br /> * [[C4L2010_manning_discount|Manning Publications Discount]] - discount code (40% off) for use by attendees through Feb. 28, 2010<br /> * Thanks also to our other sponsors!<br /> * [[C4L2010planning|2010 Planning]]<br /> * [[C4L2010planning:_wishlist | 2010 Planning Wishlist]] - planning page for issues, expectations, etc. for the 2010 conference<br /> <br /> === Code4Lib 2009 Conference ===<br /> <br /> * [[BookRaffle]] - coordinate begging publishers for books to raffle off at the conference<br /> * [http://inkdroid.org/c4l2009/attendees Get FOAFed] - add your FOAF profile to the network of c4l2009 attendees<br /> * PreConferences:<br /> ** [[GIS_preconf_code4libcon2009]] - Open source GIS just like mom used to make<br /> ** [[LinkedData]] - A proposal for a linked-data code4lib2009 pre-conference<br /> ** [[LibX_Preconference]] - Proposal for a half-day pre-conference targeted at developers who wish to use the LibX 2.0 platform<br /> ** [http://code4lib.org/2009/oclc-precon OCLC Grid Services Preconference]<br /> * [[RoommatesRidesEtc]] - Find roommates for Code4Lib 2009, share rides, etc.<br /> * [[2009 Conference Buzz]] - Conference announcements and a place for code4libbers to plan stuff<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>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=40219 2014-01-07T21:08:18Z

<p>Ejlynema: /* Wifi / Electrical / IRC / Streaming Video Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please 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 hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (Manning) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> * Sarah Shealy (Packt) and general wrangling if/when needed<br /> * Shaun Ellis (Rosenfeld Media and O'Reilly eBooks)<br /> <br /> Current Status:<br /> * O'Reilly is also offering a free ebook to all attendees. This is in the form of a printed voucher that should be bundled with the t-shirt and other swag. Shaun Ellis is responsible for the printing of the vouchers.<br /> * Rosenfeld Media is shipping a number of giveaway titles directly to Tim McGeary a couple weeks before the conference.<br /> <br /> Shaun also mentioned that we have a prospectus this year that would be great to send along with our requests to the publishers. You can find it at: http://code4lib.org/files/Code4LibProspectus.pdf<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> * Joyce Chapman (State Library of NC)<br /> * Dre (NCSU)<br /> * [[User:DataGazetteer|Peter Murray]] (LYRASIS)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> * Kelly Leong (Duke)<br /> * Dre (NCSU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU) -- nominated as lead<br /> * Tim Shearer (UNC)<br /> * Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (ranti.junus@gmail.com)<br /> * Roy Tennant (OCLC)<br /> * Trevor Thornton (hellotrevorthornton@gmail.com)<br /> * Lucas Mak (makw@mail.lib.msu.edu)<br /> * [[User:DataGazetteer|Peter Murray]] (LYRASIS)<br /> * Tod Olson (tod at uchicago dot edu)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- lead<br /> * Cory Lown (NCSU)<br /> * Bohyun Kim (FIU)<br /> * Santi Thompson (University of Houston) sathompson3@uh.edu<br /> * Sarah Shealy (sarah.shealy@outlook.com)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> * Bohyun Kim<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> As of 12-18-2013 this committee has been combined with the Wifi/Electrical/IRC committee<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- lead<br /> *Josh Wilson, State Library of NC (joshwilsonnc at gmail)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> * [[User:LauraAkerman|Laura Akerman]], liblna@emory.edu<br /> <br /> == Wifi / Electrical / IRC / Streaming Video Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur, in addition the committee is responsible to work with the local hosts to figure out the requirements for video / streaming video and work to get final A/V estimates by late November 2013 to use for the final budget<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> * [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org<br /> * [[User:RileyChilds|Riley Childs]], Riley@TFSGEO.com <br /> * Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> * Jeff Campbell - UNC - CH<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_t-shirt_design_proposals&diff=40176 2014-01-03T13:08:49Z

<p>Ejlynema: /* Code4Lib 2014 T-Shirt Design Proposals */</p> <hr /> <div>= Code4Lib 2014 T-Shirt Design Proposals =<br /> <br /> Designs for the official Code4Lib 2014 conference are now being solicited! Submit your proposal by &lt;strike&gt;January 3&lt;/strike&gt; '''January 5''' for consideration! <br /> <br /> What to do:<br /> * Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.<br /> * Include your name and e-mail address with your proposal.<br /> * If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design on the Dieboldatron.<br /> * Place a horizontal rule (----) on a separate line after your submission.<br /> <br /> Design considerations:<br /> * T-shirt designs should be one-sided, single color designs suitable for screenprinting.<br /> * This year's shirt will NOT BE BLACK. We anticipate that it will be available in 3 colors: Carolina Blue (light blue), Duke blue (royal blue), and NC State red, as long as this works with the t-shirt design itself.<br /> <br /> Tedious administrivia:<br /> * All proposals posted to this wiki page before 11:59 PM EST &lt;strike&gt;January 3&lt;/strike&gt; '''January 5''' will be considered.<br /> * The winning design will be selected via community-wide voting in January.<br /> * Questions? Direct them to cdmorris22 (at) gmail (dot) com and joshwilsonnc (at) gmail (dot) com. One of us will get you an answer.<br /> <br /> == Sample submission == <br /> <br /> Joe Ouroboros, joe (at) loopback.edu :<br /> <br /> [[Image:Reset-200.png]]<br /> <br /> This is my awesome design. It'll win one of these years.<br /> <br /> ----<br /> <br /> == Submissions ==<br /> <br /> List your submissions below!<br /> <br /> ----<br /> <br /> Jeffrey Sabol jeffrey.sabol@cui.edu:<br /> <br /> [[File:code4lib_tshirt.jpeg]]<br /> <br /> White ink on a dark color T-shirt OR Black ink on a light color shirt <br /> <br /> ----<br /> <br /> Charlie Morris cdmorris22 at gmail dot com<br /> <br /> [[File:C4l2014_piggy-_charlie_morris.png]]<br /> <br /> [http://thenounproject.com/term/pig/5271/ Pig] designed by aLf from the Noun Project. <br /> <br /> ----</div>

Ejlynema https://wiki.code4lib.org/index.php?title=2014_t-shirt_design_proposals&diff=40123 2013-12-10T14:13:37Z

<p>Ejlynema: /* Code4Lib 2014 T-Shirt Design Proposals */</p> <hr /> <div>= Code4Lib 2014 T-Shirt Design Proposals =<br /> <br /> Designs for the official Code4Lib 2014 conference are now being solicited! Submit your proposal by '''January 3''' for consideration! <br /> <br /> What to do:<br /> * Post an image file of your print-ready proposal by editing this wiki page. You can host the image yourself or use the [[Special:Upload|Upload file]] feature of the wiki. If your print-ready document is different from your displayed image, include a link to the print-ready file.<br /> * Include your name and e-mail address with your proposal.<br /> * If you want, you can add a line or two of explanatory text, color specifications, etc., which will be included with your design on the Dieboldatron.<br /> * Place a horizontal rule (----) on a separate line after your submission.<br /> <br /> Design considerations:<br /> * T-shirt designs should be one-sided, single color designs suitable for screenprinting.<br /> * This year's shirt color is TBD. We are working with vendors to determine cost-effective options. Note that we anticipate that the t-shirts will NOT BE BLACK.<br /> <br /> Tedious administrivia:<br /> * All proposals posted to this wiki page before 11:59 PM EST January 3 will be considered.<br /> * The winning design will be selected via community-wide voting in January.<br /> * Questions? Direct them to cdmorris22 (at) gmail (dot) com and joshwilsonnc (at) gmail (dot) com. One of us will get you an answer.<br /> <br /> == Sample submission == <br /> <br /> Joe Ouroboros, joe (at) loopback.edu :<br /> <br /> [[Image:Reset-200.png]]<br /> <br /> This is my awesome design. It'll win one of these years.<br /> <br /> ----<br /> <br /> == Submissions ==<br /> <br /> List your submissions below!<br /> <br /> ----<br /> <br /> Jeffrey Sabol jeffrey.sabol@cui.edu:<br /> <br /> [[File:code4lib_tshirt.jpeg]]<br /> <br /> White ink on a black T-shirt<br /> <br /> ----</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39477 2013-08-22T15:37:23Z

<p>Ejlynema: /* Code4Lib 2014 Committees */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please 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 hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> The Code42014 Conference Committee meets bi-weekly on Tuesdays at 11am EDT. If you would like to join the calls or have an agenda item, email one or both of the co-Leads: Emily Lynema (NCSU) and Tim McGeary (UNC).<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> * [[User:DataGazetteer|Peter Murray]] (LYRASIS)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> * Kelly Leong (Duke)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU) -- nominated as lead<br /> * Tim Shearer (UNC)<br /> * Kevin Reiss (Princeton University) -- kr2 [at] princeton dot edu<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (ranti.junus@gmail.com)<br /> * Roy Tennant (OCLC)<br /> * Trevor Thornton (hellotrevorthornton@gmail.com)<br /> * Lucas Mak (makw@mail.lib.msu.edu)<br /> * [[User:DataGazetteer|Peter Murray]] (LYRASIS)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- lead<br /> * Cory Lown (NCSU)<br /> * Bohyun Kim (FIU)<br /> * Santi Thompson (University of Houston) sathompson3@uh.edu<br /> * Sarah Shealy (sarah.shealy@outlook.com)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> * Bohyun Kim<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (UNC, Lead, tim.mcgeary@unc.edu)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- lead<br /> *Josh Wilson, State Library of NC (joshwilsonnc at gmail)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> * [[User:DataGazetteer|Peter Murray]], Peter.Murray@lyrasis.org<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39380 2013-07-31T12:26:37Z

<p>Ejlynema: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU) -- nominated as lead<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> * Roy Tennant (OCLC)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- lead<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- lead<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39379 2013-07-31T12:26:20Z

<p>Ejlynema: /* Scholarships Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU) -- nominated as lead<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> * Roy Tennant (OCLC)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- lead<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- nominated as lead<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39372 2013-07-30T20:49:37Z

<p>Ejlynema: /* Pre-conference Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU) -- nominated as lead<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- nominated as lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- nominated as lead<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- nominated as lead<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39371 2013-07-30T20:49:03Z

<p>Ejlynema: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- nominated as lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- nominated as lead<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU) -- nominated as lead<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39370 2013-07-30T20:48:42Z

<p>Ejlynema: /* Scholarships Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- nominated as lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU) -- nominated as lead<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39369 2013-07-30T20:48:26Z

<p>Ejlynema: /* Program Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com) -- nominated as lead<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39368 2013-07-30T20:48:01Z

<p>Ejlynema: /* Keynote Speakers Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU) -- lead<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39367 2013-07-30T20:47:47Z

<p>Ejlynema: /* Book Give-Away Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling (nominated as lead)<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39365 2013-07-30T20:26:50Z

<p>Ejlynema: /* Code4Lib 2014 Committees */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. It has been shared with code4libcon and code4lib2014 google groups.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39364 2013-07-30T19:01:04Z

<p>Ejlynema: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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 /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39363 2013-07-30T19:00:30Z

<p>Ejlynema: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Obtain user sizes as part of registration -- January 13, 2014 - February 14, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39362 2013-07-30T19:00:20Z

<p>Ejlynema: /* T-Shirt Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> Call for T-shirt designs - December 2, 2014 - January 3, 2014&lt;br /&gt;<br /> Voting on T-shirt designs - January 13, 2014 - January 24, 2014&lt;br /&gt;<br /> Obtain user sizes as part of registration -- January 13, 2014 - February 14, 2014&lt;br /&gt;<br /> Get bids based on sizes and design - January 27, 2014 - February 14, 2014&lt;br /&gt;<br /> Order t-shirts by February 17, 2014<br /> <br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39361 2013-07-30T18:59:17Z

<p>Ejlynema: /* Streaming Video Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> Work with local team to get solid A/V estimates by late November 2013 to use for final budget.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39360 2013-07-30T18:57:33Z

<p>Ejlynema: /* Program Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft of program schedule verified with Keynote Committee (# keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39359 2013-07-30T15:57:33Z

<p>Ejlynema: /* Code4Lib 2014 Committees */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> A Code4Lib 2014 Google Calendar is available with all proposed deadlines if you would like to add it to your personal calendar. <br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft (keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39358 2013-07-30T15:49:52Z

<p>Ejlynema: /* Scholarships Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft (keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39357 2013-07-30T15:49:42Z

<p>Ejlynema: /* Scholarships Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft (keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> Call for applicants -- November 18, 2013 - December 13, 2013&lt;br /&gt;<br /> Determine winners -- December 14, 2014 - January 5, 2014&lt;br /&gt;<br /> Notify winners -- January 6, 2014 (must be before registration)<br /> <br /> <br /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39356 2013-07-30T15:48:05Z

<p>Ejlynema: /* Onsite Volunteer Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference. Could be a help to the program committee to solicit MCs, timers, mike runners (if needed), IRC volunteers, registration helpers (if needed), etc.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft (keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39355 2013-07-30T15:47:05Z

<p>Ejlynema: /* Program Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <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.<br /> <br /> Call for talk proposals -- October 14 - November 8, 2013&lt;br /&gt;<br /> First draft (keynotes) - November 15, 2013&lt;br /&gt;<br /> Voting on talks -- November 18, 203 - December 6, 2013&lt;br /&gt;<br /> Full program draft (talks vs. keynotes vs. breakouts vs. lightning talks) - early December, say December 9, 2013&lt;br /&gt;<br /> Notify accepted talk proposers -- complete by January 3, 2014 (or earlier!)&lt;br /&gt;<br /> Post final program schedule with talks - January 13, 2014<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39354 2013-07-30T15:33:05Z

<p>Ejlynema: /* Pre-conference Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014&lt;br /&gt;<br /> Send rosters to pre-conf organizers -- by February 21, 2014<br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39353 2013-07-30T15:32:08Z

<p>Ejlynema: /* Pre-conference Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> Call for pre-conf proposals -- October 14, 2013&lt;br /&gt;<br /> Deadline for pre-conf proposals -- December 6, 2013 &lt;br /&gt;<br /> Finalize pre-confs before registration opens -- January 3, 2014<br /> <br /> <br /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39352 2013-07-30T15:30:15Z

<p>Ejlynema: /* Keynote Speakers Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013&lt;br /&gt;<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013&lt;br /&gt;<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39351 2013-07-30T15:29:20Z

<p>Ejlynema: /* Keynote Speakers Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> Call for Keynote Speaker nominations - August 5, 2013 - August 30, 2013<br /> Keynote speaker voting - September 9, 2013 - September 20, 2013<br /> Have speakers finalized by November 15, 2013<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39350 2013-07-30T15:28:32Z

<p>Ejlynema: /* Book Give-Away Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> Need about 2 months to get books shipped to the conference location. So, efforts should aim to wrap up by say January 20, 2014.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39310 2013-07-24T13:05:36Z

<p>Ejlynema: /* Streaming Video Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> * Jason Casden (NCSU)<br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Bret Davidson (NCSU)<br /> * Jeff Campbell (UNC)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> * Yan Wang (NCCU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * Tom Johnson (Johnson.tom@gmail.com)<br /> * Kevin Beswick (NCSU)<br /> * Ranti Junus (MSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> * Cory Lown (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> * Greg Klaiber - Media Resources Center, UNC Libraries, (klaiberg AT email DOT unc DOT edu)<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> * Ranti Junus<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema https://wiki.code4lib.org/index.php?title=Code4Lib_2014_Conference_Planning_Volunteers&diff=39279 2013-06-11T17:44:42Z

<p>Ejlynema: /* Program Committee */</p> <hr /> <div>= Code4Lib 2014 Committees =<br /> <br /> If you are interested in helping out with a particular part of the Code4Lib 2014 conference, create an account on this wiki and sign-up for one or more of the groups below (called 'committees' for lack of a better term). Each committee should select a committee lead that will coordinate the activities of the committee and its work with the hosting site. Discussions of a non-sensitive nature should take place on the Code4LibCon mailing list for transparency and future reference. Please feel free to improve the summary statements for each of the committees.<br /> <br /> We hope to include at least one local person on each committee.<br /> <br /> == Book Give-Away Committee ==<br /> <br /> This committee solicits books and other prizes to be given away in raffles during the conference. This committee is responsible for identifying some means of performing the actual raffle (aka, a random picker app or other tool for selecting winners). Drawing names out of a hat could be low-tech entertaining.<br /> <br /> * Kevin S. Clarke (O'Reilly) and general wrangling<br /> * Michael B. Klein (Pragmatic) and winner-picker app<br /> <br /> == Keynote Speakers Committee ==<br /> <br /> This committee plans who to invite for the keynote speakers. They gather possibilities (including soliciting from the community), organize voting, and work with the speakers to arrange their travel.<br /> <br /> * Jason Casden (NCSU)<br /> <br /> == Onsite Volunteer Committee ==<br /> <br /> This committee solicits volunteers to do whatever tasks are needed in person at the conference.<br /> <br /> * Kevin S. Clarke<br /> * Kevin Beswick (NCSU)<br /> <br /> == Pre-conference Committee ==<br /> <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 /> * Adam Constabaris (NCSU)<br /> * Tim Shearer (UNC)<br /> <br /> == Program Committee ==<br /> <br /> This committee plans the structure of the program, arranges the voting on presentations, etc. This includes soliciting both pre-conferences and regular talks. These folks will also manage the flow of the program at the conference -- introducing speakers or soliciting other volunteers to MC.<br /> <br /> * head wrangler still needed!<br /> * Kevin Beswick (NCSU)<br /> <br /> == Scholarships Committee ==<br /> <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 /> * Jason Ronallo (NCSU)<br /> <br /> == Social Activities Committee ==<br /> <br /> The committee plans, proposes, and organizes the evening activities.<br /> <br /> * Jason Raitz<br /> * Rosalyn Metz<br /> * Dre<br /> * Becky Yoose<br /> <br /> == Sponsorships Committee ==<br /> <br /> This committee organizes the sponsorship activities. For 2014, this responsibility will include evaluating new levels of sponsorship that provide new types of benefits to sponsors (ex: vendor tables in the conference area, handouts / flyers, etc.). Usually it includes people within the Code4Lib community who think their institution or company might be interested in sponsoring the conference. These folks may not be the decision makers at the sponsors, but they are Code4Lib's contacts.<br /> <br /> * Tim McGeary (lead worrier)<br /> * Roy Tennant (OCLC)<br /> * Shaun Ellis (shaune@princeton.edu)<br /> * Robert H. McDonald (Indiana)<br /> * Sean Chen (Duke)<br /> * Thomas Dowling (Wake Forest)<br /> * Will Sexton (Duke)<br /> * Jeff Campbell (UNC-CH)<br /> * Brett Bonfield (Collingswood Public)<br /> <br /> == Streaming Video Committee ==<br /> <br /> This committee is responsible for working with local hosts to figure out what resources are available to enable video / streaming video for the conference.<br /> <br /> - Francis Kayiwa<br /> <br /> == T-Shirt Committee ==<br /> <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.<br /> <br /> *Charlie Morris (NCSU)<br /> <br /> == Voting Activities Committee ==<br /> <br /> This committee organizes the voting process and works with the other committees that involve voting (keynote, program, T-shirt) to ensure a relatively smooth process.<br /> <br /> *Adam Constabaris (NCSU)<br /> <br /> == Whatever Committee ==<br /> <br /> This committee does whatever the organizers can't talk anyone else into doing.<br /> <br /> * Francis Kayiwa<br /> * Kevin S. Clarke<br /> * Dre<br /> <br /> == Wifi / Electrical / IRC Committee==<br /> <br /> This committee is responsible for working with local planners to ensure that wifi will be able to support the needs of the code4lib community, figuring out how much electrical will be needed and ensuring it is available, and making sure that the IRC will run smoothly at the conference. These folks may be called on during the conference to help CONCENTRA remedy problems that occur.<br /> <br /> * [[User:highermath|Cary Gordon]], cgordon@chillco.com<br /> <br /> This is a newly proposed committee.<br /> <br /> = Documentation =<br /> To help with documention, no need to sign up, just start editing.<br /> * [[How To Plan A Code4LibCon]]<br /> <br /> == Documentation Interest Group ==<br /> Promote ongoing documentation efforts.<br /> <br /> [[Category: Code4Lib2014]]</div>

Ejlynema