This is not an answer to your question but it's tangentially related.
Someone I greatly respected ran an open-source project with the policy of merge everything. Completely flip this idea of carefully review, debate and revise every PR. His theory was that it helps to build an open community, and if something breaks someone else will revert that commit. He says that the main branch was almost always stable, a massive improvement to how it was run previously. He passed several years ago and for some reason this reminded me of him.
I guess what I'm trying to say is if you get something out there that people find useful, the code will be looked at. It doesn't help you if you're looking for someone to collaborate sorry.
There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.
Just build a proof of concept
Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
Build something internally that you yourself will use
Only once something is good enough and is used internally, then release it to beta.
So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.
That's Wikipedia's approach, arguably one of the most successful "open source" projects in history - certainly not without its problems, but overall it's pretty great
Yes that's right. I was only just transitioning into adulthood and Pieter mentored me and profoundly changed how I view many things. It wasn't just zeromq but that was the main thing. I still keep his books at hand on my bookshelf. His death impacted me greatly.
Would love something like this, but it's very hard to get such a community working.
Most of the time there will be way more people wanting a review of their code than people wanting to put in the work and review something.
Maybe some kind of point system could work. Like one needs to review at least two times before you can get your work reviewed.
However they have some strict rules on what is allowed so it may not be suitable for open source projects. Two problematic ones are: 1) The poster must be the author/owner of the code. You, for example, can't post code that someone else has written. 2) All code that is to be reviewed must be included in the post. You can't just link to a repository.
There was something like that on Reddit but I can’t remember the sub. I haven’t seen one here. The best way to get reviews of open source is via contributions to larger projects. That of course doesn’t answer your question directly but is worth noting.
I’d recommend joining some discord or matrix servers for the language you work in or likeminded folk. They tend to have channels for that, and some have really helpful communities.
eta: I just checked my local instance and saw a community with very few subs and zero posts called /c/reviewmycode. Somebody has to post first.