[varbhat]

I don't understand how using Radicle will free my code as they say in the site.

So,how is using Radicle better than:

1. main repo on https://github.com

2. mirror repo on https://repo.or.cz

3. mirror repo on https://codeberg.org

4. local backup on my device and hard-disk.

peer-to-peer is beautiful concept but note that git is already distributed VCS. you can have many remotes and mirrors. Just that p2p is not necessary here in git and using Radicle doesn't free my Code.

[GuB-42]

GitHub is more than just a git host.

It has an issue tracker, pull request manager, manages releases and users,... All this cannot be replicated with a simple "git clone".

What Radicle seems to do is to offer some sort of social network on top of git. The novelty here is not the decentralized nature of git, in fact it is what radicle relies on to make its social network decentralized.

[LockAndLol]

So you need 3 accounts on 3 different services to achieve what radicle does.

OK, let's say you use your Github account for all of them instead, now you have centralized your accounts and if you're another youtube-dl, Popcorn-Time or just happen to be unlucky enough have the nationality of a country that the USA likes to hate against, that account is gone.

As for updating all those mirrors, how do you do that? `git push --all` ? `git push --mirror` ? Is git configured to so automatically? Or are you going to configure push hooks on one of those services?

What about your issue/ticket and PR/MR management? Where will that be? Are you going to use an in-git solution like https://github.com/MichaelMure/git-bug, somehow sync everything using custom scripts or wait for https://forgefed.peers.community/ to be finalized and implemented by all code hosts?

How are you going to collaborate with others?

How are you going to introduce newcomers to all these options?

Do you know of a tool that solves most (or all) of those issues?

[half-kh-hacker]

If your main repo lives on GitHub, your (primary) issue tracking is tied to GitHub.

[varbhat]

Actually, it's not fault of git. Workflow of git takes place through email and patches.

But,github wanted to make this process easier for the people,hence they included issues,fork and PR model. It was easily done with intuitive interface without necessity of email for workflow, but if you have asked me, i would have issues,wiki,etc. integrated within repo just like Fossil VCS.

p2p is cool but not solution to this . gitea/gitlab/etc. already provide importing of issues with repos and if not,they must provide that feature.

[xwvvvvwx]

> if you have asked me, i would have issues,wiki,etc. integrated within repo just like Fossil VCS.

This is exactly what radicle does.

[phoe-krk]

> Actually, it's not fault of git. Workflow of git takes place through email and patches.

This invokes the "it's not a bug, it's a feature" mechanism. E.g. Fossil has no problem integrating issues, merge requests, and wiki pages inside its repositories.

[varbhat]

Actually, Gitlab and Gitea allows mirror of Github repos with Issues/wiki/PR etc. So, having issues in Github is not at all problem.

I just gave you example of Fossil VCS which has issues,PR,etc. baked into VCS itself.

Actually,what Radicle is doing is to extend git with p2p and not inventing new VCS with issues,etc. baked in.

What i am telling is that p2p doesn't solve this unclear problem and p2p isn't much beneficial to git.

And will there be enough peers to guarantee availability of repo ?

[viraptor]

> Actually, Gitlab and Gitea allows mirror of Github repos with Issues/wiki/PR etc.

But GitHub does not mirror the issues/PRs from anyone, so it's a very one-sided connection.

[varbhat]

That's problem of GitHub.

[cloudhead]

So when GitHub is down, how do users know to pull from your mirrors? How about push?

[scoopertrooper]

Notes in the readme? How long are you expecting one of the biggest websites in the world to be down?

[cloudhead]

A couple of hours[0]? One entire day[1]?

[0]: https://www.theverge.com/platform/amp/2020/6/29/21306674/git...

[1]: https://github.blog/2018-10-30-oct21-post-incident-analysis/

[FpUser]

For some people like forever. Developers can be banned because their country/area happen to fall under US sanctions.

[berkes]

Or because a German law firm (ab)uses a US copyright directive that Github, a US company has to follow?