Github labels improvement

[asvae]

I'm brainstorming ideas on label imrovements. Expecting most of these to be factored out, but maybe one or two are good enough to try.

• Increasing value and dificulty range (1-7, maybe 0-10 even). I feel limited by how low I can go. I.e. for difficulty we sometimes have issues that are literally one line of code: d0 - should work for that nicely (can't be easier). Right now I would set d1 to something like story rework, which is much more involved than one line fix. For value - same thing. We have some issues like Polish: va-backtop #3880, that are below the seabed in terms of value, far below median v1. Maybe instead of difficulty we might consider meaning of depth? I.e. how deep task goes. Then size - would define how vide.
• This also allows us to use maximums properly. I.e. v9-10 would be something we should jump on immediately. And d10 shouldn't be possible.
• Adding detailed description of every value and difficulty. Right now it's too much "up to developer".
• Add expertise label set. Idea is that some issues require only some html/js/vue knowledge, when some others require good understanding of different areas of vuestic or exotic knowledge to be handled efficiently. I can think on couple of such labels on the fly, but we probably can add more as we go:
  • e:balenciaga - design/colors/beautifulness skills
  • e:nuxt-plugin - this issue might be too hard if you didn't have any prior experience working with nuxt plugins
  • e:vuestic-core - you would need knowledge from contribution guide before starting with this issue
  • e:vuestic-advanced - this task would probably require a lot of experience, but even if you don't have it - feel free to take a bite.
  • e:storybook - please read this guide if it's first time you're working with storybook on vuestic-ui.
    Key idea is that these labels do not describe what has to be done, but rather act as a limiter for developer without sufficient experience. We should use these sparingly only for deadliest issues. Probably at some point we might have some sort of a guide linked to issues like this, so that developer can go, look up a guide and learn the tools, then come and start working on issue with good understanding.
• Add size label set. Story, could be small, but difficult. Or it could be large, but simple, which is sometimes not clear from difficulty alone. If we take accessibility improvements or story rework - task itself is not difficult, it's just very big. We can also use clothing sizes here (S, M, L, XL etc).

[m0ksem]

I wouldn't make this complex. The idea behind difficulty labels is to give devs the idea who could do this: 1 - newbie, 2 - newbie with great vue/js skills, 3 - contributor, 4 - contributor with great skills, core team member. It doesn't actually matter how much time does task take for me as repo owner - everyone can determinate time on their own. I just want to give a hint which tasks are better to pick up. We're not making sprints with strict deadlines.

About expertise. We use blue labels already. Generally all tasks related to ui, but sometime tasks can be related to nuxt (even if changes required in ui, not packages/nuxt). Same with any or package.

I believe labels are useless for core team for the most part, we have a projects and sprints.