36 lines
1.5 KiB
Markdown
36 lines
1.5 KiB
Markdown
|
|
|
|
# Grid Enhancement Proposal
|
|
|
|
GEP stands for Grid Enhancement Proposal.
|
|
|
|
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
|
|
|
|
- The why and how needs to be well enough defined and specified
|
|
- 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 gaves the community time to discuss the GEP
|
|
- The GEP should provide a concise technical specification of the new feature and a rationale for the feature if relevant
|
|
|
|
## Process
|
|
|
|
- A GEP gets registered in the TFChain
|
|
- The community has to approve the GEP
|
|
- Guardians can block a GEP and ask for a re-vote and explain why the re-vote is needed. For example if:
|
|
- A mistake in the process would have been made
|
|
- Something would happen which puts any of the entities related to TF in danger, e.g. not in line with T&C (legally)
|
|
- Values are not followed (planet/people first)
|
|
- A change violates our security (e.g. introduction of non opensource in our TF Stack)
|
|
- A change has the potential to damage someone in our community
|
|
- Guardians and/or the TFCoop team will then implement the GEP
|
|
|
|
## Voting Power
|
|
|
|
- 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*
|
|
|