PyCon is organized and run by volunteers from the Python community. Everyone who is attending PyCon is welcome, and all help is very much appreciated.
Want to get started? Check the outline below, and consider signing up for the pycon-organizers mailing list! It's how our community stays informed throughout the year, and signing up doesn't commit you to anything.
If you're new to PyCon, or would just like to help others feel at home, head on over to the Welcome (Un)committee page: http://us.pycon.org/2012/community/welcome
Have a quick look at the Schedule of Volunteering Events!
Helping set up the conference and tutorials is fun, useful, and a great way to meet fellow Pythonistas. To learn more, head over to the Volunteering On-Site page for information, schedules, and sign-up forms: http://us.pycon.org/2012/community/volunteer/onsite
Sprinting is a great way to contribute to projects and learn from others too - head over to the Development Sprints page for more information.
Also, don't forget to monitor @pycon on Twitter while at the conference.
PyCon may only be one week out of the year, but there's plenty to be done in the 51 weeks leading up to it!
Here are some ways you can help:
One great way you can help is by simply letting people know about PyCon. Amazingly this is the first year in PyCon's 10 year history the conference has sold out, but it's never too early to promote PyCon. The more interest we have, the more we are able to do for the community! Head over to the Publicizing Pycon page for some ideas: http://us.pycon.org/2012/community/volunteer/publicizing/
The pycon-organizers mailing list is the go-to place for conference planning. The list is active year-round, since we start planning in mid-Summer for the following year's PyCon. Head over to http://mail.python.org/mailman/listinfo/pycon-organizers and sign up!
Do you want to develop your leadership skills? Sign up for a role on the PyCon Conference Staff. There are always openings to fill, or you can suggest creating a new role if you see an unmet need.
You might consider joining one of the three core committees that help create PyCon: