| Hi everyone, As part of the GitLab Ultimate Rollout¹, the team have gradually been deploying scoped labels across our GitLab instance (credit to the GitLab Ultimate Task Force for their ongoing work here). This work is being tracked in the Scoped Label Strategy and Rollout epic². Scoped labels are groups of mutually exclusive labels that are prefixed with a single term, or “scope", like so: ‘scope::label’. You can read more about scoped labels and their use-cases on GitLab Docs³, but one example you may already be familiar with are the Priority labels⁴ that were deployed last year. Several months ago we also deployed a suite of scoped Product labels⁵, combining numerous existing labels used across GitLab. Today, the new scoped Product labels are primarily used in the Applications, Product and UX groups on GitLab, but may be of relevance to other teams too. This week we grouped various existing labels — Bug, Task, Documentation, Feature and Technical Debt, in addition to a new Enhancement label — into scoped Kind labels⁶. These labels should be used to classify work items (e.g. epics, issues, tasks et cetera) based on the work needing done. Any work items that were previously tagged with one of the existing labels should be migrated automatically over to the corresponding new label. For example, if you had an issue tagged as “Bug”, that issue should now be tagged as “Kind::Bug”. Equally, when you search for the “Bug” label in the work item attributes sidebar, you’ll notice that GitLab will return the “Kind::Bug” label instead now. New labels like Product:: and Kind:: are intended to encourage consistency across GitLab, but Team Leads and project maintainers should decide for themselves if using these labels as part of their workflow would be beneficial. The aim here is to provide helpful tools for issue-wranglers, and not to burden everyone with unnecessary labelling bureaucracy. If you would like to see an additional label added to either of these scoped sets, or have any other feedback, please open an issue in tpo/team⁷ or feel free to ping me directly. Note that if the label you would like to add is specific to a certain team or project, with less applicability to the wider organization, it may make more sense to add it at the group or project level rather than the TPO level. Thanks, Duncan [1] GitLab Ultimate Rollout: https://gitlab.torproject.org/groups/tpo/-/work_items/1 [2] Scoped Label Strategy and Rollout: https://gitlab.torproject.org/groups/tpo/-/work_items/5 [3] Scoped Labels (GitLab Docs): https://docs.gitlab.com/user/project/labels/#scoped-labels [4] Priority labels: https://gitlab.torproject.org/groups/tpo/-/labels?search=priority:: [5] Product labels: https://gitlab.torproject.org/groups/tpo/-/labels?search=product:: [6] Kind labels: https://gitlab.torproject.org/groups/tpo/-/labels?search=kind:: [7] tpo/team: https://gitlab.torproject.org/tpo/team/-/work_items — Duncan R. Product Manager & UX Lead My working hours may not be your working hours. If I message you outside of your working hours, know that I do not expect an immediate response and that I support your right to disconnect.
|
Attachment:
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx