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

• …
  

The top priority for the board in January was finishing the hiring of our event manager. We’re super excited to introduce Anežka Müller! Anežka is a freelance event manager and a longtime member of the Czech Python community. She’s a member of the Pyvec board, co-organizes PyLadies courses, PyCon CZ, Brno Pyvo, and Brno Python Pizza. She’ll be working closely with the board and OPS team, mainly managing communication with service providers. Welcome onboard!

Our second priority was onboarding teams. We’re happy that we already have the Programme team in place—they started early and launched the Call for Proposals at the beginning of January. We’ve onboarded a few more teams and are in the process of bringing in the rest.

Our third priority was improving our grant programme in order to support more events with our limited budget and to make it more clear and transparent. We went through past data, came up with a new proposal, discussed it, voted on it, and have already published it on our blog.

Individual reports:

Artur

• Updating onboarding/offboarding checklists for Volunteers and Board Members
• Started development of https://github.com/EuroPython/internal-bot
• Event Manager onboarding
• Various infrastructure updates including new website deployment and self-hosted previews for Pull Requests to the website.
• Setting up EPS AWS account.
• Working out the Grant Guidelines update for 2025
• Attending PyConWeb and FOSDEM
• Reviewing updates to the Sponsors setup and packages for 2025
• More documentation, sharing know-how and reviewing new proposals.

Mia

• Brand strategy: Analysis of social media posts from previous years and web analytics. Call with a European open-source maintainer and a call with a local events organizer about EP content.
• Comms & design: Call for proposal announcements, EP 2024 video promotions, speaker mentorship, and newsletter. Video production - gathering videos from speakers, video post-production, and scheduling them on YouTube shorts, and social media.
• Event management coordination: Calls with the event manager and discussions about previous events.
• Grants: Work on new grant guidelines and related comms.
• Team onboarding: Calls with potential comms team members and coordination.
• PR: Delivering a lightning talk at FOSDEM.
  

Cyril

• Offboarding the old board
• Permission cleanup
• Team selection
• Onboarding new team members
• Administrative work on Grants

Aris

• Worked on the Grants proposal
• Teams selection
• Follow-up with team members
• Board meetings
• Financial updates
• Community outreach: FOSDEM

Ege

• Working on various infrastructure updates, mostly related to the website.
• Reviewing Pull Requests for the website and the internal bot
• Working on the infrastructure team proposal.

Shekhar

• Timeline: Discussion with the Programme Team, and planning to do the same with the other teams.
• Visa Request letter: Setup and Test Visa Request Automation for the current year
• Team selection discussion with past volunteers
• Board Meetings

Anders

• ...

TL;DR:

• We are making small changes to the Grant Programme
• We are increasing transparency and reducing ambiguity in the guidelines.
• We would like to support more events with our limited budget
• We’ve introduced caps for events in order to make sure all grants are fairly given and we can support more communities.
• We’ve set aside 10% of our budget for the local community.
  

Background:

The EPS introduced a Grant Programme in 2017. Since then, we have granted almost EUR 350k through the programme, partly via EuroPython Finaid and by directly supporting other Python events and projects across Europe. In the last two years, the Grant Programme has grown to EUR 100k per year, with even more requests coming in.

With this growth come new challenges in how to distribute funds fairly so that more events can benefit. Looking at data from the past two years, we’ve often been close to or over our budget. The guidelines haven’t been updated in a while. As grant requests become more complex, we’d like to simplify and clarify the process, and better explain it on our website.

We would also like to acknowledge that EuroPython, when traveling around Europe, has an additional impact on the host country, and we’d like to set aside part of the budget for the local community.

The Grant Programme is also a primary funding source for EuroPython Finaid. To that end, we aim to allocate 30% of the total Grant Programme budget to Finaid, an increase from the previous 25%.

Changes:

• We’ve updated the text on our website, and split it into multiple sub-pages to make it easier to navigate. The website now includes a checklist of what we would like to see in a grant application, and a checklist for the Grants Workgroup – so that when you apply for the Grant you already know the steps that it will go through later and when you can expect an answer from us.
• We looked at the data from previous years, and size and timing of the grant requests. With the growing number and size of the grants, to make it more accessible to smaller conferences and conferences happening later in the year, we decided to introduce max caps per grant and split the budget equally between the first and second half of the year. We would also explicitly split the total budget into three categories – 30% goes to the EuroPython finaid, 10% is reserved for projects in the host country. The remaining 60% of the budget goes to fund other Python Conferences. This is similar to the split in previous years, but more explicit and transparent.

Using 2024 data, and the budget available for Community Grants (60% of total), we’ve simulated different budget caps and found a sweet spot at 6000EUR, where we are able to support all the requests with most of the grants being below that limit. For 2025 we expect to receive a similar or bigger number of requests.

We are introducing a special 10% pool of money to be used on projects in the host country (in 2025 that’s again Czech Republic). This pool is set aside at the beginning of the year, with one caveat that we would like to deploy it in the first half of the year. Whatever is left unused goes back to the Community Pool to be used in second half of the year.

Expected outcome:

• Fairer Funding: By spreading our grants out during the year, conferences that happen later won’t miss out.
• Easy to Follow: Clear rules and deadlines cut down on confusion about how much you can get and what it’s for.
• Better Accountability: We ask for simple post-event reports so we can see where the money went and what impact it made.
• Stronger Community: Funding more events grows our Python network across Europe, helping everyone learn, connect, and collaborate.

The board has been working tirelessly over the past month to bootstrap the organization of the 2025 conference and lead the Society toward a more sustainable and stable future!

In December, we focused on three main areas:

1. Onboarding
2. Hiring an Event Manager
3. Bootstrapping the 2025 conference

Onboarding:

All board members received access to the tools and resources they needed and went through important information in the board wiki to help everyone get started smoothly. We also had 6 board meetings.

Hiring an Event Manager:

This was a big priority and an important step for the future of the Society. We reached out to a candidate and we’re excited that they are interested to cooperate with us! We worked together to define their role, gathered resources for them, and drafted the first version of their contract. We are looking forward to working with them soon!

This is a big move toward making the Society’s future more stable and sustainable.

Bootstrapping the 2025 conference:

In December, we announced that the 2025 conference is happening in Prague. We also have a new website with a new logo. We defined team responsibilities, launched the Calls for Contributors, and promoted it within the EPS, the local community, and on social media. We reached out to our first co-leads to get things moving and currently we are onboarding our first team members.

Individual reports:

Artur

• Onboarding new board members - setting up access, sharing resources, setting up the board wiki and documentation
• Wrapping up the GA2024, and publishing missing records for GA2023
• Setting up the new server for EP websites
• Helping with the helpdesk migration
• Setting up new infrastructure for EP2025
• Coordinating the EP2025 conference launch
• Setting up the framework for the Event Manager - responsibilities and the paperwork
• Setting up Project Management tools for the Board/2025 Team.
• Board Meetings

Mia

• Finished all tasks and released videos and materials for GA 2023 and GA 2024.
• Went through the board Wiki and onboarded to board resources and tasks.
• Scheduled social media posts regarding the conference announcement and informed the local community about it.
• Updated the team descriptions document and the Calls for Contributors form, then launched the Calls for Contributors. Announced the Calls for Contributors internally and on social media. Delivered a lightning talk announcing the Calls for Contributors on the local meetup.
• Worked on the brand strategy: documented the current state and described personas. Analyzed our media and web presence, attendance data, community voting, and participant feedback. Researched similar-sized conferences for inspiration. Finally, created a 2025 brand proposal for the website and documented everything.
• Met with a CPython core developer to brainstorm ideas for the conference, followed by a meeting with the program co-lead.
• Reviewed previous venue contract discussions and compared the current contract to the previous one.
• Had a call with the event manager, helped define their role in the Wiki, and drafted the first version of the Letter of Engagement.
• Scheduled social media posts for the end of the year.

Cyril

• Onboarding to the board tasks (getting access, information on the tools used)
• Checked the 2024 GA recording for flare ups
• Updated the helpdesk instance and other infrastructure tasks
• Looked through the old tickets and tried to understand why they are open
• Set up part of the environments for the new teams
• Helped defining the context for the event manager job
• Looked through the old documents and provided cleaned up versions for part of the teams
• Prepared the responses from potential conference organisers for the selection
• Helped onboard the first Co-Leads

Aris

• Onboarding to the board resources and tasks
• Helped with the EM responsibilities and scope
• Feedback on the call to actions and co-lead recruitment
• Updated accounting information with info from the SEB accounts
• Board meetings

Ege

• Onboarding to the board tasks (getting access, information on the tools used)
• Launched the initial website for 2025
• Prepared call-to-action cards for the website (for CfC and pre-feedback form)
• Discussed the options for the new website/static server/repository structure
• Communicated with the PSF Trademarks Committee for the approval of the new logo variations
• Had a meeting with a CPython core developer to get feedback and explore ideas to improve EuroPython and EuroPython Society
• Discussed ideas for new EuroPython Branding

Shekhar

• Worked on EP Timeline Discussion and facilitation
• Helped to reach previous on-site volunteers for co-lead recruitment
• Board Meetings

Anders

• Initial board meeting
• Initiated data updates to local authorities

We’re happy to announce our new board for the 2024-2025 term:

• Anders Hammarquist
• Aris Nivorils
• Artur Czepiel (Chair)
• Cyril Bitterich
• Ege Akman
• Mia Bajić (Vice Chair)
• Shekhar Koirala

You can read more about them in their nomination post at https://www.europython-society.org/list-of-eps-board-candidates-for-2024-2025/. The minutes and the video recording of the General Assembly 2024 will be published soon.

Together, we will continue to serve the community and head off to the preparations for EuroPython 2025!

At this year’s EuroPython Society General Assembly (GA), planned for Sunday, December 1st, 2024, 20:00 CET, we will vote in a new board of the EuroPython Society for the term 2024/2025

List of Board Candidates

The EPS bylaws require one chair, one vice chair and 2 - 7 board members. The following candidates have stated their willingness to work on the EPS board. We are presenting them here (in alphabetical order by first name).

We will be updating this list in the days before the GA. Please send in any nominations or self-nominations to board@europython.eu. For more information please check our previous post here: https://europython-society.org/2024-general-assembly-announcement/

Please note that our bylaws do not restrict nominations to people on this list. It is even possible to self-nominate or nominate other candidates at the GA itself. However, in the interest of giving members a better chance to review the candidate list, we’d like to encourage all nominations to be made before the GA.

The following fine folks have expressed their desire to run for the next EPS board elections: Anders Hammarquist, Aris Nivorils, Artur Czepiel, Cyril Bitterich, Mia Bajić, Shekhar Koirala.

Anders Hammarquist

Pythonista / Consultant / Software architect

Anders is running his own Python consultancy business, AB Struse, since 2019 and is currently mostly involved with using Python in industrial automation. He has been using Python since 1995, and fosters its use in at least four companies.

He helped organize EuroPython 2004 and 2005, and has attended and given talks at several EuroPythons since then. He has handled the Swedish financials of the EuroPython Society since 2016 and has served as board member since 2017.

Aris Nivorlis

Pythonista / Geoscientist / Data Steward

Aris is a researcher at Deltares, a non-profit research institute in the Netherlands, where he combines his expertise in geoscience with his passion for Python and data stewardship to address real-world challenges. His journey with Python started during his doctoral studies, where he became a passionate advocate for the language and supported several colleagues in adopting Python for their research.

Aris has been involved in the Python community for the past four years. He is the Chair of PyCon Sweden and has been a core organizer for the past three conferences. He was a EuroPython organizer in 2024, leading the Ops Team, an experience he describes as both challenging and incredibly rewarding.

Aris is running for the EuroPython Society (EPS) Board to work in shaping its future direction. He is particularly interested on how EPS can further support local Python communities, events, and projects, while ensuring the success of the EuroPython conference. Aris aims to build on the foundation of previous efforts, working toward a more independent and sustainable organisation team for EuroPython. One of his key goals is to lower the barriers for others to get involved as volunteers, organizers, and board members, fostering a more inclusive and accessible society.

Artur Czepiel (nomination for Chair)

Software developer

I started using Python in 2008 and attended my first EuroPython in 2016, and it’s been an incredible journey ever since. Over the years, I’ve had the opportunity to contribute to five EuroPython conferences, including serving four terms on the board and chairing the conference last year.

Despite that, I still have new ideas for improvements and a couple of unfinished projects I’d like to see moving forward. :)

Cyril Bitterich

Operations dude / Organiser / Systems Engineer

Cyril’s first contact with the EuroPython community was back in 2019 in Basel during a break between workshops. Starting with helping prepare goodie bags, he went on to assist with setting up the conference location, and took on the role of a general runner during the event. After becoming a late addition to the Ops team in Dublin, he was part of the Ops and Programme teams for both Prague editions of the conference. His firefighting skills proved invaluable as he supported other teams and the general organisation, making him a de facto member of the 2024 core organisers team.

Enjoying the warmth of the community and gaining experience in a lot of different roles, it's now time for him to pass on the lessons he’s learned in a more structured way.  Having taken on smaller and ad-hoc leadership roles during the conference, he now aims to play an even more active role in the year-to-year operations of the EuroPython community.

With a background in successfully playing firefighter at organising capoeira events for 100 to 2000 attendees at locations all over the world (Asia and Antarctica are still on the to-do list 😉), and working with leaders, teams and attendees from diverse cultures, his knowledge and experience extend far beyond the last 3 years of EuroPython conference.

His goal is to bring more structure to the EPS as a whole and the conference teams where needed. A key focus is ensuring effective communication, be it through improving documentation or maintaining open and regular dialogue with the teams and everyone else involved Ultimately, he aims to help strike a healthy balance between the community-driven, volunteer spirit with the  professionalism expected from an established conference like EuroPython. However, the aim is not to disrupt or rebuild everything from scratch. Instead, he seeks to build on the strong foundation established by the board members active in the last years - while shamelessly taking full advantage of their counsel along the way.

This should establish a stable foundation within the EuroPython Society that can be adopted or directly used by other local communities in Europe. On the EPS side, this will hopefully open up resources to support other communities based on their specific needs.

Ege Akman

Pythonista / Open Source Advocate / Student

(Nomination added after Ege's election to the board at GA 2024.)

I started using Python in 2019 and have since had the opportunity to support several Python communities and initiatives.

In 2021, I initiated the Python in Turkish project, aiming to translate the Python Documentation into Turkish with the help of our amazing Python Turkey community.

In 2023, I began contributing to the Python Docs Work Group, where we focused on topics including infrastructure, tooling, content, and translations for docs.python.org.

In the summer of 2023, I discovered EuroPython! Witnessing people dedicate their time and effort to make the conference happen truly amazed me. Meeting some of the most incredible people in the universe at EuroPython inspired me to give back and contribute to the organization.

In 2024, I was part of the Operations Team, primarily working on our website, Program API, and Discord bot. This year, I ran for the board to learn and contribute in any way I can. Some areas I want to focus on include creating a more sustainable and efficient infrastructure, fostering greater collaboration and outreach to universities, and building an openly accessible knowledge base for conference organizers.

Mia Bajić

Software Engineer & Community Events Organizer

I’m a software engineer and community events organizer. Since joining the Python community in 2021, I’ve led Pyvo meetups, brought Python Pizza to the Czech Republic, and contributed to PyCon CZ 23 as well as EuroPython 2023 & 2024. I've spoken on technical topics at major conferences, including PyCon US, DjangoCon, EuroPython and many other PyCons across Europe.

I’m running for the board to learn, grow, and give back to the community that has given me so much. The main topic I would like to focus on is sustainability. I value setting clear goals, fostering open and transparent culture, and delivering measurable results.

Inspired by the folks from the Django Software Foundation, I decided to share more about my background, motivations, and small improvements I’d like to see implemented this year on my blog: https://clytaemnestra.github.io/tech-blog/eps-elections.

Shekhar Koirala

Machine Learning Engineer

I joined EuroPython as a remote volunteer in 2022 and later became part of the onsite volunteer team in Dublin the same year. Over the past two years, I’ve worked with the Ops team, supporting other onsite volunteers. My volunteering experience also includes contributions to Python Ireland and PyData Kathmandu. This year, I attended PyData Amsterdam, PyCon Sweden, and a non-Python volunteer-led conference in Berlin, Germany, where I sought to understand what truly makes a conference great. I realized that, at the core, it’s the people and their love for the community that make a conference exceptional.

Whether or not I join the board, I will continue volunteering for EuroPython. But if I am selected as a board member, I aim to support volunteers and foster a wholesome environment, just as I have always experienced. I also want to strengthen the connection between EuroPython and the local community.

Professionally, I work as a Machine Learning Engineer at Identv, using Python for both work and hobbies. Recently, I delivered a talk and conducted a workshop at PyCon Ireland, and I’m excited to kickstart my open-source journey. Beside sitting in front of the computer, I love to hike, take photos and try not to get lost in the wild.

What does the EPS Board do ?

The EPS board is made up of up to 9 directors (including 1 chair and 1 vice chair); the board runs the day-to-day business of the EuroPython Society, including running the EuroPython conference series, and supports the community through various initiatives such as our grants programme. The board collectively takes up the fiscal and legal responsibility of the Society.

For more details you can check our previous post here: https://europython-society.org/2024-general-assembly-announcement/#what-does-the-board-do

We’re excited to invite you to this year’s General Assembly meeting! We’ll gather on Sunday, December 1st, 2024, from 20:00 to 21:00 CET. Just like in recent years, we’ll use Zoom, and additional joining instructions will be shared closer to the date.

The General Assembly is the highest decision making body of the society and EPS membership is required to participate. Membership is open to individuals who wish to actively engage in implementing the EPS mission. If you want to become a member of EuroPython Society you can sign-up here: https://www.europython-society.org/application/

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 Board members. The duties and responsibilities of the Board are substantial: the board collectively takes up the fiscal and legal responsibility of the Society.

A major topic is the annual EuroPython conference. While we would like to transition to a model with an independent organising team, we are not there yet. Therefore, the Board still needs to be involved in the conference organisation.

Beyond the conference, the Board also manages several critical areas, including:

• Managing EPS membership
• Overseeing finances and budgets
• Running the grant programme
• Maintaining infrastructure and resources

Furthermore, specifically for 2025, and following the recommendation from the previous Board, we would like to focus on four key topics that are important for the Society's future and sustainability:

• Hiring an Event Manager/Coordinator
• Selecting a location for 2026 and possibly 2027
• Strengthen community outreach
• Improving the fiscal and legal framework

Time Commitment

The Society is entirely volunteer-driven and serving on the board requires a significant time commitment. Everyone has a different schedule, so most of the work is usually done asynchronously. However, all board members attend the 1.5-hour board call held every two weeks in the evening, CE(S)T timezone. Everyone's time is valuable and please consider that the less time or effort you can dedicate, the more the workload may shift to other Board members.

All things considered you will need a few hours every week.

Who should apply?

You want to invest your time and knowledge into building a better structure for the EuroPython Society? Or you want to work on building connections between different Python-based communities? Then this might be for you! Please keep in mind the time commitments mentioned above.

You are not expected to be perfect in any of the skills needed and you will be supported in learning how things work. That being said, having experience in a non-profit organisation, whether within the Python world (such as EPS, PSF, DSF, local Python communities etc.) or any other similar organisation, would be beneficial for onboarding and understanding the organisational structure, culture and dynamics.

In the past having or willing to learn the following skills helped organising the conference:

• Good communication skills
• Organisation skills
• Experience organising events with more than 1000 people
• Working with volunteer-based communities
• Working in big teams

Why should you apply?

You get the chance to shape and influence the future of EuroPython

You gain skills useful to run non-profits in different European countries - including cross border challenges

You can help grow and empower local communities

You can build relationships and connections with fellow community members

You can build a more diverse and inclusive Python community by serving the mission of EuroPython Society

I am interested, what should I do?

If you’re considering running for the Board or nominating another EPS member, we’d love to hear from you! Although the formal deadline is during the General Assembly, we kindly request you send your nomination as early as possible to board@europython.eu. We will publish the initial list of candidates on Tuesday, 26th of November 2024. If you’re not sure if this is a good idea or not – please email anyway and we will help you figure it out! 🙂

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.

You can find examples of previous nominations here: https://www.europython-society.org/list-of-eps-board-candidates-for-2023-2024/.

Your nomination should highlight why you want to run for the Board. What is your vision for EPS and in which projects you want to be involved. 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.

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 teams (see 2024 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.

Your help does not need to be limited to the conference. Infrastructure and connections need to be maintained all around the year for example. Your time and support would make a big difference! Stay tuned to our social platforms for announcements about these opportunities.