Skip to content

Learn to run a PyCon (AU)

Jack Skinner edited this page Apr 18, 2026 · 1 revision

Over PyCon AU’s history, it's been quite common for future conference directors to be ‘in the organisers room’ during a previous organising effort. Sometimes volunteering in a particular role, and other times as a silent observer to watch and learn how the conference gets made.

There’s no formal committee or process for how to run a PyCon AU, or who steps up to do it. It’s an organic, conversational and collaborative process. While that's exciting to some, we realise it can be a little daunting to others, filled with ambiguity and uncertainty.

In 2026 we’re piloting an experiment called ‘the shadow team’. If you’re interested in helping run a future PyCon AU, the shadow team is an opportunity to ‘shadow’ the 2026 core team and learn what goes on behind the scenes. While its obligation free, we hope the shadow team will join us as silent participants in some fortnightly (and then weekly) meetings, review documents, and ask questions in a dedicated chat channel.

Importantly, our shadow team experiment is a silent participant: functionally it's a read-only role to most of PyCon AU organisers discord, with a dedicated space to ask questions and chat about your own ideas for future PyCon’s AU. Shadow team members aren’t expected to own decisions, contribute to ‘work’ or otherwise be contributing during calls.

Note: by default, the shadow team doesn’t include a free ticket to the conference. If your aspirations turn to fruition, we can probably figure something out.

Most importantly, to get all this started, reach out and say hi! Email contact@pycon.org.au to connect with the current conference directors to start a conversation.

Clone this wiki locally