Skip to main content

We're Ready for Your Proposals

Maybe you’ve been to PyCon before, maybe you’ve seen the videos online, maybe you’ve even seen our Call for Proposals for PyCon 2012. Maybe you asked your boss for time off March 7-15, 2012 to join us in Santa Clara, CA for PyCon. Well, maybe you’re not that far along, but maybe you’re thinking about it. Here’s one thing you should think about: You should propose a talk. Yes, I said it. You, the reader, should propose a talk at PyCon.

You’re probably thinking, “I don’t even know this guy and he thinks I should propose a talk?” Nope, I probably don’t know you, but you probably know something I don’t know. You’ve probably had experiences I haven’t had. You probably work on some really cool stuff that I don’t work on. You’re what PyCon needs. We’re looking for members of the Python community to talk about what they’re up to. New or old, beginner or expert, the conference starts and ends with you.

Each year, PyCon’s schedule is not only made up of a wide array of topics, but of approaches. There’s always plenty of “how” talks: how to use a library, how to write documentation, how to bring Python into your organization. We get a number of “why” talks: why you should test, why you should look at alternative implementations, why you should look at Python 3. There’s always a few “status” talks: status of Unicode in Python 3, status of packaging, status of various projects. There’s also panels, investigations, crazy demos, and a lot more. You certainly know some how’s and why’s, might have some status to show, could chip in to a panel, share your best practices on a topic, or present a deep dive on a problem. You could also do something totally new. In fact, we’d love that. We need that.

If you’re short on topic ideas, the #pycontalksiwant tag on Twitter is starting to fill up with some good ones. @nedbat wants to know what Python could learn from other languages. @doughellmann wants to know some devops tips and tricks. @BigJasonWebb wants to know how to get an organization to use Python 3, and @johnmarshall is wondering how people are upgrading to Python 3.

Take a look and see if you can contribute to any of those topics -- the talks aren’t going to write themselves. Any contribution here helps, especially in adding the topics you’d be interested in seeing, since we haven’t yet figured out mind reading.

If you’re ready to submit a talk, check out http://us.pycon.org/2012/speaker/ and our Call for Proposals. You’ve got 53 days to submit your proposals, and you can follow along here or on twitter for regular updates. We have a lot of surprises up our sleeves!

Comments

Popular posts from this blog

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…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…