status-im/swarms
2
0
Fork 0
mirror of https://github.com/status-im/swarms.git synced 2025-02-23 15:18:24 +00:00
Code Issues Projects Releases Wiki Activity

add draft of subjective delegation liquid democracy for placehold 172

Browse Source
This commit is contained in:
Ricardo Guilherme Schmidt 2018-04-15 04:09:54 -03:00
parent 926de35936
commit 7c2833a5ac
1 changed files with 78 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

78
ideas/172-topic-democracy.md Normal file
View File

@ -0,0 +1,78 @@
# Democracy
Please submit a PR with the following template filled in. See README.md for more info.
<!-- Please Review https://docs.google.com/document/d/1CaFM2ZXGOKf05_LXMPJeNNy5qJOdAq91EF2Gn2QUBFI/edit# for more details -->
<!-- in PR the document should be named as`DEV#1-title.md` -->
## Preamble
Idea: 172-topic-democracy
Title: Subjective Delegation Liquid Democracy
Status: Draft
Created: 2018-04-15
## Summary
A democracy where you can specify delegate for carbon-voting specific multi level topics or fallback to a predefined defaults if none set.
## Swarm Participants
<!-- Each contributor pledges to the idea with their FOCUS value. (hours per week) -->
<!-- Here all roles in swarm are defined and filled, one of the contributors should responsibility of the Idea as Lead. -->
<!-- Testing/Evaluation support role is also mandatory to check in on specified Goal dates or earlier. -->
<!-- Lead Contributor is the Owner of the Idea. If required, they can get support from a PM, but should be responsible for end to end execution of the Idea. This includes ensuring appropriate resources are allocated, setting realistic timelines and milestones, and any post-launch metrics or bug fixes that are attributed to the Idea -->
<!-- A swarm requires at minimum 3 contributors and 1 evaluator/tester -->
<!-- 'Contributor' should be replaced with a descriptive role type. -->
- Lead Contributor: Ricardo Guilherme Schmidt
- Testing & Evaluation: <!-- @username -->
- Contributor: <!-- @username -->
- Contributor: <!-- @username -->
- PM: <!--- @username -->
- UX (if relevant): <!-- @username -->
<!-- - Contributor: @username -->
## Product Overview
For a democracy where every member understands basic about every subject required for senstive actions inside the network is utopic.
As Status Network decisions would be democratic for the users of the platform, a optional voting capability would be given to SNT owners, where they could set their delegate, or vote by themselfs.
When users don't vote and don't delegate, their influence would be delegated to SGT (Status Genesis Tokens) owners consensus.
<!-- A short (~200 word) description and motivation of the Idea. Without clear explanation the Idea should not proceed. Can include User Stories -->
<!-- Testing/Evaluation role accepts responsbility to checkin at Goal dates, -->
<!-- forces discussion to continue implementation or recommend disband and post-mortem. -->
### Product Description
<!-- What functionality are you adding? What will this look like from a user perspective? Why is this important? -->
### Requirements & Dependencies
<!-- Are there bugs or feature requests in other repositories that are part of this Idea? -->
<!-- There is no approval unless the idea requires to be reviewed by supporting organelles (Financial, Hiring, or Design). -->
<!-- The Swarm must develop a fully fleshed out Requirements document for the idea to proceed, to the satisfaction of participants. -->
### Minimum Viable Product
<!-- Mandatory, completes the Idea in the fastest route possible, can be hacky, needed to feel progress. See https://imgur.com/a/HVlw3 -->
Goal Date: <!-- Date for evaluation in ISO 8601 (yyyy-mm-dd) format -->
Description: <!-- Description of Deliverables-->
## Dates
Goal Date: <!-- Date for evaluation in ISO 8601 (yyyy-mm-dd) format -->
Description: <!-- Description of Deliverables-->
Testing Days required: <!-- Days required at the end of development for testing -->
## Success Metrics
<!-- Assuming the idea ships, what would success look like? What are the most important metrics that you would move? -->
<!-- Example: Onboarding conversion rate. Target >30% full funnel -->
## Exit criteria
<!-- Launch new onboarding UI flow -->
## Supporting Role Communication
<!-- Once Requirements and Goals are fleshed out, then it should be communicated to supporting organelles if required -->
## Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).