Move self-monitoring category to Enablement
GitLab self-monitoring is meant to enable self-hosted GitLab administrators with the tools to operate GitLab. This is enablement. The Monitor group, specifically the former APM team was building monitoring tools to monitor customer applications, not GitLab.
With the disbandment of the APM group, and the knowledge for Prometheus that went with it, it is inefficient for the Monitor group to continue to own the self-monitoring category.
We decided to leave things as is the previous year, we should find a better solution this year.
Proposed solution
Shift Self-Monitor category to Enablement.
Alternatives
- Abandon and not support/maintain the category
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
Chief Product Officer @sfwgitlab
-
VP of Product @adawar
-
The Product Director relevant to the stage group(s) - @kencjohnston @joshlambert
-
The Engineering Director relevant to the stage group(s) - @sgoldstein -
The Engineering Director relevant to the stage group(s) - @cdu1 -
Director of Product Design @vkarnes
-
CEO
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @edjdev
-
Vice President of Development @clefelhocz1
-
Vice President of Quality @meks
-
Vice President of User Experience @clenneville
-
The Product Marketing Manager relevant to the stage group(s) -
Senior Manager, Technical Writing @susantacker
After Approvals and Merge
-
Create an issue in the triage-ops project to update GitLab Bot automation -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels