owned this note
owned this note
Published
Linked with GitHub
# Investigating more labels
In recent Triaging module meetings, there has been discussion around adding extra labels to the Blender issue tracker. Labels being the tags attached to reports, like: `Status|Confirmed`, `Type|Report`, `Module|EEVEE & Viewport`, `Interest|Metal`. We would love input from developers on the topic of adding new labels, so we have a few questions we'd like to ask:
1. As a developers, outside of the `Module` and `Status` labels, do you regularly look at, or search/sort by labels? If no, then is there a reason you aren't using them, and what could be done to improve the label system so you will use it more often? This is to gauge if it's worth investing time in adding/adjusting labels.
2. Do you think there are any areas labels need to be improved in? Whether that's the labels theirself, or how triagers and developers are using the labels.
3. The triaging module would like to add hardware labels for major CPU and GPU vendors (E.g. `Hardware|Intel`, `Hardware|AMD`). How do people feel about this?
The triaging module is mostly interested in using it for their own purposes. If a triager can't reproduce a issue, and it seems like it's hardware specific issue, then they can add the `Hardware|{VENDOR}` label to make it easier for someone with the relevant hardware to find the issue and test it.
4. For large rewrites of systems where both features avaliable at once (E.g. Grease Pencil to Grease Pencil v3), would adding labels for these rewrites be helpful for developers?
This can be done in phases. Start by adding a `Interest|Grease Pencil v3` and `Interest|Grease Pencil` label, then once EEVEE-Next EVEE Cycles, rename `Interest|Grease Pencil` to `Interest|Grease Pencil-Legacy` (for LTS releases that have EEVEE-Legacy) and rename `Interest|Grease Pencil v3` to `Interest|Grease Pencil`.
5. Some modules cover many areas of Blender, and there's no easy way to direct a bug report to the people working on subprojects inside a large module using just labels. For example, there's no `Interest|Transform` label for the transform subproject of the Modelling module. Would adding more interest labels that correspond to these "subprojects" and other areas of Blender be useful to developers? This can be decided upon on a module-by-module basis if desired.
---
## Note for triaging module:
### I don't know if we should add this to the discussion as it doesn't fit in with the theme of "more labels". Encouraging module owners to reivew and update their module page is important. But is this the right way to ask them to do it? We could just ask modules to update their pages in Blender chat.
We would like to encourage all modules to review their [module page](https://projects.blender.org/blender/blender/wiki) and update the topics they cover. Along with have a discussion around whether or not subprojects need to be shifted between modules, or if new modules need to be created.