How is this related to the $RAD coin?
From a technical standpoint, Radicle (P2P git protocol) is not related to $RAD.
$RAD is the token of the organization that has been funding Radicle over the years.
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
21–30 of 299 posts
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#22This looks like a fine project for its purpose, but I think git is already open-source and p2p. You don't need sh What's missing in git is code issues, wikis, discussions, github pages and most importantly, a developer profile network. We need a way to embed project metadata into .git itself, so source code commits don't mess up with wikis and issues. Perhaps some independent refs like git notes? https://git-scm.com/…
> and most importantly, a developer profile network
What has the world come to where that is the most important part?
--
I think gerrit used to store code reviews in git.
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#23I hear about Radicle every time crypto market goes up. Is anybody seriously using it ?
This got down-voted so fast! :)
Serious question though: how much budget was spent on Radicle, how many people did work on it, and who is using it ?
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#24I wish people would define precisely what they mean by "peer to peer" (or more commonly, "distributed"). Its such an ambigious term now it can mean anything when used as a buzzword.
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#25Earlier quoted context omitted.
Yes, this is how radicle stores this data. ; ) https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3trNYnLW...
https://docs.radicle.xyz/guides/protocol is probably a better resource (but this guide is still Work In Progress)
> Radicle’s predefined COB types are stored under the refs/cobs hierarchy. These are associated with unique namespaces, such as xyz.radicle.issue and xyz.radicle.patch, to prevent naming collisions.
This looks like an interesting approach. I have question, to avoid copy a large .git project, we have partial cloning and cloning depth. If `cobs` grows too large, how can we partially clone it? Like select issues by time range?
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#26This looks like a fine project for its purpose, but I think git is already open-source and p2p. You don't need sh What's missing in git is code issues, wikis, discussions, github pages and most importantly, a developer profile network. We need a way to embed project metadata into .git itself, so source code commits don't mess up with wikis and issues. Perhaps some independent refs like git notes? https://git-scm.com/…
While Git is designed in some way for peer-to-peer interactions, there is no deployment of it that works that way. All deployments use the client-server model because Git lacks functionality to be deployed as-is in a peer-to-peer network.
For one, it has no way of verifying that the repository you downloaded after a `git clone` is the one you asked for, which means you need to clone from a trusted source (ie. a known server). This isn't compatible with p2p in any useful way.
Radicle solves this by assigning stable identities[0] to repositories that can be verified locally, allowing repositories to be served by untrusted parties.
[0]: https://docs.radicle.xyz/guides/protocol#trust-through-self-...
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#27Earlier quoted context omitted.
> What's missing in git is code issues, wikis, discussions, github pages and most importantly, a developer profile network. Radicle adds issue tracking and pull requests. Probably some of those other features as well. On mobile there are buttons on the bottom of the screen in the op link, click those and you get to the issue tracking tab and the pull request tabs etc
But that’s not what parent meant. Those things should be embedded in the git repository itself, in some kind of structure below the .git/ directory. That would indeed make the entire OSS ecosystem more resilient. We don’t need a myriad of incompatible git web GUIs, but a standard way of storing project management metadata alongside version control data. GitHub, Gitea, Gitlab, and this project could all store their da…
Radicle does store such data in git - issues, patches (PRs) etc. Also, the entire project (protocol, cli, web ui etc) is fully open source.
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#28I wish people would define precisely what they mean by "peer to peer" (or more commonly, "distributed"). Its such an ambigious term now it can mean anything when used as a buzzword.
I haven't seen the term misused very often - the way it is defined in Radicle and most other peeer-to-peer systems is how Wikipedia defines it[0]; specifically this part: "Peers are equally privileged, equipotent participants in the network".
So a peer to peer system is one where all participants are "equally privileged in the network". This usually means they all run the same software as well.
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#29Can this handle patch stacks or is this just another pull/merge request model with all the flaws that entails?
It can handle them, though we haven't built that much tooling around them. However, unlike GitHub, updates to PRs (Patches in Radicle) are non-destructive, just like Gerrit[0], and code reviews are tied to specific revisions of patches. This is in my opinion one of the biggest flaws in GitHub's model.
Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
#30Hi HN. I am the co-founder of the project. If you are interested in how the protocol works under the hood, start here: https://docs.radicle.xyz/ Docs are still WIP though.
How much budget was spent on Radicle, how many people did work on it, how long you've been building it and who is using it ?