Should we adopt a naming convention for labels on the repo?

Currently, on the ^tips opensource command we tell the user they can use a label that doesn’t exist on the repo yet (“command:opensource”):

IMO, creating this label would help filter the list of issues, so that someone that wants to make these sort of changes (tips and advice) can easily find them. Before creating the label, I think we could start thinking about a naming convention on our custom labels.

Examples

For example, Angular seems to have a convention based on defining a type and associating a color to it. Then there is a scope to define the subsection on the type of label (e.g. browser: edge). Note: I tried finding docs explaining this, but I couldn’t. I’m just assuming their convention is sort of based on conventional commits, hence the “type” and “scope” 🙂.

Another example of this idea is on Gitlab on Scoped labels.

You can also check out this article that states the Electron repo uses a similar convention:

Let me know your thoughts on this idea 😃.

[mikeysan]

Yep. Looks to me like it has been fullfilled.

[eddiejaoude]

Great idea 👍