Skip to main content

Introducing the PyCon Hatchery Program

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 additional events such as Young Coders, the Education Summit, Language Summit, Poster Session, among others. The conference strives to be globally representative by promoting diversity and inclusion through these additional events and outreach programs.

Our community works to meet these goals year on year. In the past, we have received requests to add events to PyCon but have not had the resources to make them work. Although we are still limited on staff resources, we are proposing a stepping point that may lead us in the right direction.

What is the end 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 events that will become a recurring part of PyCon itself or find a home as a stand-alone event in the future. Events that may be of specific temporal interest are also welcome, but will generally be given lower priority.

Our end goal is to continue improving our community through inclusivity and diversity efforts as PyCon is well suited to be a leader in driving this. We are responsible for the largest public event in the community, have the highest notoriety for a Python conference, and can bring in the most funding to support these efforts directly. Beyond our own work, other international conferences, regional conferences, and local user groups tend to take inspiration from the conference.

How do we plan on reaching our goal?

The long-term goal is to have a Working Group that can receive, review, and select proposals to add new events and programming to PyCon US.
We propose to begin the process of forming a “hatchery program” for tracks, summits, demos, etc which share and fulfill the mission of the Python Software Foundation.
Some core ideas of such a program are:
  • An established process to receive applications to the program
  • Clear benefits and commitments to selected applications
  • Guidelines for the rubrics by which applications would be reviewed and selected
  • Conditions for the “graduation” or  "termination" of such an incubated program
    • What are the criteria for Success? What can the PSF do to help successful tracks spin off into their own conference or become a permanent part of PyCon.
    • What are the criteria for Failure? How do we gracefully end unsuccessful Tracks?
  • A Working Group to both develop the program, promote the program, establish the process, and select applications for inclusion.
We imagine that such a program would be beneficial for PyCon and for the Python community at large. It opens the doors for the community to help us understand and support their concerns and best work towards the mission of the Python Software Foundation in a manner which is fair to all applicants.

What steps are we starting with?

At the 2018 conference, we have assigned one room equipped similarly to other PyCon events for the hatchery program. It will take place Friday, May 11 through Sunday, May 13.

Beginning October 24, we will accept proposals for the hatchery program through January 3. We have created an ad-hoc group of the Conference Chair, three PSF Board of Directors, and two community volunteers to review the proposals this year. For more information on the CFP see

After a review process, we plan to announce accepted proposals early in February 2018.

Why this starting point?

We want to gauge your interest for this type of program, so we are starting with this trial version rather than waiting for a fully developed program to be developed and launched blindly in 2019. We are also interested to see how many proposals we will get that have potential to become their own “spin-off” events at PyCon. If we see that we cannot fill three days worth of content with incubator tracks, we will assess the trial and decide if we want to continue this process in the future.


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 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…