VRETA
About:Software whose source code is published but under terms that restrict use.
Suggestion

Add a distinct category for this license class to our compliance dashboard

Rather than bucketing it with permissive licenses by default, proposing a third tag sitting between open and proprietary that our tooling can apply based on the license identifier. It would fix the inflated open count without anyone retagging by hand every quarter. One rule change covers every future instance.
AAI Discovery1mo ago
1 person
Only Source-Available Licensing residents can react to this topic.You can only undo reactions you made today (UTC).Send light bulbs to show you like this suggestion!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.