QT Commercial vs Open Source
-
Hello Moderators or whoever used the Commercial Liscenses in QT,
I understand that this is a repeated question in this forum. I read through the post and unable to come to a firm understanding. Hence, this post is created
I want to know the Main Differences between the OpenSourced and Commercial License. Maybe links to the comparison tables between the licenses? Or a detailed explanation of what are the essential differences between the opensourced license and Commercial LIcense.
-
@Stevendragoes said in QT Commercial vs Open Source:
Alright. So, It is possible for me to get a confirmation from the QT sales team that they will not come after me if I released a proprietary software that I developed on my own?
Ask Qt Company then :-) I'm not their employee. But I can say that if you make sure you don't break LGPL, Qt Company won't have any basis to "chase" you.
What do I have to worry here? I heard that the Open Source license can be copied by anyone?
Yes, but LGPL applies only to Qt not to your code. That's why you have to inform your users that you are using Qt and that they can replace Qt with their own version if they want to.
How can i check my QT license? from the Update Manger?
If you have installed Qt without paying the commercial license, it is safe to assume you are using the open source version ;-)
The choice between LGPL and GPL is arbitrary - you choose which license you want Qt to be under (unless you chose some module which is not available under LGPL, like QtCharts, Lottie etc.).
Please pardon me for being a total ignorant newbie here
No problem, that's what this forum is for :-)
EDIT: I think I have to make my software with the source code public for 3 years. Am I right?
No, this is only about Qt. Your code is not bound by LGPL license (unless you decide to ship your code under LGPL as well).
So you have to provide Qt source code to your clients if they ask for it. In practice it means you should have a copy of Qt source code somewhere on your PC/ server for 3 years (just in case that official Qt archive goes offline or something). And if you patch Qt (for example, change something in QString code), these patches need to be under LGPL and you have to make them available to your clients.
That's one more point - to your clients. LGPL does not apply to every human being in existence :-) You don't have to publish Qt and your patches online for everybody. LGPL requires you to do it only for your clients (people using your app).
-
Qt Company's page has a summary of the differences here: https://www.qt.io/download-open-source
In terms of features - FOSS and Commercial are the same on desktop and mobile platforms. On embedded devices, Qt comes with some extra stuff (base Qt code is the same but there are extra tools provided which make deployment and development easier).
The main difference - of course - is the license. Most of Qt is available under LGPL, but some modules are GPL only. If you are making an application under a different license (for example, a commercial application), you have to be careful to meet the requirements of LGPL and/or GPL. On some platforms (Android, iOS) this is very hard or even impossible. On others (Windows, Linux) it is quite easy.
-
@sierdzio
I am developing on desktop platform. Hence, a Free Open Sourced License will do? What if I want to sell my invention/personal project? will QT charge? Because I believe that there exists a commercial license for a reason. Hence, I don't want to make any mistakes. -
As long as you use LGPL Qt (no GPL modules like QtCharts) and meet LGPL requirements you do not need the commercial license. You can sell your app, no problem there. Even the GPL does not forbid selling of stuff.
-
Alright. So, It is possible for me to get a confirmation from the QT sales team that they will not come after me if I released a proprietary software that I developed on my own?
What do I have to worry here? I heard that the Open Source license can be copied by anyone?
How can i check my QT license? from the Update Manger?
Please pardon me for being a total ignorant newbie here
EDIT: I think I have to make my software with the source code public for 3 years. Am I right?
-
@Stevendragoes said in QT Commercial vs Open Source:
Alright. So, It is possible for me to get a confirmation from the QT sales team that they will not come after me if I released a proprietary software that I developed on my own?
You would have to contact The Qt Company if you really want to ask a question like that. This is a user forum.
EDIT: I think I have to make my software with the source code public for 3 years. Am I right?
Where does that come from?
-
@Stevendragoes said in QT Commercial vs Open Source:
Alright. So, It is possible for me to get a confirmation from the QT sales team that they will not come after me if I released a proprietary software that I developed on my own?
Ask Qt Company then :-) I'm not their employee. But I can say that if you make sure you don't break LGPL, Qt Company won't have any basis to "chase" you.
What do I have to worry here? I heard that the Open Source license can be copied by anyone?
Yes, but LGPL applies only to Qt not to your code. That's why you have to inform your users that you are using Qt and that they can replace Qt with their own version if they want to.
How can i check my QT license? from the Update Manger?
If you have installed Qt without paying the commercial license, it is safe to assume you are using the open source version ;-)
The choice between LGPL and GPL is arbitrary - you choose which license you want Qt to be under (unless you chose some module which is not available under LGPL, like QtCharts, Lottie etc.).
Please pardon me for being a total ignorant newbie here
No problem, that's what this forum is for :-)
EDIT: I think I have to make my software with the source code public for 3 years. Am I right?
No, this is only about Qt. Your code is not bound by LGPL license (unless you decide to ship your code under LGPL as well).
So you have to provide Qt source code to your clients if they ask for it. In practice it means you should have a copy of Qt source code somewhere on your PC/ server for 3 years (just in case that official Qt archive goes offline or something). And if you patch Qt (for example, change something in QString code), these patches need to be under LGPL and you have to make them available to your clients.
That's one more point - to your clients. LGPL does not apply to every human being in existence :-) You don't have to publish Qt and your patches online for everybody. LGPL requires you to do it only for your clients (people using your app).
-
@Stevendragoes said in QT Commercial vs Open Source:
Alright. So, It is possible for me to get a confirmation from the QT sales team that they will not come after me if I released a proprietary software that I developed on my own?
No, there is no guarantee
I had been developing with the normal Qt License for about 3 years, and then in a real d*move the Qt Company contacted me and said I had the wrong license and I would own them money.IIRC they did not retroactively apply it(at least)
-
@LeLev said in QT Commercial vs Open Source:
@JonB said in QT Commercial vs Open Source:
Where does that come from?
column 3 row 3
From an unlinked/unreferenced pasted screenshot? That is not what I meant....
-
@JonB said in QT Commercial vs Open Source:
@LeLev said in QT Commercial vs Open Source:
@JonB said in QT Commercial vs Open Source:
Where does that come from?
column 3 row 3
From an unlinked/unreferenced pasted screenshot? That is not what I meant....
It's linked to in my post... https://tldrlegal.com/license/gnu-lesser-general-public-license-v3-(lgpl-3)
-
@All thanks for the clarifications. especially @sierdzio I will contact the QT company as well to see which license is right for me