0xrsydn/research
1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
research/radicle-decentralized-git/next-steps.md

1.3 KiB
Raw Blame History

Next Steps — Radicle: Decentralized Git Network & Forge

Part of radicle-decentralized-git/index

Trial plan (seed node beside Forgejo)

  • Install Radicle (rad 1.10.0) on hermes-vm or greencloud-vps via Nix
  • Initialize node identity key; back up the private key securely
  • Publish one public repo (candidate: research vault or idx-cli) to the Radicle network
  • Verify clone from a second machine / peer over rad://
  • Evaluate: does anyone external find/use it? Is the seed node stable?

Decision triggers

  • External collaborator actually wants to contribute over Radicle → invest in dedicated clan-private seed service
  • Agent-native collaboration via COBs becomes attractive → design a custom COB type for our workflows
  • greencloud-vps outage showed Forgejo is a single point of failure → make Radicle mirror part of the resilience story

Open questions

  • Where should the seed run: hermes-vm (agent box, always-on) vs greencloud-vps (public services box)?
  • Should public repos be dual-published (Forgejo + Radicle) or migrated?
  • How does Radicle interact with our Forgejo mirroring automation (github-release, forgejo-repo-mirroring skills)?
  • Nix packaging: is radicle in nixpkgs, or do we package the release binary?