GEP: Procedures and Documentation #295

New Issue

mik-tf · 2024-10-07T19:04:28Z

mik-tf commented

2024-10-07 19:04:28 +00:00

GEP: Procedures and Documentation

Introduction

We propose clear and simple guidelines for the ThreeFold DAO grid enhancement proposal system. This document can serve as a guide for the ThreeFold circles working on GEPs.

Circles' Goals

We want to make sure as many people as possible participate, and that everyone understands the GEP.
- How: Communicate on all channels GEP details.
We want to make sure the community members speak their mind and discuss before and during the GEP periods.
- How: Invite discussions on forum and chats
We want to make sure Devs and Ops circle also participate in discussion if needed, e.g. to make sure the GEP propositions can be implemented on the grid.
- How: In weekly TF meeting, comms circle discusses with ops+devs circles the GEP details.

TF Community

The DAO is at its base composed of people taking decisions for the greater good of the project. We want to make sure the community members are taking part of the process.

During the pre-GEP period, people can discuss the GEP and propose improvements.
During the GEP period, people can vote and ask question on the official GEP specs.
During the post-GEP period, people can discuss the outcome of the vote and the way forward.

GEP Specs

We define specs to serve as a template for future GEPs.

Pre-GEP period
- Duration: 15 days
- Description
  - Period where people discuss the upcoming GEP
  - This is the time where we can improve the GEP before having the final official version
- Specs
  - Start: 15 days before a GEP vote
  - End: The day before GEP period
GEP period
- Duration: 15 days
- Description
  - Period where people can vote for the GEP
  - Can still discuss, but not on changing the GEP, but on understand the official GEP position
- Specs
  - Starts when ops submit a GEP on TFChain linked to a forum post
  - Ends at the end of the voting period
Post-GEP period
- Duration: Open
- Description
  - Period where peole discuss the GEP outcome
- Specs
  - Start: After GEP period
  - End: Open

Note: We propose 15-day periods, but this can be changed if needed. It serves as a template.

Circles' Tasks

We define clear tasks for the Comms, Devs and Ops circles.

Comms Circle
- Make sure people know about the GEP (communicate on all channels multiple times)
- Create the GEP draft on the forum
- Discuss with the community (pre-GEP period)
- Update draft from community feedback and devs tech feedback
- Invite people to vote during the GEP period
- Announce the outcome in the post-GEP period
- Check with Ops and Devs circles that GEP specs can be implemented
Ops Circle
- Create the GEP on TFChain
- Publish official GEP forum post
Devs Circle
- Implement changes from the GEP if it passes

GEP Data

Comms circle can provide participation data on the GEP.

# of farms to participate
# of farms to vote yes/no
# of nodes to participate
# of nodes to vote yes/no
% of active node to vote yes/no
% of active farm to vote yes/no

References

This should be discussed with all circles before the next GEP.

@despiegk
@gosam
@sabrinasadik
@thabeta

<h1> GEP: Procedures and Documentation </h1> <h2> Table of Contents </h2> - [Introduction](#introduction) - [Circles' Goals](#circles-goals) - [TF Community](#tf-community) - [GEP Specs](#gep-specs) - [Circles' Tasks](#circles-tasks) - [GEP Data](#gep-data) - [References](#references) --- ## Introduction We propose clear and simple guidelines for the ThreeFold DAO grid enhancement proposal system. This document can serve as a guide for the ThreeFold circles working on GEPs. ## Circles' Goals - We want to make sure as many people as possible participate, and that everyone understands the GEP. - How: Communicate on all channels GEP details. - We want to make sure the community members speak their mind and discuss before and during the GEP periods. - How: Invite discussions on forum and chats - We want to make sure Devs and Ops circle also participate in discussion if needed, e.g. to make sure the GEP propositions can be implemented on the grid. - How: In weekly TF meeting, comms circle discusses with ops+devs circles the GEP details. ## TF Community The DAO is at its base composed of people taking decisions for the greater good of the project. We want to make sure the community members are taking part of the process. - During the pre-GEP period, people can discuss the GEP and propose improvements. - During the GEP period, people can vote and ask question on the official GEP specs. - During the post-GEP period, people can discuss the outcome of the vote and the way forward. ## GEP Specs We define specs to serve as a template for future GEPs. - Pre-GEP period - Duration: 15 days - Description - Period where people discuss the upcoming GEP - This is the time where we can improve the GEP before having the final official version - Specs - Start: 15 days before a GEP vote - End: The day before GEP period - GEP period - Duration: 15 days - Description - Period where people can vote for the GEP - Can still discuss, but not on changing the GEP, but on understand the official GEP position - Specs - Starts when ops submit a GEP on TFChain linked to a forum post - Ends at the end of the voting period - Post-GEP period - Duration: Open - Description - Period where peole discuss the GEP outcome - Specs - Start: After GEP period - End: Open > Note: We propose 15-day periods, but this can be changed if needed. It serves as a template. ## Circles' Tasks We define clear tasks for the Comms, Devs and Ops circles. - Comms Circle - Make sure people know about the GEP (communicate on all channels multiple times) - Create the GEP draft on the forum - Discuss with the community (pre-GEP period) - Update draft from community feedback and devs tech feedback - Invite people to vote during the GEP period - Announce the outcome in the post-GEP period - Check with Ops and Devs circles that GEP specs can be implemented - Ops Circle - Create the GEP on TFChain - Publish official GEP forum post - Devs Circle - Implement changes from the GEP if it passes ## GEP Data Comms circle can provide participation data on the GEP. - \# of farms to participate - \# of farms to vote yes/no - \# of nodes to participate - \# of nodes to vote yes/no - % of active node to vote yes/no - % of active farm to vote yes/no ## References This should be discussed with all circles before the next GEP. @despiegk @gosam @sabrinasadik @thabeta

❤️ 1

mik-tf added the

Story

label 2024-10-07 19:04:28 +00:00

mik-tf added this to the Sep 30 – Oct 13 project 2024-10-07 19:04:28 +00:00

gosam modified the project from Sep 30 – Oct 13 to Oct 14 – Oct 27

2024-10-14 10:09:13 +00:00

gosam commented

2024-10-15 08:48:22 +00:00

Along with #294, this is waiting to be discussed this Thursday during development stakeholder meeting.

mik-tf commented

2024-10-17 14:49:42 +00:00

Update

Discussed in the meeting the issue 294, but not this one. Will discuss next Monday.

# Update - Discussed in the meeting the issue 294, but not this one. Will discuss next Monday.

mik-tf commented

2024-10-21 14:55:46 +00:00

Update

As discussed with engineering circle, here is the outcome:
We don't go with this.
What we do:
- When we are in the process of discussing a GEP, engineering circle will write forum post(s) to let the community know about the situation. So no one is surprised when a GEP is opened.
- We then create a GEP with a given voting period and we invite community members to ask questions during this period
- We make it clear that it's up to community members to ask questions if they have any

# Update - As discussed with engineering circle, here is the outcome: - We don't go with this. - What we do: - When we are in the process of discussing a GEP, engineering circle will write forum post(s) to let the community know about the situation. So no one is surprised when a GEP is opened. - We then create a GEP with a given voting period and we invite community members to ask questions during this period - We make it clear that it's up to community members to ask questions if they have any

mik-tf closed this issue

2024-10-21 14:55:46 +00:00

Sign in to join this conversation.