We’re excited to invite you to this year’s General Assembly meeting! We’ll gather on Wednesday, 17 December 2025 20:00 CET, held online via Zoom. EPS membership is required to participate and additional joining instructions will be shared closer to the date.

You can find more details about the agenda of the meeting, as it is defined in our bylaws here:  https://www.europython-society.org/bylaws/ (Article 8).

One of the items on the Agenda is electing the new Board.

What does the Board do?

The Board consists of a chairperson, a vice chairperson and 2-7 other board members. The Board carries the Society’s legal and fiscal responsibility, but in practice the largest part of the workload revolves around one thing: EuroPython conference organisation.

Board members currently handle substantial parts of the planning, decision-making, coordination, and operational oversight of the conference. This requires:

• Understanding how the conference is structured and run
• Being able to work with volunteer teams and external partners
• Managing recurring issues around finances, logistics, and continuity

Beyond the conference, the Board also oversees membership, budgets, grants, infrastructure, and long-term planning and sustainability (including hiring an event manager, selecting future locations, strengthening outreach, managing trademarks, legal compliance, and many more).

Furthermore, specifically for 2026:

• Hiring the second part-time Event Manager in the EP2026 location.
• Finaid and reimbursements restructuring
• Building and coordinating the EP2026 Team.
  

Time Commitment

Serving on the Board is a volunteer role, and it does take a steady amount of time each week. There’s a 1.5-hour meeting every two weeks in the evening CE(S)T, plus a few hours of ongoing async work. Around conference season, things naturally get a bit busier than that.

If a member can’t commit that time, their tasks fall to others, so thinking carefully about your availability is really important.

Who Should Consider Running?

Working on the board means making decisions about various aspects of the conference. Therefore having experience being on previous EuroPython teams is necessary. Also, you will need to:

• Dedicate consistent weekly time
• Be willing to learn how the Society and the conference operate

It’s great if you can also bring some experience from other non-profits, community organising, or event work (helpful, but not mandatory)

How to Nominate Yourself

Email your nomination to board@europython.eu before 10 December 2025. In your nomination statement, please focus on your EuroPython experience - what you’ve already helped move forward or complete, and what you hope to work on in the next Board term. We will publish the list of candidates on 12 December 2025.

During the General Assembly, you will have the opportunity to introduce yourself and share with our members why you believe they should vote for you. Each candidate will typically be given one minute to present themselves before members cast their votes.

If you're on our EPS Organisers' Discord, there's a dedicated channel for interested candidates. Please ask in the general channel, and we’ll be happy to add you.

It sounds a lot, I want to help, but I can’t commit to that

That’s completely understandable! Serving on the Board comes with significant responsibilities, time commitments, and administrative tasks. If that’s not the right fit for you, but you’re still interested in supporting us, we’d love your help! There are many other ways to get involved. We have several workgroups (see 2025 Teams Description document, as an example) that work on conference preparations during the months leading up to the event, and we also need volunteers to assist onsite during the conference.

A warm welcome to Martin Borus as the second elected EuroPython Society Fellow in 2025.

EuroPython Society Fellows

EuroPython Society Fellows have contributed significantly towards our mission, the EuroPython conference and the Society as an organisation. They are eligible for a lifetime free attendance of the EuroPython conference and will be listed on our EuroPython Society Fellow Grant page in recognition of their work.‌

Martin has been part of the Europython Conferences volunteers since 2017.
Some have “met” him the first time in a response on an issue sent to the helpdesk or during the organisation meetings of the Ops team.
Others interacted with him as a volunteer at reception, out in the halls, a tutor in a Humble Data tutorial, a session chair, or a room manager in a tutorial or talk.
While pretending to be just an “On-site volunteer” or a member of the “Operations team” — over time, he has taken over not only the organisation of the registration desk, but also developed and orchestrated the training of session chairs.
He also expanded the programme with the informal session for first time conference attendees, which have been well received by all attendees.

The EuroPython Society Board would like to congratulate and thank all Fellows for their tireless work towards our mission! If you want to send in your nomination, check out our Fellowship page and get in touch!

Many thanks,
EuroPython Society
https://www.europython-society.org/

Hi everyone. Today, we are honoured to announce a very special recognition.

The EuroPython Society has posthumously elected Michael Foord (aka voidspace) as an Honorary EuroPython Society Fellow.

Michael Foord (1974–2025)

Michael was a long-time and deeply influential member of the Python community. He began using Python in 2002, became a Python core developer, and left a lasting mark on the language through his work on unittest and the creation of the mock library. He also started the tradition of the Python Language Summits at PyCon US, and he consistently supported and connected the Python community across Europe and beyond.

However, his legacy extends far beyond code. Many of us first met Michael through his writing and tools, but what stayed with people was the example he set through his contributions, and how he showed up for others. He answered questions with patience, welcomed newcomers, and cared about doing the right thing in small, everyday ways. He made space for people to learn. He helped the Python community in Europe grow stronger and more connected. He made our community feel like a community.

His impact was celebrated widely across the community, with many tributes reflecting his kindness, humour, and dedication:

• In memoriam on discuss.python.org
• My friend Michael by Nicholas Tollervey

At EuroPython 2025, we held a memorial and kept a seat for him in the Forum Hall:

• In Memoriam: Michael Foord (EuroPython 2025 session video)
• Photo of the reserved seat
  

A lasting tribute

EuroPython Society Fellows are people whose work and care move our mission forward. By naming Michael an Honorary Fellow, we acknowledge his technical contributions and also the kindness and curiosity that defined his presence among us. We are grateful for the example he set, and we miss him.

Our thoughts and thanks are with Michael's friends, collaborators, and family. His work lives on in our tools. His spirit lives on in how we treat each other.

With gratitude,
Your friends at EuroPython Society

The 2025 version of the EuroPython conference took place both online and in person in July 2025. This was the third conference under our current Code of Conduct (CoC), and we had Code of Conduct working group members continuously available both online and in person.

Reports

Over the course of the conference, the Code of Conduct team was made aware of the following issue:

• One person was uncomfortable with certain phrases being used in one of the poster sessions. The author was informed, and the phrases reported were removed by the author from their poster presentation promptly.

Thank you the Code of Conduct team responded to the issue reported.

In April, our top priority was to kick off discussions about the 2026 venue. We successfully launched the Call for Venues and are now actively working on choosing a new location for next year.

We also helped release the schedule and coordinated all the related activities.

On top of that, we worked with our event manager to confirm a few more details, sign contracts, handle billing, and take care of similar administrative tasks.

Individual reports:

Artur

• Sponsor management
• Various small infrastructure updates, mainly in our static files hosting and the internal discord bot.
• Adding data sync and parsing from pretalx and pretix to the internal discord bot.
• Call for venues 2026 and related calls with communities
• Regular sync with the event manager
• Program: coordination of the documentary premiere with producers

Mia

• Communications: migration to Canva; copywriting for social media & articles
• Call for Venues 2026: kick-off and calls with communities
• Payments
• Design: coordination of design items with the designer; reviews
• Website: PR reviews; page updates
• Grants program: communication with recipients and administrative tasks
• Community outreach: DjangoCon Europe
• Program: coordination of the documentary premiere with producers
• Regular sync with the event manager
• PSF Grant Work

Aris

• Ops team activities, meetings and planning
• Tickets/vouchers documentation and workflow
• Accounting updates
• Payments

Ege

• Promotional material orders for PyCon US: Stickers, Posters, Retractable roll up banner, laminated info sheets
• Website and Programme API updates
• PR reviews

Shekhar

• FinAid: Completed Round 1 of our Financial Aid Programme
• Visa Application Letter: Distribution and Management

Anders

• VAT Report for March

Cyril

• …

This year, for the first time, the EuroPython Society had a booth at PyCon US. 🎉

It was a great chance to meet people from other Python communities, catch up with old friends, and make some new ones. At our booth, we gave out stickers (including a sneak peek of our 2025 ones), talked about our grants programme, and shared what the Society has been up to.

PyCon US was also where something special was announced. The filmmakers from Cult Repo, formerly known as Honeypot, are working on a documentary about the history of Python and its vibrant community. It features over 20 core developers, from the early days of Python to the newest contributors. They showed a trailer during the opening session on the third day and announced that the premiere will happen at EuroPython!

We managed to take a group photo with some of us during the PyLadies auction, which many of us attended. With such a full schedule, it can be tricky to get everyone together, so we were happy to catch that moment.

Outside of the talks and sessions, we also spent some evenings together just hanging out and catching up. These moments are always a highlight of any conference.

We are especially happy to share that our chair, Artur Czepiel, received a community award. So did Laís Carvalho, a former board member, and Raquel Dou, a former chair.

Karolina Surma, a member of Czech PyLadies and the 2023 programme team, also received an Outstanding PyLady Award for her contributions to the PyLadies community in the Czech Republic

Congratulations to all of you and thank you for all the time and energy you give to the community!

Thank you to the PyCon US organisers for running such a fantastic event and for giving us space to be part of it.

Thank you to our board member Ege Akman for sorting out materials and helping get everything ready for the booth.

And a big thank you to everyone who stopped by to chat. It was a pleasure to meet you. See you next year!

Are you a community builder dreaming of bringing EuroPython to your city? The Call for Venues for EuroPython 2026 is now open! 🎉

EuroPython is the longest-running volunteer-led Python conference in the world, uniting communities across Europe. It’s a place to learn, share, connect, spark new ideas—and have fun along the way.

We aim to keep the conference welcoming and accessible by choosing venues that are affordable, easy to reach, and sustainable. As with the selection process in previous years, we’d love your help in finding the best location for future editions.

If you'd like to propose a location on behalf of your community, please fill out this form:

👉 https://forms.gle/ZGQA7WhTW4gc53MD6

Even if 2026 isn’t the right time, don’t hesitate to get in touch. We'd also like to hear from communities interested in hosting EuroPython in 2027 or later.

Questions, suggestions, or comments? Drop us a line at board@europython.eu—we’ll get back to you!

EuroPython Society Board

In March, we achieved two significant milestones alongside several smaller improvements and operational work.

We launched our ticket sales, dedicating substantial effort to setting up the ticket shop, coordinating with multiple teams, and promoting the event.

We also open our call for sponsors, investing considerable time in budgeting, setting up and improving the process, and onboarding our sponsors.

Individual reports:

Artur

• Budget projection updates
• Ticket launch and related activities.
• Sponsor setup update and managing some of the sponsor interactions
• Configuration upgrade of our static sever.
• Catering negotiations.
• Internal discord bot updates.
• Financial aid meetings.
• Billing flow updates.

Mia

• Website: Ticket requirements, PR review, and content updates.
• Design: T-shirt review, creation of social media assets for ticket sales and sponsors, and a briefing with a designer.
• Budget: Budget proposal.
• Sponsors: Cold emailing, sponsor packages, and coordination of the sponsor launch.
• Comms: Creation, review, and scheduling of content for the ticket sale launch and call for sponsors; speaker cards; automation proof of concept; International Women’s Day communications; newsletter writing and review; board report; and YouTube videos communications.
• PyCon US Booth: Coordination and paperwork.
• Grants Program: Communication with recipients.
• Venue: Re-signed contract.
• Calls with the event manager.
  

Aris

• OPS work, meetings, planning.
• Accounting updates.
• Billing workflow.
• Payments
  

Ege

• Read the Docs previews
• Programme API setup.
• Implementing a redirection system in the website.
• Dependency updates and tailwind migration.
• Website: issues and PR reviews.
  

Shekhar

• Financial Aid: Planned how to handle responses and evaluated the process.
• Ops: GitHub for task tracking and monitored integrations with team members.
  

Cyril

• …

Anders

• …
  

We, the EuroPython Society, were proud partners of Brno Python Pizza. Here’s what they shared with us about the event.

By now, the concept of combining Pizza and Python is well established and documented, it just works! But adding Brno into the mix makes it feel a little bit special for our local community. This was the second Pizza Python in Czechia, following the highly successful event in Prague.

While Prague set a high bar with its buzzing gathering of Python enthusiasts and pizza lovers, Brno brought its own unique flavor to the table, that was definitely no pineapple.

Attendees

We capped the event at 120 attendees — the comfortable maximum for our venue. While we didn’t require attendees to disclose gender or dietary info, we did include optional fields in the ticket form. Based on the responses, we had 99 men and 34 women registered, including both in-person and online tickets. Unfortunately, nobody ticked the box for non-binary or transgender options, which will serve as valuable information for future inclusivity improvements..

We also asked about dietary preferences so we could make sure everyone would be fed and happy. The majority (98) had no restrictions, but we were glad to accommodate 6 vegetarians, 6 vegans, 2 gluten-free eaters, 1 halal, and one “no bananas 🍌”. The last one was the hardest to accommodate because when we called up pizzerias and told them how many pizzas we would like, they thought we were certainly bananas…

The event ran smoothly, with no breaches of the Code of Conduct reported—a testament to the respectful and friendly atmosphere fostered by the community.

The menu

At Brno Python Pizza, we served up a feast sliced into 21 talks on the schedule, several lightning talks and plenty of opportunities to network. Each talk was kept short and snappy, capped at 10 minutes, ensuring a fast-paced and engaging experience for attendees. This is absolutely perfect for us that are having slightly underdeveloped focus glands. Not everyone likes mushrooms on their pizza, neither does everyone enjoy listening purely about AI advances. That’s why we curated a diverse menu of topics to cater to our diverse audience.

Feedback, Things to improve and the Future

From what we’ve gathered, people enjoyed the event and are eager to attend again. They enjoyed the food, talks and that topics were varied and the overall format of the event.

The feedback gathering is also the main thing to improve as we have only anecdotal data. For the next time we have to provide people with a feedback form right after the event ends.  

If you ask us today if we would like to organise another edition of Python Pizza Brno, we will say "definitely yes", but we will keep the possible date a secret.

Stream and more photos

Stream is available here and rest of photos here.

In February, our top priority was event logistics and organizational planning. We worked closely with our event manager, Anežka, on important aspects such as the venue, catering, and other logistics. We're happy to announce that the contract with the venue has been signed!

Another priority was budget planning. Our funding comes from ticket sales and sponsors. We reviewed fixed costs and discussed our strategy for this year. We want to keep the event as affordable as possible to allow more people to attend while also attracting sponsors. At the same time, we need to make sure that the event breaks even and remains financially sustainable in the long term. We also worked on defining sponsorship packages.

The third priority was onboarding the remaining co-leads and teams. Some board members are still involved in specific teams to support new co-leads and other newcomers. We're making sure that everyone has the support and tools they need to contribute.

Individual reports:

Artur

• Budget: Discussing different scenarios and overall plan for the budget.
• Sponsorship setup: Packages, team meetings and internal sponsorship flow and infrastructure
• Updates to the internal discord bot and the community voting app
• Community: Attending FOSDEM & Python Pizza Brno
• Finaid: onboarding and working out the plan for setup updates for 2025.
• Event logistics: Working with Anežka and the rest of the team on various items regarding different providers, contracts and payments.

Mia

• Comms & Design: worked on the design brief and budget proposal. Drafted and scheduled some community voting and reviews posts. Reviewed others. Comms & Design team calls. Website design coordination & calls.
• Budget: worked on the proposal & spreadsheets.
• Sponsorship: helped define sponsorship packages and pricing. Reviewed and helped prepare content for the web and other materials. Coordinated communication between multiple people.
• Infrastructure: code reviews.
• Community: attended Brno Python Pizza.

Aris

• Billing: Setup payments for grants and vendors
• Billing: Looked into the current billing workflow and how it can be optimized.
• Budget: Onboarding myself to the spreadsheet, looked and discussed the different scenarios
• Ops: Onboarding team members, capacity planning and kickoff meeting
• Community: Attending FOSDEM & Python Pizza Brno

Ege

• Transfer 2025 Discord server ownership to EPS account
• 22-24 website migration
• Website PRs
• Program API setup with the new deployment logic

Shekhar

• PR for Visa Application process for EuroPython 2025 Conference.
• Overviewing Budget sheet for EuroPython 2025 Conference
• Overviewing Grant programme and the existing proposals from various conferences.
• Finaid team coordination and helped launch the FINAID programme.

Cyril

• …

Anders

• …