Earlier quoted context omitted.
I'm not sure I see the point of building a complex platform with governance and whatnot. What I want is an easy way to publish my projects and for other people to contribute, I need something more like email (independent, self-hosted servers with a well defined protocol to communicate between them) than Facebook. I don't care about the governance of my git remote, or getting money out of it. I care about it being rel…
I feel that there is a real need for permanent Storage with respect to Open Source. Code breaks when old packages are unpublished or repositories deleted. Push once and fetch forever solves this. Also Centralized solutions are providing open source collaboration tools for free, storage for free, because of their revenue from enterprise customers. What happens when they decide to shut down? or change their policies? o…
Using git (generally github) repositories for dependency management is, IMO, a hack and so it's not surprising that it often breaks. I like the way buildroot handles it (I'm sure they're not the only ones, but that's the one project I'm most familiar with):
- The buildroot buildbot fetches third party packages dependencies and archive them.
- When you build your buildroot image locally, it attempts to fetch from the third party directly. If the file doesn't exist anymore, it falls back onto the buildroot cache instead.
You could also easily add your own caching layer in there if you wanted too. I think that's distributed computing at its best: simple and robust, with a clear and easily understandable architecture. No blockchain-based proof-of-stake distributed storage, just a series of wget. And of course since everything is authenticated with a strong hash it's always perfectly safe.