#14. VATZ biweekly meeting at 2022-08-03 08:00:00 -06:00:00

[xellos00]

Retrospect

1. Overall

2. Statistic Rate

Sprint	Issue fulfillment	progress rate(%)
12	4/16	25
13	7/20	35

Thanks for your hard work for 2 weeks.
The target progress rate for each sprint is 40% to 55%.

---

• Finished

  • 2. Documentation for Vatz Project Design #151
  • Gather and share general idea and discuss 1st protocol plugins Hierarchy and its structures.  #157
  • Critical or Warning Notification behaviors include reminders.  #163
  • Run VATZ on local MacOs #167
  • Plugin Devlopement: Common - Volume #168
  • Refactoring executor module #179
  • Refactoring notification module #181

• Move to Sprint 13

  • Add unit test sample to Vatz #85
  • vatz-proto buffer's Github action enhancement #87
  • Create How to create a unit test and implements with github action documents #119
  • Plugin Development : Osmosis #121
  • Plugin Development : Agoric #127
  • Research for Prometheus to apply into notification for Protocol #146
  • Enhance Notification behaviors per status.  #174
  • Documentation to Updated CLI for 1.1 #175
  • Documentation to How to install and start VATZ #176
  • Developments for VATZ CLI Commands  #178
  • Managements Plans for VATZ #187

---

Discussion:

• 1st edition Plugins for Vatz per protocol #88

[xellos00]

동요

• liveness checking message is coming as CRITICAL Alert #199
• HealthCheck : refactoring into individual layers  #211
• Remove default.yaml that is already defined in CLI basic #217

[rootwarp]

Joonkyo

• CLI - start VATZ #208
• CLI - Init command #213
• CLI - List plugins which are configured #220

---

• Start CLI command. #209
• Add init subcommand. #214

[meetrick]

황제

• no update

[heejin-github]

희진

• fatal error: concurrent map writes #206
  • Use sync.Map for execute status #215
• Plugin Development : Solana #118

[gnongs]

진홍

• Plugin Development : Agoric #127

[kim201212]

형기

• Check golang lint automatically #196

[xellos00]

TODO

• Github action for go lint
• Get a secret for VATZ (action purpose only)

[xellos00]

Way to Start Official Plugins

1. make start with script

---

Bin -> each scripts

• Build
• Start
• Stop
• Clean
  Make

---

for current meeting.

1. We do not want to have many official plugins
2. our end-user will be who is more advanced than our knowledges
3. We need to narrow down on selection.
4. Let's settle official plugins first and then apply above.