Skip to main content

Part 20: Future Growth (PyCon 2008 Chairman's Report)

PyCon has shown impressive growth. As PyCon continues to grow, we'll continue to outgrow venues. At some point growth will plateau, and eventually we may even see declines, but for the near future growth seems to be on the menu. (I'm not expecting PyCon 2009 to grow another 77%; but who knows?) Keeping the community/volunteer nature of PyCon as it grows will be a challenge.

We have to decide which direction to take. I see several options:

  • Cap attendance. We had about 1040 people at PyCon 2008, and the venue has a hard limit of about 1200 people.

    Hopefully we won't need to take this drastic a measure. We'll do everything we can to avoid it.

  • Raise rates to limit attendance. This would mostly affect the attendance of hobbyists, independent consultants, developers at startups & small businesses, and students. One way to counter that would be to offer discounts or financial aid, but that entails a lot of additional work (I know, having handled financial aid last year, and advised Ted Pollari this year), and many would be reluctant to apply for aid.

    -1 from me. Raising the rates would prevent many students and hobbyists from attending, which would turn PyCon into a corporate-only conference and remove all community spirit.

  • Continue to expand. This implies larger venues, which are often more expensive. Hotels only get so big, after which conference/convention centers come into play. We may have to charge more in order to make use of larger venues. Sponsorship may cover it, but we don't know yet.

    In order to keep the conference affordable, we'll probably have to continue expanding sponsorship. As we saw this year, we have to be careful to keep the community spirit with expanded sponsorship. I think it's possible, and I think sponsors will be fine with the compromises they may have to make compared to larger corporate conferences. One advantage that an affordable community conference like PyCon has over corporate conferences is the investment that attendees make (self-funding, taking time off work, wanting to attend). That's very valuable to sponsors.

  • Split PyCon by sector, e.g.:

    • "PyCon: Developers" for core developers, contributors, and advanced users.
    • "PyCon: Learners" for new and inexperienced users.
    • "EduPyCon" for the education sector; etc.
    • Project-specific conferences.

    SciPy (2008) already exists for scientific users; the PSF should support that more.

  • Split PyCon by region: into two or more smaller annual regional conferences.

    I don't like either of the splitting options. Forcing a split would segregate the community, preventing cross-pollination. Key attendees, like Guido, would not be able to attend all of the smaller conferences. And smaller conferences may not be able to attract the quality of speakers and sponsors that a single conference does.

    I think regional and sector-specific conferences are inevitable, and good for the community. But these should begin at the local/group/project level. The PSF shouldn't start up such conferences, but we should definitely play a supporting role.

    Helping user groups seems like a good route to encourage larger local events.

  • Help existing conferences to feature Python tracks. OSCON already has a Python track, but the PSF isn't directly involved with it (although individual PSF members are); we could participate more in the planning. Conferences such as LinuxWorld or Usenix could add such tracks; perhaps we could encourage them to do so.

    We could bridge between the Python community and regional conferences such as Penguicon, offering help finding speakers, maybe funding travel, and sponsoring the conference.

    The big advantages to this approach are that we'd only be concerned about content, and we'd be free to leave the logistics of food, venue selection, etc. up to someone else. The disadvantages are that we'd now be vulnerable to bad decisions by the conference's management (but the expenditure per conference would be much lower for us), and the PSF also wouldn't be getting a cut of any profits.

The current status of the PSF precludes much of the kind of support described above, as we're all volunteers with day jobs. I hope this status changes before long.

One area that was lacking this year, and that we really need to work on as we grow, was navigation. We had maps in the program guide, but not nearly enough signs in the venue itself. As PyCon grows it will be more and more spread out, so we need signage both to help people find where they want to go, and to remind people what is available (specifically: open space, expo hall, lounge, & registration/information).

Ideas and opinions would be welcome!

This article incorporates text and ideas from Andrew Kuchling. Thanks Andrew!

Comments

Popular posts from this blog

Tutorials Due Friday, Ticket Sales Moving Quickly

Tutorial Deadline Approaching!

We’re only a few days away from the deadline for PyCon tutorials—November 24—so be sure to get your submissions in by the end of the day Friday! We’re looking for all sorts of tutorials to help our community learn and level up, so be sure to check out our Call for Proposals for more details and enter your proposal in your dashboard soon!

Talk, Poster, and Education Summit proposals are due January 3. See https://us.pycon.org/2018/speaking for all of your proposal needs.

Registration

We opened our registration a few weeks ago and are 40% of the way through our Early Bird pricing, which gives discounted rates to the first 800 tickets sold. For corporate tickets, you’ll save over 20% by buying early, and individuals save over 12%. The regular $125 student tickets are dropped to $100 during early sales. Click here for more details and to register!

If our Financial Aid program can help you attend PyCon, we encourage your application. We’ll be accepting applica…

Python Education Summit celebrates its 6th year in 2018

Teachers, educators, and Python users: come and share your projects, experiences, and tools of the trade you use to teach coding and Python to your students. The Annual Python Education Summit is held in conjunction with PyCon 2018, taking place on Thursday May 10. Our Call for Proposals is open until January 3rd, and we want to hear from you! See https://us.pycon.org/2018/speaking/education-summit/ for more details.

What we look for in Education Summit talks are ideas, experiences, and best practices on how teachers and programmers have implemented instruction in their schools, communities, books, tutorials, and other places of learning by using Python.

Have you implemented a program that you've been dying to talk about?Have you tried something that failed but learned some great lessons that you can share?Have you been successful implementing a particular program?
We urge anyone in this space to submit a talk! We’re looking for people who want to share their knowledge and leverage…

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…