Cookiecutter maintenance - consider joining collaborative community like Jazzband

[jaklan]

Hi guys, as we can observe in the last years - Cookiecutter has experienced a real slowdown since, at least, 21 Apr 2020, when the last significant update was released (1.7.2). Although recently sth moved on and version 2.x is almost there, it's quite clearly visible the core maintenance is still on the shoulders of @audreyfeldroy and @pydanny, and after reading #1555 it's easy to notice they don't have enough time to push it forward alone.

We have 184 open issues, 59 open pull requests and it's growing, and even if we talk about 2.x we can see how problematic is to finalise the release smoothly (i.a. the packages are still not published to PyPI - #1636).

So that's why I would propose moving Cookiecutter to some collaborative community, which would be able to help with maintaining the project. The Python-oriented one I know is Jazzband, which has over 1100 members and ~60 projects in their portfolio, especially django-debug-toolbar, pip-tools, tablib, but probably there's more such initiatives.

Cookiecutter is one of the essential tools in the Python eco-system and it just doesn't deserve to suffer from the maintenance issues - especially when there are people around who would be glad to help with that!

[insspb]

Hi @jaklan

I do not see the difference between jazzband and our organization form. We are currently independent from jazzband rules, and open sourced as well. So if somebody want to contribute we are always open for contribution. Unfortunately pull requests quality/description/docs or coverage usually not enough to fast merge and require changes or attention of team. I do not think that jazzband will change pull requests quality.

As for jazzband projects, many of them are on 1-2 maintainers and also very long updated, so I do not see big difference (like celery related projects on jazzband)

[jaklan]

@insspb jazzband was only an example. The clou is Cookiecutter was practically dead for the last months - as I described in the original issue. Moment of releasing 2.0 was a hope that sth would change, but then we were waiting almost half a year to fix problems with the lack of release on PyPI... @ssbarnea can probably tell more about problems with reaching anyone who could give him required permissions to push the topic forward.

Having said that, I see sth change recently and actually some PRs were merged and releases were done. I don't know the details, but I hope it means things moved forward on the maintainance side and Cookiecutter got a new life.