Voting settings not behaving as users expect

[ivelin]

Problem

There seems to be a disconnect between the expectations that users have with voting settings in the UI and the consequent behavior of the contract and UI. Here is a thread related to a situation where users set 75% supermajority parameter but it turned out the contract uses simple majority rule.
https://discord.com/channels/923399898769018921/925091695677309059/1005085447720014005

Solution

• Reconsider UI flow for voting parameter settings at new DAO deployment.
• Expose more clearly the current voting rules in the UI.
• Allow users to adjust settings in UI
• Write 100% unit test coverage for governance functions in the UI.
• Write 100% unit test coverage for subgraph scripts related to governance functions.
• Write 100% unit test coverage for smart contract functions related to governance.

[nerderlyne]

Governance settings for proposals are set more in line with user expectation and behaviour now. I don't think this was the case at the time Sporos was deployed.

https://github.com/kalidao/kali-ui/blob/main/components/deploy-dao/checkout/index.js see 142

[nerderlyne]

What flow would you suggest for governance settings specifically?

I am interested in converting the flow to a page with templates(entity + gov settings + extensions). This will also tie in with a guide expanding on each template.

[ivelin]

What flow would you suggest for governance settings specifically?

I am interested in converting the flow to a page with templates(entity + gov settings + extensions). This will also tie in with a guide expanding on each template.

Good question. I pinged our UX gigabrains to chime in here.