Shared labels for issues
We should probably have some common set of labels in GNOME projects. For example, newcomers has always been a commonly used keyword in our Bugzilla instance.
Gitlab
Gitlab currently provides the following set of labels by default:
bug, confirmed, critical, discussion, documentation, enhancement, suggestion, supportBugzilla
To make sure that bugs from our Bugzilla instance can map well to Gitlab, we should consider the keywords that are already in use. I used some regex to take the keywords of the bugs from the last 100 days and turn them into a frequency table:
| frequency | keyword |
|---|---|
| 172 | newcomers |
| 146 | ui-review |
| 131 | usability |
| 131 | I18N |
| 47 | accessibility |
| 35 | keynav |
| 33 | L10N |
| 28 | string |
| 23 | documentation |
| 21 | API |
| 20 | security |
| 19 | perf |
| 18 | probabledup |
| 16 | STACKTRACE |
| 13 | memory |
| 13 | build |
| 8 | HELPWANTED |
| 3 | printing |
| 3 | multihead |
| 3 | AffectsTails |
| 2 | portability |
| 1 | HIG |
Other label schemes
-
Sane GitHub Labels suggests to create 3 types of labels: Status, Type and Priority labels. Each label then needs to have a prefix of the given type (e.g. Status: Accepted).
-
https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/ proposes 10 categories for labels. Each label should use the color of the specific category.