Skip to main content

PyCon US 2013: Now accepting Launch day sponsors!

That's right folks - the PyCon US team starting planning and executing for PyCon 2013 before PyCon 2012 even ended. We're revving up our engines as we speak to fully launch PyCon 2013, March 13th-21st in Santa Clara CA once again.

Last year we had over 2300 attendees from all over the world - PyCon 2012 was the largest gathering of Python hackers in history. This year, we've set a hard cap of 2500 total attendees (this includes sponsor registrations). We fully expect to sell out the conference once again - and we've got huge things in store for 2013.

PyCon 2013 will be the last year we hold it in Santa Clara for this cycle - PyCons 2014 and 2015 will be held in Montreal Canada, and this is my final year as PyCon chair - so let's make this one as epic a blowout as last year's was.

With our launch, we are now signing up launch day sponsors - these sponsors get additional billing, visibility and, well community appreciation for being launch day partners, and will be part of a large PR push we are planning.

If you and your company are interested - send an email to jnoller@gmail.com for the 2013 prospectus, which we have revised based on feedback from past years.

I'm excited to once again be chairing the conference, and having the honor of working with our sponsors, attendees and the privilege of working for the Python Community.

Jesse Noller, PyCon 2013 Chair

Comments

Popular posts from this blog

Hatchery Program Returns for 2019

PyCon is known around the world as the Python community’s premier event, attracting people from 39 countries. Outside of the main track of talks, PyCon is home to a growing number of events such as Young Coders, the Education Summit, Language Summit, Poster Session, and most recently the PyCon Charlas. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs. Our community works to approach these goals year on year. While we regularly receive requests to add events to PyCon, we have not had an established process for accepting and evaluating the community’s suggestions. By introducing the PyCon Hatchery Program in 2018, we took an initial step to introduce a long term process for evolving PyCon. What is our goal?We want to support our community and enable them to add events to PyCon that are important to our community. The long-term goals of this program are to support and grow sustainable programs th…

Pycon 2019 Call for Proposals is Open!

The time is upon us again! PyCon 2019’s Call for Proposals has officially opened for talks, tutorials, posters, education summit presentations, as well as the hatchery program PyCon Charlas. PyCon is made by you, so we need you to share what you’re working on, how you’re working on it, what you’ve learned, what you’re learning, and so much more.

Please make note of important deadlines for submissions:
Tutorial proposals are due November 26, 2018.Talk, Charlas, Poster, and Education Summit proposals are due January 3, 2019.
Who should write a proposal? Everyone! If you’re reading this post, you should write a proposal. PyCon is about uniting and building the Python community, and we won’t advance as an open community if we’re not open with each other about what we’ve learned throughout our time in it. It isn’t about being the smartest one in the room, so we don’t just pick all of the expert talks. It’s about helping everyone move together. “A rising tide lifts all boats,” if you will.

We…

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…