Licensing question

[andrey-pr]

Hello.
According to LICENSE file, this project is licensed by Apache 2.0. But it also uses QT (through PyQt6 lib) framework, that is GPL and requires to make same licensing conditions to any derivative work.
I would recommend you to change project license to GPL, to make project compliant to QT license.
(I'm not a QT representative or any other official person and not related to QT at all. I just passed by and noticed license incompatibility :-)

[maresb]

Hi @andrey-pr, you're right that we're in a licensing quandary, thanks for bringing this to my attention.

Labelle has existed for many years under the Apache license and I don't feel comfortable imposing GPL on our existing userbase. Moreover I have doubts about my authority as a maintainer to relicense the contributions that our contributors made under the Apache license.

Qt is only used by labelle-gui, which is effectively an add-on that we bundle with the normal labelle CLI. We have been intending for a while to break this out as a separate package (see #40 (comment)). I think the sensible thing to do here is to GPL labelle-gui (and rename it to labelle-qt because I hope to eventually provide other GUIs). I'm no legal expert, but I'd argue under common sense that given the dependencies of the GUI component, that relicensing the GUI component to GPL is the most practical and pragmatic way forward.

Most (if not all) the contributions to the GUI code were by @MooVx, @tomers, and me, so we should seek their opinions. (We should also check the Git history for other GUI contributors I missed.)

[maresb]

Repinging @MooVx and @tomers, would you consent to relicensing your contributions to GPL so that we can resolve the license incompatibility?

[tomers]

I agree with Ben. If needed, relicense labelle-gui, however, I don't think we need or want to relicense the other packages (indeed, we should refactor into packages soon enough). Note that I am not sure at all that we need to relicense the GUI code, since it depends on whether we statically or dynamically link QT. See https://chatgpt.com/s/t_68c8ff4dbddc81919459bcf653638887. Tomer

…

On Wed, Sep 10, 2025 at 3:08 AM Ben Mares ***@***.***> wrote: *maresb* left a comment (labelle-org/labelle#107) <#107 (comment)> Reping @MooVx <https://github.com/MooVx> and @tomers <https://github.com/tomers>, would you consent to relicensing your contributions to GPL so that we can resolve the license incompatibility? — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAUL4Z2Y2CRIHDBRNVV2M33R5TZHAVCNFSM6AAAAAB2ATS5BSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZSG4ZDSOBRGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>