Rename Application Performance group to Cloud Connector group
Summary
GitLab's vision is to deliver business value to our customers by streamlining DevSecOps processes. We can help self-managed customers simplify their administration and operation of GitLab installations by hosting features that would be difficult to operate or scale on behalf of self-managed customers. We can think of this as an extension to self-managed instances, where some features are instead operated by us. This would be similar to what Jetpack does for Wordpress, MongoDB Management Service for MongoDB, or iCloud for an iPhone user. Features provides this way will be bundled under the GitLab Cloud Connector product umbrella (formerly: GitLab Plus). On a spectrum of privacy / isolation, GitLab Cloud Connector users sit in between the continuum of fully air-gapped deployments and GitLab Dedicated.
Our initial use case is to support AI features that require large amounts of computation power, bringing these otherwise inaccessible capabilities to our self-managed cohort. Future potential opportunities include managed runners, a native secrets manager and remote development. GitLab Cloud Connector works closely with feature teams to ensure all customers are able to benefit from GitLab features.
We do this by facilitating an instance-level authentication between self-managed installations and GitLab Cloud Connector. Our goal is to abstract away the differences between our customers' deployment choices and enable features team to focus on domain-specific opportunities.
Process and Examples
- https://about.gitlab.com/handbook/product/product-categories/#changes
- Rename Sharding team/category to Pods
- Rename Telemetry to Product Analytics
- Rename Product Analytics to Product Intelligence
Approvals
-
Chief Product Officer - @david
-
Enablement Director of Product - @joshlambert
-
Enablement Director of Engineering - @cdu1
-
Director of Product Design - @vkarnes
Informed
-
CTO (Jörg) -
Chief Product Officer (David) -
VP Development (Christopher) -
VP Infrastructure & Quality (Mek) -
Engineering Productivity -
Product Marketing Manager
Things to update
No Workflow Impact
-
Update handbook pages -
Group Direction and Category Strategy - /direction/application_performance/
-
Team page !130035 (merged) - /handbook/engineering/development/enablement/data_stores/application_performance/index.html.md.erb
-
All other pages owned by the application_performance Group -
Approach and Common Themes - /handbook/engineering/development/enablement/data_stores/application_performance/approach.html.md.erb
-
Knowledge Sharing - s/handbook/engineering/development/enablement/data_stores/application_performance/knowledge.html.md.erb
-
2020 Impact - /handbook/engineering/development/enablement/data_stores/application_performance/2020.html.md.erb
-
-
Section page - /handbook/engineering/development/enablement
-
Enablement Product Section Direction - direction/enablement/
-
-
Update internal handbook pages -
docs.gitlab.com -
Greenhouse Job Description and Title
Potential Workflow Impact
-
stages.yml
andcategory.yml
-
GitLab projects -
gl-retrospectives and async-retrospectives (#13711) -
gitlab-org/application-performance
-
-
~"group::application performance" label to ~group::cloud connector
-
Slack channel names -
Change Slack channel references in stages.yml
-
-
Triage ops -
Update team.yml
for relevant team members -
Update Ally.io -
Update CODEOWNERS -
gitlab-comwww-gitlab-com
-
gitlab-org/gitlab
-
-
Update BambooHR/Workday
Communications
-
Announce in: -
Slack: #s_enablement, #whats-happening-at-gitlab, #g_application_performance, #development, #vp-development, #cto
-
Engineering Week in Review
-