Engineering Circle Meeting 2024-09-12

<h1>Engineering Circle Meeting 2024-09-12 </h1>

<h2>Table of Contents</h2>

- [Attendees](#attendees)
- [Main Content and TODO](#main-content-and-todo)
- [TODISCUSS - Next Meeting](#todiscuss---next-meeting)

---

## Attendees

- Lee
- Mik
- Sabrina
- Scott

## Main Content and TODO

- git.ourworld.tf ops
  - TODO
    - Sabrina creates an issue to check how to manage the gitea instance, just like we deal with github instance
  - Notes
    - check the ops process for gitea git.ourworld.tf
      - make sure the process is effective and can be done by different person to avoid bottleneck/SPOF
- Ops snapshot node
  - TODO: Sabrina will check with Bert post 19 sept.
  - Reference: https://github.com/threefoldtech/tfchain/issues/981

## TODISCUSS - Next Meeting

- To discuss
  - Farmerbot-farmer-minting issue
    - scott will present the issue and we can discuss with Thabet, Jan and Kristof on the call: we can't afford to lose farmers, and the error was on TF side, not the farmers.
    - for now the proposition is (not ideal for farmers, we risk to lose farmers and nodes)
      - make sure it doesn't happen again
        - check with the team who implemented the changes
          - ZOS team
      - can't compensate from treasury
      - can't remint
        - not fair for non-fbot-farmer compared to fbot-farmer
  - Farmers deploying on their own nodes
    - for now they can get up to 90% discount
      - 50% utilization rewards
      - 50% dedicated node
      - 60% staking discount
        - 0.5 * 0.5 * 0.4 = 0.1
    - If TFT price goes up, farmers can rent their full node and still farm TFT
      - not sustainable
        - starting from 2 cents tft
          - farmers can make more money by renting the whole node and still farm
    - Discussion
      - how can we make sure this isn't happening for ZOS v4
      - we'd need a GEP to change the discount and rewards
  - info_grid manual (github) to info_tfgrid manual (git.ourworld.tf) migration
    - discuss how to do this smoothly
      - e.g. 
        - replace info_grid manual by info_tfgrid manual on manual.grid.tf
    - OR we wait for the new markdown docs app?
  - GEP TFT Voting
    - Reference: https://docs.google.com/document/d/1Ovi2ecDI2G75CecLr2tKs7W5a69Ntxo-9F-qaVW7kFI/edit#heading=h.kyru52g80m08
    - TODISCUSS
      - check with team: add cool down for unpassed GEPs
      -  there should be some kind of "cool down" period before the (ammended) proposal is voted again depending on the percentage of votes  against the proposal if it doesn't pass
         -  e.g.
            -  between 50 and 60 percent: 2 weeks cool down
            -  under 50 percent: 2 months cool down
         -  TODO
            -  discuss cool down details
            -  when ready we can submit the GEP
               - add forum post + GEP to dashboard (ops + comms circles)