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
Please provide MIT-licensed NuGet packages for MIT-licensed source code. #18771
Comments
@terrajobst @weshaggard @ericstj any thoughts here? |
Some affected packages: |
Hello! |
@DDoSolitary it means we will strongly consider the issue for 2.0. |
If it helps, there was some movement on getting cli to be licensed under MIT: dotnet/cli#5112 |
We are going to switch most packages to MIT. This should happen in the first half of 2017. We wanted to do it earlier, but have had a lot of competing priorities. Major point is that we've heard the feedback, get it and are going to change. |
@richlander do you think you can have this done before v2.0 release? or this one not tied to the release? I am asking because this is marked as v2.0 issue. |
I think we should address this in 2.0 time-frame. This is highly voted issue, opened for quite some time. |
@richlander please advise when you'll have this issue done? Thanks. |
@terrajobst can we start updating the license link for our NuGet packages. If you give me the password, I'll do it ;) We'll update the license in the packages for .NET Core 2.0. |
Update: Turns out that the only way to update the license is to update the nupkg. So, we've started updating the packages. I thought you could update the license through the NuGet Gallery config UI. You cannot. That's why I created dotnet/buildtools#1447. 1447 == 1337 ... right? |
@richlander is this done yet? we are trying to hit ZBB in a few days :-) |
I moved the issue to 2.1 as we have addressed the repos shipping for v2.0. we just need to apply the change to corert too which is 2.1. |
The changes above fixed the URL on the nuget frontpage. The nuget packages still include dotnet_library_license.txt file with the MS .NET LIBRARY EULA license. |
@jkotas I was changing the license url as originally suggested and was what @richlander trying to fix in the PR dotnet/buildtools#1447. but I agree we need to fix the dotnet_library_license.txt issue too. |
🎉 👏 |
There are a lot of useful MIT-licensed libraries in this repository. However, many of them are published on NuGet under a much more restrictive license, which forbids modifications, interferes with the GPL, and allows Microsoft to "collect information about you and your use of the software".
These terms are toxic to both open-source and commercial use, and they will force us to package and maintain our own forks of these libraries for the benefit of the much more friendly MIT terms. Please consider relicensing the official NuGet packages to match the source code.
The text was updated successfully, but these errors were encountered: