[DRAFT] - Simplify the Developer DAO Improvement Proposal (DDIP) Process

Quorum Requirement: A minimum of 50% of existing members of the Governance allowlist must comment on the proposal.

I am not loving replacing the forum vote with this comment requirement. First, it gives the existing members veto power. Second, as it just requires comments a comment that is meant to encourage future discussion or disagree with the proposal.

We are hoping to avoid stalling at the forum stage. We did not want to reduce the forum voting quorum because of possible sybil attacks on the forum votes.

I suggest we move to a Discord vote with a reduced quorum. The Discord vote will be protected by the membership token-gating, ensuring only members are voting. This will let us reduce the voting requirement and move quickly.

The poll can be created at the same time as the forum posting and run for 5 days. This will add no time to the new process.

1 Like

Thanks for the feedback and suggestion. Hearing the concerns. For context, the approach was inspired by Gitcoin’s approach.

I don’t believe moving the vote from one place to another is an answer. Core to these suggested changes is the view that asking people to vote on the same things twice feels like a bad UX for members who actually want to participate.

Regardless of where or how those votes are done. cc @Erik_Knobl @luan

In current wording, they collectively have a veto, but no single person does. So long as > 50% (imagine we’d make this a number as the list grows) have shared their views, all it needs is one of these people to support it for it to be elevated. This is basically how budgets work currently although reading back it’s not totally clear here this was the intention. Will amend.

As more people join this group, that power gets decentralised relatively quickly into the hands of folks who’ve contributed which gives us a nice path to decentralising leadership whilst maintaining Sybil resistance.

Think it’s important we have somewhere that “if you submit a proposal that asks the foundation directors to break the law, it will be rejected” - is there another place you’d suggest we have it?

It makes me think, though… if there is a possibility of the law’s being broken, checking that after the vote might not make the most sense :joy:. I am unsure exactly how to handle this but I will stew on it and take a look at other Governance structures and would love any ideas!

@Bobbay would be good to know how the org’s you’re a delegate in handle this

  1. All members with power to move proposals to snapshot have soft veto power somehow. The question here is: is that really a bad thing?
  2. Agreed, more clarification on “comments” may be needed @kempsterrrr
  3. Interested to hear the rationale behind having two votes in a single process. What is this step trying to accomplish?
1 Like

Thoughts on this :point_up:?

I feel we need people engaging and sharing their views, good or bad, and once enough people who have contributed a lot (enough $CODE to be on the allowlist) have shared their views, it’s OK to go to a vote. I don’t feel any arbitrary rules would help, tbh. I would prefer to see more stuff get to snapshot and be rejected than less stuff, and it all gets accepted as feels healthier for Governance.

I would suggest more definition on what a “comment” is. Should they clearly endorse/reject the proposal? Asking for clarification counts? A neutral comment counts?
Otherwise, yes, I agree with the overall proposal.

I’m leaning towards not putting any specific requirements into the comments for a few reasons:

  • as the DAO continues to decentralise, my hypothesis is how much someone participates correlates quite strongly to how much value people place on their comments/opinions. feels more natural to let people engage how they want, and then members can judge based on that. suspect this will become more important if/when we introduce delegation.

  • we also don’t know the answers to what is right and what is wrong. a primary goal for this proposal is to speed up Governance and get us to do it more. the hypothesis here is the more rules there are, the fewer folks will participate

  • this approach IMHO encourage people who want to influence to think freely and get involved in governance, campaign for their own ideas/suggestions/changes in their own way

Ofc interested in seeing what some criteria here might look like if folks have ideas

cc: @Erik_Knobl & @kempsterrrr

I just view our DAO as very different than Gitcoin - it’s formation, financial control, etc. And thus the governance process should reflect that.

A smaller quorum vote that allows DAO members to control what moves forward and what doesn’t seems more democratic. I don’t necessarily buy it’s a bad UX if we have users opt-in to the role that notifies users of a pre-vote.

I do think if we keep it as proposed with the comments, it’s still good and an improvement on the current process.

I was thinking this was already ratified through the foundation acceptance, so no need to list it other places. The process will be followed regardless.

Completely agree mate. The next thing I’m working through is a new operating model that replaces the current budget process with something that sets a much higher bar but empowers people further and removes commercial concerns from the day-to-day DAO coordination and Governance challenges so folks can more freely create value, some of which will flow back to the DAO to be re-allocated by Governance.

this is in the works here. still early though.

Opt-in notifications is a good solution atm, as long as we don’t request any minimum amount of votes, just a positive/negative result.
We may also find more engagement/discussion of proposals in Discord. I’m open to try it.

@Erik_Knobl @willblackburn @wolovim @luan @isiah @Bobbay

Aiming to elevate this to a forum vote tomorrow. If anyone has any final thoughts would appreciate them before the last edit :pray:

Expect this is going to need a concerted effort to pass 100 votes on the forum (a large reason I think this proposal is an important step for us to move faster with Govenance).

1 Like

I don’t believe giving power to comments will provide the improvement you are hoping for unless those comments are from a selected amount of people I.e. budget stewards, core d_d people, D_D council.

Who are the governance allow listed members?

I like that we are removing the forum vote though. It’s a big step forward and this image is a good depiction(ty @kempsterrrr ) of what we should aim for, but ill have more context once I know how these gov members are

@isiah was going to hold a Proposal Q&A. Can we do that before the forum vote? When could that be held? Sooner is better.

Thanks for the quick reply!! Re Governance allow list

This is not really about giving power to comments. What is being suggested in once > 50% of folks already recognised by the DAO via $CODE allocation have shared their views, greenlight light for another to move to snapshot - regardless of if comments are good/bad.

Tomorrow? We have the TH I think cc @luan

vote really needs to go up tomorrow looking at timelines otherwise we’re going to be hard blocked to move anything in Jan as we wont be able to pass this during the holidays IMHO.

also @willblackburn @isiah any reason why this Q&A can’t happen during the vote?

(who is 0x4e8AD3c90f026E4d034b81BA0e1A929E77D80b36 in the allow-list?)

What happens if those members just ignore the DDIP? If I have a proposal, ping those members, and they just don’t post? What happens if the majority of members become inactive?

this is my old address. needs to be rotated out.

Good question. I mentioned in one of the comments above as this list grows we’d probably wont to make it a number rather than a % (or reduce the %) as expecting that many people to stay on top of Governance is a big ask.

1 Like

This proposal has now been moved for a forum vote - P-21: Simplifying the Developer DAO Improvement Proposal (DDIP) Process