openlp-core team mailing list archive

[Bastian Germann <bastiangermann@xxxxxxxxxxx>]

A problematic import is also the uno module. Depending on the
OpenOffice/LibreOffice version this is a license violation as well.
OpenOffice <= 2 should be okay. But nobody uses these old versions
today.

OpenOffice 3 is LGPLv3 licensed and Apache OpenOffice is Apache v2
licensed, which are incompatible with GPLv2 only.

LibreOffice is MPL2 licensed but in the uno.py license statement it
states that this file uses Apache v2 Code. MPL2 itself should be
compatible with GPLv2 but Apache v2 is not. I do not know what this
means exactly, but my suggestion is that the combination is also an
Apache v2 violation.

Relicensing to GPLv3 would also heal this situation, so the relicensing
seems to be the better option.

-- 
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/1795876

Title:
  License violations

Status in OpenLP:
  New

Bug description:
  OpenLP (GPLv2 only) is currently violating at least two licenses: PyQt5's GPLv3 only and request's Apache 2.0.
  There are two options to heal these violations: relicense OpenLP or replace the dependencies. A third option would be aquiring a commercial PyQt5 license from Riverbank and replacing requests only, but as it is paid per developer this seems to be infeasible for an open source project.

  REPLACING
  =========
  Replacing requests would be feasible: urllib is already used throughout the codebase. Just use it for the currently three files which import requests as well.

  I do not know if it would be feasible to replace PyQt5 with PySide2.

  RELICENSING
  ===========
  You would have to use the GPLv3 license to heal both of the violations (GPLv3 is compatible with Apache 2.0). You could also use GPLv2 or later, but the logical license combined with PyQt5 is always GPLv3. That leads to another issue: pysword is GPLv2 only and a license move would require you to drop this optional dependency. But I guess this would be a minor issue as it is not released yet (?).

  I do not know if relicensing is feasible as you would have to ask the
  majority of copyright holders to agree with the license change.

  In either case you should inform your users not later than with your
  next (fixed!) release about the license violation as they could be in
  trouble using OpenLP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1795876/+subscriptions