Give admin of this project to someone who will merge Pull Requests.

[wroscoe]

This looks like a very useful tool but has fallen behind even though the fixes have been submitted in pull requests.

[jcarbaugh]

@g3rd I'll defer to you on this since you initially developed the package!

[tom-price]

Hoping to further this discussion with some input. I've pulled #15 #18 and #20 locally and have been working with them in a project of my own after properly merging them and their associated migrations.

I also now have some contributions to give back to the project, but as they're dependant / integrate with the existing PR's feel blocked.

[jcarbaugh]

@tom-price we'll get these reviewed and merged today. Going forward, I'm going to have a discussion with our team to see if this is a project we plan to continue support and pass it off to someone else if needed.

[oudeismetis]

@wroscoe and @tom-price
Sorry for the slow replies to this. Thank you for the much needed nudge on this project!

We are taking some short term steps to improve this project (#15 already merged), but are still discussing how we want to support this project long term.

[MicahLyle]

Hi,

do any of you need help maintaining this project, or merging pull requests?

I'm using this project right now in something I'm working on, and I noticed that currently, deleting repeatable jobs does not indeed cancel the job in the scheduler. I'd be happy to work on a few features if needed, just let me know (@tom-price)!

[mattjegan]

Hey @MicahLyle, I reached out to istrategylabs last week to see if they had a decision on this yet however I haven't heard anything on the state of the project yet. As mentioned then, I'm also happy to help out with the maintenance of this project whether it be merging PRs or triaging issues.

[g3rd]

I'm late to the party!
Picking back up. Anyone still around?

[g3rd]

@mattjegan @MicahLyle I am back on the project as a maintainer.

[tom-price]

@g3rd I'm on vacation the next 2 weeks but other than then am happy to contribute to the project's momentum. I am still actively using this in my projects.

[eskhool]

@g3rd @tom-price are you guys still maintaining this project in 2022? We are a small team of Django developers in a funded startup that are using this project and can maintain it going forward in case you are unable. Do let me know.

Thanks for the good work!

[tom-price]

I'm keen to continue to working on this; however, not while unilaterally merging / pushing changes. I've had some difficulty getting feedback when submitting PRs.

The other packages I work with / use are all for private internal use so having someone onboard with more familiarity with the standard practices for public projects would be great for me.

[eskhool]

This package like many others is in serious need of active maintenance otherwise it will keep getting forked. Case in point, for Django 4 @cunla has already created another pypi package when he didn't hear back for 2-3 months. It should have just been another version/branch of the code of this with a compatibility table if required.

For now we have also forked this at grocurv/django-rq-scheduler. Ideally my team would take over maintenance, with daily review of PRs and managing compatibility across Django versions at the same pypi address as the present.

@g3rd pls let us know if this works for you. We will obviously accredit the origin in the fork page

[cunla]

@eskhool Not sure if you are aware, I took ownership over the package and I am maintaining it regularly here