Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated version of Django Q: Django Q2 #701

Open
GDay opened this issue Oct 21, 2022 · 4 comments
Open

Updated version of Django Q: Django Q2 #701

GDay opened this issue Oct 21, 2022 · 4 comments

Comments

@GDay
Copy link
Collaborator

GDay commented Oct 21, 2022

I have been using library a lot and was a bit concerned that it hasn't been updated in over a year. Therefore, I have created a fork in which I have merged a few of the current open PRs. I have also pushed a few patches myself.

The new repo/package: https://github.com/GDay/django-q2.
It's compatible with django-q, you don't need to change any code to make this work. Just swap the libraries.

What I have done so far:

And perhaps a few more things that I forgot.

There are a few more bugs that I have encountered with Django Q that I am going to solve over the next few days and I plan to keep the Q2 library up to date for the foreseeable future. I am also open to adding a few collaborators to make sure the project stays alive.

Also, it looks like Ilan (the author of this project) has replied a few times in this thread: #664. If this project does indeed get brought back to life in the near future (with more maintainers), then I am happy to archive my repo and create PRs for the changes that I have made myself back to this project.

Let me know if there are any questions.

@PsychicSmurf
Copy link

This is awesome. Thank you so much for picking this up.

@jimjag
Copy link

jimjag commented Nov 10, 2022

Agreed. If you call out for additional developers/contributors/collaborators/maintainers, I volunteer.

@GDay
Copy link
Collaborator Author

GDay commented Nov 10, 2022

@jimjag thanks! I have just added you as a collaborator. It might be better to move my repo to an organization to get some more fine-grained permission levels.

@jimjag
Copy link

jimjag commented Nov 14, 2022

Not a bad idea (about the org)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants