dotnet / dotnet/source-build

Are the Third Party Notices in source-build-reference-packages actually correct?

Open
#2,147 4 comments 1 reaction 0 assignees View on GitHub
area-prebuilts
Dominant language
No language data
Stars
287
Forks
145
Avg merge
1d 22h
Merged PRs (30d)
10

Description

source-build-reference-packages have a bunch of `THIRD-PARTY-NOTICES.TXT` files. For example:

- https://github.com/dotnet/source-build-reference-packages/blob/main/src/targetPacks/ILsrc/microsoft.netcore.app/2.1.0/THIRD-PARTY-NOTICES.TXT
- https://github.com/dotnet/source-build-reference-packages/blob/main/src/textOnlyPackages/src/microsoft.netcore.platforms/2.1.0/THIRD-PARTY-NOTICES.TXT

Are these licenses applicable to the "code" in source-build-reference-packages? The reference packages contain only API references for .NET libraries, not implementations. The licenses are mostly for the underlying implementations that the .NET API uses (eg, libunwind, zlib, unicode data, brotli, ...). Those implementations aren't present in source-build-reference-packages, probably the license doesn't apply to this code?

Should we remove the third party notices files to make it clearer that the code in this repo is not licensed under those third party licenses?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.