Earlier quoted context omitted.
I personally don't think GitHub's PR model is superior to e-mail based patch management for two reasons. First, e-mail needs no additional middleware at git level to process (I can get my mails and directly start working on my machine), plus e-mail is at least one of Git's native patch management mechanisms. This is not about spam, server management or GitLab/Gitea/whatever issue. This is catering to most diverse wor…
the problem with mail-based patch management is that it doesn't scale well, management wise... when you have hundreds of patches and multiple reviewers who can review them, Github/Gitlab environments make it easier to prioritize the patches, assign who will do the review, filter the patches based on tags, and keep track of what wasn't reviewed yet..., mail-based patch management is fine for smaller projects, but Linu…
[citation needed]
It's what "open source" enables, but it may not necessarily be a desired goal of a FLOSS project.