The purpose of this discussion is to streamline the process in which community “temp-checks” occur which simultaneously adding “temp-checks” to community rep (community council voters) duties and removing them from the core teams responsibility.
Currently the way temp-checks are done seems random. From the community perspective, if we aren’t doing them every single SLURP it feels like the community doesn’t “get a say” and while holding reSDL that can feel extremely frustrating, disappointing, and worst case cause dissent.
While the community recognizes that “not every SLURP should have a community vote”, the very nature of 2 community (rep) votes on the council negates this train of thought. Community is the very heart of a DAO. The true purpose of this Discussion is to highlight and ensure the 2 community representative votes on the council are properly able to gauge community sentiment before casting their votes.
Simultaneously this will/should remove any and all “duty” of the Core contributors or SLURP posters from running “temp-check” in the future (unless they so choose to).
PROPOSAL to be tried out (could become a SLURP later if required):
-
Add “Temp-Checks” to the community representative (council voters) required duties and/or the NAILS position (which they are also in agreeance with). (A community temp check space has already been created on snapshot.org). This will allow either the 2 community reps or NAILS to create the temp checks and remove this “responsibility” from the core contributors.
-
“Temp-Checks” will be created within 48-72 hours of new SLURP posting MAXIMUM so that the community sentiment may be gathered WELL BEFORE a council vote occurs. The community 100% recognizes that this “temp-check” shall not interfere with the speed of a council vote. IE: if the SLURP is posted for discussion for 2 days before a 5 day vote is created, the “temp-check” shall end 12-24 hours before the council vote ends as to not further burden the governance process. The last thing this discussion and process is meant to do is add further burdens to the governance process. This Discussion is intended to highlight and ensure the community reSDL weight is heard via the representative’s votes.
-
“Temp-Checks” Shall always end BEFORE Council votes end as to not further burden the protocol. The community understands this is not further adding any governance to the protocol, this is simply a way to streamline the process in which the community can make their reSDL weight be heard.
-
A new Snapshot.org group named "Stake.LINK Community Temp Check Proposals " has already been created with the author privileges going to both community reps and NAILS.
This meta-discussion could easily be transferred to become an official SLURP if it sees success, but for now we can try this out in an unofficial capacity. In tandem with this discussion being posted a Temp-Check will be created to show the way it will work from now on and allow community to vote (even if there is nothing official happening) to see the process and understand that the community reps want to represent the community of reSDL’er properly and to the fullest extent.
