Vatz Official Plugins Developments & Managements

[xellos00]

Checklist

• [x] New Feature for the Service/Plugin (Vatz)
• [ ] Enhancement (Vatz)
• [ ] others(etc. e.g, documentation, project policy management)

---

Is your feature request related to a problem? Please describe.

A clear and concise description of what the problem is. such as Ex. I'm always frustrated

I was frustrated due to absents of VATZ official plugins.

Describe the solution you'd like| Ex

A clear and concise description of what you want to happen

As we discussed, we are going to create two official plugins and extend and boost its qualities as possible.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you have considered.

Please, fill out following Todo Items with main assignee.

Previous Agenda

• [x] 1. Create a two VATZ official plugin Repos that has same code hierarchy.

  • (SDK) COSMOS Hub (vatz-plugin-cosmoshub)
  • (SDK) Linux (SystemUtil)

• [x] 2. Documentation (TODOs)

  • [x] How to guide for install, build, start, stop, clean.
  • [x] How to communicate VATZ
  • [x] troubleshooting
    • [x] proper work
    • [x] error

• [ ] 3. Release & version planning

  • 3.1. First main release will be 1.0 and it comes after
    • 1 => v1 or v2 (when major proto buff has updated)
    • 0 => 2 ,3,4 (minor update has done momentally)
    • x => hot fix (any hot fix comes after)

  • 3.2 unified versioning is required or not will put on vote. Type	VATZ	Cosmos-hub	SystemUtil
    Start version	1.0	1.0.	1.0
    Unified	1.2	1.2	1.2
    Individuals	1.2	1.0.	1.0

• [ ] 4. CI (@kim201212 )

  • When PR raised
    • [ ] Test
    • [ ] Build
  • Release
    • [ ] Release tag

---

Child Issue

• 225

• 236

[xellos00]

@heejin-github I create a Parents issue #241 and registered those two items as child

• Plugin Development : Cosmos: #236
• Plugin Development : Sysutil: #242

Can you set main assignee for those child issues?