Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/open-services/open-registry
Community Owned JavaScript Registry
https://github.com/open-services/open-registry
javascript nodejs non-profit npm open-service registry repository
Last synced: 14 days ago
JSON representation
Community Owned JavaScript Registry
- Host: GitHub
- URL: https://github.com/open-services/open-registry
- Owner: open-services
- License: mit
- Created: 2019-04-11T13:30:58.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-05-26T22:36:15.000Z (over 2 years ago)
- Last Synced: 2024-04-12T02:21:19.448Z (7 months ago)
- Topics: javascript, nodejs, non-profit, npm, open-service, registry, repository
- Language: Clojure
- Homepage: https://open-registry.dev
- Size: 10.9 MB
- Stars: 267
- Watchers: 13
- Forks: 8
- Open Issues: 31
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: docs/contributing.md
- License: LICENSE
- Governance: docs/governance.md
- Roadmap: docs/roadmap.md
Awesome Lists containing this project
- awesome - open-registry - Community Owned JavaScript Registry (Clojure)
README
## Open-Registry - Open JavaScript Module Registry
Website: https://open-registry.dev
Preliminary npm proxy: https://npm.open-registry.dev
LiberaPay for donations: https://liberapay.com/open-registry-community
> A user-focused registry of JavaScript libraries used, organized and funded by the community
### Features of Open-Registry
- Serves a mirror of the npm Registry (npm.open-registry.dev)
- Community funded
- Governed by the community
- Sole focus on providing a library registry
### Try it out
Wanna see how it's performing? You can try it out by using `https://npm.open-registry.dev`
as the `registry` config in your preferred client.
```
# npm
npm config set registry https://npm.open-registry.dev
# yarn
yarn config set registry https://npm.open-registry.dev
```
### Why Open-Registry?
Rather than relying on private, for-profit companies to host all of our
programing libraries (such as npm Inc hosting the npm Registry), we should
move towards a different model where the stability and durability of the registry
does not depend on a company but the community who is the user of the registry.
If we as a community can come together and fund our own registry, we'll
have full control of what the registry should be and how long we can make it
last.
The initial idea is to setup a full mirror of npm and serve it to the public.
All the metrics will be public and viewable by anyone, and same with the data
in the registry itself.
This will of course need to be paid for, which will also be public. All the
payments and bills that will occur because of Open-Registry, will be publicly
trackable, and also the income which will be by donations.
So, it's time for developers to put their money where their mouth is, and start
prove that a self-organizing community can self-care about it's needs.
### Metrics Interface
What would you want to know?
- Number of instances for hosting
- How many errors are happening currently?
- How many packages is the registry serving currently?
- How many of those are cached?
- How far back are we from the npm registry?
### Some Handy Links
- https://baremetrics.com/open-startups
- https://en.wikipedia.org/wiki/Public_utility
- https://en.wikipedia.org/wiki/Public_service
- https://en.wikipedia.org/wiki/Dead_man%27s_switch
- https://docs.opencollective.com/help/developers/api
- https://medium.com/open-collective/open-collective-graphql-api-preview-3b42ed1d55ff
- https://graphql-docs-v2.opencollective.com/account.doc
- http://www.apache.org/foundation/how-it-works.html#meritocracy
- https://opensource.guide/leadership-and-governance/
- https://status.npmjs.org/
- https://github.com/open-services
- https://github.com/victorb/open-registry