WorldconVotingSystems / WorldconVotingSystems/nomnom
Refactoring and Evolving
@offbyone is already working on this.
Since Jun 16, 2024.
- Dominant language
- Python
- Stars
- 17
- Forks
- 15
- Avg merge
- 11m
- Merged PRs (30d)
- 1
Description
This is a roll-up issue for the things I want to do to the code after Glasgow is done, but before we need to collect nominations for Seattle or LA
I want to look into migrating away from environ-config to django-configuration; it looks like it'll fit the needs of the application better, and may make it easier to maintain and extend the configuration
I'd like to try to move from celery to django-q2 as a more django-native background job implementation. Probably with the ORM backend.
I want to get the new developer experience nailed down; starting from a clean checkout, how easy is it to get going?
I want to get the "add a new convention" experience down.
### Tasks
- [ ] Investigate migrating to https://django-configurations.readthedocs.io/en/latest/patterns.html
- [ ] Investigate migrating to django-q2
- [ ] https://github.com/WorldconVotingSystems/nomnom/issues/155
- [ ] https://github.com/WorldconVotingSystems/nomnom/issues/154
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.