Difference between revisions of "2017 Lessons Learned"

From Code4Lib
Jump to: navigation, search
(Program & Keynotes)
(Ideas!)
Line 59: Line 59:
 
=== Ideas! ===
 
=== Ideas! ===
  
* Coming soon.
+
* 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.
 
+
 
[[Category:Code4Lib2017]]
 
[[Category:Code4Lib2017]]

Revision as of 14:12, 27 October 2016

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.