News: 1609855869

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Open-source contributors say they'll pull out of Qt as LTS release goes commercial-only

(2021/01/05)


The Qt Company has followed up on its plan to make long-term support releases commercial-only by closing the source for 5.15 today, earning protests from open-source contributors who say that the 6.0 release, which remains open, is not yet usable.

Qt is a cross-platform application framework available both under open-source and commercial licences. It was around one year ago that the Qt Company [1]stated its plan to make LTS releases commercial-only, along with some other changes designed to encourage open-source users either to contribute to the project or buy a commercial licence.

On 8 December CTO and chief maintainer Lars Knoll noted the [2]arrival of Qt 6.0 , "the first release of a major new version."

Qt 6.0 has a new graphics architecture which takes advantage of the native 3D graphics API of each platform on which it runs, as well as the next generation of QML (Qt Modeling Language) for defining a user interface. However, Knoll acknowledged that 6.0 still has limitations.

It "does not yet support many of the add-on modules that can be found in Qt 5.15," he said, and also refered to "clean-up work and refactoring" that is still needed as well as forthcoming work on "the stability of the new releases."

Knoll added: "We plan to have most of the important add-ons ported by the time we release Qt 6.2."

Yesterday senior VP Tuukka Turunen [3]posted : "With Qt 6.0.0 released and the first patch release (Qt 6.0.1) coming soon, it is time to enter the commercial-only LTS phase for Qt 5.15 LTS. All the existing 5.15 branches remain publicly visible, but they are closed for new commits (and cherry-picks)... closing happens tomorrow, 5th January 2021.

"After this the cherry-picks go to another repository that will be available only for the commercial license holders... first commercial-only Qt 5.15.3 LTS patch release is planned to be released in February."

According to last year's QT post, the idea is that non-commercial users shift to 6.0 so that they can still use the latest release for free. Responses to Turunen's post suggested that this is not realistic for many users. "That's some brilliant timing, given that no actual qt 6 release even exists yet (yeah, 6.0 is a joke given that you intend to break binary compat in 6.1)," said one developer.

Another said: "Qt6 has half of the modules required by my project not yet available, so upgrading is not possible. On the other hand, 5.15 LTS is closed for the open source users – this is quite a heavy restriction for me since my project is non-profit and open source. Buying a commercial license is not an option."

Turunen responded that "for the open-source users Qt 5.15 is similar to Qt 5.13 and Qt 5.14 (non-LTS releases)."

Security

The problem is that these releases are in effect no longer maintained. If there is a security issue, or a fix needed to support some change in one of the target operating systems, open-source users will not get that fix other than in the not-ready version 6.0.

Open-source contributor Thiago Macieira, an Intel software architect, [4]said of the decision : "That means I will not be participating in the development of those fixes, commenting on what's appropriate or not, reviewing backports, or bug reports."

"Tend to agree," said Konstantin Ritt, another developer. "If there is a decision to close 5.15 sources, there'll be no more work from external/unpaid contributors."

Turunen responded that: "This is well understandable and expected. The Qt Company is prepared to handle the Qt 5.15 LTS phase work."

But this is not a complete answer to the wider question of Qt viability for open-source users.

A possible solution is a community-driven fork of Qt 5.15 to which bug fixes could be backported. This is under discussion [5]here .

David Edmundson, a maintainer for the Qt-based KDE Linux desktop, noted that: "Whilst that is a valid option, it is not an ideal outcome."

Last year Knoll [6]said : "None of these changes should affect how Qt is being developed. There won't be any changes to Open Governance or the open development model."

However, these new complaints demonstrate that the commercially driven changes do impact the development model.

Many open-source projects struggle to reconcile free availability of code with commercial sustainability, but Qt is seemingly not one of them. Its last [7]interim statement for July-September 2020 reported "very strong profitable growth" with net sales up 30.6 per cent year on year and a 26.5 per cent operating margin. ®

Get our [8]Tech Resources



[1] https://www.theregister.com/2020/01/28/new_qt_terms_changes_are_necessary_for_our_business_model/

[2] https://www.qt.io/blog/qt-6.0-released

[3] https://lists.qt-project.org/pipermail/development/2021-January/040798.html

[4] https://lists.qt-project.org/pipermail/development/2021-January/040799.htmlhttps://lists.qt-project.org/pipermail/development/2021-January/040799.html

[5] https://bugreports.qt.io/browse/QTQAINFRA-4121

[6] https://lists.qt-project.org/pipermail/development/2020-January/038316.html

[7] https://www.qt.io/stock/interim-statement-11-3092020-1603951200000-2808857?hsLang=en

[8] https://whitepapers.theregister.com/

J27

Fork it!

Geoffrey W

Q2 - "What are we gonna do now?", "What are we gonna do now?", "What are we gonna do now?" - (Spike Milligan telly show for the uninitiated.)

WonkoTheSane

[1]Pic

[1] https://i.kym-cdn.com/entries/icons/facebook/000/017/204/CaptainAmerica1_zps8c295f96.jpg

Pic

TimMaher

That didn’t look very like Spike.

Anonymous Coward

Actually, given that Qt is GPL-licensed and if the fork earns more momentum than the closed-source version, it could very well end in a situation where the "official" version would be unable to import these new developments and patches and fall behind.

That would be karmastic.

Yet Another Anonymous coward

But forking a now obsolete old branch just to support existing non-commercial users doesn't sound like the sort of exciting new project which will attract may contributors.

It would make more sense to fork 6.0 and say *BEEP* to the Qt company and go on your own - especially since they have shown that they aren't planning to play nicely in future.

"...say that the 6.0 release... is not yet usable."

Def

So just like all the other versions then. ;)

Andy Landy

Qt is GPL-licensed

actually Qt is a proper mish-mash of licenses: https://doc.qt.io/qt-5/licenses-used-in-qt.html

i've used Qt on and off for many years now, so this change is all a bit sad

does anyone here have any experience of CopperSpice (https://www.copperspice.com/)? been thinking about making the jump myself for a year or two now, curious to hear of anyone else's experience.

One less reason to bother with QT.

jilocasin

Shame really, I actually prefer KDE to Gnome these days. The QT mouthpiece commented that he expected people wouldn't be doing anymore free work, I don't think he realized that was for 6+, not just the recently closed 5.15 version. The company has just lost a lot of developers, reviewers, etc.

Madison's Inquiry:
If you have to travel on the Titanic, why not go first class?