Opened 9 years ago
Last modified 7 years ago
#494 new task
Assure that the Qt licensing model is valid for SasView
| Reported by: | piotr | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Admin Tasks |
| Component: | SasView | Keywords: | |
| Cc: | Work Package: | SasView Admin |
Description (last modified by butler)
PyQt/Qt requires the code to be licensed with a GPL or GPL-compatible license.
BSD licensing which GitHub projects have by default might be too lax in this case so we need to investigate this issue a bit.
Change History (3)
comment:1 Changed 8 years ago by butler
- Description modified (diff)
- Milestone changed from WishList to Admin Tasks
- Type changed from enhancement to task
comment:2 Changed 8 years ago by ajj
comment:3 Changed 7 years ago by pkienzle
Commercial license requires one license per active developer. The number of active developers in not well defined, but presumably would be one per code camp attendee?
Commercial license must be purchased prior to first release of the proprietary application. Not sure if this means you can do a GPL release of your application before releasing a non-GPL version.
The entire product must be released as GPL if any part is GPL, but that does not prevent us from having the different licenses on the different files. In particular, sasmodels and the non-GUI sasview libraries can be released as BSD.
PySide (Qt4) and PySide2 (Qt5) are LGPL. Don't know if they work with sasview. Wheels for PySide2 are available here:
http://download.qt.io/snapshots/ci/pyside/5.11/latest/pyside2/
Qt is LGPL so not a problem
PyQt? is GPL which is a problem. Option for ESS to buy commercial license which might solve problem. Needs more investigation.