The most successful code review tools have a clear path to getting your patch included.
It feels much more collaborative to ask for changes before a patch is accepted. Afterwards, a reviewer can be seen as difficult, even with the same feedback!
miniblog.
Related Posts
If you created a large, successful OSS project, would you want to be BDFL or move on after a period?
I see tradeoffs on both sides, although it's not a decision I've needed to make myself.
This article discussing forking sqlite draws an interesting parallel between forking and the prisoner's dilemma: forking as a solo contributor is rarely successful, unless others also wish to fork!
https://glaubercosta-11125.medium.com/sqlite-qemu-all-over-again-aedad19c9a1c
tree-sitter has been amazingly successful at getting developer tools to work together.
Neovim has a bunch of people contributing to parsers when they notice highlighting issues. That benefits the whole ecosystem: semgrep, difftastic, even Emacs!