|
Size: 6224
Comment:
|
Size: 10209
Comment: Added myself as Sprint Coordinator
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 28: | Line 28: |
| `Audio/Visual Coordinator`_ | `Audio/Visual Coordinator`_ Carl Karsten carl@personnelware.com |
| Line 40: | Line 40: |
| `Graphic Designer`_ | `Graphics Coordinator`_ Atul Varma varmaa@gmail.com |
| Line 44: | Line 44: |
| `Network Coordinator`_ | `Network Coordinator`_ Sean Reifschneider jafo@tummy.com (I have always liked meeting girls) |
| Line 48: | Line 48: |
| `Publicity Coordinator`_ ------------------------------------- ----------------------- `Software Coordinator`_ Doug Napoleone ------------------------------------- ----------------------- `Sponsorship Coordinator`_ ------------------------------------- ----------------------- `Tote bag and Giveaway Coordinator`_ ------------------------------------- ----------------------- `Volunteer Coordinator`_ |
`Publicity Coordinator`_ Catherine Devlin catherine.devlin@gmail.com ------------------------------------- ----------------------- `Software Coordinator`_ Doug Napoleone doug.napoleone@gmail.com (`I like cereal <http://www.youtube.com/watch?v=5WNeJZQC8iI>`__) ------------------------------------- ----------------------- `Sponsorship Coordinator`_ Van Lindberg van.lindberg@gmail.com ------------------------------------- ----------------------- `Tote bag and Giveaway Coordinator`_ Don Spaulding donspauldingii@gmail.com (I have always liked Free Stuff.) ------------------------------------- ----------------------- `Volunteer Coordinator`_ Chris McAvoy chris.mcavoy@gmail.com |
| Line 64: | Line 64: |
| `Program Committee Chair`_ | `Program Committee Chair`_ Ivan Krstić |
| Line 68: | Line 68: |
| `Keynote Coordinator`_ | `Keynote Coordinator`_ Noah Kantrowitz (noah . coderanger . net) |
| Line 72: | Line 72: |
| `Lightning Talks Coordinator`_ Jacob Kaplan-Moss ------------------------------------- ----------------------- `Open Space Coordinator`_ |
`Lightning Talks Coordinator`_ Jacob Kaplan-Moss (I've always liked being hit by lightning) ------------------------------------- ----------------------- `Open Space Coordinator`_ Peter Kropf pkropf@gmail.com (I work therefore I am) |
| Line 78: | Line 78: |
| `Sprint Coordinator`_ ------------------------------------- ----------------------- |
`Sprint Coordinator`_ Facundo Batista (facundo//taniquetil/com/ar) ------------------------------------- ----------------------- `Python Lab Coordinator`_ Cosmin Stejerean (cosmin [at] offbytwo [dot] com) ------------------------------------- ----------------------- |
| Line 83: | Line 84: |
`Registration Desk Staffers`_ |
`Registration Desk Staffers`_ Walker Hamilton signalfade (gmail) |
| Line 105: | Line 105: |
| * 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. |
|
| Line 123: | Line 126: |
| See http://wiki.python.org/moin-pycon/Keynote_Speakers. | |
| Line 141: | Line 145: |
| * 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. |
|
| Line 171: | Line 193: |
| Coordinates everybody else. Acts as main point of contact for the meeting planners & venue. Recruits and delegates. Chief cook & bottle-washer. | |
| Line 177: | Line 200: |
| * Oversee software packages used for management of the conference. * Manage the integration and development of custom solutions. |
|
| Line 184: | Line 209: |
| 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 <http://us.pycon.org/TX2007/PythonLabNotes>`__ on last years `event <http://us.pycon.org/TX2007/PythonLab>`__. * `Problems <http://us.pycon.org/common/talkdata/PyCon2007/036/problems.zip>`__ and `Solutions <http://us.pycon.org/common/talkdata/PyCon2007/036/solutions.zip>`__ from last year. Have more from Wesley Chun, will post soon. |
|
| Line 192: | Line 231: |
| <TBD> On Tutorial Day: |
* Get the word out (Call for Proposals). Post to the Python lists (general, dev, tutor, announce, SIGs, etc.) as well as specialty lists (Django, TurboGears, wxPython, PyQt, etc.) letting people know that proposals are being accepted. When you post, make sure you include: * The tutorial date (mention it is separate from the general conference) * Tutors are paid (verify the amount before you post it!) * The submission deadline. * The handout deadline. * Include a link to the submission page. * Decide which tutorials to present (get help as required from PyCon chair, program committee members, etc.). * Send accept & decline notices by email. * Notify instructors that IRS forms are required. * Follow-up with instructors on handouts. * Collect handout PDFs and duplicate them in sufficient numbers. On Tutorial Day (or ideally, the evening before): |
| Line 200: | Line 255: |
| * Collect, duplicate and distribute class notebooks. | * Distribute class handouts. |
| Line 207: | Line 263: |
---- CategoryPyConPlanning_ |
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 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
Keynote Speakers
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:
- Get the word out (Call for Proposals). Post to the Python lists (general, dev, tutor, announce, SIGs, etc.) as well as specialty lists (Django, TurboGears, wxPython, PyQt, etc.) letting people know that proposals are being accepted. When you post, make sure you include:
- The tutorial date (mention it is separate from the general conference)
- Tutors are paid (verify the amount before you post it!)
- The submission deadline.
- The handout deadline.
- Include a link to the submission page.
- Decide which tutorials to present (get help as required from PyCon chair, program committee members, etc.).
- Send accept & decline notices by email.
- Notify instructors that IRS forms are required.
- Follow-up with instructors on handouts.
- Collect handout PDFs and duplicate them in sufficient numbers.
On Tutorial Day (or ideally, the evening before):
- Label rooms
- Check A/V equipment: present, works
- Distribute laser pointers to each instructor.
- Obtain audio release form from each instructor.
- Distribute class handouts.