WorldconVotingSystems / WorldconVotingSystems/nomnom

Investigate migrating to django-q2

Open
#266 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

development wontfix
Dominant language
Python
Stars
17
Forks
15
Avg merge
11m
Merged PRs (30d)
1

Description

Instead of celery, it might be that django-q2 will work for background workers; that might be simpler. Try that out.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the current Celery background-worker configuration and usage, then assess whether django-q2 can replace it and document the migration scope and validation criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.