Are you saying that Git should implement those features?

Shameless plug: https://github.com/MichaelMure/git-bug

Yes I realize the irony of pushing a project hosted on github when it's down.

Fossil [1] has those integrated, along with a built-in web interface (which git kinda has)

[1] https://www.fossil-scm.org/

I wish fossil had become more mainstream. It seemed such a cool tool when I tried it 8 to 9 years ago.

Having data outside of the repo is pretty strange in itself, that breaks the federated approach of git.

As few people seem to use Git without those features it would probably be a good idea. Git isn't really decentralized if large parts of the workflow are vendor specific and not cloned.

I'm not sure how active Linus still is in git development, but at least historically, the issue there is that the Linux kernel dev workflow doesn't use any of those features.

That's not really true. Kernel development users PRs, but they're implemented as mailing list threads. They also do code reviews which are implemented as... mailing list threads. It's the most decentralised and vendor-agnostic implementation we can have right now.

So an ideal solution would use mailing list threads as the protocol with a custom UI on top. Same as we use git as the protocol with GitHub eye candy on top. Imagine github as we have now, but all data for issues and PRs are saved as e-mail. Of course, that doesn't benefit GitHub in any way, so we'll never have that.

Yes, but if you're happy to do everything by mailing lists, you don't have to worry about github going down.

That would be pretty neat.

I’m getting errors on pushes too