added last meeting

This commit is contained in:
Mik-TF 2024-08-07 10:41:20 -04:00
parent b605499ade
commit 3cce3dafa6

View File

@ -0,0 +1,132 @@
<h1>Engineering Meeting: 24-08-07</h1>
<h2>Table of Contents</h2>
- [Introduction](#introduction)
- [Attendees](#attendees)
- [Subject to Discuss](#subject-to-discuss)
- [Main Content](#main-content)
- [Todo Next Meeting](#todo-next-meeting)
---
## Introduction
We provide information on the recent engineering meeting.
## Attendees
- Sabrina
- Scott
- Mik
## Subject to Discuss
- HDD-only node
- farming rewards?
- Announcement of grid 3.15
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/204
- Defining products
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/219
- TF protection against cyber treats
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/225
- Recent GEP
- https://git.ourworld.tf/tfgrid/circle_promotion/issues/226
## Main Content
- HDD
- didn't change rewards on this
- farmers should check if they want to add SSD to get more rewards
- we can see later with the team if we can change the farming rewards
- TODO
- discuss with thabet and jan
- add folder with documents meeting in circle_engineering
- add meetings in markdown when we have meeting
- question on violation status on grid for some nodes
- what happens with node assigned violation for network health check in zos
- events are not properly inscribed in tfchain
- some nodes won't mint for this reason
- just for July minting period
- still open discussion
- situation:
- with fbot node, when nodes wake up, cause sequence of events that is not correct with minting
- todo: check difference with minting then go from there
- scott proposition
- minting code can be adjusted to properly register the fact that nodes wake up
- some potential change that could resolve that
- todo: scott checks minting differences, and we discuss this with Lee on next meeting
- issues
- 3.15
- still early to announce grid 3.15
- still thinking of changes needed
- discussion needed with the team
- define all products
- questions
- what are we planning to do
- two ways
- defining products so we can communicate about them
- or defining the products so we can implement them
- todo
- postgresql study done
- can see if it's worth it, if we can do it, see different options
- Juggler
- Timur is working on it to be implemented
- then we can see how to offer this as a product
- we will study the others
- once we have a basic overview
- we decide if some can be implemented, i.e. TF offers products
- general steps
- develop product specs in-house
- develop product itself
- e.g. juggler
- use product in-house
- once it's used in-house and well oiled
- we can commercialize it
- this means doing the last steps to offer a viable product and monetize it (e.g. fiat payments via stripe)
- goal
- to be able to clearly explain the products
- steps
- define the product
- develop the product for in-house
- develop the product to commercialize
- who is responsible for these commercial products?
- DMCC all except Hero
- protection against cyber treat
- from dev perspective
- not sure if we have reached a consensus
- next meeting: priority
- GEP
- this is done
- close the recent GEP
- write new issues
- 1. issue
- and write a new GEP
- for updated proposed GEP
- need to discuss this with the team
- once we have a consensus, we can write the forum
- 2. issue
- importance of participation in GEP
- weight in vote
- can be sabotaged by big farmers
- grid deployment project
- people blocked because of the hub
- hub has progression
- boot generator is being worked on
- todo meeting with bert and maxime
## Todo Next Meeting
- discuss if we change farming rewards for HDD-only node
- violation of minting for some nodes
- Scott checks the differences
- discuss with Lee and Jan
- 3.15
- discuss with the team the specs
- define all products
- discuss and get feedback from other members
- gep update
- discuss how we decide the 80% consensus
- protection against cyber treats
- priority for next meeting
- discuss how we proceed