Brett Sun

cc @delfipolito This looks like something to do with docusaurus rendering

~~Ah yes, we must have updated packages/etc. for this repo to be compatible with node 12 (lots of older crypto libraries broke with node 12 and `scrypt`).~~ ~~In the meantime,...

No strong feelings, but `build.aragon.org` does sound a bit like a nightly build URL (but maybe not for most of the audience). If anything, `developers.aragon.org` might sound the best. >...

Highly agree with @0xGabi; we have a lot of room to improve the experience for both _technical power_ users as well as _developers_, and these two have very different needs....

Been thinking about this a bit more, and starting to come down to: - One site (hack.aragon.org, aragon.org/hack, or `s/hack/build/`) to act as a map - Introduce the areas of...

@lkngtn @john-light Can we close this in favour of AGP-1?

We should also include [`CODEOWNERS`](https://help.github.com/articles/about-codeowners/) in the governance process.

@john-light Agreed on adding a small section just to mention it.

From [EIP1167](https://eips.ethereum.org/EIPS/eip-1167), the bytecode contained in the proxies don't include any invalid opcodes so I don't think that's the case. However, the proxies previous to #252 were computing the proxy...

@bpierre Agreed, I really like how this looks and it's much simpler :). > Govern REST API Agree that we can keep this in our minds, but wait until we...