Product sections, stages, groups, and categories

1. You are here:
2. Handbook
3. Product Handbook
4. Product sections, stages, groups, and categories

On this page

• On this page
• Interfaces
• Hierarchy
  • Naming
  • More Details
  • Solutions
  • Capabilities
  • Layers
  • Category Statuses
• Changes
  • Examples
  • Changing group name
  • Changing category name
  • Changing category maturity
• DevOps Stages
  • Dev section
    • Manage stage
      • Authentication and Authorization group
      • Import and Integrate group
      • Foundations group
    • Plan stage
      • Project Management group
      • Product Planning group
      • Knowledge group
      • Optimize group
    • Create stage
      • Source Code group
      • Code Review group
      • IDE group
  • CI section
    • Verify stage
      • Pipeline Execution group
      • Pipeline Authoring group
      • Runner group
      • Runner SaaS group
      • Pipeline Security group
    • Package stage
      • Package Registry group
      • Container Registry group
  • CD section
    • Deploy stage
      • Environments group
  • Sec section
    • Secure stage
      • Static Analysis group
      • Dynamic Analysis group
      • Composition Analysis group
      • Vulnerability Research group
    • Monitor stage
      • Respond group
      • Observability group
    • Govern stage
      • Security Policies group
      • Threat Insights group
      • Compliance group
  • Data Science section
    • Anti-Abuse stage
      • Anti-Abuse group
    • ModelOps stage
      • AI Assisted group
      • MLOps group
      • DataOps group
  • Analytics section
    • Analytics stage
      • Analytics Instrumentation group
      • Product Analytics group
  • Growth section
    • Growth stage
      • Acquisition group
      • Activation group
  • Fulfillment section
    • Fulfillment stage
      • Purchase group
      • Provision group
      • Utilization group
      • Fulfillment Platform group
      • Billing and Subscription Management group
  • Enablement section
    • Systems stage
      • Distribution::Build group
      • Distribution::Deploy group
      • Gitaly::Cluster group
      • Gitaly::Git group
      • Geo group
    • Data Stores stage
      • Application Performance group
      • Global Search group
      • Database group
      • Tenant Scale group
  • SaaS Platforms section
    • SaaS Platforms stage
      • Delivery group
      • Scalability group
      • GitLab Dedicated group
      • Switchboard group
      • US Public Sector Services group
  • Single-Engineer Groups section
    • Mobile stage
      • Mobile DevOps group
    • Deploy stage
      • Five Minute Production App group
    • Low-Code/No-Code stage
      • No-code Automation group
• Possible future Stages
• Maturity
• Other functionality
  • Other functionality in Plan stage
    • Project Management group
  • Other functionality in Create stage
    • Code Review group
    • IDE group
  • Other functionality in Verify
    • CI Group
    • Pipeline Authoring Group
  • Other functionality in Monitor stage
  • Other functionality in Manage stage
  • Other functionality in Engineering Productivity
  • Other functionality in Quality Engineering
  • Other functionality in Analytics
    • Product Analytics group
  • Facilitated functionality
  • Shared responsibility functionality
• Categories A-Z

Principles - Processes - Categorization - GitLab the Product - PM Responsibilities - Being a PM - Performance Indicators - Leadership

Interfaces

We want intuitive interfaces both within the company and with the wider community. This makes it more efficient for everyone to contribute or to get a question answered. Therefore, the following interfaces are based on the product categories defined on this page:

• Home page
• Product page
• Product Features
• Pricing page
• DevOps Lifecycle
• DevOps Tools
• Product Direction
• Stage visions
• Documentation
• Engineering Engineering Manager/Developer/Designer titles, their expertise, and department, and team names.
• Product manager responsibilities which are detailed on this page
• Our pitch deck, the slides that we use to describe the company
• Strategic marketing specializations

Hierarchy

The categories form a hierarchy:

1. Sections: Are a collection of stages. We attempt to align these logically along common workflows like Dev, Sec and Ops. Sections are maintained in data/sections.yml.
2. Stages: are aligned logically starting with the 7 loop stages of Plan, Create, Verify, Secure, Package, Deploy, and Monitor. We then add the value stages that we talk about in marketing. These include Manage and Govern. Lastly, we add the team stages: Growth, Systems and Data Stores. These stages have groups that rally around the same users, GitLab integrators, GitLab itself, and GitLab administrators, respectively. Stages are maintained in data/stages.yml. Each stage has a corresponding devops::<stage> label under the gitlab-org group.
3. Group: A stage has one or more groups. Groups are maintained in data/stages.yml. Each group has a corresponding group::<group> label under the gitlab-org group.
4. Categories: A group has one or more categories. Categories are high-level capabilities that may be a standalone product at another company. e.g. Portfolio Management. To the extent possible we should map categories to vendor categories defined by analysts. There are a maximum of 8 high-level categories per stage to ensure we can display this on our website and pitch deck. (Categories that do not show up on marketing pages show up here in italics and do not count toward this limit.) There may need to be fewer categories, or shorter category names, if the aggregate number of lines when rendered would exceed 13 lines, when accounting for category names to word-wrap, which occurs at approximately 15 characters. Categories are maintained in data/categories.yml. Each category has a corresponding Category:<Category> label under the gitlab-org group. Category maturity is managed in the product Category Maturity Change process
5. Features: Small, discrete functionalities. e.g. Issue weights. Some common features are listed within parentheses to facilitate finding responsible PMs by keyword. Features are maintained in data/features.yml. It's recommended to associate feature labels to a category or a group with feature_labels in the data/categories.yml or data/stages.yml.

Notes:

• Groups may have scope as large as all categories in a stage, or as small as a single category within a stage, but most will form part of a stage and have a few categories in them.
• Stage, group, category, and feature labels are used by the automated triage operation "Stage and group labels inference from category labels".
• We don't move categories based on capacity. We put the categories in the stages where they logically fit, from a customer perspective. If something is important and the right group doesn't have capacity for it, we adjust the hiring plan for that group, or do global optimizations to get there faster.
• We don't have silos. If one group needs something in a category that is owned by another group, go ahead and contribute it.
• This hierarchy includes both paid and unpaid features.

Naming

Anytime one hierarchy level's scope is the same as the one above or below it, they can share the same name.

For groups that have two or more categories, but not all categories in a stage, the group name must be a unique word or a summation of the categories they cover.

If you want to refer to a group in context of their stage you can write that as "Stage:Group". This can be useful in email signatures, job titles, and other communications. E.g. "Monitor:Health" rather than "Monitor Health" or "Monitor, Health."

When naming a new stage, group, or category, you should search the handbook and main marketing website to look for other naming conflicts which could confuse customers or employees. Uniqueness is preferred if possible to help drive clarity and reduce confusion. See additional product feature naming guidelines as well.

More Details

Every category listed on this page must have a link to a direction page. Categories may also have documentation and marketing page links. When linking to a category using the category name as the anchor text (e.g. from the chart on the homepage) you should use the URLs in the following hierarchy:

Marketing product page > docs page > direction page

E.g Link the marketing page. If there's no marketing page, link to the docs. If there's no docs, link to the direction page.

Solutions

Solutions can consist of multiple categories and are typically used to align to a customer challenge (e.g. the need to reduce security and compliance risk) or to market segments defined by analysts such as Software Composition Analysis (SCA). Solutions are also often used to align to challenges unique to an industry vertical (e.g. financial services), or to a sales segment (e.g. SMB vs Enterprise).

Solutions typically represent a customer challenge, and we define how GitLab capabilities come together to meet that challenge, with business benefits of using our solution.

Market segments defined by analysts don't always align to GitLab stages and categories and often include multiple categories. Two most frequently encountered are:

1. Software Composition Analysis (SCA) = Dependency Scanning + License Compliance + Container Scanning
2. Enterprise Agile Planning (EAP) = Team Planning + Planning Analytics + Portfolio Management + Requirements Management

We are intentional in not defining SCA as containing SAST and Code Quality despite some analysts using the term to also include those categories.

Capabilities

Capabilities can refer to stages, categories, or features, but not solutions.

Layers

Adding more layers to the hierarchy would give it more fidelity but would hurt usability in the following ways:

1. Harder to keep the interfaces up to date.
2. Harder to automatically update things.
3. Harder to train and test people.
4. Harder to display more levels.
5. Harder to reason, falsify, and talk about it.
6. Harder to define what level something should be in.
7. Harder to keep this page up to date.

We use this hierarchy to express our organizational structure within the Product and Engineering organizations. Doing so serves the goals of:

• Making our groups externally recognizable as part of the DevOps lifecycle so that stakeholders can easily understand what teams might perform certain work
• Ensuring that internally we keep groups to a reasonable number of stable counterparts

As a result, it is considered an anti-pattern to how we've organized for categories to move between groups out of concern for available capacity.

When designing the hierarchy, the number of sections should be kept small and only grow as the company needs to re-organize for span-of-control reasons. i.e. each section corresponds to a Director of Engineering and a Director of Product, so it's an expensive add. For stages, the DevOps loop stages should not be changed at all, as they're determined from an external source. At some point we may change to a different established bucketing, or create our own, but that will involve a serious cross-functional conversation. While the additional value stages are our own construct, the loop and value stages combined are the primary stages we talk about in our marketing, sales, etc. and they shouldn't be changed lightly. The other stages have more flexibility as they're not currently marketed in any way, however we should still strive to keep them as minimal as possible. Proliferation of a large number of stages makes the product surface area harder to reason about and communicate if/when we decide to market that surface area. As such, they're tied 1:1 with sections so they're the minimal number of stages that fit within our organizational structure. e.g. Growth was a single group under Enablement until we decided to add a Director layer for Growth; then it was promoted to a section with specialized groups under it. The various buckets under each of the non-DevOps stages are captured as different groups. Groups are also a non-marketing construct, so we expand the number of groups as needed for organizational purposes. Each group usually corresponds to a backend engineering manager and a product manager, so it's also an expensive add and we don't create groups just for a cleaner hierarchy; it has to be justified from a span-of-control perspective or limits to what one product manager can handle.

Category Statuses

Categories can have varying level of investment and development work. There are four main investment statuses:

1. Accelerated - Top category for product strategy that has received additional investment in the next year
2. Sustained - Categories where new features will be added in the next year
3. Reduced - Categories where scope and ambition is decreased although, new features will still be added in the next year
4. Maintenance - Categories where no new features will added

Typically, product direction pages will transparently state the investment status of the category for the fiscal year based on annual product themes and investment levels.

Changes

The impact of changes to sections, stages and groups is felt across the company.

All new category creation needs to be specifically approved via our Opportunity Canvas review process. This is to avoid scope creep and breadth at the expense of depth and user experience.

Merge requests with changes to sections, stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:

1. Chief Product Officer
2. VP of Product
3. The Director of Product relevant to the affected Section(s)
4. The Director of Engineering relevant to the affected Section(s)
5. Director of Product Design

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

1. Chief Technology Officer
2. VP of Development
3. Director of Quality Engineering
4. Engineering Productivity (by @ mentioning @gl-quality/eng-prod)
5. The Product Marketing Manager relevant to the stage group(s)
6. Senior Manager, Technical Writing

After approval and prior to merging, ping the Engineering Manager for Quality Engineering in the MR, if there are changes that:

• Add a new category, group, stage or section
• Move an existing category to a new or existing group
• Move an existing group to a new or existing stage
• Move an existing stage to a new or existing section
• Rename a group, stage or section
• Delete a group, stage or section

This is to ensure that GitLab Bot auto-labeling can be updated prior to the change, which can be disruptive if missed.

Upon approval, tag the group Technical Writer in the merge request to ensure documentation metadata is updated after the category change is merged.

Examples

Because it helps to be specific about what is a significant change and what should trigger the above approval process, below are two non-exhaustive lists of examples that would and would not, respectively, require approval.

Changes that require the above approvers include:

• Changes to a section, stage, group, or category name
• Removal or addition of a section, stage, group, or category

Changes that require approval only from the relevant Product Director include:

• Changing a category maturity date
• Changes to section or group member lists
• Changes to a category vision page

Changing group name

When changing the name of a group, make sure to go through the following steps:

• Create a MR to change the group name in data/stages.yml using the Group-Stage-Category-Change template
• Get the required signoff
• Merge the group name change MR
• Create an issue in the triage-ops project to update GitLab Bot automation for Stage or Group change
• Tag the group's Technical Writer in the merge request to ensure documentation metadata is updated after the group change is merged
• Share MR in #product, #development, #g_engineering_analytics and relevant #s_, #g_, and #f_ Slack channels
• Review direction pages, groups, projects, epics, issues, templates and documentation to ensure the name change is applied consistently.
• Rename Slack channels to reflect the new group name

Changing category name

When changing an existing category name, there are some considerations to the order of events:

• First, create a MR to change the name in data/stages.yml and spec/homepage/category_spec.rb.
• Get sign off from all required stakeholders listed in the instructions above. Final signoff should be requested in the #ceo channel with a link to the MR once all other signoffs are complete.
• Merge the name change MR.
• Tag the category's technical writer so that they can update the documentation metadata
• Re-name the category direction page with a new MR. Search for the old category name on the category direction page to ensure the name has been updated in all places.
• Use the #it-help Slack channel to request an update to Slack channel name for the re-named category

Changing category maturity

We primarily use the Category Maturity Scorecard process to determine category maturity.

Typically, category maturity moves up from planned to minimal to viable to complete to lovable. However, maturity can also be downgraded. For example, in cases where we discover a JTBD is not met (see example), or when we change the definition of maturity, we may choose to move category maturity down.

When downgrading product maturity, we adjust our customer's current expectations about our product. This is particularly impactful to our go-to-market team members in customer success and product marketing. We need to do the following to enable alignment between all affected and interested parties:

• Raise an MR for the downgrade and clearly state the reasons for change in the description (see example)
• Inform VP, Product Management by adding them as Reviewer on the MR
• Notify the product group counterparts in the MR; Product Marketing, Product Designer, Engineering Manager, and Technical Writer
• Post the MR in the #customer-success slack channel prior to merging, to allow the team to assess impact and adjust
• Post the MR in the #product slack channel for awareness

DevOps Stages

Dev section

Product: Orit Golowinski • Development: Tim Zallmann • Product Design: Taurie Davis, Marcel van Remmerden • UX Research: [["Ashley Knobloch", "Danika Teverovsky", "Ben Leduc-Mills"]] • Support: Shaun McCann • Product Marketing: Aathira Nair • Quality: Ramya Authappan • Analyst Relations: Ryan Ragozzine • Infrastructure Manager: Gerardo Lopez Fernandez • Legal & Corporate Affairs: Iris Gorman

Manage stage

Product Management: Urvi Chetta • Development: Michelle Gill • Product Design Manager: Chris Micek

Authentication and Authorization group

Development totals: 8 BE, 1 FE

Product Manager: Hannah Sutor • Product Marketing Manager: Aathira Nair • Support: Cynthia Ng • Backend Engineering Manager: Adil Farrukh • Frontend Engineering Manager: Adil Farrukh • Software Engineer in Test: Sanad Liaquat • Backend Engineering: Bogdan Denkovych, Drew Blessing, Imre Farkas, Jarka Košanová, Jessie Young, Małgorzata Ksionek, Smriti Garg, Aboobacker MK • Frontend Engineering: Eduardo Sanz-Garcia • UX Researcher: Ashley Knobloch • Technical Writer: Jon Glassman • Application Security Engineer: Rohit Shambhuni • Customer Success: • Internal Customers: Customer Support Department, (TBD), Security Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Manage Authentication and Authorization Paid GMAU] • Features in this Group

• User Management Viable • Documentation • Direction Page
• System Access Complete • Documentation • Direction Page

Import and Integrate group

Development totals: 5 BE, 1 FE

Slack Channel: g_manage_import_and_integrate • GitLab Group: @gitlab-org/manage/import-and-integrate • Product Manager: Magdalena Frankiewicz • Product Marketing Manager: Aathira Nair • Support: Olivier Némoz Saint-Dizier, Anton Smith • Backend Engineering Manager: Martin Wortschack • Frontend Engineering Manager: Martin Wortschack • Software Engineer in Test: TBD • Backend Engineering: Bojan Marjanović, Carla Drago, George Koltsov, Luke Duncalfe, Martin Wortschack, Rodrigo Tomonari • Frontend Engineering: Justin Ho, Martin Wortschack • UX Researcher: Ashley Knobloch • Technical Writer: Evan Read, Ashraf Khamis • Application Security Engineer: [Félix Veillette-Potvin] • Customer Success: • Internal Customers: Alliances Department, ([Morgan Joscelyn]), Customer Success, (TBD), Quality Department, (TBD), Infrastructure Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Manage Import and Integrate GMAU] • Features in this Group

• API • Documentation • Direction Page
• Integrations Viable • Documentation • Direction Page
• Webhooks • Documentation • Direction Page
• Importers • Documentation • Direction Page
• Internationalization • Documentation • Direction Page

Foundations group

Development totals: 6 FE

Slack Channel: g_manage_foundations • GitLab Group: @gitlab-org/manage • Product Manager: Christen Dybenko • Engineering Manager: Sam Beckham • Support: TBD • Software Engineer in Test: TBD • Frontend Engineering: Lukas Eipert, Mark Florian, Olena HK., Paul Gascou-Vaillancourt, Scott de Jonge, Thomas Hutterer • Product Design Manager: Chris Micek • UX Researcher: Ashley Knobloch • Product Designers: Jeremy Elder, Austin Regnery, Dan Mizzi-Harris • Technical Writer: Suzanne Selhorn • Application Security Engineer: Dominic Couture • Customer Success: • Internal Customers: Alliances Department, (TBD), Customer Success, (TBD), Quality Department, (TBD), Infrastructure Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Driving Pajamas adoption] • Features in this Group

• Design System • Documentation • Direction Page
• GitLab Documentation Site • Documentation • Direction Page
• Navigation & Settings • Direction Page

Plan stage

Product Management: Melissa Ushakov • Development: John Hope • Product Design Manager: Jacki Bauer

Project Management group

Development totals: 5 BE, 4 FE

Handbook • Product Manager: Gabe Weaver • Product Marketing Manager: Heather Simpson • Support: Ben Prescott • Backend Engineering Manager: Donald Cook • Frontend Engineering Manager: Donald Cook • Software Engineer in Test: Désirée Chevalier • Backend Engineering: Alexandru Croitor, Brett Walker, Eulyeon K., Heinrich Lee Yu, Mario Celi • Frontend Engineering: Coung Ngo, Deepika Guliani, Natalia Tepluhina, Simon Knox • UX Researcher: Danika Teverovsky • Product Designer: Emily Sybrant (interim) • Technical Writer: Marcin Sędłak-Jakubowski • Application Security Engineer: Costel Maxim • Customer Success: Christiaan Conover, Edmond Chan • Internal Customers: Engineering Department, (TBD), Product Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Plan Project Management Paid GMAU] • Features in this Group

• Team Planning Viable • Documentation • Direction Page

Product Planning group

Development totals: 3 BE, 2 FE

Product Manager: Amanda Rueda • Product Marketing Manager: Heather Simpson • Support: TBD • Backend Engineering Manager: Kushal Pandya • Frontend Engineering Manager: Kushal Pandya • Software Engineer in Test: TBD • Backend Engineering: Eugenia Grieff, Jan Provaznik, Nicolas Dular • Frontend Engineering: Florie Guibert, Rajan Mistry • UX Researcher: Danika Teverovsky • Product Designer: Nick Brandt • Technical Writer: Marcin Sędłak-Jakubowski • Application Security Engineer: Ottilia Westerlund • Customer Success: • Internal Customers: Engineering Department, (TBD), Product Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Plan Product Planning Paid GMAU] • Features in this Group

• Portfolio Management Viable • Marketing Page • Documentation • Direction Page
• Design Management Viable • Documentation • Direction Page
• Requirements Management Minimal • Documentation • Direction Page
• Quality Management Minimal • Documentation • Direction Page

Knowledge group

Development totals: 2 BE, 1 FE

Handbook • Product Manager: Matthew Macfarlane • Product Marketing Manager: Heather Simpson • Backend Engineering Manager: John Hope • Frontend Engineering Manager: John Hope • Backend Engineering: Kassio Borges, Naman Jagdish Gala • Frontend Engineering: Himanshu Kapoor • UX Researcher: [Danika Teverovksy] • Technical Writer: #docs Slack channel • Application Security Engineer: Costel Maxim • Customer Success: Simon Mansfield • Internal Customer: [Technical Writing], ([Susan Tacker]) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Plan Knowledge Paid GMAU] • Features in this Group

• Wiki Viable • Documentation • Direction Page
• Pages Complete • Marketing Page • Documentation • Direction Page

Optimize group

Development totals: 4 BE, 3 FE

Product Manager: Haim Snir • Product Marketing Manager: Aathira Nair • Engineering Manager: Brandon Labuschagne • Support: [Gabriel Yoachum] • Software Engineer in Test: TBD • Backend Engineering: Adam Hegyi, Charlie Ablett, Felipe Artur, Pavel Shutsin • Frontend Engineering: Alex Pennells, Ezekiel Kigbo, Rudy Crespo • UX Researcher: Danika Teverovsky • Product Designer: Libor Vanc • Technical Writer: Lorena Ciutacu • Application Security Engineer: Costel Maxim • Customer Success: • Internal Customers: Engineering Department, (TBD), Product Department, (TBD), Quality Department, (TBD), Development Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Plan Optimize GMAU] • Features in this Group

• Value Stream Management Viable • Marketing Page • Documentation • Direction Page
• DORA Metrics Minimal • Marketing Page • Documentation • Direction Page
• DevOps Reports Minimal • Documentation • Direction Page

Create stage

Product Management: Sarah Waldner • Development: Darva Satcher • Product Design Manager: Andy Volpe

Source Code group

Development totals: 7 BE, 3 FE

Handbook • Product Manager: Torsten Linz • Product Marketing Manager: Heather Simpson • Support: TBD • Backend Engineering Manager: Sean Carroll • Frontend Engineering Manager: André Luís • Software Engineer in Test: Anastasia McDonald • Backend Engineering: Gavin Hinfey, Igor Drozdov, Jerry Seto, Patrick Cyiza, Joe Woodward, Robert May, Vasilii Iakliushin • Frontend Engineering: André Luís, Denys Mishunov, Jacques Erasmus, Nataliia Radina • UX Researcher: Ben Leduc-Mills • Product Designer: Michael Le • Technical Writer: Amy Qualls, Marcin Sędłak-Jakubowski • Application Security Engineer: Costel Maxim • Customer Success: Conley Rogers, Kristof Goossens, Simon Mansfield • Internal Customers: Engineering Department, (TBD), Marketing Department, (Saumya Upadhyaya), Product Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Create Source Code GMAU] • Features in this Group

• Source Code Management Lovable • Marketing Page • Documentation • Direction Page

Code Review group

Development totals: 5 BE, 3 FE

Handbook • Product Manager: Kai Armstrong • Product Marketing Manager: Heather Simpson • Support: Ben King • Backend Engineering Manager: Matt Nohr • Frontend Engineering Manager: André Luís • Software Engineer in Test: Jay McCure • Backend Engineering: Sincheol (David) Kim, Gary Holtz, Kerri Miller, Marc Shaw, Patrick Bajao • Frontend Engineering: André Luís, Phil Hughes, Stanislav Lashmanov, Thomas Randolph • UX Researcher: Ben Leduc-Mills • Product Designers: Matthew Nearents, Alex Fracazo • Technical Writer: Amy Qualls • Application Security Engineer: Greg Alfaro • Customer Success: • Internal Customers: Engineering Department, (TBD), Marketing Department, (TBD), Product Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Create Code Review GMAU] • Features in this Group

• Code Review Workflow Lovable • Marketing Page • Documentation • Direction Page
• GitLab CLI Viable • Documentation • Direction Page
• Editor Extensions New in 2023 • Direction Page

IDE group

Development totals: 2 BE, 2 FE

Handbook • Product Manager: Eric Schurter • Product Marketing Manager: Heather Simpson • Support: Brad Sevy • Backend Engineering Manager: David O'Regan • Frontend Engineering Manager: David O'Regan • Software Engineer in Test: Nivetha Prabakaran • Backend Engineering: Chad Woolley, David O'Regan, Vishal Tak • Frontend Engineering: David O'Regan, Enrique Alcántara, Paul Slaughter • UX Researcher: Ben Leduc-Mills • Product Designer: Julia Miocene • Technical Writer: Ashraf Khamis • Application Security Engineer: Greg Alfaro • Customer Success: • Internal Customers: Marketing Department, (TBD), Engineering Department, (TBD), Finance Department, (TBD), People Operations, (TBD), Product Department, (TBD) • Infrastructure Manager: Gerardo Lopez Fernandez • Focus: [Create IDE GMAU] • Features in this Group

• Web IDE Viable • Documentation • Direction Page
• Remote Development Minimal • Documentation • Direction Page

CI section

Slack Channel: ci-section • Handbook • Product: • Product: Jackie Porter • Development: • Development: Sam Goldstein • Product Design: Marcel van Remmerden • UX Research: Erika Feldman • Support: • Product Marketing: • Quality: Vincy Wilson • Analyst Relations: Ryan Ragozzine • Legal & Corporate Affairs:

Verify stage

Product Management: Jackie Porter • Development: Cheryl Li • Product Design Manager: Rayana Verissimo

Pipeline Execution group

Development totals: 7 BE, 2 FE

Product Manager: Jackie Porter • Product Marketing Manager: Heather Simpson • Support: Manuel Grabowski • Backend Engineering Manager: Caroline Simpson • Frontend Engineering Manager: Caroline Simpson • Software Engineer in Test: Richard Chong • Backend Engineering: Allison Browne, Drew Cimino, Fabio Pitino, Hordur Freyr Yngvason, Marius Bobin, Max Fan, Tianwen Chen • Frontend Engineering: Jose Ivan Vargas, Payton Burdette • UX Researcher: Erika Feldman • Technical Writer: Marcel Amirault • Application Security Engineer: Dominic Couture • Customer Success: Kristof Goossens, Rachel Fuerst, Vladimir Dzalbo • Internal Customers: Quality Department, (TBD), UX Department, (TBD), Infrastructure Department, (TBD), Engineering Department, (TBD), AutoDevOps and Kubernetes Group, (TBD) • Focus: [Verify & Runner SMAU] • Features in this Group

• Continuous Integration (CI) Complete • Marketing Page • Documentation • Direction Page
• Merge Trains Viable • Documentation • Direction Page
• Code Testing and Coverage Viable • Documentation • Direction Page
• Review Apps Complete • Marketing Page • Documentation • Direction Page
• CI/CD Visibility Planned 2024 • Documentation • Direction Page

Pipeline Authoring group

Development totals: 6 BE, 2 FE

Product Manager: Dov Hershkovitch • Product Marketing Manager: Heather Simpson • Support: Manuel Grabowski • Backend Engineering Manager: Mark Nuzzo • Frontend Engineering Manager: Mark Nuzzo • Software Engineer in Test: Tiffany Rea • Backend Engineering: Avielle Wolfe, Furkan Ayhan, Kasia Misirli, Laura Montemayor, Leaminn Ma, Sam Kim • Frontend Engineering: Briley Sandlin, Frédéric Caplette • UX Researcher: Erika Feldman • Product Designer: Sunjung Park • Technical Writer: Marcel Amirault • Application Security Engineer: Dominic Couture • Customer Success: Kristof Goossens, Rachel Fuerst, Vladimir Dzalbo • Internal Customers: Quality Department, (TBD), UX Department, (TBD), Infrastructure Department, (TBD), Engineering Department, (TBD), AutoDevOps and Kubernetes Group, (TBD) • Focus: [Verify & Runner SMAU] • Features in this Group

• Pipeline Composition Viable • Marketing Page • Documentation • Direction Page

Runner group

Development totals: 10 BE

Slack Channel: g_runner • Product Manager: Darren Eastman • Product Marketing Manager: Heather Simpson • Support: Justin Farmiloe • Backend Engineering Manager: Nicole Williams • Frontend Engineering Manager: Nicole Williams • Software Engineer in Test: Zeff Morgan • Backend Engineering: Adrien Kohlbecker, Arran Walker, Axel von Bertoldi, Davis Bickford, Georgi Georgiev, Joe Burnett, Pedro Pombeiro, Romuald Atchadé, Tomasz Maczukin, Vladimir Shushlin • Frontend Engineering: • UX Researcher: Erika Feldman • Product Designer: Gina Doyle • Technical Writer: Fiona Neill • Application Security Engineer: Dominic Couture • Infrastructure Security Engineer: [Joe Dubail] • Customer Success: Kristof Goossens, Rachel Fuerst, Vladimir Dzalbo • Internal Customers: Infrastructure Department, (TBD), Engineering Department, (TBD) • Site Reliability Engineering: Rehab Hassanein • Focus: [Verify & Runner SMAU] • Features in this Group

• GitLab Runner Core Lovable • Documentation • Direction Page
• Runner Fleet Complete • Documentation • Direction Page

Runner SaaS group

Slack Channel: g_runner_saas • Product Manager: [Gabriel Engel] • Product Marketing Manager: Heather Simpson • Support: Justin Farmiloe • Backend Engineering Manager: Nicole Williams • Frontend Engineering Manager: Nicole Williams • Software Engineer in Test: Zeff Morgan • Backend Engineering: • Technical Writer: Fiona Neill • Application Security Engineer: Dominic Couture • Infrastructure Security Engineer: [Joe Dubail] • Customer Success: Kristof Goossens, Rachel Fuerst, Vladimir Dzalbo • Internal Customers: Infrastructure Department, (TBD), Engineering Department, (TBD) • Site Reliability Engineering: Rehab Hassanein • Focus: [Verify & Runner SaaS SMAU] • Features in this Group

• GitLab Runner SaaS Viable • Documentation • Direction Page

Pipeline Security group

Development totals: 4 BE, 2 FE

Product Manager: Jocelyn Eillis • Product Marketing Manager: Heather Simpson • Support: Brie Carranza • Backend Engineering Manager: Scott Hampton • Frontend Engineering Manager: Scott Hampton • Backend Engineering: Albert Salim, Dmytro Biryukov, Erick Bajao, Maxime Orefice • Frontend Engineering: Miranda Fluharty, Mireya Andres • UX Researcher: Erika Feldman • Product Designer: Veethika Mishra • Technical Writer: Marcel Amirault • Application Security Engineer: Dominic Couture • Customer Success: • Internal Customers: Quality Department, (TBD), UX Department, (TBD), Infrastructure Department, (TBD), AutoDevOps and Kubernetes Group, (TBD) • Focus: [Verify Pipeline Security Sum of AMAUs] • Features in this Group

• Build Artifacts Minimal • Documentation • Direction Page
• Secrets Management Minimal • Documentation • Direction Page

Package stage

Slack Channel: s_package • Handbook • Product Management: Tim Rizzi • Development: Crystal Poole

Package Registry group

Development totals: 4 BE, 1 FE

Slack Channel: g_package-registry • Slack Alias: @package-registry-group • GitLab Group: @gitlab-org/ci-cd/package-stage/package-registry-group • Handbook • Product Manager: Tim Rizzi • Product Marketing Manager: Heather Simpson • Support: TBD • Backend Engineering Manager: Crystal Poole • Frontend Engineering Manager: Crystal Poole • Software Engineer in Test: Sofia Vistas • Backend Engineering: David Fernandez, Dzmitry Meshcharakou, Moaz Khalifa, Rad Batnag • Frontend Engineering: Rahul Chanila • UX Researcher: Erika Feldman • Technical Writer: Marcel Amirault • Application Security Engineer: Greg Myers • Customer Success: • Internal Customers: Distribution Team, (TBD), Infrastructure Department, (TBD) • Focus: [Package Registry GMAU] • Features in this Group

• Package Registry Viable • Documentation • Direction Page
• Helm Chart Registry Viable • Documentation • Direction Page

Container Registry group

Development totals: 5 BE, 1 FE

Slack Channel: g_container-registry • Slack Alias: @container-registry-group • GitLab Group: @gitlab-org/ci-cd/package-stage/container-registry-group • Handbook • Product Manager: Tim Rizzi • Product Marketing Manager: Heather Simpson • Support: TBD • Backend Engineering Manager: Crystal Poole • Frontend Engineering Manager: Crystal Poole • Software Engineer in Test: Sofia Vistas • Backend Engineering: Adie Po, Hayley Swimelar, Jaime Martínez, João Pereira, Suleimi Ahmed • Frontend Engineering: Rahul Chanila • UX Researcher: Erika Feldman • Technical Writer: Marcel Amirault • Application Security Engineer: Greg Myers • Customer Success: • Internal Customers: Distribution Team, (TBD), Infrastructure Department, (TBD) • Focus: [Container Registry GMAU] • Features in this Group

• Container Registry Viable • Documentation • Direction Page
• Dependency Proxy Viable • Documentation • Direction Page
• Dependency Firewall Planned 2024 • Direction Page

CD section

Slack Channel: cd-section • Product: • Product: [Mike Flouton] • Development: • Development: Sam Goldstein • Product Design: Marcel van Remmerden • UX Research: Will Leidheiser • Support: • Product Marketing: • Quality: [Joanna Shih] • Analyst Relations: • Legal & Corporate Affairs:

Deploy stage

Slack Channel: s_deploy • GitLab Group: @gitlab-org/ci-cd/deploy-stage/environments-group • Handbook • Product Management: Viktor Nagy • Development: Nicolò Maria Mezzopera • Product Design Manager: Rayana Verissimo

Environments group

Development totals: 6 BE, 3 FE

Slack Channel: g_environments • Slack Alias: @Environments Group • Handbook • Product Manager: Viktor Nagy • Product Marketing Manager: Aathira Nair • Support: Lewis Brown • Backend Engineering Manager: Nicolò Maria Mezzopera • Frontend Engineering Manager: Nicolò Maria Mezzopera • Backend Engineering: Hunter Stewart, Mikhail Mazurskiy, Pam Artiaga, Shinya Maeda, Tiger Watson, Timo Furrer • Frontend Engineering: Andrei Zubov, Andrew Fontaine, Anna Vovchenko • UX Researcher: Will Leidheiser • Product Designer: Emily Bauman • Technical Writer: Phillip Wells • Application Security Engineer: Ameya Darshan • Customer Success: • Internal Customers: Quality Department, (TBD), Delivery Team, (John Skarbek), Reliability Engineering, (Devin Sylva), Distribution Team, (TBD), Security Department, (TBD), AutoDevOps and Kubernetes Group, (TBD) • Focus: TBD • Features in this Group

• Auto DevOps Viable • Marketing Page • Documentation • Direction Page
• Continuous Delivery Complete • Marketing Page • Documentation • Direction Page
• Deployment Management Viable • Marketing Page • Documentation • Direction Page
• Environment Management Viable • Documentation • Direction Page
• Feature Flags Viable • Documentation • Direction Page
• Infrastructure as Code Viable • Documentation • Direction Page
• Release Orchestration Viable • Documentation • Direction Page

Sec section

Product: Hillary Benson • Development: Wayne Haber • Product Design: Taurie Davis • UX Research: [["Michael Oliver", "Will Leidheiser"]] • Support: TBD • Product Marketing: Brian Mason • Quality: Vincy Wilson • Analyst Relations: • Infrastructure Manager: Steve Loyd (Acting) • Legal & Corporate Affairs: Iris Gorman

Secure stage

Slack Channel: s_secure • GitLab Group: @gitlab-org/secure • Handbook • Development: Thomas Woodham • Product Design Manager: Justin Mandell

Static Analysis group

Development totals: 7 BE, 2 FE

Slack Channel: g_secure-static-analysis • Slack Alias: @secure_static_analysis_team • GitLab Group: @gitlab-org/secure/static-analysis • Product Manager: Connor Gilbert • Product Marketing Manager: Brian Mason • Support: David Coy, Christopher Mutua • Backend Engineering Manager: Amar Patel • Software Engineer in Test: TBD • Backend Engineering: Ahmed Hemdan, Craig Smith, James Liu, Lucas Charles, Ross Fuhrman, Serena Fang, Vishwa Bhat • Frontend Engineering: Dheeraj Joshi, Jannik Lehmann • UX Researcher: Michael Oliver • Product Designer: Michael Fangman • Technical Writer: Russell Dickenson • Application Security Engineer: Nikhil George • Customer Success: Bryan Miller, Brian Wald, Sam Morris • Internal Customers: Security Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Static Analysis Paid GMAU] • Features in this Group

• SAST Complete • Documentation • Direction Page
• Secret Detection Viable • Documentation • Direction Page
• Code Quality Minimal • Documentation • Direction Page

Dynamic Analysis group

Development totals: 3 BE

Slack Channel: g_secure-dynamic-analysis • Slack Alias: @secure_dynamic_analysis_be • GitLab Group: @gitlab-org/secure/dynamic-analysis-be • Product Manager: Derek Ferguson • Product Marketing Manager: Brian Mason • Support: Kate Grechishkina • Backend Engineering Manager: Thomas Woodham • Backend Engineering: Cam Swords, David Nelson, Mike Eddington • UX Researcher: Michael Oliver • Technical Writer: Russell Dickenson • Application Security Engineer: Nikhil George • Customer Success: Bryan Miller, Brian Wald, Sam Morris • Internal Customers: Security Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Dynamic Analysis Paid GMAU] • Features in this Group

• DAST Complete • Documentation • Direction Page
• Fuzz Testing Viable • Documentation • Direction Page
• API Security Viable • Documentation • Direction Page
• IAST New in 2023 • Direction Page
• Attack Emulation New in 2023

Composition Analysis group

Development totals: 9 BE, 1 FE

Slack Channel: g_secure-composition-analysis • Slack Alias: @secure_composition_analysis_dev • GitLab Group: @gitlab-org/secure/composition-analysis-dev • Product Manager: Sara Meadzinger • Product Marketing Manager: Brian Mason • Support: Katrin Leinweber • Backend Engineering Manager: Olivier Gonzalez • Software Engineer in Test: Will Meek • Backend Engineering: Adam Cohen, Aditya Tiwari, Fabien Catteau, Oscar Tovar, Igor Frenkel, Nick Ilieskou, Olivier Gonzalez, Philip Cunningham, Shao Ming Tan, Tetiana Chupryna • Frontend Engineering: Fernando Cardenas • UX Researcher: Michael Oliver • Technical Writer: Russell Dickenson • Application Security Engineer: Nikhil George • Customer Success: Bryan Miller, Brian Wald, Sam Morris • Internal Customers: Security Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Composition Analysis Paid GMAU] • Features in this Group

• Software Composition Analysis Viable • Documentation • Direction Page
• Container Scanning Viable • Documentation • Direction Page

Vulnerability Research group

Development totals: 3 BE

Slack Channel: g_secure-vulnerability-research • Product Manager: Hillary Benson • Product Marketing Manager: Brian Mason • Support: Mario Mora • Backend Engineering Manager: Mark Art • Backend Engineering: Isaac Dawson, Julian Thome, Michael Henriksen • Technical Writer: #docs Slack channel • Application Security Engineer: Nikhil George • Customer Success: • Internal Customers: Security Department, (TBD), Engineering Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Paid GMAU] • Features in this Group

• GitLab Advisory Database • Direction Page
• Security Benchmarking • Direction Page

Monitor stage

Slack Channel: s_monitor • Slack Alias: @Monitor Group • GitLab Group: @gitlab-org/monitor • Handbook • Product Management: Hillary Benson • Development: Sam Goldstein • Product Marketing Manager: Aathira Nair

Respond group

Development totals: 4 BE, 2 FE

Slack Channel: g_respond • Slack Alias: @monitor-respond-group • Handbook • Product Manager: Kevin Chu • Product Marketing Manager: Aathira Nair • Support: Cody West • Backend Engineering Manager: François Rosé • Frontend Engineering Manager: François Rosé • Backend Engineering: Peter Leitzen, Rajendra Kadam, Sarah Yasonik, Vitali Tatarintev • Frontend Engineering: Paulina Sedlak-Jakubowska, Tristan Read • UX Researcher: Will Leidheiser • Technical Writer: Marcin Sędłak-Jakubowski • Application Security Engineer: [Félix Veillette-Potvin] • Customer Success: • Internal Customers: Infrastructure Department, (Dave Smith), Engineering Department, (Sam Goldstein) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Respond GMAU] • Features in this Group

• Incident Management Viable • Documentation • Direction Page
• On-call Schedule Management Minimal • Documentation • Direction Page
• Runbooks Planned 2024 • Documentation • Direction Page
• Service Desk Viable • Marketing Page • Documentation • Direction Page

Observability group

Development totals: 4 BE, 1 FE

Slack Channel: g_observability • Slack Alias: @observability-group • Handbook • Product Manager: Hillary Benson • Product Marketing Manager: Aathira Nair • Backend Engineering Manager: Nicholas Klick • Frontend Engineering Manager: Nicholas Klick • Backend Engineering: Ankit Bhatnagar, Arun Sori, Joe Shaw, Paweł Rozlach • Frontend Engineering: Daniele Rossetti • UX Researcher: Will Leidheiser • Technical Writer: #docs Slack channel • Application Security Engineer: Ottilia Westerlund • Infrastructure Security Engineer: [Joe Dubail] • Customer Success: • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Acquisition Integration] • Features in this Group

• Metrics Planned 2024 • Documentation • Direction Page
• Tracing Planned 2023 • Documentation • Direction Page
• Logging Planned 2024 • Documentation • Direction Page
• Error Tracking Minimal • Documentation • Direction Page

Govern stage

Slack Channel: s_govern • GitLab Group: @gitlab-org/govern • Handbook • Product Management: Sam White • Development: Phil Calder • Product Design Manager: Justin Mandell

Security Policies group

Development totals: 6 BE, 2 FE

Slack Channel: g_govern_security_policies • Product Manager: Grant Hickman • Product Marketing Manager: Brian Mason • Engineering Manager: Alan (Maciej) Paruszewski • Backend Engineering: Alishan 'Ali' Ladhani, Andy Soiron, Bala Kumar Subramani, Dominic Bauer, Marcos Rocha, Sashi Kumar Kumaresan • Frontend Engineering: Alexander Turinske, Artur Fedorov • UX Researcher: Michael Oliver • Product Designer: Camellia Yang • Technical Writer: Russell Dickenson • Application Security Engineer: Ottilia Westerlund • Customer Success: Caleb Cooper, John Feeney, Mirko Brandner, Yu-Chen Hsueh • Internal Customers: Security Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Security Policies Paid GMAU] • Features in this Group

• Security Policy Management Minimal • Documentation • Direction Page

Threat Insights group

Development totals: 8 BE, 5 FE

Slack Channel: g_govern_threat_insights • Product Manager: Alana Bellucci • Product Marketing Manager: Brian Mason • Fullstack Managers: Thiago Figueiró, Neil McCorrison • Support: Gerardo Gutierrez • Software Engineer in Test: Harsha Muralidhar • Backend Engineering: Brian Williams, Gregory Havenga, Malcolm Locke, Mehmet Emin Inac, Michał Zając, Mo Khan, Subashis Chakraborty, Zamir Martins Filho • Frontend Engineering: Daniel Tian, Dave Pisek, Lorenz van Herwaarden, Samantha Ming, Savas Vedova • UX Researcher: Michael Oliver • Product Designer: Rebecca "Becka" Lippert • Technical Writer: Russell Dickenson • Application Security Engineer: Ottilia Westerlund • Customer Success: Caleb Cooper, John Feeney, Mirko Brandner, Yu-Chen Hsueh • Internal Customer: Security Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Threat Insights Paid GMAU] • Features in this Group

• Vulnerability Management Viable • Documentation • Direction Page
• Dependency Management Viable • Documentation • Direction Page
• Software Bill of Materials Viable • Documentation • Direction Page

Compliance group

Development totals: 7 BE, 1 FE

Product Manager: Derek Ferguson • Product Marketing Manager: Brian Mason • Engineering Manager: Nathan Rosandich • Support: TBD • Software Engineer in Test: Mark Lapierre • Backend Engineering: Aaron Huntsman, Harsimar Sandhu, Hitesh Raghuvanshi, Huzaifa Iftikhar, Jay Montal, Sam Figueroa, Michael Becker • Frontend Engineering: Illya Klymov • UX Researcher: Michael Oliver • Technical Writer: Evan Read • Application Security Engineer: Kevin Morrison • Customer Success: Caleb Cooper, John Feeney, Mirko Brandner, Yu-Chen Hsueh • Internal Customers: Customer Support Department, (TBD), Security Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Steve Loyd (Acting) • Focus: [Govern Compliance Paid GMAU] • Features in this Group

• Audit Events Viable • Documentation • Direction Page
• Compliance Management Viable • Documentation • Direction Page
• Release Evidence Minimal • Documentation • Direction Page

Data Science section

Product: Hillary Benson • Development: Wayne Haber • Product Design: Taurie Davis • UX Research: Nick Hertz • Support: TBD • Product Marketing: Saumya Upadhyaya • Quality: Vincy Wilson • Legal & Corporate Affairs: Tiffany Chen

Anti-Abuse stage

Product Management: Jensen Stava • Development: Phil Calder

Anti-Abuse group

Development totals: 3 BE

Slack Channel: g_anti-abuse • Handbook • Product Manager: Jensen Stava • Engineering Manager: Jay Swain • Support: Michael Gibson • Backend Engineering: Alex Buijs, Eugie Limpin, Hinam Mehra • Technical Writer: Phillip Wells • Application Security Engineer: Nick Malcolm • Features in this Group

• Instance Resiliency Minimal • Documentation • Direction Page
• Insider Threat Minimal • Direction Page

ModelOps stage

Slack Channel: s_modelops • Handbook • Product Management: Taylor McCaslin • Development: Wayne Haber • Product Design Manager: Justin Mandell

AI Assisted group

Development totals: 7 BE

Slack Channel: g_ai_assisted • Handbook • Product Manager: [Neha Khalwadekar] • Engineering Manager: Monmayuri Ray • Software Engineer in Test: TBD • Backend Engineering: Alexander Chueshev, Alper Akgun, Andras Herczeg, Bruno Cardoso, Hongtao Yang, Stephan Rayner, Tan Le • UX Researcher: Nick Hertz • Product Designer: Katie Macoy • Technical Writer: #docs Slack channel • Application Security Engineer: Nick Malcolm • Features in this Group

• Workflow Automation Minimal • Documentation • Direction Page
• Intelligent Code Security Planned 2023 • Direction Page
• Code Suggestions Minimal • Documentation • Direction Page

MLOps group

Development totals: 1 BE

Slack Channel: g_mlops • Product Manager: Taylor McCaslin • Engineering Manager: Monmayuri Ray • Backend Engineering: Eduardo Bonet • Technical Writer: #docs Slack channel • Application Security Engineer: Nick Malcolm • Features in this Group

• MLOps Minimal • Documentation • Direction Page

DataOps group

Slack Channel: s_modelops • Product Manager: Taylor McCaslin • Engineering Manager: Monmayuri Ray • Technical Writer: #docs Slack channel • Application Security Engineer: Nick Malcolm • Features in this Group

• DataOps Planned 2023 • Direction Page

Analytics section

Slack Channel: ops-section • Handbook • Product: Justin Farris • Development: Tim Zallmann • Product Design: Taurie Davis • UX Research: Nick Hertz • Product Marketing: Saumya Upadhyaya • Quality: Ramya Authappan • Legal & Corporate Affairs: Eugene McCrann

Analytics stage

Slack Channel: analytics-section • Handbook • Product Management: Sam Kerr • Development: Tim Zallmann • Product Design Manager: Justin Mandell • UX Researcher: [["Nick Hertz"]]

Analytics Instrumentation group

Development totals: 6 BE

Handbook • Product Manager: Tanuja Jayarama Raju • Product Marketing Manager: Saumya Upadhyaya • Support: TBD • Backend Engineering Manager: [Sebastian Rehm] • Software Engineer in Test: TBD • Backend Engineering: Ankit Panchal, Sebastian Rehm, Jonas Larsen, Michał Wielich, Mikołaj Wawrzyniak, Niko Belokolodov, Piotr Skorupa • UX Researcher: Nick Hertz • Technical Writer: Lorena Ciutacu • Application Security Engineer: Greg Myers • Customer Success: Hugo Azevedo • Internal Customers: Sales Department, (TBD), Marketing Department, (TBD), Product Department, (TBD), Customer Success, (TBD), Data Team, (TBD) • Features in this Group

• Service Ping Viable • Documentation
• Application Instrumentation Minimal • Direction Page

Product Analytics group

Handbook • Product Manager: James Heimbuck • Product Marketing Manager: Saumya Upadhyaya • Support: TBD • Backend Engineering Manager: Dennis Tang • Software Engineer in Test: [Carlo Catimbang] • Backend Engineering: • UX Researcher: Nick Hertz • Product Designer: Kevin Comoli • Technical Writer: Lorena Ciutacu • Application Security Engineer: Greg Myers • Customer Success: Hugo Azevedo • Internal Customers: Sales Department, (TBD), Marketing Department, (TBD), Product Department, (TBD), Customer Success, (TBD), Data Team, (TBD) • Site Reliability Engineering: Nels Nelson • Features in this Group

• Product Analytics New in 2023

Growth section

Product: Sam Awezec • Development: Phil Calder • Support: Shaun McCann • Product Marketing: Saumya Upadhyaya • Quality: Vincy Wilson • Analyst Relations: Ryan Ragozzine • Infrastructure Manager: Dave Smith • Legal & Corporate Affairs: Tiffany Chen

Growth stage

Slack Channel: s_growth • GitLab Group: @gitlab-org/growth • Handbook • Development: Phil Calder • Internal Customers: Sales Department (TBD), Marketing Department (TBD), Product Department (TBD), Finance Department (TBD)

Acquisition group

Development totals: 4 BE

Slack Channel: g_acquisition • Handbook • Product Manager: Gayle Doud • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: Kamil Niechajewicz • Support: TBD • Backend Engineering: Doug Stull, Roy Liu, Ross Byrne, Serhii Yarynovskyi • UX Researcher: TBD • Technical Writer: #docs Slack channel • Application Security Engineer: Nikhil George • Customer Success: Hugo Azevedo • Infrastructure Manager: Dave Smith • Features in this Group

• Conversion Experiment • Direction Page
• Expansion Experiment • Direction Page
• Measurement and Locking • Direction Page
• Onboarding • Direction Page

Activation group

Slack Channel: g_activation • Handbook • Product Manager: Paige Cordero • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: Kamil Niechajewicz • Support: TBD • Backend Engineering: • UX Researcher: TBD • Technical Writer: #docs Slack channel • Application Security Engineer: Nikhil George • Customer Success: Hugo Azevedo • Infrastructure Manager: Dave Smith • Features in this Group

• Adoption Experiment • Direction Page
• Activation Experiment • Direction Page

Fulfillment section

Product: Omar Fernandez • Development: Jerome Ng • Product Design: Marcel van Remmerden • UX Research: Nick Hertz • Support: John Lyttle • Product Marketing: Saumya Upadhyaya • Quality: Vincy Wilson • Analyst Relations: • Infrastructure Manager: Dave Smith • Legal & Corporate Affairs: Iris Gorman

Fulfillment stage

Product Management: Omar Fernandez • Development: Jerome Ng • Product Marketing Manager: Saumya Upadhyaya • Product Design Manager: Jacki Bauer • UX Researcher: [["Nick Hertz"]]

Purchase group

Development totals: 3 BE, 2 FE

Slack Channel: g_purchase • Product Manager: Alex Martin • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: [Shreyas Agarwal (Interim)] • Support: Sokunrotanak Srey • Software Engineer in Test: Valerie Burton • Backend Engineering: Bishwa Hang Rai, Josianne Hyson, Shreyas Agarwal • Frontend Engineering: Angelo Gulina, Vamsi Vempati • UX Researcher: Nick Hertz • Technical Writer: Fiona Neill • Application Security Engineer: Rohit Shambhuni • Infrastructure Manager: Dave Smith • Features in this Group

• Purchase Viable • Direction Page
• Seat Cost Management Viable

Provision group

Development totals: 4 BE

Slack Channel: g_provision • Product Manager: Courtney Meddaugh • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: Isabel Sandin • Support: Keven Hughes • Software Engineer in Test: Dan Davison • Backend Engineering: Amparo Luna, Corinna Gogolok, Paulo Barros, Qingyu Zhao • Frontend Engineering: • Technical Writer: Fiona Neill • Application Security Engineer: Rohit Shambhuni • Infrastructure Manager: Dave Smith • Features in this Group

• SM Provisioning Viable
• SaaS Provisioning Viable
• Commerce Integrations Minimal • Direction Page

Utilization group

Development totals: 4 BE, 3 FE

Slack Channel: g_utilization • Product Manager: [Alex Martin (Acting)] • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: Chase Southard • Support: Shem Gyll • Software Engineer in Test: TBD • Backend Engineering: Jason Goodman, Mohamed Hamda, Suraj Tripathi, Vijay Hawoldar • Frontend Engineering: Ammar Alakkad, Kos Palchyk, Sheldon Led • UX Researcher: Nick Hertz • Technical Writer: Fiona Neill • Application Security Engineer: Nick Malcolm • Infrastructure Manager: Dave Smith • Features in this Group

• Consumables Cost Management Viable • Direction Page

Fulfillment Platform group

Slack Channel: g_fulfillment_platform • Product Manager: Manuel Gass • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: James Lopez • Backend Engineering: • Frontend Engineering: • Technical Writer: #docs Slack channel • Application Security Engineer: Ottilia Westerlund • Infrastructure Manager: Dave Smith • Site Reliability Engineering: Ahmad Sherif • Features in this Group

• Fulfillment Infrastructure Viable • Direction Page
• CustomersDot Application Viable • Direction Page
• Fulfillment Admin Tooling Minimal • Direction Page

Billing and Subscription Management group

Development totals: 2 BE, 4 FE

Slack Channel: g_billing_and_subscription_management • Product Manager: Tatyana Golubeva • Product Marketing Manager: Saumya Upadhyaya • Engineering Manager: Ragnar Hardarson • Support: Firdaws Farukh • Software Engineer in Test: Chloe Liu • Backend Engineering: Aman Luthra, Ryan Cobb • Frontend Engineering: Diana Zubova, Laura Meckley, Michael Lunøe, Sharmad Nachnolkar • UX Researcher: Nick Hertz • Product Designer: Emily Sybrant • Technical Writer: #docs Slack channel • Application Security Engineer: Ottilia Westerlund • Infrastructure Manager: Dave Smith • Features in this Group

• Billing & Payments Viable
• Subscription Management Viable

Enablement section

Product: Joshua Lambert • Development: Chun Du • Product Design: Taurie Davis • UX Research: Will Leidheiser • Support: TBD • Product Marketing: Saumya Upadhyaya • Quality: Kassandra Svoboda • Analyst Relations: Ryan Ragozzine • Infrastructure Manager: Dave Smith • Legal & Corporate Affairs: Iris Gorman

Systems stage

Slack Channel: s_enablement • GitLab Group: @gitlab-org/enablement-section • Handbook • Development: Chun Du

Distribution::Build group

Development totals: 6 BE

Slack Channel: g_distribution • Slack Alias: @distributionteam • GitLab Group: @gitlab-org/distribution • Handbook • Product Manager: Dilan Orrino • Product Marketing Manager: Saumya Upadhyaya • Support: Diana Stanley, Nathan Black, Chris Kaburu • Backend Engineering Manager: DJ Mountney • Software Engineers in Test: Grant Young, Nailia Iskhakova • Backend Engineering: Andrew Patterson, Balasankar 'Balu' C, David 'DJ' Mountney, Dmitry Makovey, Dustin Collins, Robert Marshall • UX Researcher: Will Leidheiser • Technical Writer: Axil, Evan Read • Application Security Engineer: Kevin Morrison • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD), Customer Success, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Distribution PPI] • Features in this Group

• Build Complete • Documentation • Direction Page

Distribution::Deploy group

Development totals: 6 BE

Slack Channel: g_distribution • Slack Alias: @distributionteam • GitLab Group: @gitlab-org/distribution • Handbook • Product Manager: Dilan Orrino • Product Marketing Manager: Saumya Upadhyaya • Support: Diana Stanley, Nathan Black, Chris Kaburu • Backend Engineering Manager: Peter Lu • Software Engineers in Test: Grant Young, Nailia Iskhakova, Vishal Patel • Backend Engineering: Clemens Beck, Hossein Pursultani, Jason Plum, Jason Young, João Alexandre Prado Tavares Cunha, Mitch Nielsen, Peter Lu • UX Researcher: Will Leidheiser • Technical Writer: Axil, Evan Read • Application Security Engineer: Kevin Morrison • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD), Customer Success, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Distribution PPI] • Features in this Group

• Omnibus Package Lovable • Documentation • Direction Page
• Cloud Native Installation Complete • Documentation • Direction Page

Gitaly::Cluster group

Development totals: 6 BE

Slack Channel: g_gitaly • Handbook • Product Manager: Mark Wood • Product Marketing Manager: Saumya Upadhyaya • Support: Gerardo Gutierrez, [David Wainaina] • Backend Engineering Manager: Andras Horvath • Software Engineer in Test: John McDonnell • Backend Engineering: Andras Horvath, Justin Tobler, Patrick Steinhardt, Pavlo Strokov, Quang-Minh Nguyen, Sami Hiltunen, Will Chandler • Technical Writer: Evan Read • Application Security Engineer: Greg Myers • Customer Success: Conley Rogers, Kristof Goossens, Simon Mansfield • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Site Reliability Engineering: Furhan Shabir, Steve Azzopardi • Focus: [Gitaly GMAU] • Features in this Group

• Gitaly • Documentation • Direction Page

Gitaly::Git group

Development totals: 5 BE

Slack Channel: g_gitaly • Handbook • Product Manager: Mark Wood • Product Marketing Manager: Saumya Upadhyaya • Support: Gerardo Gutierrez • Backend Engineering Manager: John Cai • Software Engineer in Test: John McDonnell • Backend Engineering: Christian Couder, James Fargher, John Cai, Karthik Nayak, Patrick Steinhardt, Toon Claes • Technical Writer: Evan Read • Application Security Engineer: Ameya Darshan • Customer Success: Conley Rogers, Kristof Goossens, Simon Mansfield • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Site Reliability Engineering: Furhan Shabir, Steve Azzopardi • Focus: [Gitaly GMAU] • Features in this Group

• Gitaly • Documentation • Direction Page

Geo group

Development totals: 7 BE, 1 FE

Slack Channel: g_geo • GitLab Group: @gitlab-org/geo-team • Handbook • Product Manager: Sampath Ranasinghe • Product Marketing Manager: Saumya Upadhyaya • Support: Bo Carbonell, Łukasz Korbasiewicz • Backend Engineering Manager: Juan Silva • Frontend Engineering Manager: Juan Silva • Software Engineer in Test: Nick Westbury • Backend Engineering: Aakriti Gupta, Douglas Barbosa Alexandre, Gabriel Mazetto, Ian Baum, Javiera Tapia, Juan Silva, Michael Kozono, Valery Sizov • Frontend Engineering: Zack Cuddy • UX Researcher: Will Leidheiser • Technical Writer: Axil • Application Security Engineer: Ameya Darshan • Internal Customer: Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Geo Paid GMAU] • Features in this Group

• Geo-replication Complete • Marketing Page • Documentation • Direction Page
• Disaster Recovery Complete • Documentation • Direction Page
• Backup/Restore of GitLab instances Minimal • Documentation • Direction Page

Data Stores stage

Slack Channel: s_enablement • GitLab Group: @gitlab-org/enablement-section • Handbook • Development: Nick Nguyen • Product Design Manager: Chris Micek

Application Performance group

Development totals: 4 BE

Slack Channel: g_application_performance • GitLab Group: @gitlab-org/memory-team • Handbook • Product Manager: Roger Woo • Product Marketing Manager: Saumya Upadhyaya • Support: [Gabriel Yoachum] • Backend Engineering Manager: [Paul Phillips] • Software Engineer in Test: TBD • Backend Engineering: Aleksei Lipniagov, Matthias Käppler, Nikola Milojevic, Roy Zwambag • UX Researcher: Will Leidheiser • Technical Writer: Jon Glassman • Application Security Engineer: Kevin Morrison • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Memory PPI] • Features in this Group

• Application Performance • Direction Page
• Redis • Direction Page
• Rate Limiting Framework • Direction Page

Global Search group

Development totals: 6 BE, 1 FE

Slack Channel: g_global_search • GitLab Group: @gitlab-org/search-team • Handbook • Product Manager: Joshua Lambert (Interim) • Product Marketing Manager: Saumya Upadhyaya • Support: Vlad Stoianovici, Cleveland Bledsoe Jr • Backend Engineering Manager: Changzheng Liu • Frontend Engineering Manager: Changzheng Liu (Interim) • Software Engineer in Test: TBD • Backend Engineering: Dmitry Gruzd, John Mason, Madelein van Niekerk, Ravi Kumar, Siddharth Dungarwal, Terri Chu • Frontend Engineering: Tomáš Bulva • UX Researcher: Will Leidheiser • Technical Writer: Ashraf Khamis • Application Security Engineer: Kevin Morrison • Internal Customers: Engineering Department, (TBD), Customer Success, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Paid GMAU] • Features in this Group

• Global Search Viable • Documentation • Direction Page
• Code Search Minimal • Documentation • Direction Page

Database group

Development totals: 7 BE

Slack Channel: g_database • GitLab Group: @gitlab-org/database-team • Handbook • Product Manager: Roger Woo • Product Marketing Manager: Saumya Upadhyaya • Support: Ben Prescott • Backend Engineering Manager: Alex Ives • Backend Engineering: Alex Ives, Diogo Frazão, Jon Jenkins, Krasimir Angelov, Leonardo da Rosa, Matt Kasa, Prabakaran Murugesan, Simon Tomlinson • UX Researcher: Will Leidheiser • Technical Writer: Amy Qualls • Application Security Engineer: Kevin Morrison • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Database PPI] • Features in this Group

• Database • Direction Page

Tenant Scale group

Development totals: 8 BE, 1 FE

Slack Channel: g_tenant_scale • GitLab Group: @gitlab-org/tenant-scale-group • Handbook • Product Manager: Christina Lohr • Product Marketing Manager: Saumya Upadhyaya • Support: Ben Prescott, Asmaa Hassan, Bruno Freitas • Backend Engineering Manager: Arturo Herrero • Backend Engineering: Abdul Wadood, Alex Pooley, Arturo Herrero, Dylan Griffith, Kamil Trzciński, Manoj Memana Jayakumar, Omar Qunsul, Rutger Wessels, Thong Kuah • Frontend Engineering: Peter Hegman • UX Researcher: Will Leidheiser • Product Designers: Mike Nichols, Amelia Bauerly • Technical Writer: Lorena Ciutacu • Application Security Engineer: Rohit Shambhuni • Internal Customers: Quality Department, (TBD), Infrastructure Department, (TBD) • Infrastructure Manager: Dave Smith • Focus: [Database PPI] • Features in this Group

• Cell • Direction Page
• Groups & Projects Complete • Documentation • Direction Page
• User Profile • Documentation • Direction Page
• Organization • Documentation • Direction Page

SaaS Platforms section

Product: Fabian Zimmer • Development: Marin Jankovski • Product Design: Marcel van Remmerden • UX Research: Will Leidheiser • Support: TBD • Product Marketing: Saumya Upadhyaya • Quality: Kassandra Svoboda • Analyst Relations: • Infrastructure Manager: Dave Smith • Legal & Corporate Affairs: Iris Gorman

SaaS Platforms stage

Slack Channel: s_platforms • GitLab Group: @gitlab-com/gl-infra/platform • Handbook • Product Design Manager: Rayana Verissimo

Delivery group

Slack Channel: g_delivery • GitLab Group: @gitlab-org/delivery • Handbook • Product Manager: [Sam Wiskow] • Product Marketing Manager: Saumya Upadhyaya • UX Researcher: Will Leidheiser • Technical Writer: #docs Slack channel • Application Security Engineer: Ameya Darshan • Infrastructure Manager: Dave Smith • Features in this Group

• Delivery • Documentation • Direction Page

Scalability group

Slack Channel: g_scalability • GitLab Group: @gitlab-org/scalability • Handbook • Product Manager: [Sam Wiskow] • Product Marketing Manager: Saumya Upadhyaya • Technical Writer: #docs Slack channel • Application Security Engineer: Rohit Shambhuni • Infrastructure Manager: Dave Smith • Features in this Group

• Scalability • Documentation • Direction Page
• Error Budgets • Documentation • Direction Page
• Infrastructure Cost Data • Direction Page
• Capacity Planning • Documentation • Direction Page

GitLab Dedicated group

Development totals: 1 BE

Slack Channel: f_gitlab_dedicated • GitLab Group: @TBD • Handbook • Product Manager: Andrew Thomas • Product Marketing Manager: [Saumya Upadhyaya & Heather Simpson] • Support: Brie Carranza, Matthew Badeau • Backend Engineering Manager: [Oriol Lluch] • Frontend Engineering Manager: TBD • Backend Engineering: Sean Arnold • Product Design Manager: Rayana Verissimo • UX Researcher: Will Leidheiser • Product Designer: Ali Ndlovu • Technical Writer: #docs Slack channel • Application Security Engineer: Greg Alfaro • Infrastructure Manager: Dave Smith • Focus: [GMAU] • Features in this Group

• GitLab Dedicated • Documentation • Direction Page

Switchboard group

Development totals: 1 BE

Slack Channel: g_dedicated_switchboard • GitLab Group: @TBD • Handbook • Product Manager: [Loryn Bortins] • Product Marketing Manager: [Saumya Upadhyaya & Heather Simpson] • Support: TBD • Backend Engineering Manager: [Amy Shiel] • Frontend Engineering Manager: TBD • Backend Engineering: Sean Arnold • Product Design Manager: Rayana Verissimo • UX Researcher: Will Leidheiser • Product Designer: Ali Ndlovu • Technical Writer: #docs Slack channel • Application Security Engineer: Greg Alfaro • Infrastructure Manager: Dave Smith • Focus: [GMAU] • Features in this Group

• Switchboard Planned 2023 • Documentation • Direction Page

US Public Sector Services group

Slack Channel: TBD • Slack Alias: @TBD • GitLab Group: @TBD • Product Manager: Chris Balane • Product Marketing Manager: TBD • Support: TBD • Backend Engineering Manager: Stephen Dumesnil • Software Engineers in Test: Andy Hohenner, Brittany Wilkerson • Backend Engineering: • UX Researcher: TBD • Technical Writer: #docs Slack channel • Application Security Engineer: Greg Myers • Infrastructure Manager: Dave Smith • Focus: [GMAU] • Features in this Group

• US Public Sector Services • Documentation • Direction Page

Single-Engineer Groups section

Mobile stage

Product Management: David DeSanto

Mobile DevOps group

Slack Channel: mobile-devops • Features in this Group

• Mobile DevOps • Direction Page

Deploy stage

Product Management: Kenny Johnston

Five Minute Production App group

Development totals: 1 BE

Slack Channel: 5-minute-production-app • Product Sponsor: Kenny Johnston • Backend Engineering: Sri Rangan • Focus: [Five Minute Production App AMAU] • Features in this Group

• 5 Minute Production App • Direction Page

Low-Code/No-Code stage

GitLab Group: @gitlab-org/incubation-engineering/no-code-low-code • Handbook • Product Management: [Tao Guo]

No-code Automation group

Slack Channel: incubation-eng • Application Security Engineer: Nick Malcolm • Features in this Group

• No-code Automation • Direction Page

Possible future Stages

We have boundless ambition, and we expect GitLab to continue to add new stages to the DevOps lifecycle. Below is a list of future stages we are considering:

1. Data, maybe leveraging Meltano product
2. Networking, maybe leveraging some of the open source standards for networking and/or Terraform networking providers
3. Design, we already have design management today

Stages are different from the application types you can service with GitLab.

Maturity

Not all categories are at the same level of maturity. Some are just minimal and some are lovable. See the category maturity page to see where each category stands.

Other functionality

This list of other functionality so you can easily find the team that owns it. Maybe we should make our features easier to search to replace the section below.

Other functionality in Plan stage

Project Management group

• markdown functionality
• assignees
• milestones
• due dates
• labels
• issue weights
• quick actions
• email notifications
• to-do list
• Real-time features (excluding real-time collaboration)

Other functionality in Create stage

Code Review group

• Merge Requests
• GitLab CLI

IDE group

• GitLab Workflow extension for Visual Studio Code

Other functionality in Verify

CI Group

• CI Abuse Response

Pipeline Authoring Group

• CI/CD Template Management and Contributions

Other functionality in Monitor stage

Other functionality in Manage stage

Other functionality in Engineering Productivity

• GDK

Other functionality in Quality Engineering

• Reference Architectures
• GitLab Environment Toolkit (GET)
• GitLab Performance Tool (GPT)
• Performance Test Data
• Zero Downtime Testing Tool

Internal Customers: Create:Gitaly, Enablement section, SaaS Platforms section, Infrastructure Department, Support Department, Customer Success

Other functionality in Analytics

Product Analytics group

• Analytics Dashboards - used by many groups to add visualizations or provide pre-configured dashboards to users

Facilitated functionality

Some product areas are have a broad impact across multiple stages. Examples of this include, among others:

• Shared project views, like the project overview and settings page.
• Functionality specific to the admin area and not tied to a feature belonging to a particular stage.
• UI components available through our design system, Pajamas.
• Dashboards for displaying analytics, such as Product Analytics, Value Stream Analytics, and others.

While the mental models for these areas are maintained by specific stage groups, everyone is encouraged to contribute within the guidelines that those teams establish. For example, anyone can contribute a new setting following the established guidelines for Settings. When a contribution is submitted that does not conform to those guidelines, we merge it and "fix forward" to encourage innovation.

If you encounter an issue falling into a facilitated area:

• For issues that relate to updating the guidelines, apply the group::category label for the facilitating group.
• For issues that relate to adding content related to a facilitated area, apply the group::category label for the most closely related group. For example, when adding a new setting related to Merge Requests, apply the group::source code label.

Shared responsibility functionality

There are certain product capabilities that are foundational in nature and affect or refer to horizontal components of the architecture that have an impact across functional groups and stages.

These capabilities may refer to "Facilitated Functionality" (see section above) where the mental models are owned by a particular group, while anyone can contribute. However, there may be others that will not have a clear owner because they don’t fall squarely into any particular group’s purview of product categories. Prime examples of this are issues related to the improvement or evolution of foundational components, frameworks and libraries that are used by several or all groups across the organization. Another example could be components created by special task groups in the past that have been since dissolved and that have not required continued development to justify the funding of a dedicated permanent group to maintain them.

Whatever the source of the functionality, rather than thinking of these components as "not having an owner", it is important to think of them as being owned by everyone through the lens of shared responsibility. "Shared responsibility" means that every group should be committed and responsible to contribute to their continued maintenance, improvement and innovation.

Contribution, in this context, may manifest in different ways:

• Triage by coordinating conversations with stakeholders from different functions and at different levels to find the right owner and/or set the right level of priority.
• Product feature scoping and UX design by fleshing out the details of implementation in requirements documents and/or mockups.
• Technical scoping and feasibility analysis for possible technical and architectural approaches to implementation
• Actual implementation and release activities

It does not mean, however, that a single group should necessarily be solely responsible for all of these activities. Multiple groups could end up collaborating in execution. This coordination however requires a careful triage of the shared responsibility issues in the issue tracker where a single DRI coordinates these activities.

For more information please review this section in the quality department handbook to learn more about a decentralized approach to triaging these types of issues.

Categories A-Z

Category	Group
5 Minute Production App (five_minute_production_app)	Five Minute Production App
API (api)	Import and Integrate
API Security (api_security)	Dynamic Analysis
Activation Experiment (experimentation_activation)	Activation
Adoption Experiment (experimentation_adoption)	Activation
Application Instrumentation (application_instrumentation)	Analytics Instrumentation
Application Performance (application_performance)	Application Performance
Attack Emulation (attack_emulation)	Dynamic Analysis
Audit Events (audit_events)	Compliance
Auto DevOps (auto_devops)	Environments
Backup/Restore of GitLab instances (backup_restore)	Geo
Billing & Payments (billing_and_payments)	Billing and Subscription Management
Build (build)	Distribution::Build
Build Artifacts (build_artifacts)	Pipeline Security
CI/CD Visibility (ci-cd_visibility)	Pipeline Execution
Capacity Planning (capacity_planning)	Scalability
Cell (cell)	Tenant Scale
Cloud Native Installation (cloud_native_installation)	Distribution::Deploy
Code Quality (code_quality)	Static Analysis
Code Review Workflow (code_review_workflow)	Code Review
Code Search (code_search)	Global Search
Code Suggestions (code_suggestions)	AI Assisted
Code Testing and Coverage (code_testing)	Pipeline Execution
Commerce Integrations (commerce_integrations)	Provision
Compliance Management (compliance_management)	Compliance
Consumables Cost Management (consumables_cost_management)	Utilization
Container Registry (container_registry)	Container Registry
Container Scanning (container_scanning)	Composition Analysis
Continuous Delivery (continuous_delivery)	Environments
Continuous Integration (CI) (continuous_integration)	Pipeline Execution
Conversion Experiment (experimentation_conversion)	Acquisition
CustomersDot Application (customersdot_application)	Fulfillment Platform
DAST (dynamic_application_security_testing)	Dynamic Analysis
DORA Metrics (dora_metrics)	Optimize
DataOps (dataops)	DataOps
Database (database)	Database
Delivery (delivery)	Delivery
Dependency Firewall (dependency_firewall)	Container Registry
Dependency Management (dependency_management)	Threat Insights
Dependency Proxy (dependency_proxy)	Container Registry
Deployment Management (deployment_management)	Environments
Design Management (design_management)	Product Planning
Design System (design_system)	Foundations
DevOps Reports (devops_reports)	Optimize
Disaster Recovery (disaster_recovery)	Geo
Editor Extensions (editor_extensions)	Code Review
Environment Management (environment_management)	Environments
Error Budgets (error_budgets)	Scalability
Error Tracking (error_tracking)	Observability
Expansion Experiment (experimentation_expansion)	Acquisition
Feature Flags (feature_flags)	Environments
Fulfillment Admin Tooling (fulfillment_admin_tooling)	Fulfillment Platform
Fulfillment Infrastructure (fulfillment_infrastructure)	Fulfillment Platform
Fuzz Testing (fuzz_testing)	Dynamic Analysis
Geo-replication (geo_replication)	Geo
GitLab Advisory Database (advisory_database)	Vulnerability Research
GitLab CLI (gitlab_cli)	Code Review
GitLab Dedicated (dedicated)	GitLab Dedicated
GitLab Documentation Site (gitlab_docs)	Foundations
GitLab Runner Core (runner)	Runner
GitLab Runner SaaS (runner_saas)	Runner SaaS
Gitaly (gitaly)	Gitaly::Git
Global Search (global_search)	Global Search
Groups & Projects (groups_and_projects)	Tenant Scale
Helm Chart Registry (helm_chart_registry)	Package Registry
IAST (interactive_application_security_testing)	Dynamic Analysis
Importers (importers)	Import and Integrate
Incident Management (incident_management)	Respond
Infrastructure Cost Data (infrastructure_cost_data)	Scalability
Infrastructure as Code (infrastructure_as_code)	Environments
Insider Threat (insider_threat)	Anti-Abuse
Instance Resiliency (instance_resiliency)	Anti-Abuse
Integrations (integrations)	Import and Integrate
Intelligent Code Security (intel_code_security)	AI Assisted
Internationalization (internationalization)	Import and Integrate
Logging (logging)	Observability
MLOps (mlops)	MLOps
Measurement and Locking (measurement_and_locking)	Acquisition
Merge Trains (merge_trains)	Pipeline Execution
Metrics (metrics)	Observability
Mobile DevOps (mobile_devops)	Mobile DevOps
Navigation & Settings (navigation)	Foundations
No-code Automation (no_code_automation)	No-code Automation
Omnibus Package (omnibus_package)	Distribution::Deploy
On-call Schedule Management (on_call_schedule_management)	Respond
Onboarding (onboarding)	Acquisition
Organization (organization)	Tenant Scale
Package Registry (package_registry)	Package Registry
Pages (pages)	Knowledge
Pipeline Composition (pipeline_composition)	Pipeline Authoring
Portfolio Management (portfolio_management)	Product Planning
Product Analytics (product_analytics)	Product Analytics
Purchase (purchase)	Purchase
Quality Management (quality_management)	Product Planning
Rate Limiting Framework (rate_limiting)	Application Performance
Redis (redis)	Application Performance
Release Evidence (release_evidence)	Compliance
Release Orchestration (release_orchestration)	Environments
Remote Development (remote_development)	IDE
Requirements Management (requirements_management)	Product Planning
Review Apps (review_apps)	Pipeline Execution
Runbooks (runbooks)	Respond
Runner Fleet (runner_fleet)	Runner
SAST (static_application_security_testing)	Static Analysis
SM Provisioning (sm_provisioning)	Provision
SaaS Provisioning (saas_provisioning)	Provision
Scalability (scalability)	Scalability
Seat Cost Management (seat_cost_management)	Purchase
Secret Detection (secret_detection)	Static Analysis
Secrets Management (secrets_management)	Pipeline Security
Security Benchmarking (security_benchmarking)	Vulnerability Research
Security Policy Management (security_policy_management)	Security Policies
Service Desk (service_desk)	Respond
Service Ping (service_ping)	Analytics Instrumentation
Software Bill of Materials (sbom)	Threat Insights
Software Composition Analysis (software_composition_analysis)	Composition Analysis
Source Code Management (source_code_management)	Source Code
Subscription Management (subscription_management)	Billing and Subscription Management
Switchboard (switchboard)	Switchboard
System Access (system_access)	Authentication and Authorization
Team Planning (team_planning)	Project Management
Tracing (tracing)	Observability
US Public Sector Services (pubsec_services)	US Public Sector Services
User Management (user_management)	Authentication and Authorization
User Profile (user_profile)	Tenant Scale
Value Stream Management (value_stream_management)	Optimize
Vulnerability Management (vulnerability_management)	Threat Insights
Web IDE (web_ide)	IDE
Webhooks (webhooks)	Import and Integrate
Wiki (wiki)	Knowledge
Workflow Automation (workflow_automation)	AI Assisted