PyCon DE & PyData Conference Playbook & Guidelines

This playbook is our public reference for how we run our volunteer-driven conference. By sharing our experience we hope to help others to run their own conference.

We aim to update and refine this playbook continuously. We always are motivated to share our knowledge and experience with others.

We are considerate in publishing guidelines and policies that could be misused and share them within the team (and future teams) of our volunteer organisation in out protected workspace. We act responsibly by not sharing confidential or private information,

How To Use

Fork this repository and adapt the content to your needs.

👉 See the full documentation

Attribution

This document draws on years of experience from organizing of running and co-organizing events since like PyCon DE, EuroPython, EuroSciPy and PyData Berlin.

These awesome people have contributed to content this documentation was built upon:

Aeneas Christodoulou: Video; Alexander CS Hendorf: Program, Steering, Office; Alina Lenhardt: Program, Communication; Anastasia: Communication; Anja Pilz: Program; Christopher Schultz: Program; Daniel Ringler: Infrastructure, Steering; Florian Wilhelm: Program; Julio Batista Silva: Diversity; Jurik Sommer: Program; Kristian Rother: On-Site; Lisa Andreevna Chalaguine: Program; Marisa Mohr: Program; Maryam Pourranjbar Mohr: Program; Matthias Hofmann: Program; Mihail Douhaniaris: Video; Mojdeh Rastgoo: Diversity; Naa Ashiorkor Nortey: Diversity; Nils Finke: Program; Nydia Medina: Diversity; Olakunle Olaniyi: Communication; Paula González Avalos: Diversity; Ricardo Kawase: Program; Sabine Reisser: Video; Sebastian Neubauer Reisser: Video, Steering; Shivam Singhal: On-Site; Theodore Meynard: Diversity, Swag; Valentina Scipione: On-Site;

We missed mentioning you?
We value all contributions to this project, including those made in the past. If you have contributed to community-driven conferences or this playbook in the past and would like to be acknowledged:

1. Open a pull request titled "Add [Your Name] to Contributors".
2. In the pull request description, briefly describe your contribution. For example:
   • "I helped organize 2022 in program"
   • "I contributed the section on volunteer management of this playbook"

We'll review your pull request and merge it if appropriate.

Documentation

The documentation is written in Markdown and rendered with MKDocs.

MKDocs is used to generate the documentation.
Read the documentation

Extra features are added with the Material for MkDocs theme.
MKDocs Material

Community Playbooks by Pioneers Hub

This playbook was created by Pioneers Hub based on the content of many awesome people. Pioneers Hub is an organization dedicated to building and nurturing communities of experts in tech and research. The goal is to facilitate knowledge sharing, collaboration, and innovation.

Check out the Pioneers Hub GitHub repository to check more templates and tools like this to build and maintain healthy communities.