Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

license-classifications: Improve what gets assigned to the 'include-in-notice-file' category #81

Merged
merged 2 commits into from
Nov 25, 2022

Conversation

fviernau
Copy link
Member

See individual commits.

Context: #66.

@fviernau fviernau requested review from a team as code owners November 17, 2022 13:43
Do not include 'generic' and 'unknown' categories, as the corresponding
license IDs do not represent real licenses. Also do no include
Contributor License Agreements as these are irrelevant for using the
source code or the release artifact respectively.

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
The generation logic has been changed to stop including licenses of
certain categories into the notices. Re-generate the file by using [1]
to reflect that.

[1] ./gradlew generateLicenseClassifications

Signed-off-by: Frank Viernau <frank_viernau@epam.com>
@fviernau fviernau force-pushed the include-in-notices-adjustments branch from e9b71b8 to 37c3a3b Compare November 23, 2022 10:16
@fviernau fviernau enabled auto-merge (rebase) November 23, 2022 20:33
Comment on lines +61 to +62
private const val CATEGORY_GENERIC = "generic"
private const val CATEGORY_UNKNOWN = "unknown"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: The extraction of these constants is unrelated to the commit topic.

@fviernau fviernau merged commit e4ae8f0 into main Nov 25, 2022
@fviernau fviernau deleted the include-in-notices-adjustments branch November 25, 2022 14:53
@pombredanne
Copy link

@fviernau Could these categories be included in the ScanCode license DB directly to avoid data fragmentation? They are likely overlapping with some of the license flags .... I guess you are on top of it :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants