If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

1) If you want to contribute, you are required to allow Digia to include your code in proprietary releases of Qt. If you don't want your code to be sold in a closed-down, proprietary manner, you are not allowed to contribute code to Qt.

2) Qt is trying to improve support for other platforms so that they reach the same level of support as they have with Linux. Some people see this as "lack of focus on Linux."

3) There's an effort going on to make Qt run better on Android and QNX. Some people see this as "lack of focus on the Desktop."

1) If you want to contribute, you are required to allow Digia to include your code in proprietary releases of Qt. If you don't want your code to be sold in a closed-down, proprietary manner, you are not allowed to contribute code to Qt.

2) Qt is trying to improve support for other platforms so that they reach the same level of support as they have with Linux. Some people see this as "lack of focus on Linux."

3) There's an effort going on to make Qt run better on Android and QNX. Some people see this as "lack of focus on the Desktop."

1) If you want to contribute, you are required to allow Digia to include your code in proprietary releases of Qt. If you don't want your code to be sold in a closed-down, proprietary manner, you are not allowed to contribute code to Qt.

Licensor hereby grants, in exchange for good and valuable consideration, the receipt and sufficiency of which is hereby acknowledged, to Digia a sublicensable, irrevocable, perpetual, worldwide, non-exclusive, royalty-free and fully paid-up copyright and trade secret license to reproduce, adapt, translate, modify, and prepare derivative works of, publicly display, publicly perform, sublicense, make available and distribute Licensor Contribution(s) and any derivative works thereof under license terms of Digia’s choosing including any Open Source Software license.

Some people think that this was only due to KDE's agreement with Trolltech/Nokia/Digia to release Qt under a BSD license in case Qt was to be closed down. But this isn't the case. The agreement allows Digia to license code under *any* license, not just another Open Source license.

However, the effect of the KDE Free Qt Foundation agreement is pretty much the same. If the code can be relicensed under BSD, that pretty much means it can than be put in closed source software.

So the bottom line is: if you don't want your code to be BSD-style licensed and turn up using a proprietary license, you don't contribute to Qt. I suspect this would affect mostly people who are not getting paid for writing code, since this makes them look like idiots who work for free, while what they want is contributing to "make the world better" from an RMS point of view.

Dafuq: "As the Qt Project desires to facilitate the broadest Qt ecosystem and given that LGPL-only licensed code hinders participation by some Qt commercial users, the Qt Project is actively working to reduce Qt’s dependencies on LGPL-only licensed code. "

No it doesn't. They want to have CLA on as much of the LGPL licenced code as possible so they can have them as part of their Qt Commercial offering. That means that companies that have Qt Commercial licence do not have to release changes the way LGPL would otherwise require. I don't think any of the upstream Qt libaries are licenced under BSD or MIT and I don't see any reason why Digia would ever want to use them either as it would only mean that they would lose their privilege over the Qt code.

I don't see any signs of Qt dying either as Qt 5.0 was developed by over 400 people.