[COMMENCE OFFICIAL PROPOSAL]
I’d like to propose that we take a step forward in our self-governance and add an official community proposal process. I’d like to propose that the following steps be taken prior to advancing a proposal to official status on our snapshot.
Note: For the time being, I think it makes sense to empower the devs to circumnavigate these guidelines, especially in matters where time is of the essence.
Proposed Proposal Process, First Draft
Discuss ideas in Discord, Telegram, and in the Governance channel on our forums. Collect opinions and insights and craft a thorough and well-aritculated proposal.
Post your complete proposal to the “Pickle Improvement Proposals” category on the forums. During this stage, we encourage the community to suggest changes, edits and to write dissent pieces.
3. Rather than editing the initial proposal, the “proposer” will incorporate edits into new posts on the same thread until a version can be crafted that garners widespread community support.
EDIT_1 3. The proposer will edit the initial post to add or subtract based on contributions from the community. All edits must be clearly marked in the proposal.
4. The community will signal their support by using the <3 (heart / like) function. Once a version has been posted that has 20 “likes” (subject to change over time), the devs will officially announce (using announcements in discord) a 24-hour period to review the proposal prior to posting to snapshot.
EDIT_2 4. The proposer will include a poll to show support for their proposal. The proposal can be finalized once one of two metrics have been achieved: 1. 20 or more votes in the affirmative OR 2. Greater than 75% support, 48 hours after posting. Whichever of these comes first
EDIT_3 4. The proposer will include a poll to show support for their proposal. If after 24 hours, the proposal has received more than 75% votes in favor, the devs will announce it to the community. This triggers another 24-hour review period PRIOR to posting to snapshot. If a proposal never reaches 75% support on the forums, it will not be announced for official review and it will not posted to snapshot.
EDIT_4 4. The proposer will include a poll in the forum thread to gauge support for their proposal. In order for a proposal to be advanced to the official voting stage, it must meet three criteria:
a. Posted on forums for more than 48 hours
b. Received more than 20 votes on the poll
c. Received 75% “Yes” votes
Once all three of the above are met, a final 24-hour review period is announced.
Both before and during this official 24-hour review period, community members may write “dissent” pieces and tag them as such on the same thread. The text from the post tagged with “dissent” that has the most “likes” should be included in the proposal on snapshot below the language of the proposal.
All Community-created PIPs EDIT_6: that meet the criteria of “community action” should be posted to snapshot with the following details included:
A) Text version of the proposal
B) Text version of the most popular dissent piece (when applicable)
C) A Link to the official thread for the proposal.
D) The actual button language should be consistent every time as well except in cases where multiple options are presented in the proposal. Buttons will have the text:
a) Implement this proposal as written
b) Do not implement this proposal as written
- Once a proposal has cleared the 24 hour review period, it should be posted to “Core” by the dev team and announced on the announcement channel in discord.
How to get a community vote on snapshot
-Meet these criteria
1) 48 hours up
2) 20+ total votes
3) 75%+ votes in affirmative
-Devs announce proposal on Discord with 24 hour wait period
-24 hours to write dissent pieces
-Official voting begins. Proposal posted to snapshot including most popular dissent piece and two options: “Implement Proposal as Written” and “Do not Implement Proposal as Written”
EDIT_5 A Note On Community Proposals
As we work towards self-governance, it’s extremely important to understand the purposes and limitations of community proposals. Populist “wish list” items that do not meet the fundamental criteria of “community action” cannot be expected to progress. Here are a couple types of examples of what does not qualify as community action:
1- Personal / Real World Implications. For exmample: “Vote to Compel 0xPenguin to Change his Name to 0xPICKLE” might be popular, but it’s not why we’re here. “Vote to Have Devs Reveal Their Identities” is also not within the realm of community action.
2- Feature Requests. While feature requests may be voted on, they should not be considered binding, especially in cases where they may present additional risk, cost, or complexity.
3- Detrimental to the Protocol. An example of this would be something like “Vote to distribute the entire dev fund to the wallet addresses that vote YES on this proposal”. Self-explanitory.
This list is likely to grow over time, but the idea here is that we all work in good faith to understand the limits of community governance. I’d like to think I can speak for most of the active members here in saying that we trust that the devs will act in good faith at all times when considering these and any new limitations to self-governance.
— [ END OFFICIAL PROPOSAL]
Edit_6 (10/10) Added a phrase to make clear that proposals that violate the guidelines presented here and in other places will not be added to snapshot in any official capacity
If possible, I’d like to use this thread as a meta-experiment on how this could all work out. Please use your like button to signal that you would support the proposal as written. Please suggest edits if you have them and please write dissent pieces tagged with “DISSENT” at the top if you disagree with the very nature of this proposal.
I’m a bit self-conscious about number 7. It may be that the right solution is to have the community member post to “Community” but the devs still announce. Curious your thoughts.
Thanks in advance!
- Submit the proposal as written
- Do not submit the proposal as written