Set up official mirrors?

[6543]

inf view to #4618 and similar issues ...

it would be nice if there are official mirrors of the importand NewPipe source code.

[TheAssassin]

Some maintainers have set up mirrors of the NewPipe repositories already. The code will always continue to live on.

Mirroring issues/PRs and keeping them in sync is significantly harder. Suggestions appreciated!

[cha0t1c1]

https://github.com/search?q=export+GitHub+issues
https://github.com/search?q=export+GitHub+pull+request

[TheFrenchGhosty]

Gitea can mirror everything.

[TheAssassin]

Only upon migrations, it seems. Gitea mirrors don't support issues/PRs.

go-gitea/gitea#6290
go-gitea/gitea#1876

Please post your sources along with your suggestions.

[TheFrenchGhosty]

@TheAssassin You need to add your Github username/password, and the choice will appear.

Note that the mirrors are fixed (IE not updating)

[TheAssassin]

Again: you are talking about a migration, not a mirror. Migrations are one-off copies, they're imported exactly once. A true mirror is auto-updated with the remote's changes.

[TheFrenchGhosty]

Gitea only support that for the code itself.

I don't think anything exist for what you want.

[Mhowser]

I suggested using Git-ipfs in #4618, it has the benefit of being decentralized

https://docs.ipfs.io/how-to/host-git-style-repo/

https://docs.ipfs.io/concepts/what-is-ipfs/

[TheAssassin]

We're looking for solutions to back up the metadata, i.e., issues and PRs. Backing up the source code is easy.

I don't think any distributed repository stuff is viable or useful. And with so-called peer-to-peer stuff, there's privacy concerns as well.

[test2a]

This might be difficult but has the team considered a self hosted gitlab server? That would be significantly much harder to takedown with frivolous threats and actions

[6543]

git-bug may be an option for issues ... but did not use it at the moment, so I cant tell mouch about it