Imagine getting a phone call like, "Can we send our license specialist to your premises and conduct an audit of your code?".
Leveraging Qt code just went from an asset to a liability.
Imagine getting a phone call like, "Can we send our license specialist to your premises and conduct an audit of your code?".
Leveraging Qt code just went from an asset to a liability.
I really wouldn't expect that from an organization from Qt, however I /would/ expect a call like:
"Hey, congratulations on your launch! We noticed someone from your org downloaded source from us about 18 months ago. Mind if we discuss your licensing plans?"
So your company was previously violating the license and hoping nothing would happen? I certainly hope you don't randomly download code off the net just to do that.
And really, ever since the Trolltech days, Qt was dragged into open source kicking and screaming.
Nokia introduced LGPL and open governance, simply because they were not interested in Qt as a commercial product, and The Qt Company is now trying to build a business around this. With huge companies like Tesla building their product around the free version of Qt without complying with the open source licenses, it is not that hard to see why they would look for ways to find out who their actual users are.