open-registry

Thanks a lot, always nice to hear people like it! Yes, I agree with you. Open-Registry isn't tied to being just a JS registry. Open-Registry focuses it's energy on unlocking the for-profit registries first though, like npm, docker and packagist, before we'd consider moving on to other already non-profit registries. Currently, there are no plans regarding expanding it, but it wouldn't be very hard and the architecture of the application makes it very easy to expand too. While GitLabs effort is (in my mind) more well-meant than GitHubs, since it's open source, I don't think having the software open source is enough. The full development, funding and finance has to be open as well, and I don't think GitLab fits that. Basically, we need Open Source Public Utilities for core infrastructure projects like these. Edit: Also, opened a issue in Ope

I know this is a duplicate post [0], but I felt it deserved another chance at getting some discussion going about a community-supported package manager, as an alternative to NPM. Here is the repo: https://github.com/open-services/open-registry [0] https://news.ycombinator.com/item?id=19739872

Hello HN! This is the initial attempt at reclaiming one of the most important parts of the JavaScript ecosystem, the npm package registry. Initially, it just serves as a proxy with a long-term cache. But further down the line, we're planning to add additional features such as federation of registries (and hopefully fully decentralized registry even further down the line), signed packages and other features. Please let me know what you think, if something is unclear from the website and so on. Otherwise you can find the main repository on GitHub here: https://github.com/open-services/open-registry I think what needs to most attention right now, is the Governance protocol, which you can see here: https://docs.open-registry.dev/governance/ Basically, the project should be setup to be free from commercial entities and be able to survive long-