Changes

Jump to: navigation, search

Code4Lib Conference Lessons Learned

593 bytes added, 14:29, 19 November 2015
Ideas!
* To keep registration costs low, it is critical the Sponsorship Committee raise a minimum of $50,000 per year. [This really depends on the overall venue costs. If the conference is hosted on a college campus, the costs tend to be much lower, and therefore the amount of sponsorship needed is much lower - jaf]
* The [http://code4lib.org/node/487|Code4Lib2014 Sponsorship Prospectus] was a '''significant''' tool in raising money in 2014.
* It is the Sponsorship Committee's responsibility to gather all sponsor logos. Request both color and black & white Vector formats (eps, svg) as they will yeild the best results. Label all files appropriately and put in a place that can be easily shared with the t-shirt committee.
=== Registration/Attendance ===
* There may be some design fatigue in the community.
* Consider some other type of swag that doesn't involve sizing difficulties -- like re-usable coffee mugs (then attendees could use them all conference!)
* Graphics Sponsor logos should be gathered by the Sponsorship Committee as they are the ones "selling" the logo spots on the t-shirts and have sponsor contacts* When putting out a call for graphics/designs, ensure that the formats submitted are usable in production (e.g. vector formats).
=== Food/Beverage ===
* Add a Code4Lib logo to the podium
* 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.
* Use [http://www.allourideas.org/ All Our Ideas] as a way to gather ideas and get community feedback. Great for Ask Anything, Q&A, BOF, Unconferency-planning, voting, etc.
118
edits

Navigation menu