-
Notifications
You must be signed in to change notification settings - Fork 16
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
[#2138] Relicense to LGPLv3+/GPLv2+ #2149
Conversation
1d78f9b
to
cd6420f
Compare
i think we're there on the licensing front - now just need the actual code and confirmation nothing is broken. |
Should that be a separate PR or do you want me to append it to this one and rename it? |
separate please... sorry for the confusion. |
After seeing some discussion on fedi, I've been doing a little bit more reading up on the GPL family of licenses. Added in the GPLv3 and LGPLv3 was a provision that opposes digital rights management. This provision scared away a lot of developers from adopting the licenses, and many groups have done their best to avoid software using these licenses. Sources:
libs3 is licensed under LGPLv3+ or GPLv2+. Allowing distribution under the GPLv2 provides an out for vendors who don't want to deal with the apparently troublesome provision. I think we should do the same. I'll be updating this PR accordingly. |
that makes sense. i'm familiar with those concerns as well. |
b0b1605
to
da6ae65
Compare
da6ae65
to
58dcd22
Compare
Am I good to #? |
I think so. Let's do it. |
58dcd22
to
9802a8c
Compare
#'d |
In service of #2138
In order to absorb libs3 into the project, we must relicense to a compatible license with the existing libs3 code.