Changes

Jump to: navigation, search

How To Plan A Code4LibCon

2,034 bytes added, 01:48, 14 December 2016
Committee List
== General Process ==
* Apply to be a host; see also the page on [http://code4lib.org/conference/hosting Conference Hosting] at [http://code4lib.org code4lib.org]
** '''Identify venues''' for both the conference and the hotel (if different). Get some cost estimates from each. 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.
*** 2016/Portland: 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.
*** Also, when you get cost estimates, don't forget to include food costs.
*** Wireless: 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.
*** 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.
* Get approved by the community
* Find a hotel, negotiate and sign a contract with them. [[Sample RFI]]
* Have a timeline
*[[Useful information from 2012]]
 
== Important Public Resources ==
* [http://code4lib.org/logo/ Logos]
* [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.
* [[Code4Lib Conference Lessons Learned]]
== Important Private Resources ==
== Committee List ==
* Local Planning Committee
* Accessibility Committee
* [[BookGiveawayCommittee|Book Giveaway Committee]]
* Childcare
* Keynote
* Onsite Volunteer
* PreconferencePre-conference
* [[ProgramCommittee|Program Committee]]
* [[ScholarshipCommittee|Gender Diversity & Minority Scholarship Committee]]
* Slack/IRC
* Social Activities
* [[SponsorshipCommittee|Sponsorship Committee]]
* Streaming Video
* [[T-ShirtCommittee|T-Shirt Committee]]
* [[Voting|Voting]]
* Whatever
* Wifi/Electrical/IRC
* Duty Officers
=== Wireless ===
* make sure VPN is allowed
 
TODO: put actual concurrent connections and bandwidth usage data numbers in a chart here. Note when problems were occurring to give context on whether these numbers were sufficient of insufficient.
Aspiration Tech (an org doing unconference facilitation) has developed a [http://facilitation.aspirationtech.org/index.php?title=Logistics:Wireless_Best_Practices great list for assessing and negotiating event wifi].
 
=== Policies ===
A record of [[Conference_Policies]] of all kinds!
== Shortly before the Conference ==
=== Conference ===
# power - everyone would like to plug in their laptop(and possibly their phone)
# IRC Monitor for podium during speaker changes?
* Consider different colored lanyards to articulate personal photography preferences.
** Portland/2015 had color-coded lanyards:
*** Green = it's ok to take my picture
*** Yellow = please ask before taking my picture
*** Red = don't take my picture
=== Video ===
===Calls for Hosting===
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)|}
== Some Suggested Readings ==
255
edits

Navigation menu