[Qt-creator] Fw: [Development] Changes to Qt offering

Michael Jackson mike.jackson at bluequartz.net
Tue Jan 28 22:00:52 CET 2020

Yep, already stated my disappointment on the blog page. I understand these moves from a purely business view. The Qt company needs additional revenue streams to continue development of the product. I just don't think that hitting up a developer for a license because *my* project depends on Qt is the way to go. We open sourced our application in the hopes that other R&D engineers would contribute but having an annoying "make an account with this 3rd party" bit is going to drive them away.  We were looking at porting it all over to Python and now that is looking more & more like a reality.

Michael Jackson | Owner, President
      BlueQuartz Software
[e] mike.jackson at bluequartz.net
[w] www.bluequartz.net <http://www.bluequartz.net>

On 1/28/20, 12:44 PM, "Qt-creator on behalf of Jason H" <qt-creator-bounces at qt-project.org on behalf of jhihn at gmx.com> wrote:

    Mr Jackson,
    Please see below and vent accordingly.
    > Sent: Monday, January 27, 2020 at 9:34 AM
    > From: "Lars Knoll" <lars.knoll at qt.io>
    > To: "Qt development mailing list" <development at qt-project.org>
    > Subject: [Development] Changes to Qt offering
    > Hi all,
    > The Qt Company has done some adjustments to the Qt will be offered in the future. Please check out https://www.qt.io/blog/qt-offering-changes-2020 . 
    > The change consists of three parts. 
    > One is a change in policy regarding the LTS releases, where the LTS part of a release is in the future going to be restricted to commercial customers. All bug fixes will (as agreed on the Qt Contributor Summit) go into dev first. Backporting bug fixes is something that the Qt Company will take care of for these LTS branches. We’ve seen over the past that LTS support is something mainly required by large companies, and should hopefully help us get some more commercial support for developing Qt further.
    > The second change is that a Qt Account will be in the future required for binary packages. Source code will continue to be available as currently. This will simplify distribution and integration with the Marketplace. In addition, we want open source users to contribute to Qt or the Qt ecosystem. Doing so is only possible with a valid Qt Account (Jira, code review and the forums all require a Qt Account).
    > The third change is that The Qt Company will in the future also offer a lower priced product for small businesses. That small business product is btw not limited to mobile like the one Digia had some years ago, but covers all of Qt for Device Creation.
    > 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.
    > Best regards,
    > Lars
    > _______________________________________________
    > Development mailing list
    > Development at qt-project.org
    > https://lists.qt-project.org/listinfo/development
    Qt-creator mailing list
    Qt-creator at qt-project.org

More information about the Qt-creator mailing list