Help us build the next edition!
summary
EuroPython moves to a workgroup model that runs many tasks remotely, reuses the Florence conference codebase for the website, and runs talk selection with a talkboarding preference algorithm rather than a closed committee. Organizers build prelaunch sites, use mailing lists and Trello, and handle ticket sales and sponsorship (about €175–180k this year). The model works enough to put a 1,100‑attendee conference together in six months but reveals inactive members, VAT and finance wrinkles, and room for voting and diversity improvements.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:13EuroPython 2016
- 0:31EPS: Short intoduction
- 1:16Purpose of the EPS
- 9:27Conference development
- 10:39The EuroPython Workgroups
- 16:25Teams (2/4)
- 17:45Guidelines
related talks
33mKeynote: Welcome & Opening Remarks
07mOpening remarks
30mDeciding between continuity and change in your Open Source community
30mInternational cooperation within the Python community
05mLightning Talk: One Year of Meeting C++ Online
49m"State of Django" Panel
01h 34mOWASP AppSec EU 2018 Leaders Meeting
34mWhat TODO in the EU: Updates from the TODO Group European Chapter