[Boulth6]

This is a solution to a non-problem. Hosting taken down git repos is easy an due to gits design all developers already have the source code.

The real problem is hosting issues and PRs in such a way. Github has an API and it's possible to script the backup but source code gets backup automatically so when the takedown strikes it's not a big problem.

[michaelmure]

Shameless plug, but that's exactly the aim of https://github.com/MichaelMure/git-bug.

It's a distributed bug-tracker: it stores issues (and one day, PRs) within git. You can work offline and you always have a full copy of everything. It also has bridges for Github, Gitlab and Jira.

[happybeing]

Yes folks, take a look at git-bug, Michael has done a brilliant job of adding issues and comments into your git repos, and for a pre v1 project it works really well already, and you can import from / to github, gitlab and JIRA.

git-bug is a pleasure to use so I'm attempting to get it running in the browser using wasm, to create a decentralised github on p2p storage. I'm targeting Safe Network but the same approach could be used on anything with a storage backend, from NextCloud to IPFS, even [cough] AWS.

[hashworks]

While others could have a backup of a Git repository, I need to find them first — so discoverability is a problem. Next thing is integrity - how do I know that the git history I receive has not been tampered with?

[IanCal]

Do signed commits solve the integrity problem?

[hashworks]

Yes. Git commits include the hash of the previous commit, creating a cryptographic chain. If you can verify the signature at the tip of a branch you effectively verify the complete history of the branch.

Sadly not every maintainer signs their commits or tags.

[nemoniac]

Fossil is an approach to this.

https://fossil-scm.org/home/doc/trunk/www/index.wiki

[ssb1]

Not git obvs, but Fossil keeps bugs (wiki, forum) as part of the repo.

https://www.fossil-scm.org/home/doc/trunk/www/bugtheory.wiki