Find a better place for our contributors guide than linking to scanpy one

[Zethson]

Currently, we link to the scanpy one. Should we have it on our main page somewhere? Is there any better spot that feels more "scverse-wide"?

[flying-sheep]

I think we kind of need at least two versions: one for more stability focused projects that do backports, towncrier, … and one for faster dev cycles where a feature landing on main means the next release is a minor release.

But I don’t know how much we should standardize, e.g. Ilan convinced me to do conventional commits, but it took me a while to get used to it and understand the different tags. It integrates nicely with backports and towncrier, but for the fast-paced kind of project it would be kind of a chore with no benefit other than a pretty commit log when you use refined github:

[Zethson]

That's true. Another challenge is that we haven't standardized release notes across our org yet. I'd love to do this but I fear it'll be hard to convince you to switch from towncrier to something simpler that we can adopt everywhere.

So maybe there's a way to have a general version that we can always link to which can be extended/amended by packages that need more (like anndata or scanpy)?