Qt 6.5 LTS Released

[David Szent-Györgyi]

The announcement is on the Qt Group blog. Unless my memory fails me,  since Leo itself is under the MIT License, the Community Edition of Qt must be used, and that means that development needs to follow one of the open source licenses that Qt supports. QT Group offers a Web page that shows which features are supported by the various licenses and a description of Contribution via Open Source and Open Source Usage Obligations. 

For what it is worth, MacPorts developers are discussing Qt 6.5.0 dropping support for macOS 10.14 and macOS 10.15. The Supported Platforms documentation lists Windows 10 v1809 and later and Windows 11; it mentions x64 editions of various Linux distributions, so other architectures and editions of Linux and Unix are up to the integrator, the programmer, or the end user. 

[Thomas Passin]

" MIT License Compatibility

The MIT License is highly compatible with other permissive licenses. Including the BSD family of licenses. It is generally compatible with  GNU GPL group of licenses. However if you distribute the code that contains or is derivative of GNU GPL code the final project must of GPL compliant. In other words any source code must of publicly available. "

From Open Licenses: Creative Commons and other options for sharing your work

It seems that if MIT-licensed work is combined with GPL-licensed work, the combined work must be (or is) licensed under the GPL.  Basically that means that the source code must be made freely available.

[Edward K. Ream]

On Wed, Apr 5, 2023 at 5:11 PM Thomas Passin <tbp1...@gmail.com> wrote:

> The MIT License is highly compatible with other permissive licenses.

For 20+ years I have ignored software licensing issues, except to credit the work of others in Leo. See Leo's copyright notice. I don't plan to change this policy.

Edward