Commit 14fdca41 authored by Marin Jankovski's avatar Marin Jankovski Committed by Fabian Zimmer
Browse files

docs: add infra-category labels documentation

parent b16bc224

content/handbook/engineering/infrastructure/platforms/project-management/index.md

+15 −13
Original line number Diff line number Diff line
@@ -134,8 +134,9 @@ The Infrastructure Platform teams uses the following set of labels: 
|-------------|--------|

| The section label | `section::developer experience`<br/>`section::gitlab delivery`<br/>`section::gitlab dedicated`<br/>`section::production engineering`<br/>`section::tenant scale` |

| The stage label | `devops::developer experience`<br/>`devops::gitlab delivery`<br/>`devops::gitlab dedicated`<br/>`devops::production engineering`<br/>`devops::data access`<br/>`devops::runtime` |

| The group label | `group::development tooling`<br/>`group::development analytics`<br/>`group::feature readiness`<br/>`group::performance enablement`<br/>`group::test governance`<br/>`group::build`<br/>`group::release-and-deploy`<br/>`group::operate`<br/>`group::environment automation`<br/>`group::US PubSec`<br/>`group::switchboard`<br/>`group::Foundations`<br/>`group::Observability`<br/>`group::Ops`<br/>`group::Runners Platform`<br/>`group::runway`<br/>`group::database frameworks`<br/>`group::database operations`<br/>`group::durability`<br/>`group::git`<br/>`group::gitaly`<br/>`group::cells infrastructure`<br/>`group::geo`<br/>`group::organizations` |

| The group label | `group::build`<br/>`group::Cloud Cost Utilization`<br/>`group::development analytics`<br/>`group::development tooling`<br/>`group::environment automation`<br/>`group::Foundations`<br/>`group::geo`<br/>`group::git`<br/>`group::gitaly`<br/>`group::Observability`<br/>`group::operate`<br/>`group::Ops`<br/>`group::organizations`<br/>`group::performance enablement`<br/>`group::release-and-deploy`<br/>`group::Runners Platform`<br/>`group::runway`<br/>`group::switchboard`<br/>`group::tenant services`<br/>`group::test governance`<br/>`group::US PubSec` | 

| Scoped `workflow-infra::*` labels | (see below) |

| Scoped `infra-category::*` labels | (see below) |

| Optional Scoped `Service` labels | `Service::*` |



### Workflow labels
@@ -163,23 +164,24 @@ There are three other workflow labels of importance: 
| ![Stalled](/images/engineering/infrastructure/platforms/project-management/label-stalled.png) | Work is not abandoned but other work has higher priority. After applying this label, team Engineering Manager is mentioned in the issue to either change the priority or find more help. |

| ![Blocked](/images/engineering/infrastructure/platforms/project-management/label-blocked.png) | Work is blocked due external dependencies or other external factors. Where possible, a [blocking issue](https://docs.gitlab.com/ee/user/project/issues/related_issues.html) should also be set. After applying this label, issue will be regularly triaged by the team until the label can be removed. |



### Labels in gitlab-org group

### Category labels



Stage groups use [type labels](/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification) to label merge requests in projects in the `gitlab-org` group.

If you need a stage group to perform work, it is best to apply the relevant stage group label when the issue is created.

We use scoped category labels to classify the type or area of work being performed.

These labels help organize and filter issues by their functional category.



## Issue Trackers

| Category Label | Description |

| -------------- | ----------- |

| `infra-category::KTLO` | Keep the lights on. Operational work required to maintain system stability, reliability, and performance. Includes monitoring, alerting, incident response, and routine maintenance. |

| `infra-category::Tech Debt` | Technical debt and refactoring work. Bug fixes or improvements to code quality, architecture, testing, documentation, and infrastructure that reduce future maintenance burden. |

| `infra-category::Customer innovation` | Work directly driven by customer needs and feedback. Features, improvements, and solutions that enhance customer experience and address customer-reported issues. |

| `infra-category::Internal innovation` | Internal improvements and explorations. Work that improves developer experience, team productivity, or explores new technologies and approaches for future adoption. Can be foundational/architectural work if it addresses multiple classes of technical debt. |



This is a list of the group issue trackers:

### Labels in gitlab-org group



| Group | Tracker |

|-------|---------|

| Dedicated | [issue tracker](https://gitlab.com/gitlab-com/gl-infra/gitlab-dedicated/team/-/issues)|

| Delivery | [issue tracker](https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues) |

| Production Engineering | [issue tracker](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/issues)|

| Scalability | [issue tracker](https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues) |

Stage groups use [type labels](/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification) to label merge requests in projects in the `gitlab-org` group.

If you need a stage group to perform work, it is best to apply the relevant stage group label when the issue is created.



### Triage Ops

## Triage Ops



For labeling and bot notifications under [gitlab-com/gl-infra](https://gitlab.com/gitlab-com/gl-infra) we use [gitlab-triage](https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage) and the [triage-ops](https://gitlab.com/gitlab-com/gl-infra/triage-ops/) project.

For labeling, enforcing SLOs, and managing workflow labeling there are common policies that are set uniformly for projects in Infrastructure, Platform.