Proposal for Membership Committee

[lkngtn]

We would like to efficiently and securely distribute membership to new members who apply to the cooperative without each member having to vote in every new member. I propose the following procedure:

1. We require a member vote in order to issue tokens, we can use this to pre-approve a certain number of new memberships
2. We elect a membership committee by assigning the individual members the assign tokens role
3. We can define arbitrary requirements for membership and rely on the membership committee members to use their judgement when assigning membership tokens.
4. Members apply by creating an issue on the membership repo, including a signed keybase message including their ETH address.
5. A membership manager will create a PR which closes the issue and assign a token.
6. Members can be removed by a vote using the Burn Tokens permission.

[lkngtn]

I'll test this on a rinkeby org to make sure that there is no issue with using the issue tokens function with a non-transferrable, balance-capped token like the member token.

[imestin]

where can we see the source code of the issue tokens function?

[lkngtn]

@imestin https://github.com/aragon/aragon-apps/blob/master/apps/token-manager/contracts/TokenManager.sol

[0xjjpa]

@lkngtn I'm going to draft a quick spec on a possible workflow to authenticate individuals through Keybase using an ethereum address. Going to code a quick app to see if it's something we could actually use for then proceeding on requesting the membership through this instead of asking people to open Github issues.

[pythonpete32]

@lkngtn how did you get on with this? Is this still a viable possibility