88
edits
Changes
no edit summary
* Host local mirror of #code4lib IRC - http://www.tummy.com/Community/Articles/pycon2007-network/
* Rent G3 line for dedicated access for speakers (?)
* Have a contingency aircard so at least speakers can go online (?)
* Hook up to UNCA's Internet connection from the hotel (?)
* Signup sheet for nightly dinner activities
* code4lib brew for the hospitality suite
* code4lib revue?
=== Sponsorship ===
* Potential sponsor and contact list
=== Choosing speakers ===
* Ask people to write why they nominated keynote speakers
* Can we get more gender diversity of keynote & 20 minute talks? (Is this important to us?)
* Do we want to limit the number of speakers from any one organization?
* Do we want categories when voting?
* Voting needs 2 categories: geekiness and vote preference. (In 2008 the sum of these was the total IIRC)
=== Choosing 2011 venue ===
* Announce the process early in the conference so that people can get set up with logins
* Reminder during the last day of voting
=== Integration with IRC ===
* Consider suggestions from http://pistachioconsulting.com/twitter-presentations/ regarding integration with backchannel.
** e.g. offer speakers help monitoring the channel ('an ombudsman for the audience')
* Advice from dev8 via BenO:
** @davetaz setup projection/feed of the twittered #dev8d tags + @andymcg set up a netvibe channel to follow the tags elsewhere @jschneider Twitter feed screen in bkgd of these photos: http://is.gd/jOwW http://is.gd/jOxd & see @jvvw review of event: http://is.gd/jOxy
* Make it easier for people to find IRC
** "code4lib station" with signup info and help?
* Not everybody multistreams. Would multiple rooms help (reduce volume)? Or...?
=== Video ===
* Sync the timecode in the video with the IRC logs
=== Lightning Talks Do's and Don'ts ===
* Have an MC/cat herder lined up in advance
* Don't have one entity do two LTs back to back
* Ask those who've already spoken to "go last" (e.g. only present if there's time)-- "share the air"
* Create a LT do's and dont's page in the conference webspace
** link to existing LT advice