pretalx is a conference planning tool focused on providing the best experience for organisers, speakers, reviewers, and attendees alike. It handles the submission process with a configurable Call for Participation, the reviewing and selection of submissions, and the scheduling and release handling. After the event, pretalx allows speakers to receive feedback, upload their slides, and organisers to embed recordings.
Read our extensive feature list in our docs to get a better idea of what pretalx can do for you, but it probably involves everything you'll need to curate submissions and contents for a conference with up to 200 talks.
You can host pretalx yourself, as detailed in our administrator documentation, or use our public instance at pretalx.com.
pretalx is under active development. It supports everything required for talk submission, speaker communication, and scheduling. You can see our supported features in the feature list in our documentation, and our planned features in our open issues. pretalx has regular releases – you can download the latest releases with their respective changelogs on GitHub or install pretalx via PyPI.
Previous conferences using pretalx include:
- NorthSec 2019
- Journées du Logiciel Libre 2019 (a good example of our French localisation)
- EasterHegg 2019
- PrivacyWeek 2018
- hack.lu 2018
- DjangoCon 2018
- OsmoDevCon 2018
- GPN 2018
- EasterHegg 2018
- TROOPERS 2018
- MRMCD (2017, 2018)
- Note
- If you use pretalx for your event, please tell us about it!
If you want to contribute to pretalx, please choose an issue and comment on it if anything is unclear. If you find bugs you want to fix yourself, please also open an issue for documentation purposes.
Check our developer documentation on how to set up pretalx and get started on development. Please bear in mind that our Code of Conduct applies to the complete contribution process.
We publish pretalx under the terms of the Apache License. See the LICENSE file for further information and the complete license text. The licenses of all dependencies are documented in the DEPENDENCIES.rst file.
The primary maintainer of this project is Tobias Kunze <r@rixx.de>. See the CONTRIBUTORS file for a list of all the awesome folks who contributed to this project.