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

[#2138] Relicense to LGPLv3+/GPLv2+ #2149

Merged
merged 1 commit into from
Nov 30, 2023
Merged

Conversation

SwooshyCueb
Copy link
Member

In service of #2138

In order to absorb libs3 into the project, we must relicense to a compatible license with the existing libs3 code.

@trel
Copy link
Member

trel commented Nov 27, 2023

i think we're there on the licensing front - now just need the actual code and confirmation nothing is broken.

@SwooshyCueb
Copy link
Member Author

Should that be a separate PR or do you want me to append it to this one and rename it?

@trel
Copy link
Member

trel commented Nov 27, 2023

separate please... sorry for the confusion.

@SwooshyCueb
Copy link
Member Author

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.

@SwooshyCueb SwooshyCueb marked this pull request as draft November 29, 2023 18:44
@trel
Copy link
Member

trel commented Nov 29, 2023

that makes sense. i'm familiar with those concerns as well.

@SwooshyCueb SwooshyCueb changed the title [#2138] Relicense to LGPLv3+ [#2138] Relicense to LGPLv3+/GPLv2+ Nov 29, 2023
@SwooshyCueb SwooshyCueb marked this pull request as ready for review November 29, 2023 22:51
@SwooshyCueb
Copy link
Member Author

Am I good to #?

@trel
Copy link
Member

trel commented Nov 30, 2023

I think so. Let's do it.

@SwooshyCueb
Copy link
Member Author

#'d

@alanking alanking merged commit 0688587 into irods:main Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants