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

MIT license #47

Closed
dtarakanov1 opened this issue Jan 29, 2020 · 17 comments
Closed

MIT license #47

dtarakanov1 opened this issue Jan 29, 2020 · 17 comments
Assignees
Labels
available on master Fix is done on master branch, issue closed on next release enhancement New feature or request
Milestone

Comments

@dtarakanov1
Copy link

dtarakanov1 commented Jan 29, 2020

Is your feature request related to a problem? Please describe.
The BSD-3-Clause license type complicates the filesystem library usage.

Describe the solution you'd like
The MIT license is more permissive, so it would be nice to apply it instead.

Describe alternatives you've considered
Any other permissive licenses are welcome.

Additional context
Our team is going to open source some library (under MIT license) and having a dependency on the BSD license is not okay then. So if the license type is not changed, we'll have to find another filesystem implementation.

@gulrak
Copy link
Owner

gulrak commented Jan 29, 2020

I'm sorry to hear, that the chosen license is not the one fitting your needs. I selected BSD-3 because of the no-endorsement-clause and I can not see how the MIT license will give me the same effect.

Besides that, there is the legal need for all contributors to agree to a license change, and that might be difficult to obtain.

@dtarakanov1
Copy link
Author

dtarakanov1 commented Feb 5, 2020

Forgot to mention.
The rule is very simple: a BSD-3-Clause licensed library cannot be used in MIT licensed products (BSD-2-Clause can).
MIT is quite commonly used, so I suspect some of the ghc.filesystem library users just violate the license.
Fortunately there is boost.filesystem as well, though it has some downsides.

@gulrak
Copy link
Owner

gulrak commented Feb 5, 2020

It's not that I'm totally against a re-licensing to MIT, but there still is the need of every other contributor to agree to the change to MIT license, so we can give it a try:

To all contributors:

If you agree with to a re-licenseing from BSD-3-Clause to the MIT license, please reply with a 👍

@asmaloney
Copy link
Contributor

👍

@cybik
Copy link
Contributor

cybik commented Feb 5, 2020

I hereby 👍 this.

@jwnimmer-tri
Copy link
Contributor

Yes, I agree 👍 to MIT relicensing.

@karjonas
Copy link
Contributor

karjonas commented Feb 5, 2020

I agree as well. 👍

@Zer0xFF
Copy link
Contributor

Zer0xFF commented Feb 5, 2020

You have my blessings 👍

@kleuter
Copy link
Contributor

kleuter commented Feb 5, 2020

👍

2 similar comments
@JonasVautherin
Copy link
Contributor

👍

@actboy168
Copy link
Contributor

👍

@fenglc
Copy link
Contributor

fenglc commented Feb 6, 2020

I agree as well.

@jeanguyomarch
Copy link
Contributor

Yes, I agree 👍 to MIT relicensing.

@tohammer
Copy link
Contributor

tohammer commented Feb 6, 2020

I agree to MIT relicensing 👍

@gulrak gulrak self-assigned this Feb 7, 2020
@gulrak gulrak added enhancement New feature or request and removed question Further information is requested labels Feb 7, 2020
@gulrak gulrak added this to the 1.3.0 milestone Feb 7, 2020
@gulrak
Copy link
Owner

gulrak commented Feb 7, 2020

Great, all agreed! - Thank you so much for participating!

So I plan a release of v1.3.0 under MIT license around the upcomming weekend.
Thanks for bringing this up @dtarakanov1!

@asmaloney
Copy link
Contributor

@gulrak - thank you for all your work on this library!

@gulrak gulrak added the available on master Fix is done on master branch, issue closed on next release label Feb 8, 2020
@gulrak
Copy link
Owner

gulrak commented Feb 8, 2020

New release v1.3.0 just published under MIT license!

@gulrak gulrak closed this as completed Feb 8, 2020
@gulrak gulrak unpinned this issue Feb 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
available on master Fix is done on master branch, issue closed on next release enhancement New feature or request
Projects
None yet
Development

No branches or pull requests