GM 3.1 : Governance cycle V2

Author:

Ze_Boubs

Proposal date:

February 22, 2022

Summary:

Change the Governance Cycle framework ratified in the GM1.2 - Enact standard governance process based on feedbacks from the first 2 GC. Ease process management for governance team and simplify the overall process.

Risks:

Add confusion.

What are the changes being proposed?

gmDAO governance runs on a 7 day cycle.

Pre - GC :

Idea

When a community member has an idea for a proposal, they are encouraged to pitch the idea in the #dao-ideas channel, gather opinions and encourage people to chat about it.

Proposal

If the community member would like to move forward based on initial feedback, they need to create a formal proposal based on a proposal template under the draft Notion’s section and post it in the #proposals Discord channel. A discussion thread should be created under the proposal to allow for community feedback. Tag a (Governance member) and ask that it be included in the next Temperature Check when you feel it’s time to do so.

Note: The proposal can be included in the actual Tgovernance cycle if submitted prior to Day 1. Either way it will be included in the next governance cycle.

Governance Cycle Phases

Phase 1 - Temperature Check

A 2**-day temperature check** reactions will be created for each submitted proposal prior to day 1 of the governance cycle. The temp check is displayed as a 🟢 or 🔴 reaction under each proposal included in the actual GC. These reactions are meant to show contentiousness of the proposal.

During the temp check, the author can update his proposal based on the DAO's feedback, and is able to postpone his own proposal to the next GC.

Proposals must conform to a Governance template (see Proposal Types and Voter Responsibilities below) or provide a minimum one sentence explanation of why they does not conform to a template.

Notes: Proposals that cannot be executed will not move to the next step.

Proposals that have at least 20 🔴 will automatically be postponed to the next GC; as an incentive to review it and raise more consensus. However, the author will be able to force it into snapshot at the next GC regardless of any contentious opinion.

Phase 2 - Voting Off-Chain

Formal voting is conducted in Snapshot. Voting will be open for at least 48 hours. Typically, voting will open on day 3 of the governance cycle and close on day 5 .

All Snapshot proposals are decided based on single-choice vote. Some types of proposals are conducted by $gmDAO token holders, others are conducted by specific subsets of DAO contributors defined below in Proposal Types and Voter Responsibilities.

Each Snapshot proposal must include the full proposal text, a link to an immutable (IPFS or Arweave) version of the proposal text, and a link to the discord discussion.

Proposals that have at least 60% approval from 40 or more addresses pass and are queued for execution.

Phase 3 - Execution

The proposals that passed voting are now ratified and will be executed as soon as possible by the responsible entities.

This can for example involve the transfer of treasury funds which will be executed by the DAO's Gnosis multi-sig (0xe1a4cb40A1D672Bb7901b646Bb18Eb7B70BD5952)

What is the goal of this proposal?

Get rid of the temp-check vote channel, and allow members to have a quick feedback on contentious proposals. Introduce the ability for the community to postpone a proposal to the next GC to encourage consensus and discussion before voting.

It allows people to force their proposal into snapshot in the next GC even if they don’t raise consensus in the temperature check.

What is the expected impact of these changes?

Enhance commitment for members in proposals submission.

What help might be needed from gmDAO and its members?

Your answer here.

Sponsors:

Nodallydude, 0xSTVG, De-Fi Beats, cxkoda, Ze_Boubs