Use hatch-vcs by default

[Zethson]

We're so committed to hatch now, it feels weird that hatch-vcs isn't on by default.
How about we enforce this? @grst @flying-sheep

[flying-sheep]

I personally love it the flow of “just tag a release and it works, no manual bumping required”, I guess someone in the past thought it was too opinionated?

[Zethson]

Yeah totally and there's a chance that this coulda been my thinking even but now I feel like we should either go all-in on hatch or not. I have the impression we've clearly committed to hatch now. Therefore, it might be easier to for people to understand that "hatch can do everything for them".

[flying-sheep]

Yeah, both hatch and hatchling are great in what they do. They are different things though 🤓

[grst]

I think in the recent PRs we did get a bit more opinionated and this would be another such change. We are moving the scope a bit from "generic template to get started on a ecosystem project quickly" towards "common standards for scverse core packages".

Not saying this is necessarily a bad thing, but we should all agree that that's the way forward.

Personally, I'm also a big fan of the hatch-vcs workflow and wouldn't oppose this change.

[Zethson]

@grst you're right and you can call this my secret agenda if you like haha.

I think we should try to get some feedback from community members to understand whether our template has too much complexity or is nicely usable now. I'll try to ask around at our upcoming events to learn the answer.