Introduce license classifications
Problem
Licenses currently are only classified as “approved” or “blacklist” classifications; however, there are different states to account for such as: newly detected, non-classified, one-time approved (but blacklisted). These states are not explicitly classified and/or title to the user. Also, clarify the classifications, example "approved" may easily get confused with our approvals feature (as both are seen in the MR widget). Or "Blacklist" suggests a license will not be usable, but currently, we do not prohibit blacklisted licenses. (align language with expectations)
Solution
The following are terms that describe license classifications seen in the MR and license list UI:
- Uncategorized, admin has not selected classification
- Allowed, admin has classified license as acceptable
- Allow, used in the call-to-action seen in the MR (admin view) to classify license as Allowed
- Denied, project participant views this classification when admin classified license as not allowed
- Deny, used in the call-to-action seen in the MR (admin view) to classify license as unacceptable
Classifications for future iterations
- One-time approved or Out of policy, sub-classification of denied: in the case that a license has been denied, but was approved in an MR by the approval feature (designated license approver group)
- Flag for review, case where a user is unsure what to do: then has ability to flag a license for admin user to review
Edited by Kyle Mann