116 lines
3.3 KiB
Markdown
116 lines
3.3 KiB
Markdown
|
<h1>Engineering Circle Meeting 2024-12-30 </h1>
|
||
|
|
|
||
|
|
<h2>Table of Contents</h2>
|
||
|
|
|
||
|
|
- [Attendees](#attendees)
|
||
|
|
- [Main Content](#main-content)
|
||
|
|
- [3.16](#316)
|
||
|
|
- [Minting](#minting)
|
||
|
|
- [Voting](#voting)
|
||
|
|
- [Note GEP](#note-gep)
|
||
|
|
- [Product Management Meeting](#product-management-meeting)
|
||
|
|
|
||
|
|
## Attendees
|
||
|
|
|
||
|
|
- Lee
|
||
|
|
- Ahmed
|
||
|
|
- Sabrina
|
||
|
|
- Mik
|
||
|
|
- Kristof
|
||
|
|
- Scott
|
||
|
|
- Jan
|
||
|
|
|
||
|
|
## Main Content
|
||
|
|
|
||
|
|
- 3.15
|
||
|
|
- moved qsss story to 3.16
|
||
|
|
- 3.15 patch
|
||
|
|
- local network
|
||
|
|
- add ETA
|
||
|
|
- first week of January
|
||
|
|
- 03/01/2025
|
||
|
|
- 3.16
|
||
|
|
- TODO
|
||
|
|
- meeting for product management to define 3.16 stories
|
||
|
|
- define 2 remainin issues with no owner
|
||
|
|
- https://git.ourworld.tf/tfgrid/circle_engineering/issues/130
|
||
|
|
- https://git.ourworld.tf/tfgrid/circle_engineering/issues/139
|
||
|
|
- make sure every owner are aware of their stories with ETA and specs
|
||
|
|
- How to improve grid release management
|
||
|
|
- owner of engineering circle must be clear, it's thabet
|
||
|
|
- we must set owners for issues that is fitting
|
||
|
|
- owner
|
||
|
|
- someone who know how to communicate around story and know how make it in time, and escalate if needed
|
||
|
|
- executor
|
||
|
|
- someone who can complete the task
|
||
|
|
- can be written in the story
|
||
|
|
- Executor and owner can be the same person
|
||
|
|
|
||
|
|
### 3.16
|
||
|
|
|
||
|
|
- lee working on
|
||
|
|
- bridge
|
||
|
|
- urgent to complete
|
||
|
|
- todo
|
||
|
|
- Ahmed to check if we can have other resources/help from devs to fix
|
||
|
|
- mycelium
|
||
|
|
- qsfs
|
||
|
|
- blocked on zdb
|
||
|
|
- have a call tomorrow with kristof and thabet
|
||
|
|
- same hour tomorrow
|
||
|
|
- notes product management
|
||
|
|
- what we need
|
||
|
|
- what can wait
|
||
|
|
- what are the specs
|
||
|
|
- KYC, etc.
|
||
|
|
|
||
|
|
### Minting
|
||
|
|
|
||
|
|
- 3 incidents
|
||
|
|
- included tfchain nodes, issues with upgrade
|
||
|
|
- 1 in october
|
||
|
|
- 2 in november
|
||
|
|
- nodes couldn't do uptime report
|
||
|
|
- have to remint
|
||
|
|
- solution
|
||
|
|
- increase the uptime room when there are grid month updates
|
||
|
|
- e.g.
|
||
|
|
- month of update the grid
|
||
|
|
- we give 2 days of offtime possible
|
||
|
|
- Not ideal for all cases... Need something else.
|
||
|
|
|
||
|
|
### Voting
|
||
|
|
|
||
|
|
- Can we go to token-based voting, tft on tfchain
|
||
|
|
- what market does and expects
|
||
|
|
- what investors expect
|
||
|
|
- GEP
|
||
|
|
- change voting to token-based
|
||
|
|
- need discussions
|
||
|
|
- token-based or farm-based
|
||
|
|
- if vote with farmers
|
||
|
|
- when minting issues
|
||
|
|
- we can't keep on paying for it
|
||
|
|
- certain things we can't vote becausenot the full community is represented
|
||
|
|
|
||
|
|
#### Note GEP
|
||
|
|
|
||
|
|
- Way forward
|
||
|
|
- write a gep
|
||
|
|
- to go to token-based voting
|
||
|
|
- then everyone can have a stake on the project and we can take decisions with the feedback of all the community
|
||
|
|
- once we have this, we can have gep on re-minting for november and december
|
||
|
|
- for v4 the model will be token-based voting
|
||
|
|
- we can implement it now for v3 to align with market
|
||
|
|
- in the past, we granted tokens with compensation
|
||
|
|
- but we can't anymore, we need funds for foundation
|
||
|
|
- we need to ask if we re-mint for october and november
|
||
|
|
- if we ask farmers, they will always say yes remint, but we need a system where the overall community votes on GEP so it's for the best of the whole TF ecosystem
|
||
|
|
|
||
|
|
## Product Management Meeting
|
||
|
|
|
||
|
|
- check forum posts on HA
|
||
|
|
- https://forum.threefold.io/t/threefold-grid-workloads/4466/2
|
||
|
|
- https://forum.threefold.io/t/tfgrid-4-0-service-levels/4467
|
||
|
|
- discuss 3.16 management
|
||
|
|
- discuss GEP for token-based voting
|