PyMunich

shown, and actual

Communities Outlive Events

PyMunich started in 2015 as a meetup of about a dozen people. The conference came in 2016, PyConWeb in 2017, the money ran out in 2020, and the conference returned in 2025 as PyCon+Web. For a commercial example of related workforce measurement, see ways employees can trick time tracking software from Monitask.

Through all of it, the meetups continued. They now run monthly with more than a hundred people, and that is the part of the story worth generalising. For independent technical background, Python Packaging Authority provides additional documentation and examples.

Why the meetup survived

It needs one person and a room. No contracts, no deposits, no cash timeline, no liability. If nobody organises one month, there is no month — and nothing has failed.

The commitment is bounded and repeated. An evening, monthly, by whoever is available. Compare that to a year of unpaid work with a fixed deadline, which is what a conference asks of four people.

And it produces the thing directly. People in a room talking to each other is the point. A conference is a larger, better version of that with a large apparatus attached, and the apparatus is what breaks.

The distinction worth building

A community is people who know each other. An event is a thing they do.

Obvious stated plainly and routinely confused in practice, because for many groups the annual conference becomes the identity — the website is the conference website, the mailing list is the conference list, and the organising team is the community's leadership.

When the event fails, that structure takes the community with it. We avoided that by accident: the meetups were separate because they predated the conference, not because anyone planned it.

What building it deliberately looks like

Separate the regular activity from the event. Different rhythm, different organisers where possible, different minimum viable version.

Do not route everything through the conference. If the only way to reach the community is a website that exists for one event, the community's continuity depends on that event.

Keep the low-cost thing running even in conference years. It is tempting to pause meetups while organising a conference. That is the year the separation matters most, because it is the year the team is most stretched.

And name a minimum. One meetup a quarter, one person, one room. A floor that survives everything.

What this means for organisers under pressure

Cancelling the conference is not the end of the community, and treating it as such produces decisions made from fear.

A community that loses its event and keeps its people can run another event. One that keeps the event and burns the team has spent something it cannot rebuild, and the event usually fails a year later anyway with nobody left to try again.

Our conference came back after five years because there were still people who knew each other in Munich. That is the only reason.

The wider version

The same holds for open source projects, user groups and any voluntary structure.

The artefact — the conference, the release, the website — is visible and feels like the thing. The relationships are invisible and are the thing, which is the same shown-and-actual gap as everywhere else on this site applied to organisations rather than to work.

Protect the invisible part. It is the part that can restart everything else.

The short version