Revision 34 as of 2007-08-30 15:18:47

Clear message

Sign-Up Sheet

Please sign up for staff roles! If you notice a missing role, please add it (and your name, too!).

You should also subscribe to the pycon-organizers mailing list.

Role names are links to role descriptions, which follow below.

Role Name(s)
Planning
PyCon 2008 Chair David Goodger
Local Coordinators Ted Pollari & Chris McAvoy
Meeting Planning Services Conference Technology Enhancements Inc. (CTE)
Audio/Visual Coordinator Carl Karsten carl@personnelware.com
A/V Session Recording Coordinator  
Badge Coordinator Steven Githens ''.join(['sgithens','@','caret.cam.ac.uk']) (I really do live in Chicago)
Feedback/Survey Coordinator Brian Ray bray@sent.com
Financial Aid Coordinator  
Food Coordinator Skip Montanaro skip@pobox.com (I have always liked food...)
Graphics Coordinator Atul Varma varmaa@gmail.com
Communications Coordinator  
Network Coordinator Sean Reifschneider jafo@tummy.com (I have always liked meeting girls)
Power Coordinator  
Publicity Coordinator Catherine Devlin catherine.devlin@gmail.com
Software Coordinator Doug Napoleone doug.napoleone@gmail.com (I like cereal)
Sponsorship Coordinator Van Lindberg van.lindberg@gmail.com
Tote bag and Giveaway Coordinator  
Volunteer Coordinator Chris McAvoy chris.mcavoy@gmail.com
Webmasters  
Program (content: talks, tutorials, sprints, etc.)
Program Committee Chair Ivan Krstić
Program Committee  
Keynote Coordinator Noah Kantrowitz (noah . coderanger . net)
Keynote Speakers  
Lightning Talks Coordinator Jacob Kaplan-Moss (I've always liked being hit by lightning)
Open Space Coordinator  
Tutorial Coordinator Greg Lindstrom gslindstrom (gmail)
Sprint Coordinator  
Python Lab Coordinator Cosmin Stejerean (cosmin [at] offbytwo [dot] com)
Operations (at PyCon itself)
Registration Desk Staffers Walker Hamilton signalfade (gmail)

Role Descriptions

Please fill in the blanks.

A/V Session Recording Coordinator

Audio/Visual Coordinator

Badge Coordinator

Communications Coordinator

  • manage inquiries on the pycon at python dot org mailing list.
  • forward questions to the proper staff members.
  • ensure questions and problems are followed up on and a proper timely response is made.

Feedback/Survey Coordinator

Financial Aid Coordinator

Food Coordinator

Graphic Designer

Keynote Coordinator

Lightning Talks Coordinator

Local Coordinators

Meeting Planning Services

We have contracted with Conference Technology Enhancements Inc. (CTE) to negotiate & coordinate with the hotel, and to handle much of the "uninteresting" conference logistics.

Network Coordinator

  • Network architecture for the conference.
  • Equipment selection, testing, purchase, configuration, and deployment.
  • Responsible for getting wireless access points deployed.
  • Router/NAT proxy.
  • Monitoring of APs for availability during conference, tracking down failed APs.
  • Monitoring of network.
  • Getting and connecting to upstream bandwidth.
  • Debugging of peoples problems during the event.
  • Documentation (via the Wiki) of client configuration and status during the event.

Open Space Coordinator

  • Keeping the bulletin board readable during the conference.
  • In the morning, posting a list next to each open space room of what's going on that day.
  • Maybe booking some open space slots before the conference via e-mail.
  • Possibly making an announcement before each keynote of some of the day's open space events. (Or the chair can do it in his keynote introductions.)

Power Coordinator

Program Committee

Program Committee Chair

Publicity Coordinator

PyCon 2008 Chair

Coordinates everybody else. Acts as main point of contact for the meeting planners & venue. Recruits and delegates. Chief cook & bottle-washer.

Registration Desk Staffers

Software Coordinator

  • Oversee software packages used for management of the conference.
  • Manage the integration and development of custom solutions.

Sponsorship Coordinator

Sprint Coordinator

Python Lab Coordinator

A "Python Lab" where problems are announced to the group, people work on them for an hour, and then a couple of the best or interesting solutions are presented as a brief code walkthru. Something like an interactive "Python Cookbook" session, to show how the same problem might be solved differently by people at different skill levels.

  • Recruit and organize the proctors and problem writers
  • Plan the problems w/ doctests to be given. Make sure to have interesting sample solutions which have their own trade off issues to be discussed.
  • MC the event, welcoming people, giving instructions, help to form balanced groups and directing proctors. Keep discussions going and on track.
  • Details on last years event.
  • Problems and Solutions from last year. Have more from Wesley Chun, will post soon.

Tote bag and Giveaway Coordinator

Tutorial Coordinator

Pre-PyCon:

<TBD>

On Tutorial Day:

  • Label rooms
  • Check A/V equipment: present, works
  • Distribute laser pointers to each instructor.
  • Obtain audio release form from each instructor.
  • Collect, duplicate and distribute class notebooks.

Volunteer Coordinator

Webmasters

System Message: ERROR/3 (<string>, line 248)

Document or section may not begin with a transition.

CategoryPyConPlanning

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