tfgrid/circle_engineering
23
0
Fork 0
Code Issues 67 Pull Requests Packages Projects Releases Wiki Activity
698bdb6628
circle_engineering/meetings_notes/engineering_meeting_24-12-16.md
mik-tf 698bdb6628 add 16 dec notes
2024-12-16 14:14:24 -05:00

5.3 KiB
Raw Blame History

Engineering Circle Meeting 2024-12-16

Table of Contents

Attendees

  • Lee
  • Ahmed
  • Sabrina
  • Mik
  • Kristof
  • Scott

Main Content

  • Zealy
    • OK for community to do it themselves
    • TF not implicate, we let them do it and help if needed
      • Mik will help GEN (the implementor) if needed
    • If it works well, we can have a GEP later and decide that TF treasury give some TFT to help
      • Only if it works well and community accepts the GEP
  • 3.15
    • qsfs
      • scott working on it
  • 3.15 patch
    • local network
      • Jan and devs working on it
  • 3.16
    • organize it with eng circle next meeting
  • Compensation july
    • Done

TF 4.0

  • main project
  • dont do too much repos
    • use tfgrid
      • instead of tfv4 now
  • farming
    • write how we do the hosting
    • with maxime
      • another bootstrap server
      • another ISO
      • couple of weeks we can have it

Notes on Release Nodes Availability

Workload Architecture for HA storage and app

  • Devs
    • See main story:
  • Ops
    • kubernetes, nomad, glusterfs
      • thabet will open tickets

Interactions with Community

  • e.g.
    • send code of conducts
    • ask people to be respectful
    • if someone doesn't follow this
      • we can ban them and explain it
    • but we need to always be kind
    • note
      • we don't ban people if they share their criticism just if they go against code of conduts and didn't listen to warnings

TG Admin

  • check with TG if we can put ourselves as admin anonymous so we can write as "ADMIN"

GEP

  • Minting issues in November
    • TODO
      • do 10 days of voting
      • send GEP in 1-2 days
      • specific case
      • write draft on google docs
      • when accepted we publish on forum
      • mint in January
      • GEP content
        • we know last month version upgrade of the grid didn't go as expected, cause many people not to meet uptime requireemtsn, as there were another issue
          • this is what the issue was
            • ...
            • we have a workaround for it now
          • we do realize many people did not get all tockens
          • we propose to have a gep to remint only those 2 days

Minting and GEP

  • Notes
    • always require updates in minting code
    • always require a GEP
    • since we don't know in advanced, we can't know in advanced, and can't code it in advance
    • we dont know if update will lead to update
    • every minting changes must be done through a GEP

Grid Release Updates

  • Update stuff on Hetnzer
  • Flist server
    • people can run their own hubs
    • define which users can login
      • convert their images
  • admin interface part for zos over mycelium
    • Jan said bad use of mycelium
    • don't have any more notes on this
    • not good to have admin define the packets and rules, this will not work
      • aside from that
        • we are developing couple of endpoints
        • owners of node can exclude
        • check how many workloads exist
        • see DNS files
        • right now
          • single diagnosis command
          • to exclude stuff, it would be helpful
  • KYC on farmers
    • should we have kyc or email+phone verification?
      • if authorities need to contact the farmer
        • if we have email but it's a fake email, or email they don't use, etc. a burner phone
    • idea:
      • not allow for people to create farm with dashboard, only the tfconnect
        • if kyc not needed
          • create farm with TFConnect, email verification is needed
          • if we don't need KYC for farmers
            • can farmers deploy on their own node without KYC
              • it is reasonable
        • kyc needed
          • on dashboard or tfconnect app, need kyc to create farm

Stellar DEX on the phone

  • basic use
    • as before, no need xlm
  • advanced use
    • using swap, trading, etc.
      • will consume XLM
    • disclaimer: if use advanced, need to manage XLM
    • UX
      • shortcut to market
        • buy TFT, buy USDC, buy XLM
      • from there, facing conditions of having XLM
        • to buy TFT you need some XLM
          • first buy XLM first, then swap to TFT and keep some in the wallet

Availability

  • Thabet is off 24-12-18 to 24-12-29

TODO