Is default package license URL correct?
See original GitHub issueLooks like the license points to http://go.microsoft.com/fwlink/?LinkId=529443.
This is the old library license.
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT .NET LIBRARY
Shouldn’t we be defaulting to MIT? See https://github.com/dotnet/corefx/issues/12190
Issue Analytics
- State:
- Created 5 years ago
- Comments:27 (27 by maintainers)
Top Results From Across the Web
nuspec File Reference for NuGet
licenseUrl is deprecated. Use license instead. A URL for the package's license, often shown in UIs like nuget.org. When uploading a package to ......
Read more >.NET Core/Standard .csproj file, embedding license ...
Is there a way to embed the license file so that PackageLicenseFile works correctly, without adding the license file to projects using the ......
Read more >Find and evaluate NuGet packages for your project
Find and evaluate publicly available NuGet packages for your project by using advanced nuget.org search filters and syntax.
Read more >How to include licenses for packages downloaded with ...
I have a software that uses some MIT and Apache licenses. The source code is not open source and all the third-party software...
Read more >package.json
If a url is provided, it will be used by the npm bugs command. license. You should specify a license for your package...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Re: defaults - it’s still on my plate to get official guidance out there that we can agree on. But what seems to be emerging is that a) Arcade should provide “defaults” which teams are strongly recommended to use because that’s where the most value and support is found, and b) “defaults” can (almost) always be overwritten - with the team knowing that they are thus trading short term cost for (perhaps) more long term support cost.
Regardless - more soon on this…
@ericstj See https://github.com/dotnet/corefx/issues/35159 my tentative conclusion from messing with it is it’s the PATENTS.TXT, which it’s mis-recognizing (with low confidence) as containing the MS-PL, and Github puts all this together and decides it’s not clearly MIT.