pretalx / Pretalx

|logo|

.. image:: https://img.shields.io/github/workflow/status/pretalx/pretalx/Tests.svg :target: https://github.com/pretalx/pretalx/actions?query=workflow%3ATests :alt: Continuous integration

.. image:: https://img.shields.io/codecov/c/github/pretalx/pretalx.svg?colorB=3aa57c :target: https://codecov.io/gh/pretalx/pretalx :alt: Coverage

.. image:: https://img.shields.io/pypi/v/pretalx.svg?colorB=3aa57c :target: https://pypi.python.org/pypi/pretalx :alt: PyPI

.. image:: https://img.shields.io/badge/docs-passing-3aa57c :target: https://docs.pretalx.org/ :alt: Documentation

.. image:: https://img.shields.io/badge/news-blog-3aa57c :target: https://pretalx.com/p/news/ :alt: Website

.. image:: https://img.shields.io/twitter/url?label=Twitter&logoColor=%234aa57c&style=social&url=https%3A%2F%2Ftwitter.com%2Fpretalx :target: https://twitter.com/pretalx :alt: Twitter account

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 feature list_ on our main site to get a better idea of what pretalx can do for you, but it typically involves everything you'll need to curate submissions and contents for a conference with several tracks and conference days.

You can host pretalx yourself, as detailed in our administrator documentation, or use our public instance at pretalx.com. If you want to use pretalx, we recommend you follow our blog_, where we announce new versions and upcoming features.

📺 Look and feel

|screenshots|

Check out our feature list_ for more screenshots – or check the list of events_ to see how pretalx looks in the wild.

pretalx is highly configurable, so you can change its appearance and behaviour in many ways if the defaults don't fit your event. If the settings are not enough for you, you can even write plugins of your own.

🚦 Project status

pretalx is under active development_ and used by many events. It supports everything required for talk submission, speaker communication, and scheduling. You can see our supported features in the feature list, and our planned features in our open issues_. pretalx has regular releases – you can look at the changelog_ to see upcoming and past changes, and install pretalx via PyPI_.

🔨 Contributing

Contributions to pretalx are very welcome! You can contribute observations, bugs or feature requests via the issues. If you want to contribute changes to pretalx, please 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.

If you are interested in plugin development, check both our documentation and our list of plugin ideas_ in the project wiki.

💡 Project information

The pretalx source code is available on GitHub, where you can also find the issue tracker. The documentation is available at docs.pretalx.org, and you can find up to date information on our blog_ and Twitter. The pretalx package is available via PyPI.

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 [email protected] (who also runs pretalx.com_). See the CONTRIBUTORS file for a list of all the awesome folks who contributed to this project.

🧭 Users

If you want to look at conferences using pretalx, head over to the wiki for a list of events_. And if you use pretalx for your event, please add it to the list (or tell us about it, and we'll add it)!

.. |logo| image:: https://raw.githubusercontent.com/pretalx/pretalx/master/assets/logo.png :alt: pretalx logo :target: https://pretalx.com .. |screenshots| image:: https://raw.githubusercontent.com/pretalx/pretalx/master/assets/screenshots.png :target: https://pretalx.com/p/features :alt: Screenshots of pretalx pages .. _issues: https://github.com/pretalx/pretalx/issues/ .. _feature list: https://pretalx.com/p/features .. _developer documentation: https://docs.pretalx.org/developer/index.html .. _administrator documentation: https://docs.pretalx.org/administrator/index.html .. _pretalx.com: https://pretalx.com/ .. _active development: https://github.com/pretalx/pretalx/pulse .. _changelog: https://docs.pretalx.org/en/latest/changelog.html .. _PyPI: https://pypi.python.org/pypi/pretalx .. _DEPENDENCIES.rst: https://github.com/pretalx/pretalx/blob/master/DEPENDENCIES.rst .. _list of plugin ideas: https://github.com/pretalx/pretalx/wiki/Plugin-ideas .. _list of events: https://github.com/pretalx/pretalx/wiki/Events .. _many events: https://github.com/pretalx/pretalx/wiki/Events .. _our blog: https://pretalx.com/p/news/ .. _GitHub: https://github.com/pretalx/pretalx .. _docs.pretalx.org: https://docs.pretalx.org .. _Twitter: https://twitter.com/pretalx