Governance Section Improvements Epic about community HOT 8 CLOSED

Should I create a separate issue for improving the Governance Landing page (and other pages individually)?

Is it that whoever picks up a task in this issue creates their own issue and makes this issue dependant on theirs?

from community.

I just made a few of the "X Section Improvements" tickets into Epics. I think we can just make new tickets and ensure that they are linked to the right epic?

from community.

Resources from UX https://www.notion.so/makerdao/Community-Development-x-User-Research-507dac9ff86d48f7b8a334e6c9a04b3b

from community.

I'd like to create a summary of the major governance topics that come up as part of the governance conversation. I feel like this could help on-board voters and give outsiders an idea of what exactly we spend our time debating, hopefully giving them some idea of whether they would be interested.

This would include:

• Stability
• Security
• Growth
• Financials
• Tooling
• Upgrades
• Payroll

I think this covers most of the major topics that are discussed. For each I can write a bit about what is discussed and why it's important.

from community.

I have created a first draft of this page. Feel free to leave feedback here: https://docs.google.com/document/d/1OtwLCSVpfwc-0Y9N7JRd8_BSWvtqlbuvw-JNHvMnn2s/edit?usp=sharing

from community.

Other adds from @LongForWisdom:

• Write up of CMooney's instructions on how to audit executive spells. (https://forum.makerdao.com/t/how-to-audit-executive-contract-code/1292/3)
• Write up of all the parameters that governance is able to change, with descriptions and the trade-offs surrounding changing them in various ways. (Ideally divided by area)

from community.

This issue is outdated due to the new commdev portal.

The governance pages have been rethought and we are in the process of improving them for the V1 launch of the portal and will continue to improve them as the portal is maintained and further developed.

I am closing this issue, this same initiative will be captured in on a newer issue to improve those pages.

from community.

Updated issue:
#761

from community.