edits
This commit is contained in:
parent
79a925bfc2
commit
9adaed95da
@ -4,32 +4,32 @@
|
|||||||
|
|
||||||
GEP stands for 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.
|
A GEP is a document (can be on the forum) providing information to the ThreeFold community, describing a new feature or processes for the TFGrid and any other change that is managed by the TF DAO.
|
||||||
|
|
||||||
|
|
||||||
## Requirements before a GEP can be voted
|
## Requirements Before A GEP Can Be Voted
|
||||||
|
|
||||||
- The why and how needs to be well enough defined and specified
|
- 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
|
- The GEP always needs to be in line with the values planet first and people first
|
||||||
- There needs to be a forum post linked to it which gave people the time to discuss the GEP
|
- There needs to be a forum post linked to it which gaves the community time to discuss the GEP
|
||||||
- The GEP should provide a concise technical specification of the feature and a rationale for the feature if relevant.
|
- The GEP should provide a concise technical specification of the new feature and a rationale for the feature if relevant
|
||||||
|
|
||||||
## Process
|
## Process
|
||||||
|
|
||||||
- A GEP gets registered in TFChain.
|
- A GEP gets registered in the TFChain
|
||||||
- Community has to approve a GEP
|
- The community has to approve the GEP
|
||||||
- Guardians can block a GEP and ask for a re-vote and explain why re-vote is needed
|
- Guardians can block a GEP and ask for a re-vote and explain why the re-vote is needed. For example if:
|
||||||
- e.g. if mistake in process would have been made
|
- A mistake in the process would have been made
|
||||||
- e.g. if something would happen which puts any of the entities related to TF in danger, e.g. not in line with T&C (legally)
|
- Something would happen which puts any of the entities related to TF in danger, e.g. not in line with T&C (legally)
|
||||||
- e.g. if values are not followed (planet/people first)
|
- Values are not followed (planet/people first)
|
||||||
- e.g. if a change violates our security (e.g. introduction of non opensource in our TF Stack)
|
- A change violates our security (e.g. introduction of non opensource in our TF Stack)
|
||||||
- e.g. if a change has potential to damage someone in our community
|
- A change has the potential to damage someone in our community
|
||||||
- Guardians and or TFCoop Team will implement
|
- Guardians and/or the TFCoop team will then implement the GEP
|
||||||
|
|
||||||
## Voting Power
|
## Voting Power
|
||||||
|
|
||||||
- 1 TFT, 1 Vote (NEW for TFGrid 3.14 and still needs to be voted by a GEP at March 21 2024)
|
- 1 TFT = 1 Vote (NEW for TFGrid 3.14 and still needs to be voted by a GEP on March 21st 2024)
|
||||||
|
|
||||||
|
|
||||||
*some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
*Some inspiration comes from https://www.python.org/dev/peps/pep-0001*
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user