PyConWeb 2018, how was it?

The second edition of PyConWeb took place from June 30 to July 1st in Munich. We’re happy to share some facts and statistics about the conference and show some behind the-scenes processes.

When a conference is young, promotion is the most difficult part of the organization process. As organizers of PyMunich meetup, we have direct access to the local community, but reaching out to an international one is a major challenge. What helps us the most is the Python Event Calendar, lightning talks at other PyCons, and social media.

Early-bird tickets were released on April 15th 12:00, and in the very first minute, a couple of tickets were already gone. Within a few days, we got around 40 registrations. As an absolute number, this does not sound much. However, considering that 40 people paid without having announced yet any single talk on the website, nor any published speakers, nor any workshops, nothing; it was pure trust. Such things mean a lot, and are the best motivation for our team.

The conference was planned for 170 people and was sold out a few days before the event. We could allow more people in, but the problem is to place the correct amount of orders. At some point, you need to decide how many T-Shirts, lanyards, and goodies to order, and that’s your upper limit. Next year, we will plan for some buffer.

The first keynote speaker, Nicola Iarocci, arrived in Munich stylishly riding his Triumph Bonneville all the way from Ravenna, Italy. It’s 635 km, but as he said, it’s worth it.

To remind you, Nicola is the author of Eve, Cerberus, and many other open-source tools, highly appreciated by the community.

One of our main 2018 findings was the selfie photo booth. Selfie, because there was no photographer, people took pictures with their own smartphones. The problem of having a photographer is that it takes weeks to share pictures and people are most enthusiastic the very same moment the picture is taken. They want to share it, post it on social media. Therefore, there was not a dedicated photographer, just selfies:

What a success! Exactly what we wanted.

Day two started with a keynote of Katiane di Schiavi about changing the world with code.

Katiane was a volunteer in the United Nations, managing various educational projects, inlcuding one with Python. Her talk resonated so well that we found following post on twitter:

Since PyConWeb is not just Python but also Web, there are talks focused on the frontend side as well. Even hipster ones such as Flask+Vue.js

With 2 days and 3 tracks, there are always many good talks and new information. Jonathan, one of our attendees, summarized it pretty well as the “PyCon(Web) effect”.

There were no CoC violations reported, maybe because Python community is very kind, or maybe because of the PyConWeb Police hanging around. Or probably both.

We are very happy about how did everything work out, and hope that our attendees loved it as well. We would be thankful for any feedback, publicly on social media or privately on feedback@pyconweb.com.

Hope to see you next year!

A PyCon You Can’t Miss

Dear friends, did you already notice that PyConWeb 2018 happens on the last weekend of June in Munich? The debut in 2017 was so appreciated, that, of course, the next edition is already on the way.

The conference is focused on Web technologies in Python. We got numerous positive feedback about the idea of uniting worlds of Django, Plone, Tornado, TurboGears and other web-related tools within one event, and that’s exactly the direction where the conference goes.

Continue reading “A PyCon You Can’t Miss”

Learnings of PyConDE 2016

In late October 2016, we organized the PyCon.de, the main Python developer conference in Germany. With four parallel tracks, it had over 50 activities by speakers and trainers from all around Europe. We started from scratch and made it happen within five insane months. However, it was not only luck that helped, but a good plan and budget that turned out to be quite accurate. I will gladly share some insights from our story and try to simplify the job for anyone planning something similar.

Continue reading “Learnings of PyConDE 2016”