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

Switch to MIT license #9

Open
omus opened this issue Jun 3, 2020 · 11 comments · Fixed by #33
Open

Switch to MIT license #9

omus opened this issue Jun 3, 2020 · 11 comments · Fixed by #33

Comments

@omus
Copy link
Contributor

omus commented Jun 3, 2020

I noticed this package uses the GPL-3 license. Is there any particular reason for this? Using GPL-3 may limit this package's adoption. Would you be opposed to switching the package to the MIT license?

@cjdoris
Copy link
Owner

cjdoris commented Jun 6, 2020

I'm not necessarily opposed. Who do you think would not use it under GPL-3 but would use it under MIT?

@NightMachinery
Copy link

@omus commented on Jun 3, 2020, 9:38 PM GMT+4:30:

I noticed this package uses the GPL-3 license. Is there any particular reason for this? Using GPL-3 may limit this package's adoption. Would you be opposed to switching the package to the MIT license?

Freedom doesn't come for free. GPL gives free software developers a competitive edge.

@omus
Copy link
Contributor Author

omus commented Aug 25, 2020

There's a good Discourse post on mixing MIT and GPL packages: https://discourse.julialang.org/t/gpl-and-virality/7715. In my use case GPL isn't an issue I just wanted to ensure the choice of the GPL license was intentional.

@cjdoris
Copy link
Owner

cjdoris commented Aug 27, 2020

Thanks, that's a good article. Indeed the choice was intentional.

@cjdoris cjdoris closed this as completed Aug 27, 2020
@iamed2
Copy link

iamed2 commented Nov 18, 2020

@cjdoris
Copy link
Owner

cjdoris commented Nov 18, 2020

@omus I don't use this package much any more, would you be interested in maintaining it? I'd be happy to re-licence it as MIT.

@cjdoris cjdoris reopened this Nov 18, 2020
@iamed2
Copy link

iamed2 commented Nov 18, 2020

He's away on leave for a while but I can commit on behalf of Invenia, which includes @omus and @fchorney.

@Byrth
Copy link

Byrth commented Jan 21, 2021

I detect a communication gap and shall insert myself to generate alert e-mails.

@cjdoris are you amenable to the proposal?

@cjdoris
Copy link
Owner

cjdoris commented Jan 21, 2021

I'm happy to relicense this as MIT and add @omus and @fchorney as collaborators.

@mbravenboer
Copy link

mbravenboer commented Jul 15, 2021

How can we make this happen? It's a bit of a problem in the Julia ecosystem (via libPQ and Intervals)

In https://github.com/cjdoris/Infinity.jl/graphs/contributors I see that all contributors are in the discussion above, so presumably there are no other contributors who need to agree with the license change. Do any of the original contributors to this discussion make the change? If you need help with anything then the RelationalAI team can help too.

@cjdoris
Copy link
Owner

cjdoris commented Jul 24, 2021

I have merged the PR to relicense this as MIT, thanks.

Note (see #25) that there is a new package Infinities.jl which combines ideas from this package and some other places. The intention is that everything is this package ends up there and we deprecate this one. It has types to represent unsigned/signed/complex infinity. The main thing from this package not there is InfExtendedReal etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants