Summary

A clear governance process is key for the DAO future. Clear guidelines help members to promote their ideas to become without the uncertainty created by unclear or scattered resources and guidelines. This proposal presents a life-cycle that upgrades our current processes and deliver a step-by-step guide that can be followed by any member.

• Full Discussion
• Note: The proposal has received a good support on the Forum polls, showing over 90% acceptance withing the poll participants.

Motivation & Scope

We expect to address the following points to allow proposals to be positioned for voting only after achieving an execution-ready status depending on their complexity.

• Segregate Complex from Simpler proposals
• Defining an approach that uses Gates and Stages
• Creation of a workbooks and templates
• Define Votes types and characteristics
• Quality assurance and community suppor through a moderator position

We propose to introduce the following changes

1. Governance

1.1 Categories

Votes types are categorized in two main categories, and each one serve their own process flow

• Improvement proposals
• Generic Proposals

1.2 Vote Types

All votes casted in Snapshot should be following one of these categories and consider the durations given below as the minimum required for their length. Types are categorized between Critical and Non Critical.

1.3 Gate Baker

Moderation is a need to assure that:

• Members support and education over the proposal flow
• To assure submitted votes have met the gate-ready criterias
• Keep a DB for the submitted roles and segregate valid from invalid votes to support the Governance Mining eligibility criteria process
• Moderate the forum to lead conversations and keep conversations momentum and on topic.

2. Introducing Gates

Gates will act as check points designed to drive proposals efficiently and require a Snapshot vote. The amount of Gates will depend on the proposal type

• Improvement Proposals: Gate 1 >> Validation >> Gate 2 >> Execution
• Generic Proposals: Gate 1 >> Execution

2.3 Considerations

• PIP Acceptance Criteria
  • In order to pass a PIP: 5% or more of veDOUGH supply must participate (current_supply * 0.05 = result), and 60% or more of participating tokens must vote in favor (FOR)
• Maintenance
  • Casted votes not following the gate steps won’t be considered for the Governance Mining Rewards eligibility process. The only exception will be Critical votes types.
  • Snapshot entries will not be removed from the system.
• Naming Convention
  • Proposals can or can not have a PIP number. Either case it is expected that they follow the following naming structure to facilitate reading
    • Without PIP # → [Gate #] Proposal title
    • With a PIP # → [PIP-#] [Gate #] Proposal title

3. Introducing Stages

Stages are all the steps and activites that happen between gates, which do not require a Snapshot vote. They tick all the boxes for the conversation to move towards a gate vote in good shape, and determine the flow expected for the whole lyfe-cycle of each proposal type.

3.1 Generic proposal stages

• Forum Discussion: Proposed Idea to be discussed in the Forum
• Gate 1: Validate the community agreement through a vote
• Production Release: Execute the proposal

3.2 PIP stages

• Forum Discussion: Proposed Idea to be discussed in the Forum
• PIP Gate 1: Gauge members support on the Idea
• PIP Refinement: Improvement Proposal refinement
• PIP Validation: Validation of Scope
• PIP Staging: Proposal pre-gate Staging
• PIP Gate 2: PIP Voting
• Production Release: Execute the proposal

4. Processes flows charts

Flows are visual aid images to understand what to do on each step, and they vary depending on the Proposal type.

• Generic Proposal Flow
• PIP Flow
  • Standard Proposal Flow
  • Pie Proposal Flow

Benefits & Risks

Benefits

The PieDAO Governance process has been defined in several documents that are currently not linked to one another. This can create friction and uncertainty for users to submit ideas and for community members to visualize next steps. While studying the current status, two discussions opened the door to rethink the current Idea→PIP→Vote flow to include a broather set of definitions to bootstrap the whole process.

Risks

No risks identified

Next Steps

If the community vote in favor of this proposal, the next steps will be:

1. Manage all new votes under the approved process
2. Kick-off the Gate Baker role to start assisting new entries
3. Publish the process on PieDAO docs

Closing notes

Clarity during the process, good level of support, visibility on the next steps and MVP quality standards assurance are the key deliverables that will make us implement great products and changes and facilitate the decision making for the PieDAO community members.

We ask votes to show their support For or Against the current proposal, or to select Detail more if you think it’s not ready yet for implementation.