init
This commit is contained in:
30
collections/tfgrid3/governance/gep.md
Normal file
30
collections/tfgrid3/governance/gep.md
Normal file
@@ -0,0 +1,30 @@
|
||||

|
||||
|
||||
# Grid Enhancement Proposal
|
||||
|
||||
GEP stands for Grid Enhancement Proposal.
|
||||
|
||||
A GEP is a document (can be on forum) providing information to the ThreeFold community, or describing a new feature for the TFGrid or its processes or any other change as is managed by the TF DAO.
|
||||
|
||||
|
||||
## Requirements before a GEP can be voted
|
||||
|
||||
- The why and how needs to be well enough defined and specified
|
||||
- The GEP always needs to be in line with planet/people first values
|
||||
- There needs to be a forum post linked to it which gave people the time to discuss the GEP
|
||||
- The GEP should provide a concise technical specification of the feature and a rationale for the feature if relevant.
|
||||
|
||||
## Process
|
||||
|
||||
- A GEP gets registered in TFChain.
|
||||
- Community has to approve a GEP
|
||||
- Guardians can block a GEP and ask for a re-vote (e.g. if mistake in process would have been made)
|
||||
- Guardians and or TFCoop Team needs to implement
|
||||
|
||||
## Voting Power
|
||||
|
||||
- 1 TFT, 1 Vote (NEW for TFGrid 3.14 and still needs to be voted by a GEP at March 21 2024)
|
||||
|
||||
|
||||
*some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
||||
|
||||
Reference in New Issue
Block a user