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

THIRD-PARTY-NOTICES.TXT needed for windowsdesktop repo? #2723

Closed
leecow opened this issue Mar 24, 2022 · 4 comments
Closed

THIRD-PARTY-NOTICES.TXT needed for windowsdesktop repo? #2723

leecow opened this issue Mar 24, 2022 · 4 comments
Assignees

Comments

@leecow
Copy link
Member

leecow commented Mar 24, 2022

If third-party components are used in a .NET repo, a THIRD-PARTY-NOTICES.TXT detailing any third-party source code included in final built artifacts, along with the controlling license information must be included and maintained at the root of the affected repo (dotnet/runtime example).

During product build, these files are used to create a unified TPN file and included in the final installer builds (example) and source-build offerings.

Some repos will not need this notice as no third-party code is included in the final build artifacts.

Tracking issue: dotnet/runtime#61466

@RussKie
Copy link
Member

RussKie commented Mar 28, 2022

@RussKie
Copy link
Member

RussKie commented Mar 28, 2022

@singhashish-wpf please detail WPF 3rd party dependencies, if any. Thank you

@singhashish-wpf
Copy link
Member

singhashish-wpf commented Mar 29, 2022

@RussKie
strawberry-perl is being used in global.json for wpf, apart from that there doesn't seem to be any 3rd party dependencies for wpf too. But that won't ship to windowsdesktop, can someone confirm if that is to be mentioned or we are good to go?

@leecow
Copy link
Member Author

leecow commented Mar 30, 2022

Thanks all. @singhashish-wpf, we only need to document dependencies included in shipping assets. Sounds like nothing is needed here.

@leecow leecow closed this as completed Mar 30, 2022
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

No branches or pull requests

3 participants