You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2023. It is now read-only.
Unfortunately the Apache v2 license is generally considered to be incompatible with the GPLv2 license, making this library unusable from many projects.
The standard workaround for this (very common in the Rust community) is to license projects as MIT OR Apache 2.0, which means that contributions invoke the Apache 2.0 protections but downstream users can choose which license they want to accept the code under.
It would be excellent if pygtrie did as well.
The text was updated successfully, but these errors were encountered:
Second of, I honestly don’t know if I can do anything about it. I don’t really have a way to influence the license of commits copyrighted by Google.
Lastly, I never understood dual licensing as MIT or Apache. It seems dumb to me since anyone can choose MIT and ignore any protections Apache provides. A more sensible would be to dual license as Apache and GPLv2.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Unfortunately the Apache v2 license is generally considered to be incompatible with the GPLv2 license, making this library unusable from many projects.
The standard workaround for this (very common in the Rust community) is to license projects as MIT OR Apache 2.0, which means that contributions invoke the Apache 2.0 protections but downstream users can choose which license they want to accept the code under.
It would be excellent if pygtrie did as well.
The text was updated successfully, but these errors were encountered: