Creating Quick Reference Guide to Support Stable Counterparts
Request for comments
Need
I would like a quick reference guide for Support to find out who are the current Support Stable Counterparts (SSCs) for each Section/Stage/Group, other than reading through the sections, stages and groups; that page. I was interested in looking something like this up when I onboarded, I have also been asked by other onboarding SEs about who is assigned to which Group, so that they could reach out and understand what being an SSC was all about and how they could contribute further if they wished to do so.
The other aspect is to flag those areas that aren't very impactful to Support and denote this in a reference as to why there is no SSC for this area at this point in time.
Click to expand full Slack Thread
Ket 8 hours ago
Reason I'm asking is twofold:
- I want to know what managers are assigned to different Sections coz' I'm interested in finding out more/contributing at this level?
- I was after a quick ref layout for SEs interested in reaching out to existing SSCs to have a quick ref (I also had similar question from new starters wanting to know what SSCs do)
arty-chan 8 hours ago
A list of both could be generated from what's in the handbook but I've always just looked it up. As far as I'm aware, the only stage we have a manager is Fulfillment. I’m not sure we've seen a need for a manager in other areas so far but I could see it being helpful for Manage which is the one other stage where issues might have a high impact on how support works (edited)
Ket 8 hours ago
The above just had me thinking a quick table ref in our support handbook page might be helpful, and we can also list like why there isn't a need for SSCs in certain sections/stages for future peoples wondering which one they might have an interest in or looking to participate
Ket 8 hours ago Question here is: would creating the hb be needlessly duplicating?
arty-chan 8 hours ago
Just some haml coding
At the section/stage level, since it’s something that managers would take on, I’m not sure what the exact criteria would be. ICs can take any group that is available and even be a second SSC for busy groups
Approach
Data from:
- https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/sections.yml
- https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/stages.yml
- Support Readiness - GitLab 15.0
| Section | SSC _Support Manager_ |
Stage | SSC _Support Engineer_ |
Group | SSC _Support Engineer_ |
|---|---|---|---|---|---|
| Analytics | TBD |
Analytics | N/A |
Product Intelligence | @collen |
| DevOps | TBD |
Manage | @cynthia |
Authentication & Authorization Import |
@cynthia |
| DevOps | TBD |
Manage | @cynthia |
Workspace |
@cynthia @joseph
|
| DevOps | TBD |
Manage | @cynthia |
Compliance Optimize |
TBD |
| DevOps | TBD |
Plan | @bprescott\_ |
Project Management | @bprescott\_ |
| DevOps | TBD |
Plan | @bprescott\_ |
Product Planning Certify |
TBD |
| DevOps | TBD |
Create | @b_freitas |
Source Code Code Review |
TBD |
| DevOps | TBD |
Create | @b_freitas |
Editor | @brad |
| DevOps | TBD |
Create | @b_freitas |
Gitaly | @gerardo |
| DevOps | TBD |
Ecosystems | TBD |
Integrations Foundations |
TBD |
| Ops | TBD |
Verify | TBD |
Pipeline Execution Pipeline Authoring |
@calebcooper |
| Ops | TBD |
Verify | TBD |
Runner | @atanayno |
| Ops | TBD |
Verify | TBD |
Pipeline Insights | TBD |
| Ops | TBD |
Package | @nelbacha |
Package | @nelbacha |
| Ops | TBD |
Release | @jemcgrew |
Release | @jemcgrew |
| Ops | TBD |
Configure | @lwbrown |
Configure | @lwbrown |
| Ops | TBD |
Monitor | TBD |
Respond Observability |
@cody |
| Growth | N/A |
Growth | N/A |
Acquisition Activation |
N/A |
| Fulfillment | @jlyttle |
Fulfillment | N/A |
Purchase | @rverschoor |
| Fulfillment | @jlyttle |
Fulfillment | N/A |
Provision | @kevenhughes |
| Fulfillment | @jlyttle |
Fulfillment | N/A |
Utilization | @shemgyll |
| Fulfillment | @jlyttle |
Fulfillment | N/A |
Fulfillment Platform | TBD |
| Enablement | @jcolyer |
Systems | N/A |
Distribution:Build Distribution:Deploy |
@dstanley @admiralboom
|
| Enablement | @jcolyer |
Systems | N/A |
Geo | @bocarbonell |
| Enablement | @jcolyer |
Data Stores | N/A |
Memory | @mhuseinbasic |
| Enablement | @jcolyer |
Data Stores | N/A |
Global Search | @vstoianovici |
| Enablement | @jcolyer |
Data Stores | N/A |
Database Pods |
@bprescott\_ |
| SaaS Platforms | TBD |
SaaS Platforms | TBD |
Delivery Scalability GitLab Dedicated |
TBD |
| ModelOps | TBD |
ModelOps | N/A |
Applied Machine Learning MLOps DataOps |
N/A |
| Sec | TBD |
Secure | TBD |
Static Analysis Threat Insights Vulnerability Research |
@greg |
| Sec | TBD |
Secure | TBD |
Dynamic Analysis | @kategrechishkina |
| Sec | TBD |
Secure | TBD |
Composition Analysis | @katrinleinweber |
| Sec | TBD |
Anti-Abuse | TBD |
Anti-Abuse | N/A |
| Sec | TBD |
Protect | TBD |
Container Security | @joseph |
Benefit
Increased efficiency when referring to our SSC participants.
Competition / Alternatives
- Do nothing, continue referencing https://about.gitlab.com/handbook/product/categories/#devops-stages
- This page falls out of date if not feeding from https://about.gitlab.com/handbook/product/categories/#devops-stages