Skip to main content

Announcing Startup row: PyCon 2013 Edition!

For the past two years, one of our most successful and impressive experiments has been the creation of "Startup Row", where we let Python powered startups apply for free booth space, registrations and coverage. Like all things, this has only gotten better and more impressive with time.
We knew that a lot of startups used Python, but we were astounded and excited to see the number and quality of new companies that were eager to participate at PyCon and show off what they were doing.
At PyCon itself, we've continually got a lot of comments from attendees that Startup Row was their favorite part of the Expo Hall. From meeting and talking with the founders of so many great companies, it was obvious that they would go far. Last year alone, we heard from several Startup Row participants that they were even approached by potential investors - that's right, we had Angel Investors and "big boy" VCs at the conference, and the conversations that they had with the participants led to something!
Like last year, we have our eye on the startup world even more. With PyCon being held right in the heart of Silicon Valley, it seemed right to bring back Startup Row for PyCon 2013! We're even working on better booth placement, signage and flow to help guide attendees to you!

We will be highlighting some of the most promising new companies that are using Python to build their businesses - including possibly yours. If your startup uses Python, we want to hear about it - and you could be one of the startups that gets featured on Startup Row at PyCon 2013.
Here are the rules:
  • Seed stage only. For purposes of startup row, that means less than $350K in outside funding or, if self-funded, less than 18 months old.
  • You must use Python somewhere in your startup. Backend, frontend, testing, wherever.
  • No repeats. If you were on startup row last year, your startup is not eligible. We want to give a chance to as many startups as possible.
  • If you are accepted, you must guarantee your attendance for at least the Expo Hall hours on your appointed day. We will work with you as to which day is better for you.

Here are the selection criteria:
  • Interesting technology. Are you doing something hard or unique? Tell us about it.
  • Traction and reach. Are you affecting a lot of people? How?
  • Concept. Are you changing the world? Disrupting an industry? Solving a problem? Sometimes you see what a company is doing and your jaw drops. If that is your startup, we want to hear from you.
Do you want your startup to be on Startup Row? You can apply at https://www.surveymonkey.com/s/StartupRow2013

DEADLINE: All submissions must be received by February 10, 2013.
If you were a past startup row, and want to share your personal tale of what it was like - drop an email to Jesse Noller, PyCon Chair - we would love to share your story here.

Comments

The above states “All submissions must be received by February 10, 2013.” But the submission form says “APPLICATIONS MUST BE SUBMITTED BY FEB. 29th, 2013.” At least one of these should be corrected (and since it's not a leap year, possibly both).
Brian Curtin said…
Thanks for your comment. The deadline is February 28th - there will be a blog post on Monday announcing this.

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…