Viewing 4 replies - 1 through 4 (of 4 total)
  • Hi kreynen@,

    The plugin is licensed under GPLv2+. This lets users who have a specific concern with the FSF’s compatibility comments on GPLv2 and Apache 2.0 use the plugin under GPL 3.0, while other users can choose GPL 2.0.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Based on above, closing the thread.

    Thread Starter kreynen

    (@kreynen)

    Users are free to use GPL-2.0-or-later code in combination with Apache-2.0 or even commercially licensed code. Use is not the issue.

    The issue is distribution.

    GPL-2.0+ or GPL-2.0-or-later still has to be compatible with GPL-2.0. If you want to distribute a combination of code using GPL and Apache-2.0, you’d need to do that as GPL-3.0 or GPL-3.0-or-later.

    What you are doing is a violation of the GPL-2.0-or-later license.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    What you are doing is a violation of the GPL-2.0-or-later license.

    Maybe. Maybe not. I’m closing this topic as GPL conversations get ugly fast.

    This does not mean I do not support GPL. I do, quite emphatically. But, to be frank, your and my interpretations really do not matter. This is something for the plugins team to evaluate. You can contact them via [email protected].

    Please be aware that if they disagree with you then that’s really it. If they agree with your finding then they will deal with the author directly to resolve this matter.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Apache-2.0 code in a GPL-2.0 plugin?’ is closed to new replies.