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

Relicense hyprlang to lgpl 3 #27

Merged
merged 3 commits into from
Mar 3, 2024
Merged

Relicense hyprlang to lgpl 3 #27

merged 3 commits into from
Mar 3, 2024

Conversation

vaxerski
Copy link
Member

@vaxerski vaxerski commented Mar 1, 2024

Due to some annoying license incompatibilities, GPL and BSD don't like each other, so I'd like to leave this to be more permissive.

cc all contributors, please leave a comment "I consent to this change" or I'll be forced to yeet your contributions.

@fufexan @solopasha @spikespaz @earboxer

ref, gpl:
image

@fufexan
Copy link
Member

fufexan commented Mar 1, 2024

I consent to this change.

Also, please change nix/default.nix's license key from licenses.gpl3Plus to licenses.bsd3
Nevermind I did it.

@spikespaz
Copy link
Contributor

spikespaz commented Mar 1, 2024

All of my contributions released publicly to open source communities are henceforth transferred in ownership to the original Code Owner of the project which they were submitted to, who may do with them as he pleases, including but not exclusive to relicensing.

@solopasha
Copy link
Contributor

Ok, i'm drunk rn, but I consent to this change

@earboxer
Copy link
Contributor

earboxer commented Mar 2, 2024

GPL and BSD don't like each other

BSD-3-Clause is compatible with GPLv3, it's just that GPLv3 is the viral license (giving users more permissions by preventing proprietary programs from linking to it).

If the issue is that you want non-free programs to be able to use this library (as suggested by the screenshot), then I suggest using LGPL-3.0-only. (In fact, I consent to license my past contributions to hyprlang under LGPL-3.0-only.)

See https://en.wikipedia.org/wiki/License_compatibility for more information.

@spikespaz
Copy link
Contributor

@earboxer I was thinking the same thing but was too lazy to double check myself. I support this motive, the license should be LGPL.

@vaxerski
Copy link
Member Author

vaxerski commented Mar 2, 2024

ugh, fine.

@vaxerski
Copy link
Member Author

vaxerski commented Mar 2, 2024

I'll need all four of you to write again "I consent to having all my contributions to this repository relicensed to lgpl 3.0 only"

@fufexan
Copy link
Member

fufexan commented Mar 2, 2024

I consent to having all my contributions to this repository relicensed to LGPL-3.0-Only.

@solopasha
Copy link
Contributor

I consent to having all my contributions to this repository relicensed to lgpl 3.0 only

@vaxerski vaxerski changed the title Relicense hyprlang to BSD-3-Clause Relicense hyprlang to lgpl 3 Mar 2, 2024
@vaxerski
Copy link
Member Author

vaxerski commented Mar 2, 2024

@earboxer @spikespaz pretty please?

@spikespaz
Copy link
Contributor

I consent to having all my contributions to this repository relicensed to LGPL-3.0-Only.

1 similar comment
@earboxer
Copy link
Contributor

earboxer commented Mar 2, 2024

I consent to having all my contributions to this repository relicensed to LGPL-3.0-Only.

@vaxerski
Copy link
Member Author

vaxerski commented Mar 3, 2024

top

@vaxerski vaxerski merged commit 3cc06e1 into main Mar 3, 2024
16 checks passed
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

Successfully merging this pull request may close these issues.

5 participants