Skip to content

Rename License Management to License Compliance

Summary

This might very well be too late to bring up, but in writing the launch material for 11.0 we've come across the problem that the term "License Management" means something else in IT - distribution and tracking of software license usage to say within contract (https://www.gartner.com/it-glossary/slm-software-license-management, https://www.gartner.com/webinar/3710218?srcId=1-8622966176)

Steps to reproduce

It appears throughout the product (11.0).

Example Project

N/A

What is the current bug behavior?

The term "License Management" means something else in the IT space. If we don't change this then this new feature will get lost, we'll attract people expecting something else, and won't attract the people looking for what it actually provides.

What is the expected correct behavior?

Change all references of "license management" to a name more associated with the functionality

It would be better to call this something more in alignment with the competition in this space. Here is what some competitors in this space call it:

"Software Composition Analysis" seems to be the most common term (although it includes security vulnerability awareness too). Here are more vendors and an analyst calling it this:

Relevant logs and/or screenshots

NA

Output of checks

NA

Results of GitLab environment info

NA

Results of GitLab application Check

NA

Possible fixes

NA

/cc @JobV @markpundsack @johnjeremiah

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖