@marcan While it’s not great, it is one of the few truly federated systems of development. With the traditional “central git server + issue tracker + PR merge interface” methodology you do have both that centralized issue where it becomes hard to ship out your data, a big single point of failure and in the case of the Linux kernel, a pretty juicy attack target for hacking and spamming.

Another issue is that pretty much all hosted git solutions that currently exist don’t… really expect you to CLI merge except for SourceHut, but SourceHut literally exists because Drew wanted to have the mailing list development approach. They all can do it in a way where the server software will recognize the merge, but it’s often poorly documented and they’d much rather have you click the big merge button on the website.

Idk, I don’t think there’s a great answer here.