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

Please provide MIT-licensed NuGet packages for MIT-licensed source code. #18771

Closed
piedar opened this issue Sep 29, 2016 · 17 comments
Closed

Please provide MIT-licensed NuGet packages for MIT-licensed source code. #18771

piedar opened this issue Sep 29, 2016 · 17 comments
Assignees
Milestone

Comments

@piedar
Copy link
Contributor

piedar commented Sep 29, 2016

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.

@karelz
Copy link
Member

karelz commented Sep 30, 2016

@terrajobst @weshaggard @ericstj any thoughts here?

@piedar
Copy link
Contributor Author

piedar commented Oct 12, 2016

@danmoseley
Copy link
Member

@terrajobst ?

@DDoSolitary
Copy link

DDoSolitary commented Feb 21, 2017

Hello!
Does the milestone mean that there will be MIT licensed NuGet packages for v2.0?
And is there any convenient workaround for this?

@karelz
Copy link
Member

karelz commented Feb 22, 2017

@DDoSolitary it means we will strongly consider the issue for 2.0.
@terrajobst @richlander can you please chime in? It's 5 months old issue without any official response :(

@omajid
Copy link
Member

omajid commented Feb 22, 2017

If it helps, there was some movement on getting cli to be licensed under MIT: dotnet/cli#5112

@richlander
Copy link
Member

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.

@tarekgh
Copy link
Member

tarekgh commented Apr 12, 2017

@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.

@karelz
Copy link
Member

karelz commented Apr 13, 2017

I think we should address this in 2.0 time-frame. This is highly voted issue, opened for quite some time.

@tarekgh
Copy link
Member

tarekgh commented Apr 13, 2017

@richlander please advise when you'll have this issue done? Thanks.

@richlander
Copy link
Member

@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.

@richlander
Copy link
Member

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?

@tarekgh
Copy link
Member

tarekgh commented May 5, 2017

@richlander is this done yet? we are trying to hit ZBB in a few days :-)

@tarekgh
Copy link
Member

tarekgh commented May 10, 2017

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.

@jkotas
Copy link
Member

jkotas commented May 10, 2017

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.

@tarekgh
Copy link
Member

tarekgh commented May 10, 2017

@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.
Yes I follow up on that file too with @richlander and @terrajobst to know what we need to do here.

@tarekgh tarekgh closed this as completed May 15, 2017
@omajid
Copy link
Member

omajid commented May 15, 2017

🎉 👏

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 2.0.0 milestone Jan 31, 2020
@msftbot msftbot bot locked as resolved and limited conversation to collaborators Dec 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants