Next Progress for Vatz

[xellos00]

• Reference:

  • https://github.com/dsrvlabs/validators/issues/229
  • https://github.com/dsrvlabs/validators/issues/229#issuecomment-1011754548

  • https://github.com/dsrvlabs/validators/issues/229#issuecomment-1011790825

• Previous Reminder

[xellos00]

Agenda

1. Development Principle

• Git strategy.

  • Release => Periodic Release | development and need to release.

    각 서비스와 플러그인의 버전은 따로가고, 추후에 코드에서 한번 더 확인하는 과정을 넣는다. 
    (Reflection) -> 확인한다

    • Vatz version
    • Plugin version

  • Master | Main

    Main  

  • Proto Buffer => API Services

    • https://app.gitbook.com/o/-MiyxU38etxprZxihBZS/s/-Mj3CwiN6vyRfTZC-Ljw/general/contents/api_services

    PR Request => Review => Update to commit by who ask modification. 
    PPL who insists modification on PR Request has to update its code. 
    Commit Authorization. 
    Merge is done by maintainer, per Protocol    

• CI / CD

  • Github Action

  • Lint

  • Build Test

  • Integration Test @rootwarp

  • CD Pipe Line

    • https://www.youtube.com/watch?v=uijgmwOdcXQ
    • https://www.youtube.com/watch?v=KoNWlnx6E1I
    • Secret Maintenance
    • Version
      • Human readable version when it release tag
      • Version is created by first pr requester if there's any modification

---

2. Task Register

• Create an Issue to register task

  • Register Taks in Issue Vatz
  • Naming Rule: vatz-plugin-{protocol or group of protocol}
    • ex)
      • vatz-plugin-certik
      • vatz-plugin-near
      • vatz-plugin-cosmos
      • vatz-plugin-terdermint
  • Anytime required development arise by anyone
  • Close by Who close issue,
    • Execute QA prior to Merge
    • Node's Assignee is responsible for development, and check its compatibility.

• Discussion in Vatz

  • Individuals | plugins naming rule above

• Discussion

---

3. APIs | Proto Buff

• APIs for each Services

• How We are going to record prior to update Proto buffs
• Who's going to grant to accept PR request. (Review may needed.)

• API version version

  • v1 | v2

• SVC

  • Example: Node Manager, Node Watcher, etc
  • Sub SVC
    • Plugins

---

4. Agenda for Next Meeting

• Periodic Meeting, Or when it holds

[xellos00]

Git strategy How to maintain repository per services and plugins

• SVC - Node Manager, Watcher | 1 or 2 Maintainer
• Plugins Per Protocols | All assignee per protocol

[xellos00]

Every discussion has moved to Vatz discussion.