Conference Committee

Figure out what is going to happen, and make it happen.

Who is going to talk, how are we going to find them, what will they talk about, what will we eat, how should the chairs/tables be arranged, how can we get more sprinters, what else needs to go on this list?

If you think this is all under control... think again. it only looks that way because David ends up doing whatever needs to get done. Lets try to make his life easier this year.

Please subscribe to the pycon-organizers mailing list. This is the central list, so anyone doing anything should be on it.

Program Committee

Help choose the talks that will make up the PyCon Conference Days.

Last year we received almost twice as many proposals as we had slots to fill. It was tough choosing. Hopefully we'll have many high-quality proposals to choose from this year too! We need reviewers! But please note that as proposals may contain sensitive information, only people known in the Python/PyCon community will be invited to participate.

You don't have to read all the proposals. The proposal system will randomly assign talks to reviewers. The more reviewers we have, the fewer talks each person will have to review. Sign up for the program committee mailing list (where we talk) and create a web site account (so you can review and vote on proposals).

Tutorial Committee

Help choose the classes presented on "Tutorial Day"

The past few PyCons have offered tutorials on the day preceding the conference. In 2008, more people attended the tutorials than attended the PyCon 2006 conference (over 420 people attended classes; many attending all three sessions).

We have to get the word out about tutorials, get proposals sorted, choose which proposals will be offered as classes, organize class rooms, equipment, class notes, class slides, waiting lists, release forms... there is no shortage of things to do.

If this sounds appealing to you, get in touch with the tutorial coordinator and ask how you can help.

PyCon Tech

"The Python behind PyCon"

You can help write the conference software, or test/review.

Subscribe to the pycon-tech mailing list and see the PyCon-Tech homepage.

PyCon Website

Content & updates needed!

To help out with this web site, create an account, activate it, and then send e-mail to <doug.napoleone (at) gmail dot com> and <goodger (at) python dot org> from the e-mail address you used to activate the account. We will give you access to edit the site. Once you're logged in with write access, you can edit and add pages. More: Maintaining the PyCon Web Site.

See this list of website tickets (pages that need content or editing).

Local Knowhow

If you are familiar with the area, please post some tips for the out of towners.

• Where is a good place to go in the evening? (URLs to local info is handy.)
• Organize a group outing a day or 2 before/after the convention.
• Where is a bar with free wifi?

Pretty much "add content to this website" (see above).

On-Site

A lot happens at PyCon, and we need volunteers to help it happen.

• Swag bag stuffers: Someone needs to stuff the stuff into the stuff holders, typically bags.
• Registration desk staffers: Someone needs to say "What is your name?" find the persons name tag hand them their stuff.
• Session chairs: Someone needs to say "Please be seated. Our next speaker is..." It really is that easy!
• Audio/Visual team members: Requires familiarity with A/V systems used in our presentation rooms, and must also be available during designated "Presentation Staging Times" to assist presenters.

Just join the list and say something like "I'll be arriving at the venue around 2pm. What can I do to help?"