Consultation v2 — Product Scope Document

If the majority vote to “abstain” it tells me there is indeed interest in the idea (based on the high vote participation), but not enough to make a decision.

That implies that the creator either needs to provide more clarity and justification, or that we table the discussion entirely until the sentiment among the majority says that it truly needs to happen. Not Now ≠ Never

Capturing and storing these ideas for later is actually a healthy strategy.

Yes, that seems logical. But we need to define what happens if the quorum is hit and majority abstains.

From what I understood from Timan’s comment, he meant to promote to “real” proposal even if majority abstains.

From what I understand from your explanation, you’d want it to signal the proposer to improve their TC?

Last probably makes most sense to me.

Thanks for the responses, always useful.

Follow along with or contribute to the work @xStelea and me are doing on Consultation v2: GitHub - radixdlt/consultation_v2

Feedback is still much appreciated :wink:

Since it’s a temperature check, Peachy’s proposal to improve the idea makes sense.

I was still thinking about voting on “real” proposals in a DAO, where you need a go or no-go outcome, not necessarily a “retry”.