Conference planning tool: CfP, scheduling, speaker management

Overview

pretalx logo

Continuous integration Coverage PyPI Documentation Website 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 of pretalx pages

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)!

Comments
  • Report Median Review Score

    Report Median Review Score

    Problem you are facing

    Mean is a poor metric for summarising scores from multiple sources. Particularly with small numbers of reviewers. Since the mean allows a single reviewer who either hates or loves something to completely swing the score.

    Possible Solution

    A better metric is median. An alternative is mean, dropping best and worst.

    Context

    I was looking at what talks to accept for our conference. Our nominal cutoff is a score of 4. I was double checking those that were boarderline. The first one checked was scored 5, 4, 4, 4, 2, so net score of 3.8 I'ld rather be ignoring that 2 and 5 and be seeing it summarised as 4. Then when sorting it would have appears in the area of "definately accept", not "boarderline"

    size: small type: feature stage: up for grabs help wanted good first issue 
    opened by oxinabox 22
  • Reviewers can see current talk score in anonymous mode

    Reviewers can see current talk score in anonymous mode

    Current Behavior

    When navigating to event/<eventname>/reviews, if a submission has at least one review, the current score is revealed.

    Expected Behavior

    A reviewer should not be able to see comments or review scores for submissions that have not been reviewed.

    Steps to Reproduce

    1. Submit a talk into the system
    2. Review a talk at least once
    3. Create a new reviewer account
    4. Access the event/<eventname>/reviews page
    5. The current score is visible

    Context

    Ideally, a new reviewer coming into review submissions should not see the reviewers of any other reviewer. This is currently available given that individual review comments and rankings cannot be seen on any one submission before review, but the aggregate score is still visible on the submission list on the review screen.

    Your Environment

    Testing project on pretalx.com, v0.9.0

    type: bug size: small type: feature stage: up for grabs 
    opened by glasnt 19
  • Use Google Tag Manager in Pretalx

    Use Google Tag Manager in Pretalx

    Problem you are facing

    I want to include a Google Tag Manager Container in Pretalks

    Possible Solution

    Offer an option to add custom JS globally.

    Context

    We're using a couple of services on our website for tracking (Google Analytics) and support (Intercom) that rely on Java Script snippets to be injected in the website. Is that possible with Pretalx today already? Is that something that is planned?

    size: regular type: feature stage: up for grabs help wanted 
    opened by mseibert 14
  • Developer onboarding: create_test_event fails

    Developer onboarding: create_test_event fails

    Current Behavior

    Following https://docs.pretalx.org/developer/setup.html, after running the migrate and init steps, the create_test_event fails:

    Traceback (most recent call last):
      File "manage.py", line 10, in <module>
        execute_from_command_line(sys.argv)
    .
    .
    .
      File ".../pretalx/.env/lib/python3.7/site-packages/sass.py", line 738, in compile
        raise CompileError(v)
    sass.CompileError: Error: File to import not found or unreadable: .../pretalx/src/static.dist/agenda/scss/main.scss.
            on line 3:1 of stdin
    >> @import ".../pretalx/src/static.dist/agenda/scss/main.scss";
       ^
    

    Expected Behavior

    Either that command should succeed, or another preparatory step should be named in the documentation.

    Workaround (and Possible Fix)

    After init, run tox -e dev manage.py collectstatic. Then, create_test_event succeeded.

    Environment

    • Version used: git master
    • Environment name and version: Python 3.7
    • Operating System and version (desktop or mobile): Debian (testing)
    opened by shaib 14
  • [orga] Allow hiding of notes to organiser

    [orga] Allow hiding of notes to organiser

    It's now possible to hide the notes to organiser in the review phases. Those comments might uncover details that are meant for the organiser and not for the reviewer.

    How Has This Been Tested?

    Tested manually within the dev environment. Checked if a user with "is reviewer" permissions can see/cannot see the notes.

    Checklist

    • [x] My code follows the code style of this project.
    • [ ] My change requires a change to the documentation.
    • [ ] I have updated the documentation accordingly.
    • [ ] I have added tests to cover my changes.
    • [ ] All new and existing tests passed.
    • [ ] My change is listed in the CHANGELOG.rst if appropriate.
    opened by vmx 14
  • Automated build on Docker Hub

    Automated build on Docker Hub

    Problem you are facing

    Currently in order to use pretalx, you must build the image yourself. However getting updated requires you to manually check this repository for updates and re-pull and build the docker image periodically.

    Possible Solution

    I am suggesting that in addition to the pretalx-docker which has some great scripts and documentation, that pretalx be added to the Docker Hub and enable an automated build so that whenever an update is pushed to pretax the container is also updated.

    Context

    This will greatly assist in on-boarding new installations as well as allow for easier updates for existing Docker user.

    opened by lanrat 13
  • password reset emails don't get sent

    password reset emails don't get sent

    Current Behavior

    on password reset emails do not get sent, and do not show up in the history of sent emails

    Expected Behavior

    on password reset emails DO get sent, and show up in the history of sent emails

    Steps to Reproduce

    Your Environment

    • Version used: pretalx ยท v1.0.3 (using external SMTP server with authentication)
    • Environment name and version (e.g. Chrome 39, python 3.5): any browset
    • Operating System and version (desktop or mobile): any
    • Link to your instance, if in production: https://pretalx.tox.zoff.cc/toxcon2019/cfp
    opened by zoff99 12
  • Update docker install - Don't run as root

    Update docker install - Don't run as root

    • Don't run as root, run as uid 999
    • Bind on port 8000
    • change pycopg2 to pycopg2-binary (removes warning of future deprecation)

    Checklist

    • [x] My code follows the code style of this project.
    • [x] My change requires a change to the documentation.
    • [x] I have updated the documentation accordingly.
    • [ ] I have added tests to cover my changes.
    • [ ] All new and existing tests passed.
    • [ ] My change is listed in the CHANGELOG.rst if appropriate.
    opened by morisson 12
  • Anonymous reviews

    Anonymous reviews

    While sometimes it may be useful to see speakers to know how knowledgeable a submitter is, it doesn't fit the workflow of many conferences requiring anonymitiy to avoid discrimination and talk choices based on speakers rather then content. Hiding the speakers from the reviewers should be a review setting, and I'd argue that anonymisation should be the default.

    size: regular type: feature stage: up for grabs 
    opened by rixx 12
  • Non-admin can't see Items that are linked but are not scheduled.

    Non-admin can't see Items that are linked but are not scheduled.

    Problem you are facing

    I have a list of linked to items that are not on the schedule, but that i want people to be able to read. For example one of the many links in this list, is to this page

    I (having admin privs), can read them without issue (and I therefore thought everything was fine. But it turns out that only i can see them, for everyone else (including the authors) the page 404s. I thought turing on sneak-peak would fix this. But it didn't.

    Possible Solution

    Make sneakpeak allow the talk page to always be visable, regardless of if the event is now public and regardless of if it appears in the program.

    Context

    JuliaCon uses Pretalx for the review process of posters as well as scheduled talks. Posters do not occur at a specific time, but rather in a poster sesssion, which occupies a room for 1.5 hours.

    So we just put in a program item called Poster Session, and then we put in a list of all the items that are during it. And since i found the talk pages worked (for me), I thought better yet, I can link to those pages and then people will see the descriptions and everything. (Last year we did not link to the pages, we just gave the title and the author).

    We don't want to put them in the schedule because:

    1. it would confuse people into thinking they were at a particular time
    2. having 18 items in 1.5 hour block would be unreadable. (Per other issues having 9 items in a 1.5 hour block is almost unreable)
    type: bug 
    opened by oxinabox 11
  • Migration failed: AttributeError: 'NoneType' object has no attribute 'subject'

    Migration failed: AttributeError: 'NoneType' object has no attribute 'subject'

    I try to upgrade a docker based pretalix v0.7 setup to latest v1.1 but the migration step failed with following traceback:

    โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”“
    โ”ƒ โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”“  pretalx v1.1.2                                        โ”ƒ
    โ”ƒ โ”ƒ  โ”Œโ”€ยทโ”€โ”€โ•ฎ  โ”ƒ  Settings:  /etc/pretalx/pretalx.cfg                   โ”ƒ
    โ”ƒ โ”ƒ  โ”‚  O โ”‚  โ”ƒ  Database:  pretalx (mysql)                            โ”ƒ
    โ”ƒ โ”ƒ  โ”‚ โ”Œโ”€โ”€โ•ฏ  โ”ƒ  Logging:   /var/lib/pretalx/logs                      โ”ƒ
    โ”ƒ โ”ƒ  โ””โ”€โ”˜     โ”ƒ  Root dir:  /usr/lib/python3.6/site-packages/pretalx   โ”ƒ
    โ”ƒ โ”—โ”โ”โ”โ”ฏโ”โ”ฏโ”โ”โ”โ”โ”›  Python:    /usr/bin/python3                           โ”ƒ
    โ”—โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”โ”›
    Operations to perform:
      Apply all migrations: auth, authtoken, common, contenttypes, event, mail, person, schedule, sessions, submission
    Running migrations:
    Traceback (most recent call last):
      File "/usr/lib/python3.6/runpy.py", line 193, in _run_module_as_main
        "__main__", mod_spec)
      File "/usr/lib/python3.6/runpy.py", line 85, in _run_code
        exec(code, run_globals)
      File "/usr/lib/python3.6/site-packages/pretalx/__main__.py", line 9, in <module>
        execute_from_command_line(sys.argv)
      File "/usr/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
        utility.execute()
      File "/usr/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
        self.fetch_command(subcommand).run_from_argv(self.argv)
      File "/usr/lib/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
        self.execute(*args, **cmd_options)
      File "/usr/lib/python3.6/site-packages/django/core/management/base.py", line 364, in execute
        output = self.handle(*args, **options)
      File "/usr/lib/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
        res = handle_func(*args, **kwargs)
      File "/usr/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
        fake_initial=fake_initial,
      File "/usr/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
        state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
      File "/usr/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
        state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
      File "/usr/lib/python3.6/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
        state = migration.apply(state, schema_editor)
      File "/usr/lib/python3.6/site-packages/django/db/migrations/migration.py", line 121, in apply
        operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
      File "/usr/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards
        self.code(from_state.apps, schema_editor)
      File "/usr/lib/python3.6/site-packages/pretalx/event/migrations/0019_auto_20190224_0856.py", line 15, in fix_update_template
        template.subject = UPDATE_SUBJECT
    AttributeError: 'NoneType' object has no attribute 'subject'
      Applying event.0019_auto_20190224_0856...
    

    Any suggestions what I've missed or how to fix it?

    opened by xoxys 11
  • Room GUID interface is unintuitive and majorly annoying

    Room GUID interface is unintuitive and majorly annoying

    The room GUID feature is an extremely niche use case in pretalx, and not well-supported in the UI. Things we should do:

    • [ ] Hide it behind an "Advanced settings" fold
    • [ ] explain the expected format (not everybody knows what a UUID looks like)
    • [ ] offer a UUID generator button in the frontend
    size: small stage: up for grabs type: ux help wanted good first issue 
    opened by rixx 0
  • Creating an access code with a space leads to URL (and the ability to edit or delete codes) not to work.

    Creating an access code with a space leads to URL (and the ability to edit or delete codes) not to work.

    Problem and impact

    We've created different access codes for tracks at MozFest. Some of these were created with a space in the code field.

    After creating these codes, the links do not work as the space isn't encoded. After realising the mistake, we're then unable to delete or edit the access codes.

    Expected behaviour

    Either an error message is displayed, and I'm unable to save an access code with a space - or that the spaces in an access code are encoded so the URL.

    Steps to reproduce

    1. Create an access code that contains a space
    2. Copy generated URL and try to access link
    3. Try to edit or remove the link
    4. See 404 error

    Screenshots

    No response

    Link

    No response

    Browser (software, desktop or mobile?) and version

    No response

    Operating system, dependency versions

    No response

    Version

    No response

    type: bug 
    opened by marcwalsh 0
  • Compare timelines across events

    Compare timelines across events

    Organisers can get a bit antsy when submissions don't start rolling in, despite knowing that speakers tend to submit on the last day. It would be cool to extend to current timeline statistics, which only cover one event, to be able to compare multiple events and their submission stats.

    We'd compare total submissions (not filtered by track, etc), over time as defined by distance to the final deadline.

    size: regular type: feature stage: up for grabs help wanted good first issue 
    opened by rixx 0
  • Handle competing proposal notification emails

    Handle competing proposal notification emails

    Reviewers sometimes first mark a talk as accepted, then as rejected (or the other way around). For both actions, an email is generated and placed in the outbox. If organisers don't notice this, both emails will be sent out, which is very much not great.

    We don't currently have enough knowledge to fix this, since pretalx doesn't remember which proposal an email is sent for, so there's an easy and a hard solution here:

    1. Warn organisers when accepting a rejected proposal / rejecting an accepted proposal, that they'll have to delete the incorrect email, and link to the corresponding filtered search.
    2. Start connecting submission objects to QueuedMail objects, so that we can just take care of this in the background.

    We definitely want to implement the latter in the end, but we may start out with the former just to get a fix under way.

    size: small size: regular type: feature stage: up for grabs help wanted good first issue 
    opened by rixx 0
  • Assign review teams in reviewer assignments page

    Assign review teams in reviewer assignments page

    pretalx has two mechanisms to assign reviewers to proposals:

    • they can be assigned personally, either assigning proposals to reviewers or reviewers to proposals
    • they can be assigned in groups, by assigning tracks to teams

    The latter is often more handy, but it's "hidden" away in the team settings, whereas the former is more discoverable, but also way more annoying. We should promote the team to track assignments on the reviewer assignments page fairly prominently.

    size: small type: feature stage: up for grabs help wanted 
    opened by rixx 0
Releases(v2.3.1)
  • v1.0.3(Jun 26, 2019)

  • v1.0.1(Jun 3, 2019)

  • v0.8.0(Sep 23, 2018)

    Released n 2018-09-23

    Breaking changes

    • The URLs for schedule exports have changed from /myevent/schedule/export?exporter=exportername to /myevent/schedule/export/exportername โ€“ if you have hardcoded links to schedule exporters, please update them accordingly.
    • pretalx now doesn't support usernames any longer โ€“ as email addresses were already required for accounts, they are now the only means of logging in. This may confuse a few users โ€“ as an administrator, you can look up users' email addresses if they don't remember them, or change them, if necessary.

    New features

    • A human-readable time until the CfP closes is now displayed next to the end time. (#213)
    • As an organizer, it is now possible to send an email to all reviewers in the Compose Mail section. (#454)
    • In exports, HTTP Etags are now supported to allow for more aggressive caching on clients. (#492)
    • Organisers can now also reset the password for the speakers they have access to.
    • Present a public list of talks and a list of speakers.
    • The submission list now includes a graph of submissions over time.
    • The sneak peek / is_featured flag is now shown in the submissions and talk API endpoints.
    • You can now use your authentication token to access all pages you have access to, not only the API. This makes integration of exports much easier.
    • When using paper cards to build a schedule, each card comes with a QR code link to a quick scheduling form for that submission. (#240)
    • Before releasing a new schedule, the user is now shown any warnings and what the public changelog will look like.
    • The schedule editor shows warnings on scheduling conflicts, including live feedback on where a talk can be placed. (#214)
    • The review dashboard now features the same search and filter options as the submission list. (#474)
    • You can now add minimum or maximum length restrictions to abstracts, descriptions, speaker biographies, and all text-based questions. (#408)
    • When linking to a talk on social media, the talk image is now shown.
    • French translation
    • The event logo is displayed larger and up to the full width of the document below. Please check that your event still looks as intended after upgrading.
    • Allow to order rooms manually. (#149)
    • Allow to order questions manually. (#149)
    • Instead of setting a flag somewhere, pretalx now has an explicit "go live" button. There is also a corresponding signal plugins can listen to (please refer to the plugin documentation for further information).
    • For organisers, the submission/talk API endpoints now contain the question answers given by the speakers.
    • Schedules now contain a search bar to filter talks by title or speaker.
    • Schedules now feature a sidebar navigation to jump directly to a selected day.
    • Allow organisers to configure which of the default CfP fields to request and require. Please check your settings after updating, as the migration is not guaranteed to work as expected.
    • Prevent organisers from adding a non-localhost mail server without transport level security to make sure our Privacy Policy holds true.
    • Allow organisers to trigger a password reset for team members. (#415)
    • We now have tests to make sure all config options and plugin hooks are documented.
    • All manage commands available in pretalx are now included in the documentation.

    Fixed bugs

    • When a submission was removed that contained an answered (multiple-) choice question, the selected answer option was removed, too.
    • When a speaker held more than two talks, their related talks were not linked correctly. (#501)
    • Custom CSS may now also include media queries. (#505)
    • Display of times could be off in the static HTML export. (#500)
    • Not all current TLDs were used when processing markdown input to build links. (#503)
    • The schedule import in the organiser backend never worked (while the manage command for administrators did work).
    • If a review question was mandatory while submission questions were active, they would block the submission process.
    • The HTML export contained media files (not other content) from all conferences on an instance, instead of only the exported conference. (#488)
    • The behaviour of pressing enter in multi-step forms was unintuitive in some places. (#478)
    • Following the revamp of team permissions, override votes could no longer be configured. This has been corrected, and the general handling of override votes was improved. (#473)
    • Questions couldn't be deleted, only made inactive.
    • Don't show a 404 error if a reviewer tries to review their own submission, but show an error message instead. (#463)
    • Don't crash during pretalx init if no conference organiser slug is given. (#451)
    Source code(tar.gz)
    Source code(zip)
    pretalx-0.8.0.tar.gz(3.06 MB)
    pretalx-0.8.0.tar.gz.asc(833 bytes)
  • v0.6.1(May 15, 2018)

  • v0.6.0(May 6, 2018)

    v0.6.0

    Released on 2018-05-06

    Breaking Changes

    None.

    Features

    • New plugin hook: pretalx.submission.signals.submission_state_change is triggered on any state change by a submission.
    • The frab compatible xml was improved by using correct UUIDs, and includes an XML comment with a pretalx version string.
    • The general look and feel and colorscheme has been improved.
    • Organisers can make more changes to speaker profiles and submissions to ease event administration.
    • pretalx now has a concept of organisers and teams.
    • To avoid running into issues when uploading custom CSS, and ensuring smooth operations, custom colors and CSS is not used in the organiser area anymore.
    • You can now send mails from templates and use shortcuts from submissions to send mails to specific speakers.
    • Since different events have different needs, organisers can now choose if submission abstracts, descriptions, and speaker biographies are required for their event.

    Fixed bugs

    • Speakers could see their submission in the orga backend, but could access no information they did not put there themselves. (#375)
    • The API showed talks to organisers if no schedule had been released yet. It did not show the information to unauthorised users.
    • There was no possibility to reset a user's API token.
    • If an organiser changed a speaker's email address, they could assign an address already in use in the pretalx instance, resulting in buggy behaviour all around.
    Source code(tar.gz)
    Source code(zip)
    pretalx-0.6.0.tar.gz(1.79 MB)
    pretalx-0.6.0.tar.gz.asc(833 bytes)
  • v0.5.0(Mar 7, 2018)

    v0.5.0

    Released on 2018-03-07

    If you use postgresql, please use the package psycopg2-binary instead of psycopg2, which is now also noted in the dependencies for postgresql.

    Features

    • pretalx now features a Plugin API, allowing to install custom plugins. Plugins can add their own exporters, and hook into various plugin hooks to be expanded over the course of this year. Plugins can be enabled or disabled per event. Documentation can be found here: https://docs.pretalx.org/en/latest/developer/plugins/index.html
    • Organisers can now decide if reviewers should be required to submit a score or a text with their review. (#340)
    • Organisers can provide room-based information for speakers, which will be provided in emails about talk scheduling. (#93)
    • The list of submissions is now better searchable. (#318)
    • Speakers can now upload an image that will be displayed next to their talk information. (#294)
    • Reviewers can now also be asked custom questions during their review, with all capabilities that speaker questions have.
    • There are now optional review deadlines, preventing reviews to be added, modified, or removed after a certain date. (#352)
    • Individual directories for logs, media, and static files can now be configured via environment variables.
    • Organisers can now show information snippets to submitters, or speakers. (#348)
    • Allow to filter question statistics by speaker status.

    Fixed bugs

    • In the dashboard, an incorrect link was given to add new reviewers. (#344)
    • The "save" button was missing on the mail settings page. (#341)
    • Users could not see (instead not change) their submissions after CfP end, until they were either rejected or accepted. (#333)
    • In the tag, the event was displayed twice, once properly and once in a technical representation.</li> <li>Documentation fix: The environment variable for database passwords is <code>PRETALX_DB_PASS</code>, not <code>PRETALX_DB_PASSWORD</code>.</li> <li>Unconfirmed talks showed up as empty boxes in the schedule editor.</li> <li>Upgrading the privileges of an existing user did not result in an email, since no invitation was required.</li> <li>The Docker setup was broken. It is fixed, and a notice of limited support was added to the documentation. (#300)</li> <li>The orga view now always uses the event timezone.</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.5.0">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.5.0">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.5.0/pretalx-0.5.0.tar.gz">pretalx-0.5.0.tar.gz(1.84 MB)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.5.0/pretalx-0.5.0.tar.gz.asc">pretalx-0.5.0.tar.gz.asc(833 bytes)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.4.1(Feb 5, 2018) </h4> <div class="review-description"> <article class="markdown-body"> <h2>v0.4.1</h2> <p><em>Released on 2018-02-05</em></p> <p>Many thanks to @Rafiot for the timely bug reports.</p> <h2>Fixed bugs</h2> <ul> <li>CfP was uneditable due to missing "Save" button. (#335)</li> <li>No new questions could be added due to the wront template being loaded. (#336)</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.4.1">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.4.1">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.4.1/pretalx-0.4.1.tar.gz">pretalx-0.4.1.tar.gz(1.82 MB)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.4.1/pretalx-0.4.1.tar.gz.asc">pretalx-0.4.1.tar.gz.asc(833 bytes)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.4.0(Feb 4, 2018) </h4> <div class="review-description"> <article class="markdown-body"> <h1>v0.4.0</h1> <p><em>Released on 2018-02-04</em></p> <p>This release removes the dependecy <code>django-zxcvbn-password</code>. Depending on your setup, you can remove it with <code>pip uninstall django-zxcvbn-password</code> or a similar command.</p> <p>This release also expanded the <code>rebuild</code> command to take a flag <code>--clear</code>, which discards all existing compiled static files and rebuilds them from scratch. This command invocation is encouraged after an update if any event on the instance uses custom styling or custom colors.</p> <h2>Features</h2> <ul> <li>There is now a page in the organiser area listing and linking all currently possible data exports in one export page.</li> <li>You may now import XML files to release a new schedule. (#322)</li> <li>We added a new team management interface to manage all team members and permissions in one place. (#292)</li> <li>There is an <code>init</code> command for project setup. Currently it only adds the initial user, but in time it should ask for basic configuration, aswell.</li> <li>The <code>rebuild</code> command now supports a <code>--clear</code> flag to remove all static assets prior to the rebuild.</li> <li>You can choose a pattern for the header hero strip in your event color.</li> <li>You can now choose different deadlines per submission type, overriding the default deadline. (#320)</li> <li>All forms are instantly editable if you are allowed to edit them, and disabled otherwise. No more need to click "Edit"! (#325)</li> </ul> <h2>Fixed bugs</h2> <ul> <li>The schedule export could change project settings, requiring pretalx to be restarted to reset the settings. This could be avoided by unchecking "Generate HTML export on schedule release".</li> <li>When running pretalx as (in-application) superuser, permission issues could arise. pretalx now warns and offers to migrate the account to an administrator account. (#259)</li> <li>Frontend password validation was broken, and never displayed interactive password statistics. This was a display issue only.</li> <li>We removed the unused <code>max_duration</code> property of submission types. (#327)</li> <li>Users always saw the default submission type instead of their chosen one. (#329)</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.4.0">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.4.0">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.4.0/pretalx-0.4.0.tar.gz">pretalx-0.4.0.tar.gz(1.82 MB)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.4.0/pretalx-0.4.0.tar.gz.asc">pretalx-0.4.0.tar.gz.asc(833 bytes)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.3.0(Jan 16, 2018) </h4> <div class="review-description"> <article class="markdown-body"> <p><em>Released on 2018-01-17</em></p> <h2>Breaking Changes</h2> <p>None.</p> <h2>Features</h2> <ul> <li>Speakers can now be marked as "arrived". (#243)</li> <li>Visitors can download an ical file containing all talks of a single speaker (#67)</li> <li>There is now an API for speakers.</li> <li>The speaker biography is now shown in submissions in the API endpoint.</li> </ul> <h2>Fixed bugs</h2> <ul> <li>Non-superusers could not access the email sending form.</li> <li>More than one event stage could be shown as active.</li> <li>Trying to look at entered submissions without being logged in produced a server error instead of a 404.</li> <li>If notifications about new submissions were turned on, they were sent to the submitter instead of the organizer.</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.3.0">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.3.0">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.3.0/pretalx-0.3.0.tar.gz">pretalx-0.3.0.tar.gz(1.39 MB)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.3.0/pretalx-0.3.0.tar.gz.asc">pretalx-0.3.0.tar.gz.asc(833 bytes)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.2.2(Dec 11, 2017) </h4> <div class="review-description"> <article class="markdown-body"> <h1>v0.2.2</h1> <p><em>Released on 2017-12-11</em></p> <h2>Fixed bugs</h2> <ul> <li>Reviewers could not view speaker pages.</li> <li>Inviting somebody twice did not issue a second invitation object.</li> <li>Somebody who was reviewer first could not be added to the organizer team.</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.2.2">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.2.2">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.2.2/pretalx-0.2.2.tar.gz">pretalx-0.2.2.tar.gz(1.38 MB)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.2.1(Dec 6, 2017) </h4> <div class="review-description"> <article class="markdown-body"> <h1>v0.2.1</h1> <p><em>Released on 2017-12-06</em></p> <h2>Features</h2> <ul> <li>Added better meta tags, which leads to better display in social media. (#122)</li> </ul> <h2>Fixed bugs</h2> <ul> <li>Inactive questions could not be deleted (making them active first worked as a workaround). (#289)</li> <li>Choice questions could not be deleted as long as they still had answer options. (#288)</li> <li>Review team invitations sometimes failed, resulting in useless invitation objects.</li> <li>When clicking the "Save & next" button when reviewing, an internal error was encountered after the review was saved.</li> <li>Reviewers could not be removed from their team.</li> <li>URLs were always generated with 'localhost' as their host.</li> <li>When adding a submission in the orga backend with an orga user as speaker, the orga user did not receive a speaker profile.</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.2.1">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.2.1">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.2.1/pretalx-0.2.1.post1.tar.gz">pretalx-0.2.1.post1.tar.gz(1.38 MB)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.2.0(Dec 1, 2017) </h4> <div class="review-description"> <article class="markdown-body"> <h1>v0.2.0</h1> <p><em>Released on 2017-12-01</em></p> <h2>Breaking Changes</h2> <ul> <li>The default value for email SSL usage is now <code>False</code>, permitting the default configuration of <code>localhost:25</code> to work on more machines out of the box.</li> </ul> <h2>Features</h2> <ul> <li>E-mails are now sent with a multipart/HTML version, featuring the mail's text in a box, styled with the event's primary color. (#159)</li> <li>You can now choose to hide the public schedule (including talk pages and speaker pages, but excluding feedback pages and the schedule.xml export) (#126)</li> <li>Mail template placeholders are now validated so that templates including invalid placeholders cannot be saved at all. (#215)</li> <li>You can now ask questions that take an uploaded file as an answer. (#208)</li> <li>Speakers can now upload files which will be shown on their talk page. (#209)</li> <li>The review interface has been rewritten to include fewer pages with more information relevant to the user, dependent on event stages and their role in the event. (#195, #210)</li> <li>pretalx can now be configured to run with celery (an asynchronous task scheduler) for long running tasks and tasks like email sending. A new config section was added, and usage has been documented. (#38)</li> <li>A <code>rebuild</code> command was introduced that recompiles all static assets.</li> <li>Question answers now receive a nice evaluation, aggregating all given answers. (#207)</li> <li>Questions may now be marked as 'answers contain personal data'. Answers of these questions are deleted when users delete their accounts. (#233)</li> <li>We moved to a new permission system that allows for more flexible roles. Please report any bugs that may relate to incorrect permissions. (#78)</li> <li>You can now configure a custom domain to use with your event, in case you have an event specific domain for each of your events. (#171)</li> <li>You can assign "override votes" to reviewers, which function like vetos (both positive and negative), on an individual basis. (#156)</li> <li>A read only REST API was introduced. At the moment, it only supports resources for events and submissions.</li> </ul> <h2>Fixed bugs</h2> <ul> <li>pretalx crashed when an incorrect invite key was used, now it shows a 404 page (#304).</li> <li>When building absolute URLs for exports, emails, and RSS feeds, 'localhost' was used instead of the actual configured URL.</li> <li>If an account was configured to be both an orga member and a reviewer, it encountered access rights issues.</li> <li>When removing the custom event color, and then adding it again, caching issues could be encountered.</li> <li>Inactive questions (questions not shown to speakers) could not be edited.</li> <li>In some places, gravatar images of the visiting user were shown instead of the speaker.</li> <li>The event stage display could show several conflicting phases as active.</li> <li>The default submission type was not, in fact, suggested by default. (#287)</li> </ul> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.2.0">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.2.0">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.2.0/pretalx-0.2.0.post1.tar.gz">pretalx-0.2.0.post1.tar.gz(1.38 MB)</a><br> </article> </div> </div> </div> </li> <li> <div class="d-flex"> <div class="right"> <h4> v0.1.0(Nov 7, 2017) </h4> <div class="review-description"> <article class="markdown-body"> <p><em>Released on 2017-11-01.</em></p> <p>As this is the first release, there are neither new features, nor fixed bugs, nor relevant release notes. All of those are to follow!</p> <p>pretalx releases will be signed by PGP key <code>F0DAD3990F9C816CFD30F8F329C085265D94C052</code>. Further details, including the PGP key, can be found at https://pretalx.org/security.</p> <i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/tarball/v0.1.0">Source code(tar.gz)</a><br><i class="fa fa-file-code-o m-r-xs" aria-hidden="true"></i><a href="https://api.github.com/repos/pretalx/pretalx/zipball/v0.1.0">Source code(zip)</a><br><i class="fa fa-codepen m-r-xs" aria-hidden="true"></i><a href="https://github.com/pretalx/pretalx/releases/download/v0.1.0/pretalx-0.1.0.tar.gz">pretalx-0.1.0.tar.gz(1.35 MB)</a><br> </article> </div> </div> </div> </li> </ul> </div> </div> </div> </div> <div class="col-lg-4 right"> <div id="basic" class="tab-pane fade show active"> <div class="box shadow-sm rounded bg-white mb-3"> <div class="box-title border-bottom p-3"> <h6 class="m-0">Owner </h6> </div> <div class="d-flex align-items-center p-3 job-item-header"> <div class="overflow-hidden mr-2"> <h6 class="font-weight-bold -dark mb-0 text-truncate"> </h6> <div class="small text-gray-500"> </div> </div> <img class="img-fluid ml-auto" style="border-radius: 50%;" src="https://avatars.githubusercontent.com/u/26044534?v=4&s=60" alt="null"> </div> <div class="box-body p-3"> <a href="https://github.com/pretalx/pretalx" rel="nofollow" target="_blank" class="btn btn-lg btn-block btn-info mb-3"><i class="fa fa-github" aria-hidden="true"></i> GitHub </a> <a href="https://pretalx.com" rel="nofollow" target="_blank" class="btn btn-lg btn-block btn-dark mb-3"><i class="fa fa-home" aria-hidden="true"></i> https://pretalx.com</a> </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/taigaio-taiga-back-python-organization"><h6 class="font-weight-bold ">Agile project management platform. Built on top of Django and AngularJS</h6></a> <p class="mb-0 text-muted">Taiga Backend Documentation Currently, we have authored three main documentation hubs: API: Our API documentation and reference for developing from Ta</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/6905422?v=4&s=40" alt="Taiga.io" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 5.8k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 5, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/pretalx-pretalx-python-communication"><h6 class="font-weight-bold ">Conference planning tool: CfP, scheduling, speaker management</h6></a> <p class="mb-0 text-muted">pretalx is a conference planning tool focused on providing the best experience for organisers, speakers, reviewers, and attendees alike. It handles th</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/26044534?v=4&s=40" alt="null" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 496 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 31, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/caelan-pybullet-planning-python-machine-learning"><h6 class="font-weight-bold ">A repository of PyBullet utility functions for robotic motion planning, manipulation planning, and task and motion planning </h6></a> <p class="mb-0 text-muted">pybullet-planning (previously ss-pybullet) A repository of PyBullet utility functions for robotic motion planning, manipulation planning, and task and</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/3621061?v=4&s=40" alt="Caelan Garrett" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 260 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 27, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/pyannote-pyannote-audio-python-audio"><h6 class="font-weight-bold ">Neural building blocks for speaker diarization: speech activity detection, speaker change detection, overlapped speech detection, speaker embedding </h6></a> <p class="mb-0 text-muted">โš ๏ธ Checkout develop branch to see what is coming in pyannote.audio 2.0: a much smaller and cleaner codebase Python-first API (the good old pyannote-au</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/7559051?v=4&s=40" alt="pyannote" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 2.1k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 31, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/pyannote-pyannote-audio-python-natural-language-processing"><h6 class="font-weight-bold ">Neural building blocks for speaker diarization: speech activity detection, speaker change detection, overlapped speech detection, speaker embedding </h6></a> <p class="mb-0 text-muted">โš ๏ธ Checkout develop branch to see what is coming in pyannote.audio 2.0: a much smaller and cleaner codebase Python-first API (the good old pyannote-au</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/7559051?v=4&s=40" alt="pyannote" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 2.2k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 9, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/worcestertechnicalhighschool-ratatoskr"><h6 class="font-weight-bold ">Ratatoskr: Worcester Tech's conference scheduling system</h6></a> <p class="mb-0 text-muted">Ratatoskr: Worcester Tech's conference scheduling system In Norse mythology, Ratatoskr is a squirrel who runs up and down the world tree Yggdrasil to </p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/81368273?v=4&s=40" alt="null" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 4 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 22, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/optapy-optapy-python-machine-learning"><h6 class="font-weight-bold ">OptaPy is an AI constraint solver for Python to optimize planning and scheduling problems.</h6></a> <p class="mb-0 text-muted">OptaPy is an AI constraint solver for Python to optimize the Vehicle Routing Problem, Employee Rostering, Maintenance Scheduling, Task Assignment, School Timetabling, Cloud Optimization, Conference Scheduling, Job Shop Scheduling, Bin Packing and many more planning problems.</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/87315914?v=4&s=40" alt="OptaPy" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 208 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 27, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/linkedin-oncall-python-devops-tools"><h6 class="font-weight-bold ">Oncall is a calendar tool designed for scheduling and managing on-call shifts. It can be used as source of dynamic ownership info for paging systems like http://iris.claims.</h6></a> <p class="mb-0 text-muted">Oncall See admin docs for information on how to run and manage Oncall. Development setup Prerequisites Debian/Ubuntu - sudo apt-get install libsasl2-d</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/357098?v=4&s=40" alt="LinkedIn" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 928 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 22, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/netbox-community-netbox-python-devops-tools"><h6 class="font-weight-bold ">IP address management (IPAM) and data center infrastructure management (DCIM) tool.</h6></a> <p class="mb-0 text-muted">NetBox is an IP address management (IPAM) and data center infrastructure management (DCIM) tool. Initially conceived by the network engineering team a</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/44905828?v=4&s=40" alt="NetBox Community" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 11.8k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 7, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/dbader-schedule-python-job-scheduler"><h6 class="font-weight-bold ">Python job scheduling for humans.</h6></a> <p class="mb-0 text-muted">schedule Python job scheduling for humans. Run Python functions (or any other callable) periodically using a friendly syntax. A simple to use API for </p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/306708?v=4&s=40" alt="Dan Bader" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 10.4k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 2, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/AdamGold-Dryvo"><h6 class="font-weight-bold ">Driving lessons made simpler. Custom scheduling API built with Python.</h6></a> <p class="mb-0 text-muted">NOTE This is a mirror of a GitLab repository. Dryvo Dryvo is a unique solution for the driving lessons industry. Our aim is to save the teacherโ€™s time</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/747847?v=4&s=40" alt="Adam Goldschmidt" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 595 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 5, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/dbader-schedule-python-devops-tools"><h6 class="font-weight-bold ">Python job scheduling for humans.</h6></a> <p class="mb-0 text-muted">schedule Python job scheduling for humans. Run Python functions (or any other callable) periodically using a friendly syntax. A simple to use API for </p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/306708?v=4&s=40" alt="Dan Bader" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 10.4k <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 2, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/ucb-bar-cosa-python-job-scheduler"><h6 class="font-weight-bold "> CoSA: Scheduling by Constrained Optimization for Spatial Accelerators</h6></a> <p class="mb-0 text-muted">CoSA is a scheduler for spatial DNN accelerators that generate high-performance schedules in one shot using mixed integer programming</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/998197?v=4&s=40" alt="UC Berkeley Architecture Research" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 44 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 13, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/puppet-meteor-MOpt-AFL-python-deep-learning"><h6 class="font-weight-bold ">MOpt-AFL provided by the paper "MOPT: Optimized Mutation Scheduling for Fuzzers"</h6></a> <p class="mb-0 text-muted">MOpt-AFL 1. Description MOpt-AFL is a AFL-based fuzzer that utilizes a customized Particle Swarm Optimization (PSO) algorithm to find the optimal sele</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/17903718?v=4&s=40" alt="null" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 172 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 18, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/Daggerpov-background-revolution-python-graphical-user-interface-applications"><h6 class="font-weight-bold ">Desktop application for Windows/macOS users to rotate through custom, preset, and searched-for collections of backgrounds with scheduling and additional settings</h6></a> <p class="mb-0 text-muted">Background Revolution (In Development, Alpha Release) What? This will be an application for users to customize their windows backgrounds by uploading </p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/53918934?v=4&s=40" alt="Daniel Agapov" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 1 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Nov 2, 2021 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/PeterAjaaa-Pysces-python-sending-and-parsing-email"><h6 class="font-weight-bold ">Pysces (read: Pisces) is a program to help you send emails with an user-customizable time-based scheduling.</h6></a> <p class="mb-0 text-muted">Pysces (Python Scheduled-Custom-Email-Sender) Pysces (read: Pisces) is a program to help you send emails with an user-customizable time-based email se</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/89441024?v=4&s=40" alt="Peter" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 1 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jun 16, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/superpenguin612-class-schedule-python-miscellaneous"><h6 class="font-weight-bold ">Tracking development of the Class Schedule Siri Shortcut, an iOS program that checks the type of school day and tells you class scheduling.</h6></a> <p class="mb-0 text-muted">Class Schedule Shortcut Tracking development of the Class Schedule Siri Shortcut, an iOS program that checks the type of school day and tells you clas</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/74030080?v=4&s=40" alt="null" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 3 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jun 28, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/florimondmanca-aiometer"><h6 class="font-weight-bold ">A Python concurrency scheduling library, compatible with asyncio and trio.</h6></a> <p class="mb-0 text-muted">aiometer aiometer is a Python 3.6+ concurrency scheduling library compatible with asyncio and trio and inspired by Trimeter. It makes it easier to exe</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/15911462?v=4&s=40" alt="Florimond Manca" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 182 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Dec 26, 2022 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/hartwork-jawanndenn"><h6 class="font-weight-bold ">Simple alternative to Doodle polls and scheduling (Python 3, Django 3, JavaScript)</h6></a> <p class="mb-0 text-muted">What is jawanndenn? jawanndenn is a simple web application to schedule meetings and run polls, a libre alternative to Doodle. It is using the followin</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/1577132?v=4&s=40" alt="Sebastian Pipping" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 169 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Jan 6, 2023 </div> </div> <div class="box shadow-sm mb-3 rounded bg-white ads-box"> <div class="p-3 border-bottom"> <a href="/repo/Tishka17-clepsydra"><h6 class="font-weight-bold ">Clepsydra is a mini framework for task scheduling</h6></a> <p class="mb-0 text-muted">Intro Clepsydra is a mini framework for task scheduling All parts are designed to be replaceable. Main ideas are: No pickle! Tasks are stored in reada</p> </div> <div class="p-2"> <img class="lazy img-fluid mr-3" style="border-radius: 50%;max-width: 15%" data-original="https://avatars.githubusercontent.com/u/6381317?v=4&s=40" alt="Andrey Tikhonov" > <i class="fa fa-star ml-3" aria-hidden="true"></i> 15 <i class="fa fa-clock-o ml-3" aria-hidden="true"></i> Nov 4, 2022 </div> </div> </div> </div> </div> </div> <!-- footer --> <footer class="bg-white"> <div class="container"> <div class="copyright"> <div class="logo"> <a href="/"> <img src="/assets/images/logo_pythonrepo.png"> </a> </div> <p>2022.PythonRepo </p> </div> </div> </footer> <!-- footer--> <!-- Bootstrap core JavaScript --> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.4.1/jquery.min.js" integrity="sha512-bnIvzh6FU75ZKxp0GXLH9bewza/OIw6dLVh9ICg0gogclmYGguQJWl8U30WpbsGTqbIiAwxTsbe76DErLq5EDQ==" crossorigin="anonymous"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.5.0/js/bootstrap.bundle.min.js" integrity="sha512-Oy5BruJdE3gP9+LMJ11kC5nErkh3p4Y0GawT1Jrcez4RTDxODf3M/KP3pEsgeOYxWejqy2SPnj+QMpgtvhDciQ==" crossorigin="anonymous"></script> <!-- select2 Js --> <script src="https://cdnjs.cloudflare.com/ajax/libs/select2/4.0.13/js/select2.min.js" integrity="sha512-2ImtlRlf2VVmiGZsjm9bEyhjGW4dU7B6TNwh/hx/iSByxNENtj3WVE6o/9Lj4TJeVXPi4bnOIMXFIJJAeufa0A==" crossorigin="anonymous"></script> <!-- Custom --> <script src="/assets/js/custom.js"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery.lazyload/1.9.1/jquery.lazyload.min.js"></script> <script> $(function() { $("img.lazy").lazyload({ threshold :180, failurelimit :20, effect : "fadeIn" }); }); </script> <script src="//cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/highlight.min.js"></script> <script> hljs.initHighlightingOnLoad(); </script> </body> </html><script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="6074f19504bfbfc151d842e7-|49" defer></script>