Skip to main content

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, you will be ready to help with almost any project at the sprints.
  • If you might be sprinting with a project whose code is written in C, you should have the default compiler for your platform installed. This will usually be make and gcc in Linux, and the Xcode tools on the Mac. You will have the chance to learn more about these at the Intro to Sprints session.
  • Browse ahead of time our list of projects that will be sprinting. If there are projects that especially interest you, try checking out their latest source code to your laptop and attempt to build the project and run its tests successfully. If you run into snags, see whether the project has a project mailing list or IRC channel where you could ask questions. Or you could wait and ask for help from the project leads in person once you arrive on-site at the sprint itself, where they can iterate more quickly on the error you are facing. I took this approach myself in 2013 while attending my first-ever PyCon development sprint! For the CPython project, you can consult https://docs.python.org/devguide/ for the steps on how to build it.
  • Not every project that will be sprinting is listed yet on our projects page. The official list of sprinting projects is presented in a quick presentation a few minutes after the final PyCon keynote ends and the conference ends. Each project lead will come to the stage and introduce their project in around 30–45 seconds. Here is the long queue of project leads waiting to present at 2013:

The long queue of sprinters

  • If you are yourself a project lead or developer for an open source project, feel free to add your project to our list if you are prepared to come lead a sprint. Be sure that you are ready with a checkout of the latest source code, and a list of features and bugs on which both beginners and experienced programmers can work.

  • Remember to use the rule of two feet: if you are not enjoying a particular project, feel free to go visit all of the other rooms and tables and projects. Work on whichever projects you like. No one will feel bad if you leave one table and join another one.

We will be presenting an “Introduction to Sprints” workshop starting at 4:30pm on June 1st in the Oregon Ballroom 201–202. If there are spaces left, you can pre-register yourself for the session on EventBrite:

Intro to Sprints event sign-up page on EventBrite

Finally, remember to enjoy your time at PyCon. This is the time of the year when we all can meet, discuss new ideas, showcase our work, and make new friends.

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…