Who Should Pay For Source Code Availability?
Summary
The article argues that traditional forking and vendoring to ensure source code availability are inefficient and proposes Radicle, a peer-to-peer network, as a more cost-effective way to keep code reliably accessible. It compares Radicle to centralized platforms like GitHub and Codeberg, discusses seeding policies, and shares the author's personal experience adopting Radicle.