Rename License Management to License Compliance
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).
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:
"OSS License Compliance" (https://www.blackducksoftware.com/solutions/open-source-license-compliance)
"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:
CA Veracode (http://www.veracode.com/software-composition-analysis-0)
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Results of GitLab application Check