Skip to main content

Why not join the sprints this year at PyCon?

A guest post by Naomi Ceder, one of our 2016 Sprint Coordinators.

Sprinting has always been one of the hidden gems of PyCon, a part of every PyCon from the beginning, back in 2003. Hundreds of programmers stay one or more extra days after the conference to collaborate on open source projects large and small. The people who’ve done it treasure the experience. Not only do the projects that participate benefit from fresh eyes and ideas, but the sprinters usually find that they gain enormous insights into a particular problem or library, into the Python language, and even into coding in general. This year will be no exception, with many established projects sprinting and new projects joining.

Given how cool sprinting is, many of us have been puzzled that more people don’t join the PyCon sprints. Why could that be? Well, we know that everyone has their own reasons behind what they choose to attend, but in case any of the following apply, we wanted clear a few things up.

Reasons you might not be sprinting at Pycon (that totally should not stop you)

  • I’m not experienced enough.

    We’ve got that covered! We understand that not everyone has sprint experience, but we can help you, in several ways:
    • We’ll again be holding an “Intro to Sprinting” workshop on Sunday night before the sprints start. Shauna Gordon-McKeon, with several volunteers from the Python community, will present this session to help bring you up to speed on what to expect while sprinting, how to participate, as well as what projects are particularly newcomer friendly. Once we’re done, groups will organize to go out to dinner, so you can connect with your fellow first time sprinters and some people from the sprints. If you’re interested in this workshop, please visit our registration page to let us know (For information on current year sprints, see https://us.pycon.org/).
    • Well identify the sprints that are most newcomer-friendly, and give those sprint leaders whatever support we can to help them better welcome newcomers to their projects.
    • Finally, well have a help table, to give you any last minute directions or help with the sprints you might need, from installing and using common tools to suggestions on how to get the most out sprinting or just talking about how it’s going.
  • I don’t know what I’d sprint on.

    Well, that's understandable — there will be a lot of interesting projects sprinting, so deciding is never easy. However, we have help there, too. In the lead-up to PyCon, many of the sprints will be listed on the PyCon site, so you can check them out in advance. Then, at PyCon one of the last events at the main conference will be a chance for sprint organizers to present their sprints. And, as mentioned above, we’ll identify sprints that are particularly beginner friendly.
  • I don’t know anyone who’s sprinting.

    That may be true (although you’d be surprised). But the cool thing about the sprints is that by lunch time of the first day you will know people sprinting. Project maintainers, people whose talks you’ve seen, people who you’ve only met online. And you’ll be working alongside them. What a great way to connect with some new people in the Python community!
  • I don’t know how to register for the sprints. Isn’t it a hassle?

    That’s why we’re here. You don’t need to change your registration to join the sprints. There’s no additional registration fee, and you even get lunch. You do need to cover the additional lodging and other meals, but that’s it.

    If you want to sprint, the first thing to do would be to make sure you have a place to stay for the extra days. If you’ve booked a room through the PyCon registration system, you'll need to contact the registration team at pycon2016@cteusa.com as soon as possible to request the extra nights. The sprinting itself (along with lunch every day) is free, so your only expenses are your room and other meals.

    Once you have that taken care of (and booked the right flights, of course), the registration form for the Intro to Sprinting tutorial is here (For information on current year sprints, see https://us.pycon.org/). This is also free, so please sign up and join us.

Veteran Sprinters also welcome!


But you already knew that. If you’ve sprinted before the odds are you know how awesome it is. Not to worry, we didn’t forget you! We do want to keep the sprints fresh, and to keep improving them for veterans as well as newcomers. To do that we’ll be making a few additions and tweaks.

So plan to sprint!


You can check out the projects currently planning to sprint at the PyCon Sprints page and if you’re interested in the sprinting workshop just visit the registration form and sign up (For information on current year sprints, see https://us.pycon.org/). And get ready for some serious sprinting at PyCon!


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…

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…

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…