pin copier template ?

[12rambau]

I recently finished my long-waiting template for sphinx extension using the sphinxcontrib namespace.
I think it's more advanced in terms of Python packaging than the current cookiecutter and more importantly I think copier is more flexible in its approach to scaffolding.

here is the template: copier-sphinxcontrib
here is the demo of the template: sphinxcontrib-skeleton

Would it make sense to pin the template repository to the organization ?

[echedey-ls]

Hey, nice template @12rambau !
I was looking for a reference in case I find myself contributing a fork to this org, and something I miss about your demo template, is either in README or Contributing.rst, a list of tools used to develop the package. For example, the .devcontainer file, Nox, Copier, Pytest, pre-commit (how to setup is a common and important step for new contributors), maybe even add some how to create a venv, install dev dependencies instructions.

[12rambau]

oh sorry it's been a while that i didn't used it so I guess it's a bit out of shape now. In the absense of users I completely forgot I had set this up.
I need to realign it on the one I use for normal packages: https://github.com/12rambau/pypackage

Thanks for the reminder !