Voting: more granular permissions to separate creating informative and binding votes

[pythonpete32]

It is possible to open a signalling vote using the Voting app. however it requires the same permissions as a binding vote. This doesn't make that much sense. in most cases, you want only token holders to have the ability to open votes which means you have to create a vote to create a non-binding vote

[john-light]

@pythonpete32 are you suggesting that "Create new informative vote" should be its own permission separate from a "Create new binding vote" permission?

[sohkai]

Let's keep discussions about this here, but in an effort to make sure only immediately relevant items are left as open issues, I am closing this and adding a stub to aragon/aragon-apps#1101.

We currently do not parameterize newVote() with authP(), so this is technically not possible today even with an custom permissions parameter or ACL oracle.

[pythonpete32]

Pythonpete32 are you suggesting that "Create new informative vote" should be its own permission separate from a "Create new binding vote" permission?

Yes. Having the same permissions for both limits its utility. For Collab19DAO I tried to create a signalling vote, but to do so, I had to create a vote to create a signalling vote, which obviously doesn't make sense.

[sohkai]

One way to do this right now is to install two voting apps—one that is open and can allow any member to create votes, but has no permissions to actually do anything in the org, and another that is more restricted and does have permissions.

You can also chain these up, such that you go with Voting (open) --passed--> Voting (closed) --> target action

[pythonpete32]

You can also chain these up, such that you go with Voting (open) --passed--> Voting (closed) --> target action

This is a cool pattern!