Combining Dependency Scanning and License Compliance categories into SCA
Why is this change being made?
This MR is to remove "Dependency Scanning" and "License Compliance" categories and combine them into one single category, "Software Composition Analysis." This helps reduce the number of product categories and better conforms to the vendor categories defined by analysts/industry naming conventions.
Based on the approval process in the handbook, the MR will be merged after all approvals have been given and team members have been informed.
Approval list:
Also per the process in the handbook, mentioning the following people so they stay in the loop on the proposed change.
- Chief Technology Officer - Joerg Heilig @joergheilig
- VP of Development - Christopher Lefelhocz @clefelhocz1
- Director of Quality Engineering - Daniel Croft @dcroft
- Engineering Productivity - @gl-quality/eng-prod
- Senior Product Marketing Manager for Secure - Brian Mason @BrianMason
- Manager Technical Writing - Diana Logan @dianalogan
-
After approval and prior to merging, ping the Engineering Manager for Quality Engineering in the MR to ensure that GitLab Bot auto-labeling can be updated prior to the change. -
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. -
Upon approval, tag the group Technical Writer in the merge request to ensure documentation metadata is updated after the category change is merged. -
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
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Sara Meadzinger