Open 6543 opened 3 years ago
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!
Gitea can mirror everything.
Only upon migrations, it seems. Gitea mirrors don't support issues/PRs.
https://github.com/go-gitea/gitea/pull/6290 https://github.com/go-gitea/gitea/issues/1876
Please post your sources along with your suggestions.
@TheAssassin You need to add your Github username/password, and the choice will appear.
Note that the mirrors are fixed (IE not updating)
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.
Gitea only support that for the code itself.
I don't think anything exist for what you want.
I suggested using Git-ipfs in #4618, it has the benefit of being decentralized
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.
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
git-bug may be an option for issues ... but did not use it at the moment, so I cant tell mouch about it
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.
I told you in previous post that you can backup metadata with GitLab's GitHub importer.
And I explained before, more than once, that we're looking for a backup tool, not a one-off import thingy. It's generally a good idea to have backups.
We do not intend to run for the next US-company-hosted platform.
https://github.com/MichaelMure/git-bug Distributed, offline-first bug tracker embedded in git, with bridges
:point_up: to be more spicific with "git-bug"
EDIT: but this is realy off-topic now - the issue is about referencing code mirrors in official README/Docs/Website
We do not intend to run for the next US-company-hosted platform.
You can run self-hosted instance and mirror to it every day
@imShara I'm asking for official mirrors since they should be widely known and users should have trust not to get a malicious version ...
yes I can and do mirror NewPipe myselve (https://code.obermui.de/TeamNewPipe/NewPipe) - but thats not the point
@imShara please stop insisting on this. I'm surely not going to reimport the entire project every day somewhere. That's a waste of energy. It is not a solution. Neither is git-bug
, it doesn't even seem to allow imports.
We need some true backup solution. Something that can incrementally back up the data, and ideally make it easy to import the data somewhere else whenever we need to in the future.
"But you can self host" -- no, we're not looking for something to self-host. We need a backup system. Period.
Edit: in fact, git-bug seems to provide incremental back-ups. I'll check it out. Thanks @6543.
@TheAssassin git-bug has bridges witch do import and export
@ganarchy can sorta be used for this if someone decides to implement signed projects on it...
(otherwise it's kinda just a decentralized development (a la the kernel) system. so not really "official mirrors" as much as "censorship-resistant forks".)
Unrelated to this issue but youtube-dl is back. https://github.blog/2020-11-16-standing-up-for-developers-youtube-dl-is-back/
inf view to #4618 and similar issues ...
it would be nice if there are official mirrors of the importand NewPipe source code.