Add a Pipeline Foundations team to support some of Pipeline Execution's current scope and own the Continuous Integration Scaling category

Overview

Create a new group, Group::Pipeline Foundations and a new non marketing category Category:Pipeline Processing which are responsible for the foundational aspects of Pipelines including the work to partition the database already underway. This also renames Group::Pipeline Execution to Group:Pipeline Administration for clarity on what that team will work on. Full details of work breakdown are in the supporting discussion issue.

The rationale for this includes:

1. better support current initiatives and direction for the categories
2. reorganize the team with more distinct domain ownership
3. side benefit of EM gearing ratio but not the driver

New Team/Category/Engineering Split

Group::Pipeline Foundations

Responsible for the foundational aspects of CI. It's responsible to maintain the core functionality scalable, performant and stable.

• Non Marketing Category ~"Category:Continuous Integration Scaling"
• New Non Marketing Category Pipeline Processing
  • Pipeline creation
  • Pipeline processing
  • Job queue
  • Job traces

Staffing

• 1 Engineering Manager
• 3 Backend Engineers
• 1 Product Manager (split with Group:Pipeline Administration)

Group::Pipeline Administration

This is the layer directly on top which makes the CI experience richer. Provides the functionality to view pipeline data, integrations and advanced features.

• ~"Category:Continuous Integration"

  • Pipelines and job pages - including job logs
  • CI_JOB_TOKEN Pipeline Permissions
  • CI/CD Minutes
  • Analytics - CICD Analytics pipeline duration
  • External Repository Mirroring/ Future: CI for Monorepos/Future: Integrations with External SCM
  • Pipeline Schedules
  • Webhooks
  • Future: Secure Supply Chain future vision

• ~"Category:Merge Trains"

Staffing

• 1 Engineering Manager
• 4 Backend Engineers
• 2 Frontend Engineers
• 1 Product Manager (split with Group:Pipeline Foundations)
• Stable Counterparts UX/SET/Support

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:

• VP of Product @david
• The Product Director relevant to the affected Section(s) @ogolowinski @jreporter
• The Engineering Director relevant to the affected Section(s) @sgoldstein
• Director of Product Design @vkarnes

The following people need to be on the merge request so they stay informed:

• Chief Technology Officer @akramer
• 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)
• Director of Technical Writing @susantacker

After Approvals and Merge

• Create an issue in the triage-ops project to update GitLab Bot automation:
  • for Category change
  • for Stage or Group change
• Mention the product group Technical Writer to update the documentation metadata
• Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels