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

BSD or MIT #41

Open
ignatenkobrain opened this issue Dec 14, 2019 · 5 comments
Open

BSD or MIT #41

ignatenkobrain opened this issue Dec 14, 2019 · 5 comments

Comments

@ignatenkobrain
Copy link

Hello, Cargo.toml lists BSD OR MIT, however LICENSE file contains only info about BSD... Who is right?

@danielrh
Copy link
Collaborator

I suppose the license file is right... I can adjust the Cargo.toml
both licenses are sufficiently permissive that they are quite compatible.

@decathorpe
Copy link

Looks like this issue is still unresolved as of today?

@nyurik
Copy link
Contributor

nyurik commented Mar 19, 2024

Most Rust projects prefer to use Apache OR MIT approach because MIT is not very compatible with GPL (if my memory is serving me right), and so having two clause approach allows users to use code everywhere more freely.

@decathorpe
Copy link

Then the license text for MIT should probably be added to this repo too?

The current license file (https://github.com/dropbox/rust-brotli/blob/master/LICENSE) file only contains the BSD-3-Clause license text, but the MIT license requires that license text is included with redistributed sources.

Usually dual-licensed crates handle this by having two separate license files (i.e. LICENSE-Apache and LICENSE-MIT, in most cases).

MIT is not very compatible with GPL

As far as I know, the problem wrt/ GPL compatibility is actually caused by the Apache-2.0 license, not the MIT license.

@danielrh
Copy link
Collaborator

Hmmm should probably copy the license from https://github.com/google/brotli/blob/master/LICENSE

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

No branches or pull requests

4 participants