Changes

== General Timeline Process ==* Apply to be a host* Consider your action plan; see also the page on [http://code4lib.org/conference/hosting Conference Hosting] at [http://code4lib.org code4lib.org]** '''Identify your venues ''' for both the conference and the hotel (if different). This is critical, as you'll want to get Get some cost estimates from each. When we hosted in Make sure the hotel will give you a room block.*** 2006/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 *** 2016/Portland, and : we held everything in a single hotel, and we had to acquire 2x the amount of sponsorship than what appears to be normal.** '''Prepare a sample / generalized budget'''*** 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.*** Get data from previous years to estimate minimums and maximums, and fill in as much as you can ahead of time.*** 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.*** Also, when you get cost estimates, don't forget to include food costs.** WIRELESS* 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.*** make sure VPN is allowed'''Consider using a conference planner'''*** 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.*** 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.** 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.*** prepare the hotel for deluge via web when announcement is made about hotel registration available. We overwhelmed the Seattle hotel in 2012** 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.  

* Invite the community to help with join committees

* Local Planning Committee* Accessibility Committee* [[BookGiveawayCommittee|Book Give-AwayGiveaway Committee]]

* PreconferencePre-conference* [[ProgramCommittee|ProgramCommittee]]

* [[SponsorshipCommittee|SponsorshipCommittee]]

* [[T-ShirtCommittee|T-ShirtCommittee]]* [[Voting|Voting]]

* Wifi/Electrical/IRC

 == Program Committtee=Budgeting =The program committee is a self-selected group that manages talk proposals and other aspects of the program.The process works something like this: # Draft the call for proposals (searching the mailing list archives should provide some good templates) and send it out.# People put their proposals on the Code4Lib wiki (see the [[2013 talks proposals]] page as a template)#* 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)# After the proposal period ends, contact Ross Singer (rsinger) to get voting set up.# 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. ===Program Voting===Pre-conf voting may need to take place if there are more proposals than spaces. 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 'brieflyexplaining how the ballot works and to reiterate the voting criteria that's on the proposal page. 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. 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. ===Guidelines===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:* Max 2 presenters per talk (this should be checked at the proposal stage)* Max 1 talk per person* (at least) 15% talks to be decided by the program committee with "diversity" in mind. Diversity may be any of these (not an exhaustive list):** first-time presenter (should be major consideration)** gender** visible minority** technology/tool Based on [http://serials.infomotions.com/code4lib/archive/2012/201211/thread.html Proposed Changes thread]. 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. ===Schedule===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. ===Keynoter logistics=== See [[Keynote Committee Duties]]. ===Talk Acceptance Letter (samples)=== <pre>Dear <<first name last name>>, On behalf of the Code4Lib Program Planning Committee, I am pleased to notify you that your proposal, <<proposal title>> has been accepted for the Code4Lib <<year>> in <<location>>. Please reply to this message to confirm your intention to present the approved session at the Conference. If at any time in the future you need to bow out or have any program changes, please notify us immediately. You will be sent a letter of agreement soon. The schedule for the conference is here:  http://code4lib.org/conference/2011/schedule You will have 20 minutes for your talk, including questions and answers.A quick transition between speakers will be necessary. It is very important that you focus your presentation on the more unique and technical aspects of your topic whenever possible. Although Code4Libattendees come from many different work environments, they attend Code4Lib events for information technology education. Experts like you are the heart of Code4Lib. We really appreciate your contribution and look forward to working with you. Sincerely, </pre> ===Talk Rejection Letter (sample)===<pre>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: - 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.- 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 "Ask Anything" (or reply anything) open session. Also, the evening socializing opportunities are considered some of the most rewarding times of the event. Again, my condolences on not having your talk proposal accepted, but I hope we still see you in Asheville, NC in February.Roy</pre> == Sponsorship Committee =====Sample Sponsorship Request Letter===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. Topics at past conferences have included library information systems, new directions in library research, semantic web applications, andinformation technology standards, among many others. More details about the conference, including schedules of previous conferences, can be found fromhttp://www.code4lib.org/conference/ Our <> conference will be held in <> from <>. Be a part of this library success story by underwriting the conference! We have several sponsorship levels: <>I look forward to hearing from you, and can be reached at <>. Best, <>http://code4lib.org/ == Book Giveaway Committee ==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. 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). Will also need to coordinate with sponsorship/host committee about adding logos and what not to the sponsorship list if necessary. == T-shirt Committee ==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. Example: [[2013 t-shirt design proposals]] Propose to add additional restrictions:* should not be a designed used previously (do we have an archive of previous designs somewhere?)* unique (cannot be bought online already)* design should include "code4lib" and conference year in design, city optional == Money==

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

# power - everyone would like to plug in their laptop(and possibly their phone)

# live stream is awesomeVideos are streamed at https://youtube.com/code4lib# joinPresenters can opt out of having their likeness recorded and streamed. They may not opt out of having their voice and presentation (i.e. slides, etc.) recorded and streamed.me ??# YouTube LivePresenters must not use unlicensed music in their presentation. Likewise, youtubeunlicensed music must not be used between presentations.com# Video must be able to work with the house A/code4libV crew and set up the day before the main con begins.# Lighting must be provided for the speakers.

No one has claimed responsibility for putting out the call and setting the deadline, so for 2014 planning, consider . Consider having this task as the host committee, the voting committee, or perhaps the whatever committee.

* 2008:{| class="wikitable"* 2009:! Year of proposal! Text of call! Call issued! Deadline for submission! Weeks to submit! Voting start! Voting end! Weeks to vote! Announcement|-* |2010|[https://listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;tBeDRg;201002051132430800 Code4Lib 2011 Hosting Proposals Solicited]* |5 Feb|5 Mar|4 weeks|||||-|2011|[https: March 5//listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;R8d%2FBw;20101210153936%2B0000 Code4Lib 2012 Call for Host Proposals]|10 Dec, 2010* |23 Jan (Sun)|6 weeks + 3 days|25 Jan (Tue)|9 Feb (3rd day of conf)|2 weeks + 2 days|10 Feb (last day of conf)|-|2012:* 2013|[https: Jan 22//listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;9k0n8A;20111201184554%2B0000 Code4Lib 2013 Call for Host Proposals]|1 Dec, 20122011|22 Jan (Sun)|7 weeks + 4 days|25 Jan (Wed)|8 Feb (3rd day of conf)|2 weeks + 1 day|9 Feb (last day of conf)|-|2013||||||||15 April?|-* |2014|[https: January //listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;f5d2e9cb.1401 Call for proposals to host Code4Lib Conference in 2015]|29 Jan|12 Mar (Wed)|6 weeks + 1 day|14 Mar (Fri)|26 Mar|1 week + 6 days|27, 2013Mar (Thursday; last day of conf)* |-|2015|[https: January 29, 2014//listserv.nd.edu/cgi-bin/wa?A2=CODE4LIB;1b38757a.1501 Call for proposals to host Code4Lib Conference in 2016]* |8 Jan|20 Feb (Fri)|6 weeks + 2 days|23 Feb (Mon)|6 Mar|1 week + 5 days|9 Mar (Mon)|-|2016: ||19 Jan (Tue)|1 Mar (Tue)|6 weeks|3 Mar (Thu)|15 Mar (Tue)|1 week + 5 days (note conf is Mar 7-10)|16 Mar (Fri)|}