openlp-core team mailing list archive

[Bastian Germann <bastiangermann@xxxxxxxxxxx>]

If the relicensing takes place you would also have to get rid of the
LGPLv2 licensed pyxdg module. An alternative is at
https://pypi.org/project/xdg

-- 
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