Humans of EuroPython: Diego Russo on volunteering, programme work, and community ties

EuroPython is a weeklong conference with multiple tracks, tutorials, keynotes, and sprints. Diego Russo worked on the Programme Team for EuroPython 2026 and describes the specific, often overlooked responsibilities that keep the event running smoothly. His account explains how programme planning shapes attendee experience and why volunteering is a practical path into the community.

Diego's responsibilities covered a broad set of programme operations: managing the call for proposals (CfP), the mentorship programme, speaker selection, the waiting list, and the conference schedule. He was also the liaison for the keynote session featuring Guido van Rossum, Łukasz Langa, and Pablo Galindo Salgado.

Concrete tasks included reviewing proposals, choosing which talks to accept, arranging mentors for newer speakers, maintaining an ordered waiting list, and assembling a schedule across several tracks so sessions don't conflict and the programme stays balanced.

The most crucial piece Diego emphasizes is the schedule. With multiple parallel tracks, organisers must balance topics so attendees with differing interests remain engaged. The team receives far more proposals than can fit into the programme. That surplus gives organisers choice but also forces difficult decisions about which proposals to accept.

Diego also highlights how volatile the schedule can be during the event. Last-minute cancellations are common. The team must reshuffle sessions quickly and sometimes find replacement speakers during the conference itself to avoid gaps.

Diego has used Python since 2006 and first attended EuroPython in 2011. He found the community welcoming and credits Python conferences with contributing to his career path. In 2022 he started volunteering to give back. After working with Communications and Programme teams, volunteering led him to deeper technical contribution: he now contributes to CPython as a Core Developer.

Surprises and corrections to common assumptions

Diego expected he lacked enough experience to volunteer, and that held him back at first. Once involved, he found the community made it easy to learn on the job. The concrete surprise he cites is how volunteering changes the conference experience: instead of merely attending sessions, volunteers see the people, coordination, and decisions that make the event happen. That shift produced a stronger sense of belonging.

Practical takeaways for potential volunteers

• You don't need perfect experience to start. Teams onboard willing contributors who learn while doing.
• Programme work is detailed and schedule-focused: expect to make many trade-offs when allocating session slots.

Diego's account is a practical snapshot of conference programme work: careful selection, meticulous scheduling, and behind-the-scenes crisis responses. For people who care about events or want to get involved with the Python community, his experience shows how volunteering offers training, responsibility, and stronger community ties.