Summary of Proposal
To create a standardised naming system for proposals that pass their temperature check.
After a proposal passes the ‘temperature check’, that is, the non-token vote done here on Discourse, then it is assigned a ‘SIP’.
For consideration, I suggest a simple convention of:
SIP 1, SIP 2, and so forth.
The first SIP, SIP 1, is the first proposal to pass its temperature check and be placed on snapshot.
Motivation for Proposing
As the DAO matures it deserves a more structured approach to it’s discussion of proposals, as well as a clear reference on offer for each high signal proposal that passes the temp check. Therefore I believe we can take a very basic, yet high-value step, to implement a naming convention.
Reasons supporting the proposal
- Low effort implementation
- Each proposal will have a clear reference
Reasons against the proposal
- You dislike structure
- Yes to SIP 000
- No to SIP 000
This proposal didn’t reach the required quorum. However, things have evolved since we first brought this proposal up to vote. Meanwhile, as described above, the SIP convention was adopted by the protocol core team to refer to protocol updates, including core protocol specifications, client APIs, contract standards, and others.
If you plan to start contributing, make sure to follow the procedure as described here: GitHub - bloxapp/SIPs
As for DAO governance proposals, there is consensus among the team that those proposed changes shouldn’t rely on the same convention not to create confusion between both distinctive areas. We’ll monitor the situation closely, but for now, don’t use SIPs for DAO governance topics. Instead, make sure to use the correct category here on the forum. As a cleanup action, I have removed SIPs from older forum posts.
Feel free to contact me if you have additional thoughts or ideas on how to structure things.
All SIPs: SIPs/all.md at main · bloxapp/SIPs · GitHub | SIPs Discussion Board: bloxapp/SIPs · Discussions · GitHub · GitHub