On my quasi-blog: "Git without a forge"
https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/git-no-forge/
Most of my projects are hosted in bare git repositories on the web, and not on a forge site. I talk a bit about this: ways to send patches to a project like that (and which I personally prefer), and reasons why I haven't (yet?) changed my arrangements.
@simontatham
"But I’d be more interested in thoughts about how to get the best of both worlds. If there were a system for allowing contributions and their review and discussion to happen in public..."
Have you heard of and/or tried @reviewboard ? For me the workflow is much more pleasant than the traditional forge workflow. But I don't know if it allows account-less contributions.
@ivanhoe as it happens, I've been using an instance of Review Board at work very recently! But it wasn't me who set it up, so I don't know either what its account-creation options are.
I haven't really got used to it yet. One thing I keep getting caught out by is the way almost everything I do with it is entered as "draft" status, and I have to press "Publish" to let anyone else see it. I've had several code reviews delayed for a week recently when I thought I was waiting for the reviewer to respond to my comment and/or patch update, and it turned out they were waiting for me to press the green button I'd forgotten!
@simontatham Yeah the thing with the drafts is something you have to get used to. I had problems with it in the beginning too, but now I rarely forget to publish.