Infrastructure Product Management

1. You are here:
2. Handbook
3. Engineering
4. Infrastructure
5. Infrastructure Product Management

Maintained by:

On this page

• Responsibilities
• Engagement Model
  • Inbound Requests
    • How to submit customer requests related to GitLab.com
  • Outbound Requests
  • General Questions
• Workflow
• Prioritization Framework
• Issue Board

Responsibilities

The responsibilities of the Infrastructure Product Manager are documented in the job-families page.

Engagement Model

Inbound Requests

The Infra PM can help triage and prirotize inbound requests to Infrastructure from internal teams and GitLab.com customers.

Types of requests:

1. Dogfooding requests
   • e.g. Runbooks
2. Security and Compliance Requests
3. GitLab.com customer requests in remit of the Infrastructure department:
   • GitLab.com customers, especially enterprises, may often have requests related to operational capabilities or non-functional requirements of GitLab.com (e.g. availability, security, and performance of the service). Requests related to functionality within the application itself should be directed to the appropriate stage team using the standard feature request template.

Examples of requests related to operational capabilities of GitLab.com include:

1. Disaster Recovery SLA
2. Publishing an allocated range of ingress IPs
3. Data locality (e.g. a GitLab.eu instance)
4. Certifications (e.g. FedRAMP)

The Infra PM can help prioritize these requests since they will likely require engineering investment from the Infrastructure department.

How to submit customer requests related to GitLab.com

To submit customer requests related to the operational capabilities of GitLab.com, use the GitLab.com feature request template so that we can gather the necessary opportunity size data to help prioritize this request

Outbound Requests

The Infra PM can also help drive outbound requests on behalf of Infrastructure to internal teams and GitLab.com customers.

Types of requests:

1. Changes needed within the GitLab application
   • e.g. Kubernetes Migration Blockers
2. Outreach to GitLab.com customers
   • e.g. Document additional egress IP ranges for SaaS
3. Driving cost efficiences across stages
   • e.g. Registry Cost (internal only)

General Questions

For general inquiries, use the Infrastructure PM Slack Channel.

Workflow

To request assistance from the Infrastructure Product Manager, add the ~"infrapm" label to an issue. Next, the Infra PM will consider the issue by moving it to the ~"workflow::problem validation" phase for validation, scoping, and prioritization. After completing these steps, if the Infra PM determines the effort is worth pursuing, they will then follow the established Infrastructure team workflows by adding the appropriate team label and moving the issue to the ~"workflow-infra::Triage" phase for engineering review.

Prioritization Framework

To prioritize initiatives, the Infra PM uses the framework documented in the Product handbook.

Issue Board

Infrastructure Product Manager Tasks are tracked on the Infra PM Issue Board