2017 Lessons Learned
From Code4Lib
Contents
- 1 Code4Lib 2017 Lessons Learned
- 1.1 Venue planning and negotiation
- 1.2 Organizing Volunteers
- 1.3 Program & Keynotes
- 1.4 Pre-conferences
- 1.5 Sponsorships
- 1.6 Registration/Attendance
- 1.7 T-shirts / Swag
- 1.8 Food/Beverage
- 1.9 IRC
- 1.10 Scholarships
- 1.11 Registration/Sign-in (during conference)
- 1.12 Audio/Video
- 1.13 Child Care
- 1.14 Signage
- 1.15 Ideas!
Code4Lib 2017 Lessons Learned
Venue planning and negotiation
- Coming soon.
Organizing Volunteers
- Coming soon.
Program & Keynotes
- The keynote voting period was WAY too short. A week does not give people enough time to read up and do research on nominees they might want to vote for. In past years voting was up for much longer. I understand that the organizers are short on time, but any deviation from the norm should be emphasized and there should at least be a reminder announcement as we approach the deadline. I am somewhat involved with the website committee, so I imagine others that are less involved probably were also disappointed.
Pre-conferences
- Coming soon.
Sponsorships
- Coming soon.
Registration/Attendance
- Coming soon.
T-shirts / Swag
- Coming soon.
Food/Beverage
- Coming soon.
IRC
- Coming soon.
Scholarships
- Coming soon.
Registration/Sign-in (during conference)
- Coming soon.
Audio/Video
- Coming soon.
Child Care
- Coming soon.
Signage
- Coming soon.
Ideas!
- We need a communications committee, perhaps with a website subcommittee and an emails/social-media subcommittee. Draft email templates for each announcement (and reminder emails for each), specify stakeholders, and suggested send dates/windows. No more communication fails.
