django-tasks-scheduler

[tim-schilling]

Hi @django-commons/django-tasks-scheduler, I wanted to check-in with you about your project, logistics and any concerns you may have.

• Have you run into any friction having your project in Django Commons, if so, can you describe them?
• Is there anything we can do to help your team, repo out?
• Do you have any questions or concerns for us?

If you'd like to chat with us privately, our email is django-commons-admin@googlegroups.com

[williln]

Hi @django-commons/django-tasks-scheduler -- this is our semi-annual checkin. If there is anything Django Commons can do to help you or your project, please let us know! Otherwise, happy coding 🌻

[tim-schilling]

Hi @django-commons/django-tasks-scheduler this is just our semi-annual checkin. Let us know if there is anything Django Commons can do to help, or if there is anything else on your mind! Otherwise, happy coding 🥳

As an additional reminder, though not at all a suggestion/requirement. It may be worth looking through who has regularly contributed to your project to see if you'd like to elevate them to be a committer or a maintainer. I mention it because it's easy to forget to review the repositories community and helping people grow. Similarly, if you or anyone else wants to step back, that's fine too! If we can help coordinate, please let us know.

[tim-schilling]

Whoops, forgot some things. There are two other things:

1. Can the @django-commons/django-tasks-scheduler-admins please share your emails with us? You can email us at django-commons-admin@googlegroups.com to avoid publishing publicly here.
2. We are working on a new policy around project abandonment. As a community organization, we need to have clear guidelines on when the community should pass the project onto someone else or signaling that the project is in a period of low activity. We'll share this new policy with you when we have it ready for comment. This will include a timeline for adoption. If you have questions, please let us know!

[cclauss]

I see that FastAPI is tantalizingly close to being free-threaded-compatible. https://oxykodit.substack.com/p/march-2026-update

• https://github.com/fastapi/fastapi/releases -- See release: v0.136.0

I struggle to find any mention of 3.14t, free-threaded, or free-threading in the Django docs. Could django-commons do anything to focus community development around Python 3.14t and Django? I know Django is quite different from FastAPI, and that these things require significant time from deep experts, but it would be inspiring to feel momentum towards free-threaded Django.

Thanks for all that you do.

[tim-schilling]

Hi @cclauss, I think this may be a better topic on it's own. This discussion is meant to be used for Django Commons admins checking in with the django-task-scheduler project.