|
|
# How to use issue labels
|
|
|
|
|
|
## Colors
|
|
|
Since colorspace is limited, let's use color coding for each type of label that is mutually exclusive
|
|
|
|
|
|
## What do they mean ?
|
|
|
|
|
|
## Priority
|
|
|
- ~low is for low priority things, like having a Gitlab-to-Slack integration
|
|
|
- ~meh is middle priority, not low not high
|
|
|
- ~high is for important stuff to do soon
|
|
|
- ~critical is for stuff that is blocking something major (bug that bricks device to fix ASAP).
|
|
|
|
|
|
## Topic
|
|
|
|
|
|
- ~music
|
|
|
- ~video
|
|
|
- ~uiux for user interface and user experience, like navigation and icons
|
|
|
- ~architecture
|
|
|
- ~vlc for everything that's vlc lib related
|
|
|
- ~wiki for matters that concern the wiki content (best practices, solutions ...)
|
|
|
|
|
|
## Type
|
|
|
|
|
|
- ~bug, for bugs or other errors that need to be fixed
|
|
|
- ~feature, new functionalities that remain unimplemented
|
|
|
- ~change, for code changes that do not add features as is, but are not bugs either
|
|
|
|
|
|
## Decisional
|
|
|
Since gitlab has no way of handling issue status (new,open,pending codereview etc) nor issue linkage, we have to make do with labels.
|
|
|
#### Available
|
|
|
- ~new
|
|
|
- ~doing
|
|
|
- ~pending-review
|
|
|
- ~wont-fix
|
|
|
- ~duplicate
|
|
|
|
|
|
#### Not implemented yet:
|
|
|
- ~closed
|
|
|
- ~open |
|
|
\ No newline at end of file |