Looking for new maintainer

[andreyfedoseev]

Since I no longer use Django in my day-to-day work (for quite a while, actually), I don't have enough motivation to keep maintaining this project.

Thus, I'm looking for a new maintainer. You're willing to become one, please step up and let me know if the comments to this issue.

The project in its current state if half-baked for the 3.0 release. You can find the remaining issues I planned for 3.0 here:

https://github.com/andreyfedoseev/django-static-precompiler/milestone/7

My plan is:

1. Find candidate(s) for the maintainer position
2. The candidate(s) close the remaining issues linked above and prepare the 3.0 release, with my help and guidance, if needed.
3. 3.0 is released to PyPI
4. I transfer the ownership of the GitHub repository and the PyPI package to the new maintainer(s)

[presidento]

I use this project for a few SASS files for my pet project, so I am willing to help keeping the lights on with minimal effort.

• In Ensure Django 5.2 and Python 3.13 support #171, I ensured it works well with Python 3.13 and Django 5.2.
• I do not use TypeScript now, so I don't want to put effort into implementing Add TypeScript compiler #117.
• I have no problem with Incompatibility with ManifestStaticFilesStorage #151, maybe because I run collectstatic every time after compilestatic

[andreyfedoseev]

Hi @presidento

Thank you for your interest in taking over maintainership of this project, and for the PR — I appreciate your efforts.

That said, I want to be upfront with where I’m coming from regarding the 3.0 release and what I had in mind for the transition.

At the moment, the latest version of the code that I started to prepare for 3.0 only includes a few breaking changes (such as dropping support for older Django/Python versions and removing a deprecated feature). These were important maintenance steps, but on their own, I don’t think they justify a major version bump — it would feel like a release that breaks things without offering much new in return. That’s exactly why I planned to include at least one long-standing feature and a bugfix alongside the version compatibility updates.

I realize now that I don’t have the time and motivation to complete that work myself, which is why I’m looking for someone to pick it up.

From your message, I gather that you’re not especially interested in implementing the planned feature or pursuing the bugfix — which is totally fair! But because of that, I’m not quite ready to fully hand over maintainership and cut the 3.0 release just yet. I want to make sure there’s a clear and meaningful foundation for that release, especially since it introduces breaking changes.

That said, I think your contributions so far are really valuable, and I’d love to find a way to involve you if you're interested — perhaps as a co-maintainer focused on ongoing compatibility and CI-related updates. That kind of collaborative setup could work well if another person steps in who’s more focused on feature development, and together you'd be able to guide the project forward.

If you’d like to continue helping in any capacity — whether it’s reviewing open issues, helping to triage, or just keeping CI and dependencies current — that would be appreciated and a great way to grow into the role.

[presidento]

Hi @andreyfedoseev, thank you for the detailed answer. No need for a cap here. 😄 I just want to keep using django-static-precompiler with the latest Django LTS version (currently 5.2). I totally understand your concerns, and I agree with you. Would you please consider releasing 3.0a1 as an alpha version until you find the right person to keep this amazing project shining?

[andreyfedoseev]

@presidento I just released version 3.0a1