Ask HN: Best Git workflow for small open source teams

Hey HN,

I've been part of multiple smaller teams doing hobby projects, writing / maintaining open source software, and we've had multiple approaches.

Particularly, I'm wondering what you think are good/bad workflows for source control, issue management, PRs/MRs, reviews, estimation (would you estimate points on issues even in open source?), planning, the "vision" (BDFL?), etc.

This is assuming the team isn't paid much or at all and does it out of their free will, so you can't force them to do a stand-up every morning and force them to use Jira.