merge main_commsteam to main with fixed conflicts
This commit is contained in:
@@ -4,32 +4,32 @@
|
||||
|
||||
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 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.
|
||||
- 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 TFChain.
|
||||
- Community has to approve a GEP
|
||||
- Guardians can block a GEP and ask for a re-vote and explain why re-vote is needed
|
||||
- e.g. if mistake in 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)
|
||||
- e.g. if 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)
|
||||
- e.g. if a change has potential to damage someone in our community
|
||||
- Guardians and or TFCoop Team will implement
|
||||
- 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 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*
|
||||
|
||||
|
||||
@@ -1,8 +1,7 @@
|
||||
|
||||
|
||||
# Governance
|
||||
|
||||
Governance is important to us, there is a wish from TF DMCC to outsource the operations and promotion to a cooperative and the community for which we suggest a combination of GEP, Guardians and a Cooperative
|
||||
Community governance is important to us. TF DMCC is working to outsource the operations and promotion of the TF Grid with a community-led / cooperative approach. To achieve this, we are releasing a series of Grid Enhancement Proposals (GEPs), searching for a group of Guardians, and establishing the ThreeFold Cooperative.
|
||||
|
||||
## Planned for 3.14 (our next release)
|
||||
|
||||
@@ -12,5 +11,9 @@ Governance is important to us, there is a wish from TF DMCC to outsource the ope
|
||||
|
||||
## Treasury
|
||||
|
||||
<<<<<<< HEAD
|
||||
This section needs to be filled in by the team.
|
||||
|
||||
=======
|
||||
This section needs to be filled in by the team.
|
||||
>>>>>>> main_commsteam
|
||||
|
||||
@@ -5,25 +5,24 @@
|
||||
|
||||
TFGrid 3.13 requires 9 guardians to start with.
|
||||
|
||||
Requirements
|
||||
Requirements:
|
||||
|
||||
* Good knowledge how to use Linux to allow you to deploy
|
||||
and upgrade your validator starting from code.
|
||||
* At least 4h time available per week (will be more at start)
|
||||
* Willingness to participate in the forum of TF and coordinate with Coders or TFTech who is main contributor of code.
|
||||
* You feel aligned with our values of planet and people first
|
||||
* Willingness to look at open issues at least 5 times a week (there is chat and email notification) unless during the holiday period.
|
||||
* Choose a backup which can help you when needed (sick, holidays, …).
|
||||
* Complete your candidacy on our forum on … Fill in the motivation, your profile, …
|
||||
* Get at least 3 people from the community to endorse your skills and motivation.
|
||||
* Good knowledge of how to use Linux to be able to deploy and upgrade your validator starting from code
|
||||
* At least 4 hours of time available per week (this will be more at start)
|
||||
* Willingness to participate in the TF forum and coordinate with coders or TF9 who is the main contributor of code
|
||||
* You are aligned with our values of planet and people first
|
||||
* Willingness to look at open issues on Gittea (our work tool) at least 5 times a week (there are chat and email notification) unless it is during the holiday period
|
||||
* Choose a backup who can help you when needed (e.g. when sick or on holidays)
|
||||
* Complete your application on our forum (fill in your motivation and profile)
|
||||
* Get at least 3 people from the community to endorse your skills and motivation
|
||||
|
||||
What do you get in return
|
||||
What you will get in return:
|
||||
|
||||
* Eternal recognition from your Regional Internet community (-:
|
||||
* TBDk USD per month in TFT as provided by the *TFCOOP
|
||||
* The TFT will come from the *TFCOOP Treasury
|
||||
|
||||
## They will host a validator
|
||||
## Guardians will host a validator
|
||||
|
||||
- see [validator](validator.md)
|
||||
See documentation on [validators](validator.md) for more information.
|
||||
|
||||
|
||||
@@ -2,11 +2,11 @@
|
||||
|
||||
# ThreeFold Cooperative
|
||||
|
||||
ThreeFold Dubai would like to hand over the day2day operation of the TFGrid to a cooperative.
|
||||
ThreeFold Dubai would like to hand over the day to day operation of the TFGrid to a cooperative.
|
||||
|
||||
- Cooperative are very trustworthy decentralized structures which allow upto millions of people to be part of a common goal.
|
||||
- Cooperative members vote for their directors which might be the Cooperative Founders
|
||||
- Untill this is done we keep on operating from ThreeFold DMCC
|
||||
- Cooperatives are trustworthy decentralized structures which allow millions of people to be part of a common goal
|
||||
- Cooperative members vote for their directors
|
||||
- Until this is done we will continue to operate from ThreeFold DMCC
|
||||
|
||||
## Cooperative Founder
|
||||
|
||||
@@ -14,36 +14,37 @@ TF Dubai is looking for 9 ThreeFold Cooperative Founders to setup the COOP Struc
|
||||
|
||||
## Cooperative Director
|
||||
|
||||
Are voted by the members, but at start are the same as the 9 Founders.
|
||||
The cooperative directors are chosen by the members by vote. When the coop is first created the 9 founders will act as de facto directors until the first vote.
|
||||
|
||||
They are like the board of a Cooperative and need to structure how the Cooperative Members will vote and be part of the governance.
|
||||
The Cooperative will have a team which will do the day2day for the TFGrid.
|
||||
The directors are like the board of a cooperative and help to structure how the cooperative members will vote and be part of the governance.
|
||||
|
||||
The Cooperative is funded by utilization of the grid (40% at start).
|
||||
The cooperative will have a team which will carry out the day to day operations for the TFGrid.
|
||||
|
||||
Cooperative Directors and the team are renumerated for their contributions.
|
||||
The cooperative is funded by the utilization of the grid (40% at start).
|
||||
|
||||
## Cooperative Startup
|
||||
Cooperative Directors and the team are remunerated for their contributions.
|
||||
|
||||
## Starting The Cooperative
|
||||
|
||||
- ThreeFold Dubai grants 2 million TFT to TF COOP (TF DMCC and others can grant more)
|
||||
- TFCoop Founders will look for initial funding (sell the TFT, look for extra)
|
||||
- TFCoop Founders will setup the cooperative in chosen jurisdiction (might be NL)
|
||||
- TFCoop Founders will work with TFTech for technical implementation of membership (as NFT), ...
|
||||
- TFCoop founders will look for initial funding (sell the TFT, look for extra)
|
||||
- TFCoop founders will setup the cooperative in chosen jurisdiction (might be NL)
|
||||
- TFCoop founders will work with TF9 for the technical implementation of membership (as NFT etc.)
|
||||
|
||||
## Link to TFGrid DAO
|
||||
|
||||
> [The DAO on the TFGrid](tfdao.md) stays intact as is working today.
|
||||
> [The DAO on the TFGrid](tfdao.md) will stay intact as is working today.
|
||||
|
||||
## TFCoop Functions
|
||||
|
||||
- Promotion & Communication
|
||||
- Operate the TFGrid Marketplace ( which is regulated marketplace selling/buying capacity on TFGrid)
|
||||
- Operate the Tokens (exchanges, ...)
|
||||
- Operate the tools (forum, websites, ...)
|
||||
- Promotion and communication
|
||||
- Operate the TFGrid Marketplace (a regulated marketplace where selling and buying capacity on the TFGrid occurs)
|
||||
- Operate the Tokens (exchanges etc.)
|
||||
- Operate the tools (forum, websites, manuals etc.)
|
||||
- Collaborate with the Guardians for the operations of the TFChain and supporting tools
|
||||
- Define & operate the benefits for the Members
|
||||
- Distribute the TFT Fees for Utilization.
|
||||
- Define and operate the benefits for the members
|
||||
- Distribute the TFT fees for utilization.
|
||||
|
||||
## Status
|
||||
|
||||
> At start of our commercial operation (2024) we operate our Cooperative functions though our company in dubai called ThreeFold DMCC, somewhere in 2024 the cooperative will be established and all functions in relation to TFGrid transfered.
|
||||
> At the start of our commercial operation (2024) we operate our cooperative functions though our company in dubai called ThreeFold DMCC, somewhere in 2024 the cooperative will be established and all functions in relation to the TFGrid will be transfered.
|
||||
@@ -1,23 +1,23 @@
|
||||
# Validators
|
||||
|
||||
Validators & staking as is happening in TFGrid 3.14.
|
||||
Validators & staking on TFGrid 3.14.
|
||||
|
||||
- 9 [guardians](tfgrid3:guardians.md) are needed
|
||||
- they run a full TF Validator Stack (technically)
|
||||
- anyone can stake TFT on that stack
|
||||
- They will run a full TF Validator Stack (technically)
|
||||
- Anyone can stake TFT on that stack
|
||||
|
||||
reward
|
||||
Reward:
|
||||
|
||||
- 10 percent of revenue over TFGrid in TFT or INCA
|
||||
- this percentage can change over time and will be voted by GEP
|
||||
- a validator gets a monthly income to support his/her work as well in e.g. INCA or TFT
|
||||
- 10% of revenue over TFGrid in TFT or INCA
|
||||
- This percentage can change over time and will be voted by GEP
|
||||
- A validator recieves a monthly income to support his/her work as well in e.g. INCA or TFT
|
||||
|
||||
## what is deployed on a validator
|
||||
## What Is Deployed On A Validator
|
||||
|
||||
- TFChain Node (our blockchain node)
|
||||
- TFHub (let people go from docker to tfgrid ZOS flists)
|
||||
- TFHub (lets people go from docker to tfgrid ZOS flists)
|
||||
- TFBootstrap (how to install new node)
|
||||
- Explorer (has all stats)
|
||||
- Validator Code (keep the grid clean & healthy)
|
||||
- Validator Code (keeps the grid clean & healthy)
|
||||
- Monitoring Software
|
||||
- Bridges (needs to be migrated carefully, might take some time)
|
||||
|
||||
Reference in New Issue
Block a user