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
Include license in package #3621
Conversation
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## master #3621 +/- ##
==========================================
+ Coverage 83.91% 83.93% +0.01%
==========================================
Files 381 381
Lines 16876 16888 +12
Branches 2715 2717 +2
==========================================
+ Hits 14162 14175 +13
Misses 2068 2068
+ Partials 646 645 -1
|
A long time ago we switched from PackageLicenseFile to PackageLicenseExpression. Also it was a recommended way by MS, compiler reported a warning. Many projects did so. So why to bring PackageLicenseFile back again? As I understand VS (with some plugin installed?) shows package contents. OK. It is just an auxilary functionality of IDE. Perhaps later VS will learn to show license using PackageLicenseExpression. But now it cannot and it should not follow from this that the license file must be added to the package. |
I'm fine removing PackageLicenseFile. Nevertheless, I think the license.md file should be bundled within the nuget. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, generally I'm not against it as well but have you seen any such usages besides MS packages? Existence of those 3 files may be explained by MS corporate politics and does not apply to us as well as majority of other open source projects.
Well the license agreement explicitly says:
“Should we not follow our own rules?” was my thinking |
Note that the license “expression” has no legal bearing on the copyright status (in my mind), as we (the authors) specified an explicit license / copyright notice for this package. |
Legal stuff is not in my strong skills. |
Hopefully then the license should appear in Visual Studio, similar to MS packages:
Right now it looks like this: