Because upgradeability implies there will be multiple versions of a package of software, we decided to build aragonPM as the main way to distribute different versions of the packages that comprise the Aragon client. As we built it, however, we realized that its use cases could extend far beyond just ours as a publicly accessible piece of infrastructure living on Ethereum.
A package or repository (repo) in an aragonPM registry keeps track of evolving versions of its contents (the webapp component typically) and smart contract code (if applicable).
aragonPM is built on top of aragonOS. It is a Decentralized Autonomous Organization (DAO) running on the same Aragon that‘s used to build Aragon organizations (to take advantage of upgradeability and access control)!
This allows for many aragonPM registries to exist with different governance models for package creation and publishing new versions. There is an official Aragon curated instance,
aragonpm.eth, which has high-quality standards and strict restrictions on what can get published, that we use for publishing our core components.
Different aragonPM registries in which everyone can publish their packages are expected to be created by the community, and we have set up
open.aragonpm.ethon both the main and Rinkeby networks as an open instance available for anyone to publish to.
Do you have a question? Leave your comments here at our Discourse forum 👇