Meta: Overhaul label system

What is wrong?

The way we currently use labels could be improved to enable better issue discovery.

How can it be fixed

I’d like to overhaul and unify the labels in this repo and potentially apply the same rules to other repos as well. This is inspired by https://github.com/machinelabs/machinelabs which in turn is inspired by https://github.com/angular/angular

Here are two secreenshots to give an idea what it could look like.

The gist of it goes like this.

We would create labels that fall into the following categories:

comp: <component-name> (e.g. comp: p2p, comp: trinity, comp: benchmark) type: <type> (e.g. type: feature, type: bug, type: docs) effort: <effort-estimate> (e.g. effort: hours, effort: days, effort: weeks) prio: <prio> (e.g. prio: P0-critical, prio: P1-urgent, prio: P2-required) PR-state: <state> (e.g. PR-state: wip, PR-state: needs review, PR-state: blocked)

All the labels that fall into the same category share the same color (as seen on the screenshot). Nothing set in stone regarding concrete labels but I like the core idea of it. I’m happy to do the migration work we want to go that way.

[cburgdorf]

We can totally create a script that just airdrops the labels into a repo. However, for this specific repo I’d prefer to take the migration kind of approach and start by renaming existing labels because then all the issues that are currently labeled with existing labels will automatically end up with the correct new labels already applied.

[cburgdorf]

Closing this as the job seems done for this repo. Let’s just discuss if / where to push these labels to (with slight changes regarding comp: xxx) and then I’ll happily take care of that.