Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vatz Official Plugins Developments & Managements #241

Open
8 of 15 tasks
xellos00 opened this issue Aug 31, 2022 · 1 comment
Open
8 of 15 tasks

Vatz Official Plugins Developments & Managements #241

xellos00 opened this issue Aug 31, 2022 · 1 comment
Assignees
Labels
area:plugin Anything related to Vatz plugin. area:project Anything that related to Vatz project manage good_first_issue Good for newcomers type:feature-development Any development regarding Vatz service/plugin, etc. Vatz Project Name

Comments

@xellos00
Copy link
Member

xellos00 commented Aug 31, 2022

Checklist

  • 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

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

    • (SDK) COSMOS Hub (vatz-plugin-cosmoshub)
    • (SDK) Linux (SystemUtil)
  • 2. Documentation (TODOs)

    • How to guide for install, build, start, stop, clean.
    • How to communicate VATZ
    • troubleshooting
      • proper work
      • 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

@xellos00 xellos00 added Vatz Project Name type:feature-development Any development regarding Vatz service/plugin, etc. labels Aug 31, 2022
@xellos00 xellos00 added good_first_issue Good for newcomers area:plugin Anything related to Vatz plugin. area:project Anything that related to Vatz project manage labels Aug 31, 2022
@xellos00
Copy link
Member Author

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

Can you set main assignee for those child issues?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:plugin Anything related to Vatz plugin. area:project Anything that related to Vatz project manage good_first_issue Good for newcomers type:feature-development Any development regarding Vatz service/plugin, etc. Vatz Project Name
Projects
None yet
Development

No branches or pull requests

2 participants