2017 Lessons Learned - Revision history

Meta cat: added documentation for Scholarship Cmte

2017-04-19T19:51:30Z

added documentation for Scholarship Cmte

2017-03-09T19:41:19Z

add section for accesibility

2017-03-09T19:40:26Z

‎Ideas!

2017-03-09T19:39:48Z

‎Ideas!: google slides is not yet perfect

2017-03-06T04:04:01Z

‎Ideas!

2017-03-03T17:26:21Z

add website section

2017-03-03T17:20:11Z

‎T-shirts / Swag

2017-03-03T17:15:47Z

‎Sponsorships

2016-12-15T21:45:09Z

‎Program & Keynotes

2016-12-14T01:42:09Z

‎Voting

@@ Line 54: / Line 54: @@
 === Scholarships ===
-* Coming soon.
+* The schedule used for the 2017 conference, with links to templates for announcements and communication with applicants can be found at <https://docs.google.com/document/d/1nPBfP85KP7NzMrM41IwOZdigVzcXiP4NYCivKKLkeAk/edit>
 === Registration/Sign-in (during conference) ===

@@ Line 31: / Line 31: @@
 ** accompanying the invoice with a link to a form requesting upload of the logos
 ** seek out the logo from any press and marketing materials they have online and, when confirming the sponsorship and invoicing it, suggest use of it as a default unless they have a different version to provide. (This may not help, though, for sponsors from whom we need print-quality logos)
 === Registration/Attendance ===

@@ Line 77: / Line 77: @@
 * Draft email templates for each announcement (and reminder emails for each), specify stakeholders, and suggested send dates/windows.
 * '''No more communication fails.'''
-* As it's happened in the past, we should make sure that the registration process let us know if any minors register for the conference.
+* As it's happened in the past, we should make sure that the registration process lets us know if any minors register for the conference.
 * Google Slides is handy for speakers to use and as a mechanism for sharing slides, but getting presentation mode up and running is a bit awkward. Assuming that by the next time around it hasn't evolved to the point where presentation mode is as straightforward to invoke as (say) PowerPoint. Not a big deal, but if via practicing or technical tweaks the transitions can be made smoother, that would be groovy.
 [[Category:Code4Lib2017]]

@@ Line 78: / Line 78: @@
 * '''No more communication fails.'''
 * As it's happened in the past, we should make sure that the registration process let us know if any minors register for the conference.
 [[Category:Code4Lib2017]]

@@ Line 77: / Line 77: @@
 * Draft email templates for each announcement (and reminder emails for each), specify stakeholders, and suggested send dates/windows.
 * '''No more communication fails.'''
 [[Category:Code4Lib2017]]

← Older revision		Revision as of 17:26, 3 March 2017
Line 67:		Line 67:

	* Coming soon.		* Coming soon.
		+
		+	=== Website ===
		+
		+	* Any images used on the website for branding the conference should either have an appropriate CC license or permissions should be secured in advance for using such images in other contexts, including on the main Code4Lib website, printed materials, and on-site displays.

	=== Ideas! ===		=== Ideas! ===

@@ Line 38: / Line 38: @@
 === T-shirts / Swag ===
-* Coming soon.
+* It might be helpful to secure in advance permission to use the t-shirt design winner (and other submissions) in other specific contexts, including the conference website, the main Code4Lib website, signage, and displays and screensavers at the conference.
 === Food/Beverage ===

@@ Line 27: / Line 27: @@
 === Sponsorships ===
-* Coming soon.
+* When a sponsor commits, we should ask them exactly how they would like to be named in acknowledgements and sponsor listings. One 2017 sponsor ended up wanting their sponsorship to be listed in the name of one of their projects.
 === Registration/Attendance ===

@@ Line 14: / Line 14: @@
 * 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.
 * Workshop and program committees seem to work independently generally and don't explicitly coordinate their deadlines. I think they end up around the same time due to the timeline but there's obviously some variation.
 === Pre-conferences ===

@@ Line 20: / Line 20: @@
 === Voting ===
-* Get voting technology squared away and ready to spin up before the Call For Proposals start
+# Get voting technology squared away and ready to spin up before the Call For Proposals start
-* If descriptions are on a separate page from the actual voting form, double (triple?) check that the two lists match up before pushing out the voting links.
+# If descriptions are on a separate page from the actual voting form, double (triple?) check that the two lists match up before pushing out the voting links.
-* Use Dieboldatron to avoid descriptions on a separate page
+# Use Dieboldatron to address 1 & 2.
 === Sponsorships ===