Same thing happened with Oracle and Java, they lost a lot of potential new developers with their hardline approach to open source.
Qt and Open Source
11–20 of 138 posts
Re: Qt and Open Source
#12While the core product is LGPLv3+Commercial, most of their extensions are GPLv3+Commercial which makes them not suitable for a lot of apps. Hence I find it's a bit confusing to say "to be committed to open source" where in practice the only way to use their extension is either to release your apps code (given you distribute the app) or pay for commercial license. IMHO "to be committed to free software" would represen…
Re: Qt and Open Source
#13Does anyone have context for what these discussions are? That's a pretty terse message for those of us not in the loop... Edit: This article gives a bit more context. https://www.phoronix.com/scan.php?page=news_item&px=Qt-Open-...
Here is a good background article: https://www.embeddeduse.com/2019/12/21/safe-guarding-the-lgp... And here the email to which Qt Comany reacts: https://mail.kde.org/pipermail/kde-community/2020q2/006098.h... LGPL has long been a thorn in the side of Qt Company management. Nokia had bought Qt for $150 million, developed and popularized the platform, and then released everything under LGPL. Digia/The Company then boug…
Linked email from KDE:
> But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. They are aware that this would mean the end of contributions via Open Governance in practice.
TFA (the entirety):
> There have been discussions on various internet forums about the future of Qt open source in the last two days. The contents do not reflect the views or plans of The Qt Company.
> The Qt Company is proud to be committed to its customers, open source, and the Qt governance model.
So, are they claiming that they never planned to "restrict ALL Qt releases to paid license holders for the first 12 months", or are they saying this plan still counts as "committed to open source"?
Re: Qt and Open Source
#14Earlier quoted context omitted.
Here is a good background article: https://www.embeddeduse.com/2019/12/21/safe-guarding-the-lgp... And here the email to which Qt Comany reacts: https://mail.kde.org/pipermail/kde-community/2020q2/006098.h... LGPL has long been a thorn in the side of Qt Company management. Nokia had bought Qt for $150 million, developed and popularized the platform, and then released everything under LGPL. Digia/The Company then boug…
I read the linked email and now I'm even more confused about TFA. Linked email from KDE: > But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. The…
Re: Qt and Open Source
#15I really like Qt for desktop development, use it everyday, but this post makes me feel uneasy. What "discussions on various internet forums" do they mean? there's been plenty. And, which ones "do not reflect the views or plans of The Qt Company"? Why such a rushed defensive blog post?
In particular
> Unfortunately, The Qt Company is currently considering to stop this healthy cooperation
Re: Qt and Open Source
#16While the core product is LGPLv3+Commercial, most of their extensions are GPLv3+Commercial which makes them not suitable for a lot of apps. Hence I find it's a bit confusing to say "to be committed to open source" where in practice the only way to use their extension is either to release your apps code (given you distribute the app) or pay for commercial license. IMHO "to be committed to free software" would represen…
Re: Qt and Open Source
#17Earlier quoted context omitted.
Here is a good background article: https://www.embeddeduse.com/2019/12/21/safe-guarding-the-lgp... And here the email to which Qt Comany reacts: https://mail.kde.org/pipermail/kde-community/2020q2/006098.h... LGPL has long been a thorn in the side of Qt Company management. Nokia had bought Qt for $150 million, developed and popularized the platform, and then released everything under LGPL. Digia/The Company then boug…
I read the linked email and now I'm even more confused about TFA. Linked email from KDE: > But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. The…
Re: Qt and Open Source
#18I really like Qt for desktop development, use it everyday, but this post makes me feel uneasy. What "discussions on various internet forums" do they mean? there's been plenty. And, which ones "do not reflect the views or plans of The Qt Company"? Why such a rushed defensive blog post?
There are talks in the mailing list about forking QT but KDE doesn't seems to want that currently due to lack of developers for maintaining a fork
Re: Qt and Open Source
#19Earlier quoted context omitted.
I read the linked email and now I'm even more confused about TFA. Linked email from KDE: > But last week, the company suddenly informed both the KDE e.V. board and the KDE Free QT Foundation that the economic outlook caused by the Corona virus puts more pressure on them to increase short-term revenue. As a result, they are thinking about restricting ALL Qt releases to paid license holders for the first 12 months. The…
Would it even increase their short-term revenue? Users who use the FOSS licence will just wait for the next release, won't they? Unless it's urgent that they use the latest Qt, why would they pay up?
Re: Qt and Open Source
#20While the core product is LGPLv3+Commercial, most of their extensions are GPLv3+Commercial which makes them not suitable for a lot of apps. Hence I find it's a bit confusing to say "to be committed to open source" where in practice the only way to use their extension is either to release your apps code (given you distribute the app) or pay for commercial license. IMHO "to be committed to free software" would represen…
In other words, the license is not suitable for users who are not committed to open source themselves but are not willing to pay either.
Dual licensing with GPL is IMHO the best and often only viable method from the business point of view for small and medium sized companies who sell product and not just service.
QT Company has large customers that are much bigger than it is. Many of them in software business. Turning into yet another software as a service producer for Autodesk or car manufacturers is not in their interests.