The Code of Conduct Team is happy to share that we received no reports of potential code of conduct issues at PyLadiesCon 2025.

Publishing this report informs our work before, during, and after the conference. The report itself provides information about general team tasks, as well as incidents we handled.

The Code of Conduct and our Team

The PyLadiesCon Code of Conduct (CoC) and the workings of the team are directly taken from past events. For this year, there were eight active people on the team:

• Vicky Twomey-Lee (Lead)
• Cecilia Tivir
• Debbie Chou
• Jessica Greene
• Maaya Ishida
• Micaela Reyes
• Monica Iyabo
• Nathan Bransby

Before the conference

Our team had a few major tasks before the conference.

Preparing for the event

This generally meant doing anything we could ahead of the actual conference so our team could work as well as possible during the event:

• Getting up to speed with general Code of Conduct team practices
• Making sure we are familiar with moderation features across the different online platforms.
• Confirming availability so we know we will have some presence throughout the whole conference, in person as well as online (discord).
• All are registered on the PyLadiesCon Portal and assigned to Code of Conduct team

The way to report code of conduct issues for our teams was set up on our behalf by other organisers: conference_conduct@pyladies.com

For code of conduct incident reports handling, we may collect additional information about individuals mentioned in any reports. View our Code of Conduct response guidelines for more information.

During the conference

There were no incidents reported during the conference. Everyone involved played a part in fostering an excellent atmosphere throughout. The conference code of conduct was featured as an announcement channel of its own on the conference discord server, which helped set clear expectations for everyone.

After the conference

With the conference over, with no incidents reported during the event, our team’s remit was to:

• Keep an eye out for any report sent to us after the conference.
• Draft a report to PyLadiesCon organisers.
• Publish this transparency report.

Our takeaways for future events

With no incidents to report, the best we can do is to share our main takeaways for future event organisers to learn from:

• A good team makes hard work feel easy. Everyone chipped in, and had excellent support from organisers and other volunteers, especially when everyone is remote from around the world.
• This year’s process was different to last year’s. This year, the Code of Conduct team were more involved throughout the whole conference making themselves available in case any incidents arise. Make sure to know which channels on the discord server to monitor, in our case, it was predominantly:
  • #main-stream text channel
  • #main-stream-media live-stream channel
• Rostering: Work with the programme team to find out the schedule and build a roster around the times separately.

About this report

Even without any incidents to report on, we still believe publishing this report is a good way to show why our Code of Conduct is important, and how it is enforced in practice, in line with the transparency guidelines from the PyLadiesCon CoC committee. We hope that by publishing this, we will encourage people to report incidents in the future, and that other conferences can learn from our mistakes and our successes.

We welcome any feedback, and we would like to thank the PyLadiesCon community – attendees, speakers, sponsors, and organisers alike – for working with us.

We thank the organisers of DjangoCon Europe 2025 for their transparency report, which we followed as a template for this year’s report.

PyLadiesCon 2025 Code of Conduct team,

— Vicky Twomey-Lee (Lead), Cecilia Tivir, Debbie Chou, Jessica Greene, Maaya Ishida, Micaela Reyes, Monica Iyabo, Nathan Bransby

---