Group License Compliance
Problem to solve
As a compliance regulator, I want all repositories to enforce policy and configuration decisions made by the enterprise.
These same rules set in the Group should apply to each project in the related group.
Instead of repeating the configuration everywhere, we can give the ability to define approved/blacklisted licenses at group level.
Since we have group and project policies, we should figure out which is the precedence and if people can override licenses.
Implement a group setting to define License Compliance policies that will apply to all the projects in that group. The interface can be consistent to what we already have at project level in the settings page.
What does success look like, and how can we measure that?
How many License Compliance policies are defined at group level.