#7. VATZ biweekly meeting at 2022-04-27 13:00:00(KST) | 2022-05-02 23:00:00(CST) #44

[xellos00]

Over previous discussion via team members

---

1. Bi-weekly Meeting

• Vatz bi-weekly meetings are conducted in the same format as weekly-sync.
  • Share current status Issues that have been done or ongoing for two weeks
  • It can be skipped, If the review has already done and issue has closed.

2. Issue

1. Issues can be registered by anyone in the team.
   • register according to the following criteria and follow the label rule when registering an issue.
2. At least 1 to 2 issues has to be addressed over two weeks(1 sprint).
   • Assignee has to finish assigned or selected issue as much as possible, leave a comment if it can't be finished within sprint.
   • As Validator team's main task is node operation and therefore leave issue handling to each member's own will. close the issue, re-register and change to other assignee if it is difficult to proceed during the 2 sprints(4 weeks).
3. Code owner(@xellos00 ) will create an issue and assign an assignee if necessary.

3. Project operation

1. Please, ping to everyone through discord and use @dsrvlabs/validator if you need feedback
2. All members must response within 60 Hours if not, it will proceed as it has registered.
3. Review on PR has to be done at most 16 hours. (at leave a comment if you don't have a time to deal or ask other)
   • Ask Review to any 2 peoples in team + code maintainer
4. Code owner(@xellos00 ) will assign an assignee if necessary.
   • Please, ping to project owner ASAP if assignee wants to request change assignee.

---

Common to Share

1. Labeling rule

• New Labeling for project Vatz managements #66 (comment)

2. How to register issue

• Fill out assignee (leave it blank when unknown but suggest not to leave it blank as much as possible)
• Set appropriate labels
• Set project
• Set milestone.
• Set Development with PR (because you can't connect to other repo on this)
  

3. Meeting Hour Update

• 10:00:00 (KST) | 20:00:00 (CST)
• 22:00:00 (KST) | 08:00:00 (CST)
• keep as this way

---

Discussion

• New Labeling for project Vatz managements #66
• Benchmarking development process and out team management from best practice #69
• Import private repo and create documents in gitbook #72
• Vatz's versioning & tags in the policy #75
• Enhance Discord notification feature #79
• register general pull request template with in vatz platform  #82
• 1st edition Plugins for Vatz per protocol #88
  • Plugin Development : Near #98

---

Vatz-management

• bi-weekly time change

[xellos00]

1. 10:00:00 (KST) | 20:00:00 (CST) 😄
2. 22:00:00 (KST) | 08:00:00 (CST) ❤️
3. as-is 👍