Add development guide to docs#2760
Conversation
| Here is a list of labels and a brief description mentioning their intent. | ||
|
|
||
|
|
||
| **Type** |
There was a problem hiding this comment.
Like I said, I would like to add the prefix to all labels, so we could have type:bug, status:critical and so on. If nobody opposes that, I will do it and update the document.
|
|
||
| Issues specific to an operating systems. | ||
|
|
||
| * ``windows``: |
There was a problem hiding this comment.
I propose to add linux and mac to the list.
There was a problem hiding this comment.
all plugin ones should be just like plugin: name
|
|
||
| Useful to classify issues for some definite time. They should be removed after they are no longer relevant. | ||
|
|
||
| * ``EP2017 sprint``: |
There was a problem hiding this comment.
I propose to remove these labels except for mark-issue given that it is still relevant; we can leave them in the docs for example purposes.
There was a problem hiding this comment.
we can turn mark-issue into a mark plugin one
|
|
||
| Currently not clear what they are for or if they are useful. | ||
|
|
||
| * ``classes``: |
There was a problem hiding this comment.
I think we can remove these entirely (from this document and from GH).
|
i accidentally did part of this one while cleaning up yesterday |
|
Noticed this by accident hehe. Care to comment here what you would like to see changed here for us to merge it @RonnyPfannschmidt? |
|
@RonnyPfannschmidt made the changes you requested. I will update the label names as soon as we merge this. |
3 participants
I started writing about which types of labels we use on our issues because this just grew organically, and realized that we don't have a development guide so I turned it into that.
It is not exhaustive, but at least it will get the ball rolling for further additions.
also, I propose we do the following:
It is clear that labels also have a type/category associated to them. I noticed some projects (like pip and tox) use a prefix, and I suggest we adopt this idea as well. Then the classification is much clearer IMHO.
Some labels are duplicated or don't seem to have a clear purpose; I propose to just remove them.