Skip to content

Conversation

NikolaMilosavljevic
Copy link
Member

Update third-party-notices file for .NET 6.

Infra used to generate this file is in another PR: #60091

Here's the output of TPN regeneration process, specifying which repo contributes each new notice:

  New section to import: 'License notice for Angular v8.0  --------------------------------------------  The MIT License (MIT)' of https://github.com/raw/dotnet/aspnetcore/master/THIRD-PARTY-NOTICES.txt line 167
  New section to import: 'License notice for JavaScript queues' of https://github.com/raw/dotnet/runtime/master/THIRD-PARTY-NOTICES.TXT line 974
  New section to import: 'License notice for MSBuild Locator' of https://github.com/raw/dotnet/roslyn-analyzers/master/THIRD-PARTY-NOTICES.txt line 11
  New section to import: 'License notice for Newtonsoft.Json' of https://github.com/raw/dotnet/aspnetcore/master/THIRD-PARTY-NOTICES.txt line 322
  New section to import: 'License notice for NuGet.Client' of https://github.com/raw/dotnet/templating/master/THIRD-PARTY-NOTICES line 10
  New section to import: 'License notice for Roslyn Clr Heap Allocation Analyzer' of https://github.com/raw/dotnet/roslyn-analyzers/master/THIRD-PARTY-NOTICES.txt line 28
  New section to import: 'License notice for StyleCop Analyzers' of https://github.com/raw/dotnet/roslyn-analyzers/master/THIRD-PARTY-NOTICES.txt line 42
  New section to import: 'The MIT License (MIT)' of https://github.com/raw/dotnet/aspnetcore/master/THIRD-PARTY-NOTICES.txt line 194
  Importing 9 sections...

@joeloff
Copy link
Member

joeloff commented Oct 6, 2021

Question... Visual Studio has a massive TPN. In the past it's something that's been updated whenever an external component like .NET is added to VS. jQuery and Bootstrap comes to mind for ASP.NET. Should we include the changes to our TPN in the VS TPN as well?

@NikolaMilosavljevic
Copy link
Member Author

Updated the TPN to incorporate formatting/sorting changes due to updates in infra: a945962

Output of the tool:

  New section to import: 'License for fastmod (https://github.com/lemire/fastmod) and ibm-fpgen (https://github.com/nigeltao/parse-number-fxx-test-data)' of https://github.com/raw/dotnet/runtime/main/THIRD-PARTY-NOTICES.TXT line 682
  New section to import: 'License notice for Angular v8.0  --------------------------------------------  The MIT License (MIT)' of https://github.com/raw/dotnet/aspnetcore/main/THIRD-PARTY-NOTICES.txt line 167
  New section to import: 'License notice for JavaScript queues' of https://github.com/raw/dotnet/runtime/main/THIRD-PARTY-NOTICES.TXT line 974
  New section to import: 'License notice for MSBuild Locator' of https://github.com/raw/dotnet/roslyn-analyzers/main/THIRD-PARTY-NOTICES.txt line 11
  New section to import: 'License notice for Newtonsoft.Json' of https://github.com/raw/dotnet/aspnetcore/main/THIRD-PARTY-NOTICES.txt line 322
  New section to import: 'License notice for NuGet.Client' of https://github.com/raw/dotnet/templating/main/THIRD-PARTY-NOTICES line 10
  New section to import: 'License notice for Roslyn Clr Heap Allocation Analyzer' of https://github.com/raw/dotnet/roslyn-analyzers/main/THIRD-PARTY-NOTICES.txt line 28
  New section to import: 'License notice for StyleCop Analyzers' of https://github.com/raw/dotnet/roslyn-analyzers/main/THIRD-PARTY-NOTICES.txt line 42
  New section to import: 'The MIT License (MIT)' of https://github.com/raw/dotnet/aspnetcore/main/THIRD-PARTY-NOTICES.txt line 194
  Importing 9 sections...


------------------------------------------------

The MIT License (MIT)
Copy link
Contributor

Choose a reason for hiding this comment

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

❔ Which one is this associated with?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is coming from dotnet/aspnetcore/main/THIRD-PARTY-NOTICES.txt line 194

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixing.


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

License notice for StyleCop Analyzers
Copy link
Contributor

Choose a reason for hiding this comment

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

💭 While I have no objection to seeing this here, does it apply for cases where the referenced package is only a development dependency?

Copy link
Member Author

Choose a reason for hiding this comment

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

💭 While I have no objection to seeing this here, does it apply for cases where the referenced package is only a development dependency?

Good question - I'm not sure, but it would be easy to remove this one.

Copy link
Member

Choose a reason for hiding this comment

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

@richlander do we need to include dev-time dependencies in our shipping TPN? Presumably not.

Copy link
Member

@hoyosjs hoyosjs left a comment

Choose a reason for hiding this comment

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

LGTM other than the comment from Sam, where it's not clear what the last license is for.

@danmoseley
Copy link
Member

@NikolaMilosavljevic is this mergeable?

@NikolaMilosavljevic
Copy link
Member Author

@NikolaMilosavljevic is this mergeable?

Quite a few reviews are missing, but otherwise it's mergeable.

@Anipik
Copy link
Contributor

Anipik commented Oct 13, 2021

@NikolaMilosavljevic can you tag the reviewers again ? (which are required for the final merge)

@NikolaMilosavljevic
Copy link
Member Author

@mkArtakMSFT , @dougbu - we are missing aspnetcore sign-off - can you review new entries coming from dotnet/aspnetcore?

@NikolaMilosavljevic
Copy link
Member Author

@NikolaMilosavljevic can you tag the reviewers again ? (which are required for the final merge)

aspnetcore is the only one missing - I've added and tagged more reviewers for that repo.

Copy link
Contributor

@dougbu dougbu left a comment

Choose a reason for hiding this comment

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

I don't know exactly how or why some of these items are used and probably shouldn't be the approver. @mkArtakMSFT who else needs to look at this❔


------------------------------------------------

The MIT License (MIT)
Copy link
Contributor

Choose a reason for hiding this comment

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

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

License notice for musl
Copy link
Contributor

Choose a reason for hiding this comment

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

This may also be a dev / build dependency. We build (an installer?) for Linux MUSL on an Alpine image but I'm not sure exactly how that uses MUSL libraries.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed the empty line and moved under corefx.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

@NikolaMilosavljevic was this a response to https://github.com/dotnet/runtime/pull/60092#discussion_r728315386❔

Yes, that is correct - fixing the issue above. There was no way to add a comment right underneath that issue.

Copy link
Member

Choose a reason for hiding this comment

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

musl gets compiled into every WebAssembly app via emscripten. We should probably mention emscripten too /cc @lewing


License notice for Angular v8.0
--------------------------------------------
--------------------------------
Copy link
Contributor

Choose a reason for hiding this comment

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

Add a blank line after this for consistency

Copy link
Member Author

Choose a reason for hiding this comment

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

This is coming from dotnet/aspnetcore - we could fix it here, but it should also be fixed in source location to not regress in the future.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed.

limitations under the License.

License notice for Angular v8.0
--------------------------------------------
Copy link
Contributor

Choose a reason for hiding this comment

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

Shorten and add a blank line after this

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed - also removed duplicate 'Angular 8.0' notice.

OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

License notice for corefx
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a dangling header

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed - removed.

@dougbu
Copy link
Contributor

dougbu commented Oct 13, 2021

Side question: Why do you need ASP.NET sign-off on a Runtime PR❔ Is this TPN.txt file going to be used for every published asset from any repo❔

@NikolaMilosavljevic
Copy link
Member Author

Side question: Why do you need ASP.NET sign-off on a Runtime PR❔ Is this TPN.txt file going to be used for every published asset from any repo❔

Yes, this is a merged TPN, that is installed under dotnet folder - it covers everything we install there, including ASP.NET.

@NikolaMilosavljevic
Copy link
Member Author

@dougbu changes requested in your review were implemented and pushed on Friday. Can you approve for aspnetcore, or do we need someone else to do it? This is the last approval before we merge, and we'd prefer to not wait any longer.

@Anipik - fyi

@danmoseley danmoseley changed the title Update THIRD-PARTY-NOTICES.TXT [release/6.0] Update THIRD-PARTY-NOTICES.TXT Oct 18, 2021
@mkArtakMSFT
Copy link

mkArtakMSFT commented Oct 18, 2021

Side question: Why do you need ASP.NET sign-off on a Runtime PR❔ Is this TPN.txt file going to be used for every published asset from any repo❔

Yes, this is a merged TPN, that is installed under dotnet folder - it covers everything we install there, including ASP.NET.

@NikolaMilosavljevic, given that's the case, what about all the other dependencies that ASP.NET Core has? Shouldn't these also be listed here?

@NikolaMilosavljevic
Copy link
Member Author

Side question: Why do you need ASP.NET sign-off on a Runtime PR❔ Is this TPN.txt file going to be used for every published asset from any repo❔

Yes, this is a merged TPN, that is installed under dotnet folder - it covers everything we install there, including ASP.NET.

@NikolaMilosavljevic, given that's the case, what about all the other dependencies that ASP.NET Core has? Shouldn't these also be listed here?

All ASP.NET dependencies are here, in the shared file. We avoid duplication and only include a single instance of the same dependency. It's likely that many of those dependencies are also present in other repos and included in a different section of this unified file.

Is there a specific dependency of ASP.NET that should be included but it is not present?

Copy link
Member

@Pilchie Pilchie left a comment

Choose a reason for hiding this comment

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

This looks fine for aspnetcore. @dougbu is OOF today, so don't feel you have to wait for his sign-off.

@NikolaMilosavljevic
Copy link
Member Author

Unless I hear objections in the the 15 minutes, I'm going to merge this PR. @Pilchie , @mkArtakMSFT your questions have replies, can you help resolve those concerns (conversations)?

@NikolaMilosavljevic NikolaMilosavljevic merged commit 5a23dc3 into dotnet:release/6.0 Oct 18, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Nov 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.