Differences between revisions 9 and 30 (spanning 21 versions)
Revision 9 as of 2008-03-18 22:54:39
Size: 2385
Editor: hsd-lap68
Comment:
Revision 30 as of 2008-03-26 15:47:03
Size: 8195
Editor: cpe-66-1-159-102
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
General
-------

* Better/more signage.
Line 24: Line 29:

* Be more specific that talks should be more than a sales or recruiting pitch. Tell us about what you're doing!
* Point people to example lightning talk videos, once we get them posted.
* Post a list of the lightning talks once the signup sheet has been taken down; people were unsure if they
  were accepted or not, and asked at the reg. desk.
* Use "Huge Applause" sign video layover to help speakers know they're 5 minutes is up.
Line 31: Line 42:
* wired network for registration desk.
* have a networking-status page in the wiki. The Reg. desk can print it every morning and make copies available.
Line 37: Line 49:

  * The idea for an introduction 3x5 card at registration is great. "Hipster's Guide to Ridiculously Easy Group Forming"
  * Encourage group formers to create a wiki page with more info.
Line 39: Line 55:
  * open space manager to give a short introduction, possibly before the plenary sessions
Line 41: Line 58:

* more visible open space signup board

* Vertical and horizontal grid allignment lines on board.

* Overflow board for areas such as atrium, bar.

* Communicate recording options so we can capture great sessions such as "Teach Me Twisted"

Registration Desk
-----------------

* Have a simple badge printing program so that Mary can print badges w/o having to create a registration.
* make on-site registration faster -- get a terminal? do it in PayFlow's (or should I call it PayFlaw?)
  management interface? outsource the whole registration process to a third party?
* make using the reg. software faster -- shortcuts for common tasks, alt tag on the badge image, other tweaks.
Line 45: Line 78:
* Dedicate space for recruiting
Line 46: Line 80:
  * Use open space room(s)?

* Encourage sponsors to set up social events (parties, dinners, mixers, etc.).
* Make sure all sponsor bag materials are onsite the day before the tutorials so bags don't need to be handed out w/ partial content
Line 49: Line 87:

* Keep speaker names on proposals during reviews
* Organize scheduled talks into themed tracks
Line 54: Line 95:
* Better wrangling of speakers at speaking time * Better wrangling of speakers at speaking time, including:

  * Present before session
  * Session chair hands out release forms
  * Make sure all required A/V resources are available and working (sound, etc)
  * Check/set display resolution
Line 56: Line 103:
* Buffer zone around A/V setup to avoid RFI from Blackberrys and such * Buffer zone around A/V setup to avoid RFI from Blackberry devices and such
Line 59: Line 106:
   * suggestion to turn off screensavers, IM clients, etc that might interupt the talk    * suggestion to turn off screensavers, IM clients, etc that might interrupt the talk
Line 68: Line 115:
Tutorials
---------
* The evening session worked well. What about 2 days of tutorials?
* Allow for instructors to communicate with students (pre-conference)

  * wiki
  * mailing list
  * broadcast message
  * allow students to "release" their email address

* Allow time during the selection process to allow for "back and forth" between the selection committee and those proposing tutorials. This will allow for clarification, modification and/or expansion on the proposal.
* Score tutorials:

  * -2: No!
  * -1: Leaning against
  * 0: Neutral
  * +1: Leaning for
  * +2: Yes!

* Skype for scoring sessions? Much more effective than IM
* Set up 1 Google doc with all of the related with all of the tutorial related spreadsheets

  * Proposal scoring and status (accepted, rejected, awaiting input, etc.)
  * Room assignments
  * handout status (pdf received, off to printer, received from printer)
  * Tutorial status (open, canceled, full, closed)

* Have one, ''and only one'', primary contact per tutorial.
* Get a headset (microphone) for each instructor.
* Have instructors meet in a "ready room" so instructors can fill out the release form before their session.
* Explain the release form beforehand so there is no confusion (yeah, right :-)
* Notify the instructors that the handouts will be in black-and-white (with gray scale) so they will not depend on colour to make their point(s).
* Have a way to verify handouts have been delivered to the hotel before tutorial day.
* Get financial information sooner, especially for non-US instructors.
* Make a template for proposals so we have consistent section names (RTF format?)
* Ask proposals for "ideal" and "maximum" (effective) class size (but don't guarantee either)
* Get slides online for emergency access (computer dies, etc.)
* Set up a waiting list for tutorials.
* Is there a way to allow instructors to submit handout notes later? Brian said that the print shop had the jobs done before he could walk across the (very large) shop to get them. Could the notes be submitted a day or two before tutorial day?

Scheduling
----------
* Start with PSF Community Awards to allow the recipients, if present, to receive congratulations all weekend.
* Bigger raffle. No pick-up, just announce winners, pick up prizes at vendor booths. This may help us get more minor sponsors and more sponsor air-time. Unclaimed prizes can be re-raffled at later event.
Line 71: Line 162:

* A prominent contact email address for most things -- i.e. pycon-help@python.org just to field and route questions to the right person...
* More pictures of PyCon's diverse human population
* Post conference dates, locations, and Tenative Schedule as early as possible to help cost planning (flights, justification, schedule priorities, etc.)

Volunteer Coordination
----------------------

* Schedule major planning huddles for volunteers to pick up information (on paper) and updates to learn...
 * Who are the Go-To people and places for specific issues (Safety, A/V, Scheduling, ...)
 * What activities could use filler people
 * What filler tasks job requirements are (manning t-shirt and registration desk, how to assist Open Spacers, lost folk.)
 * Name, Role and 1 Quick Question round-the-room
 * Pick up Staff T-Shirts
* Volunteer name-tag banners to encourage folks to ask questions. "Need a map?"

Job Board
---------

* Physical cork board.
* Supply introduction in registration materials similar to Open Spaces.

Swag
---------
* See `the swag ideas page <2008IdeasFor2009/Swag>`_.

Suggestions for 2009

This page should be used as a place to capture the ideas that we don't want to forget to incorporate in 2009 given our fresh perspectives on 2008... so.... list away! (also, feel free to add topics/sections, the list below was just a quick start)


Financial Aid

  • Make reimbursement process easier by creating a pdf for recipients to fill out instead of making them create their own.

Food, etc.

  • Have water be available in the hallways, not just the rooms
  • Convince the food vendors / hotel to leave the food trays around for longer than the few minutes when scheduled meal breaks are. Numerous times I missed the provided food due to an extended conversation following a talk or having been in the vendor area.

General

  • Better/more signage.

Lightning Talks

  • Be more specific that talks should be more than a sales or recruiting pitch. Tell us about what you're doing!
  • Point people to example lightning talk videos, once we get them posted.
  • Post a list of the lightning talks once the signup sheet has been taken down; people were unsure if they were accepted or not, and asked at the reg. desk.
  • Use "Huge Applause" sign video layover to help speakers know they're 5 minutes is up.

Networking

  • wired network for speakers' podiums, vendors & sponsors who request it, tutorials (esp. tutorial instructors)
  • wired network for tutorials -- too many people need to install at the beginning of a tutorial and it was too easy for the wireless to go down thus holding up progress on tutorials.
  • wired network for registration desk.
  • have a networking-status page in the wiki. The Reg. desk can print it every morning and make copies available.

Open Space

  • introduction to open space for attendees
    • The idea for an introduction 3x5 card at registration is great. "Hipster's Guide to Ridiculously Easy Group Forming"
    • Encourage group formers to create a wiki page with more info.
  • more announcements about open spaces
    • open space manager to give a short introduction, possibly before the plenary sessions
    • each session chair mentions open spaces that they're interested in
    • add scheduled open spaces to the daily schedule changes sheet
  • more visible open space signup board
  • Vertical and horizontal grid allignment lines on board.
  • Overflow board for areas such as atrium, bar.
  • Communicate recording options so we can capture great sessions such as "Teach Me Twisted"

Registration Desk

  • Have a simple badge printing program so that Mary can print badges w/o having to create a registration.
  • make on-site registration faster -- get a terminal? do it in PayFlow's (or should I call it PayFlaw?) management interface? outsource the whole registration process to a third party?
  • make using the reg. software faster -- shortcuts for common tasks, alt tag on the badge image, other tweaks.

Sponsorship

  • Dedicate space for recruiting
    • Use open space room(s)?
  • Encourage sponsors to set up social events (parties, dinners, mixers, etc.).
  • Make sure all sponsor bag materials are onsite the day before the tutorials so bags don't need to be handed out w/ partial content

Talk Selection Process

  • Keep speaker names on proposals during reviews
  • Organize scheduled talks into themed tracks

Talk Logistics

  • Better wrangling of speakers at speaking time, including:

    • Present before session
    • Session chair hands out release forms
    • Make sure all required A/V resources are available and working (sound, etc)
    • Check/set display resolution
  • Headset mics to free up both hands?

  • Buffer zone around A/V setup to avoid RFI from Blackberry devices and such

  • Email in advance and/or give a handout to all presenters (including lightening talkers) to include:

    • suggestion to turn off screensavers, IM clients, etc that might interrupt the talk
    • warnings against poorly contrasting colors (e.g. yellow on green)
    • supported projector resolutions
    • recommended minimum font size for legibility at various resolutions
    • suggestion to backup their presentation prior to the day of their talk :-)
  • A spare DVI to VGA adapter per room

  • Perhaps a spare projector in the speaker's ready room which can be used to test the speaker's equipment out prior to their talk

Tutorials

  • The evening session worked well. What about 2 days of tutorials?
  • Allow for instructors to communicate with students (pre-conference)
    • wiki
    • mailing list
    • broadcast message
    • allow students to "release" their email address
  • Allow time during the selection process to allow for "back and forth" between the selection committee and those proposing tutorials. This will allow for clarification, modification and/or expansion on the proposal.
  • Score tutorials:
    • -2: No!
    • -1: Leaning against
    • 0: Neutral
    • +1: Leaning for
    • +2: Yes!
  • Skype for scoring sessions? Much more effective than IM
  • Set up 1 Google doc with all of the related with all of the tutorial related spreadsheets
    • Proposal scoring and status (accepted, rejected, awaiting input, etc.)
    • Room assignments
    • handout status (pdf received, off to printer, received from printer)
    • Tutorial status (open, canceled, full, closed)
  • Have one, ''and only one'', primary contact per tutorial.
  • Get a headset (microphone) for each instructor.
  • Have instructors meet in a "ready room" so instructors can fill out the release form before their session.
  • Explain the release form beforehand so there is no confusion (yeah, right :-)
  • Notify the instructors that the handouts will be in black-and-white (with gray scale) so they will not depend on colour to make their point(s).
  • Have a way to verify handouts have been delivered to the hotel before tutorial day.
  • Get financial information sooner, especially for non-US instructors.
  • Make a template for proposals so we have consistent section names (RTF format?)
  • Ask proposals for "ideal" and "maximum" (effective) class size (but don't guarantee either)
  • Get slides online for emergency access (computer dies, etc.)
  • Set up a waiting list for tutorials.
  • Is there a way to allow instructors to submit handout notes later? Brian said that the print shop had the jobs done before he could walk across the (very large) shop to get them. Could the notes be submitted a day or two before tutorial day?

Scheduling

  • Start with PSF Community Awards to allow the recipients, if present, to receive congratulations all weekend.
  • Bigger raffle. No pick-up, just announce winners, pick up prizes at vendor booths. This may help us get more minor sponsors and more sponsor air-time. Unclaimed prizes can be re-raffled at later event.

Website

  • A prominent contact email address for most things -- i.e. pycon-help@python.org just to field and route questions to the right person...
  • More pictures of PyCon's diverse human population
  • Post conference dates, locations, and Tenative Schedule as early as possible to help cost planning (flights, justification, schedule priorities, etc.)

Volunteer Coordination

  • Schedule major planning huddles for volunteers to pick up information (on paper) and updates to learn...

System Message: WARNING/2 (<string>, line 170)

Bullet list ends without a blank line; unexpected unindent.
  • Who are the Go-To people and places for specific issues (Safety, A/V, Scheduling, ...)
  • What activities could use filler people
  • What filler tasks job requirements are (manning t-shirt and registration desk, how to assist Open Spacers, lost folk.)
  • Name, Role and 1 Quick Question round-the-room
  • Pick up Staff T-Shirts

System Message: WARNING/2 (<string>, line 175)

Block quote ends without a blank line; unexpected unindent.
  • Volunteer name-tag banners to encourage folks to ask questions. "Need a map?"

Job Board

  • Physical cork board.
  • Supply introduction in registration materials similar to Open Spaces.

PyCon 2008IdeasFor2009 (last edited 2008-12-11 18:41:45 by DavidGoodger)

Unable to edit the page? See the FrontPage for instructions.