Skip to content

Proposed reduction in maturity for license comp

Nicole Schwartz requested to merge schwartz-secure-sca-license-compliance-maturity-rollback into master

Why is this change being made?

due to the lack of new features or significant feature enhancements for the past 2 years for license compliance, and in response to the reasonable frustration by account and sales teams at the lack of features I am proposing a feature maturity rollback for license compliance. At the time it may have been "good enough" but i believe it no longer is good enough to be "viable" and should be "minimal".

Creating this MR to decide if a rollback in maturity is appropriate for this category based on it's current lack of features and internal (and external) useability.

When we pick work back up on this (the following progress to complete for Dependency Scanning and finishing off Automatic remediation bot and putting that on hold until a SEG can pick it up) - which i expect to be either November or December we'll be looking at evaluating a complete replacement of the OSS tool License Finder or writing our own tooling (into gemnasium).

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • 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 Nicole Schwartz

Merge request reports