Publish aragonOS internal apps to aragonPM

aragon / aragonOS

(Aragon 1) Reference implementation for aragonOS: a Solidity framework for building complex dApps and protocols

GNU General Public License v3.0

686 stars 245 forks source link

Open sohkai opened 5 years ago

sohkai commented 5 years ago

Not quite sure how we should do this, since aragonCLI assumes we use a one-contract-per-repo structure, but we should publish the ACL, EVMScriptsRegistry, and Kernel to aragonAPM with their associated artifact metadata (see https://github.com/aragon/aragon.js/blob/master/packages/aragon-wrapper/artifacts/aragon/).

Maybe we could specify a contract address when creating a new repo, and then publish from a different directory that holds the metadata?

sohkai commented 5 years ago

We could also think about doing this for the DAOFactory, since it's used by so many kits: https://github.com/aragon/dao-kits/issues/64

sohkai commented 5 years ago

Notes from an offline discussion:

Investigate if upgrading to truffle 5 allows us to get the natspec docs so we don't have to use our own regex in the CLI (solidity-extractor)
Investigate how difficult it would be to generate ACL and EVMScriptsRegistry's artifact.jsons and upload them to IPFS by hand
Publish new versions of apm-* internal repos with their artifacts