Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How Does Membership Work? #23

Open
yeqbfgxjiq opened this issue Apr 29, 2019 · 3 comments
Open

How Does Membership Work? #23

yeqbfgxjiq opened this issue Apr 29, 2019 · 3 comments

Comments

@yeqbfgxjiq
Copy link
Contributor

Proposals are being drafted to change the process of determining membership for the Aragon Coop, but the outcome and timeline of that process is unknown. The current membership process is what is being used today. It seems like if I'm leading a working group in the Coop today, it might make sense for me to be a member? If so, how would that work?

@lkngtn
Copy link
Contributor

lkngtn commented Apr 29, 2019

The current membership processes is essentially:

  1. Create a PR to this repo adding the ETH address you want to use and your keybase handle.
  2. In the PR description include a keybase proof like this one (wrap it in a codeblock so the formatting doesn't get messed up):
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Im @lkngtn on keybase and my eth address for use with coop is 0x625236038836CecC532664915BD0399647E7826b
-----BEGIN PGP SIGNATURE-----

wsFcBAEBCAAQBQJcx3jXCRByBkAPIvBK2AAA2JcQALC9SGZVR8xBGecmiS4ssOMz
uNXkNrc/rvSvSPv103enoDeEcQC2w1KvOodMgR96Xhjl3IJqWt+50890fS0y0GDj
dIiFCToQsPDMVX/HH7RPXTmvIp/w1FHIsBbJQuxb59Je2u7pfpiUrWUuv97HljjX
oFrHQ/kRgrF25fRngSh6FLg3pvU6IJNTyrKOznJGDFEHPhdFSqyyyQrYj2VHxtCV
q2QGDI0YNGT/w+wotrxY8E7Lgy487sWYpDODbGhRIBbHZUHQKYzbDMatd+2pSCKm
Q21iPuC3QioTHedXQh4rJ1pQV8XjiCO3FsmGmVbIEm7BnZfGbNP/9G5MwAPtZF3I
dj3NKu0fwyfXV3ulE3D4NHXOmaiH+llW3U+jEBMNJDOWqfZnTlkYjBr5m2LDhexx
syqKOZT27QqCsko+bjOrngtoaNkJDhO5rNB/Ielj20R0KOpAq1V662Gr8xDyEd+b
zxOefSacaCmiicoKldd4fhsNmNyrcFjcgGrhVqjA1fmpKH15bKXWx2mRC4bkwEnh
4Ms0JuwS6bClk+VHk5w4HDoSUuKFgBuk+LwNwft04T0t7uHAGj1kfJTXqUQbZ6YH
Bsng7sNHap2dn6b9FBOR/B0ee8NGMCnU2qffEYkeaILbcIAu/HPjVc6lBoAYcLb7
BLUksl7yKbM4cz8NZXVK
=9vRZ
-----END PGP SIGNATURE-----

you can use keybase pgp sign -c -m "message to sign" to generate the signed message

  1. Two of the reviewers on the repo will review the PR and merge
  2. I'll mint a membership token in https://mainnet.aragon.org/#/0x940B2B518F761f4c52CDd9865C57D9a907DC5E82/0xb3f5956b4936ed618274a6e87b361d7ef5125a01

There are many ways this process could be improved. I personally do not want to be unilaterally in charge of minting tokens (its centralized and also kind of a pain). I made some suggestions here: aragoncoop/ops#1

But ultimately the whole thing is sort of in limbo until we can adequately define membership requirements and document onboarding better.

@yeqbfgxjiq
Copy link
Contributor Author

Done!

It's too bad we can't use our Ethereum addresses/keys to sign more stuff. Seems like a really natural way to integrate chat and crypto, but afaik there's no apps using the keys of your accounts for encryption and login/identity. It would be really useful, and also make it easier to integrate web3/ethereum stuff into more applications in a natural way.

@julianbrooks
Copy link
Member

julianbrooks commented May 10, 2019

There's general agreement that this process requires refining but so far no firm suggestions at all as to what may work better.
Definitely hear you Luke re requiring to either automate this process (perhaps the end-goal), or at least Gus and I taking this off your hands until properly decentra-fied, with us being a thin-layer membership committee (administrating not decision-making).

@lkngtn please let us know what this requires us to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants