On 4/12/21 8:56 AM, interest-requ...@qt-project.org wrote:
>And who's "you" here? And how exactly did that sabotage a commercial
contract between you and whoever entity gives you commercial support on
RHEL6?
The "you" would be whoever participated in the decision to drop RHEL 6.
That
On 12/04/2021 13:59, Roland Hughes wrote:
On 4/2/21 5:00 AM, Giuseppe D'Angelo wrote:
(Is there a conflict of intents here because of the massive support to
the Qt Project? I can't see how -- if anything, one could say that the
commercial decisions may drive the decisions in the Qt Project,
On 4/2/21 5:00 AM, Giuseppe D'Angelo wrote:
(Is there a conflict of intents here because of the massive support to
the Qt Project? I can't see how -- if anything, one could say that the
commercial decisions may drive the decisions in the Qt Project,
certainly NOT that the Qt Project has the
On 4/2/21 5:00 AM, Thiago Macieira wrote:
I would expect Qt to query the version of X being used, say
multi-touch isn’t supported so the app cant support it. If my customer
complained that multi-touch works on the Windows, and CentOS 7 boxes, but not
CentOS 6.
The reasoning is clear, the
On 01/04/2021 16:13, Roland Hughes wrote:
On 4/1/21 8:46 AM, Giuseppe D'Angelo wrote:
On 01/04/2021 13:40, Roland Hughes wrote:
We keep discussing the ability to upgrade Qt but not upgrade the rest of the
OS. I understand that Qt is a central component of the UI, but it's no less
critical
On 4/1/21 8:46 AM, Giuseppe D'Angelo wrote:
On 01/04/2021 13:40, Roland Hughes wrote:
We keep discussing the ability to upgrade Qt but not upgrade the rest of the
OS. I understand that Qt is a central component of the UI, but it's no less
critical than a lot of other components that you may
On 4/1/21 8:36 AM, coroberti wrote:
It looks like some business case for Roland.
Sending many emails with the links to the owned/associated
books thru the Qt mail lists
and even openly advertising them - at least two cases just recently.
Is it in line with the list policy?
Kind regards,
It looks like some business case for Roland.
Sending many emails with the links to the owned/associated
books thru the Qt mail lists
and even openly advertising them - at least two cases just recently.
Is it in line with the list policy?
Kind regards,
Robert Iakobashvili
> On 1 Apr 2021, at 14:47, Roland Hughes wrote:
>> PS: Roland, I was looking at your
>> https://www.theminimumyouneedtoknow.com/agile_book.html page, and judging by
>> this sentence, I think your review process is broken. You should probably
>> ask for your money back from your professional
On 4/1/21 6:48 AM, Volker Hilsheimer wrote:
But why should the Qt Project have to care? The Qt Project doesn’t sell into
the medical or industrial automation market.
That's the market that really made Qt. Nokia sure as Hell didn't. The
market was pursued.
If a medical device manufacturer
On 01/04/2021 13:40, Roland Hughes wrote:
We keep discussing the ability to upgrade Qt but not upgrade the rest of the
OS. I understand that Qt is a central component of the UI, but it's no less
critical than a lot of other components that you may need to upgrade in order
to deal with
> On 1 Apr 2021, at 11:55, Roland Hughes wrote:
> On 4/1/21 12:40 AM, Thiago Macieira wrote:
>> Dropping old platforms has been done since the early 2000s. Everyone who
>> adopted Qt since 3.0 has known of this. It's was not news then and it's not
>> now.
>
> It is news now.
>
> During Qt 3.x
On 4/1/21 12:40 AM, Thiago Macieira wrote:
I'm painting a scenario to understand how you'd have to handle such a
situation, when there isn't a company you can call upon to fix the problem for
you.
We keep discussing the ability to upgrade Qt but not upgrade the rest of the
OS. I understand
On 4/1/21 12:40 AM, Thiago Macieira wrote:
On Sunday, 28 March 2021 04:54:56 PDT Roland Hughes wrote:
What is "the process" criteria for new major version number? I'm
curious. Why? Because I agree with Scott. Extinction of platforms needs
to be a mandating force.
The new major version happens
On Sunday, 28 March 2021 04:54:56 PDT Roland Hughes wrote:
> What is "the process" criteria for new major version number? I'm
> curious. Why? Because I agree with Scott. Extinction of platforms needs
> to be a mandating force.
The new major version happens when we need to do a binary
On 3/30/21 5:00 AM, Henry Skoglund wrote:
On 2021-03-29 21:29, Matthew Woehlke wrote:
On 28/03/2021 09.52, Jason H wrote:
The developers at Qt Co need to push back and tell Digia "that's not
how this
works" before we get to the points of users revolting in threads on
the forums /
lists.
On 2021-03-29 21:29, Matthew Woehlke wrote:
On 28/03/2021 09.52, Jason H wrote:
The developers at Qt Co need to push back and tell Digia "that's not
how this
works" before we get to the points of users revolting in threads on
the forums /
lists.
*Before*?
I guess this thread, and the
On 28/03/2021 09.52, Jason H wrote:
The developers at Qt Co need to push back and tell Digia "that's not how this
works" before we get to the points of users revolting in threads on the forums /
lists.
*Before*?
I guess this thread, and the multiple others like it, are then
discussions on
> hush-hush "call for pricing" is a truly bogus business practice usually
> utilized by scams and used car dealers.
>
> This "gouge them for all they are worth in private" business model really
> isn't valid. Even if you adamantly claim that isn't what is going on, that is
> __exactly__ what
> hush-hush "call for pricing" is a truly bogus business practice usually
> utilized by scams and used car dealers.
>
> This "gouge them for all they are worth in private" business model
> really isn't valid. Even if you adamantly claim that isn't what is going
> on, that is __exactly__ what
> What would really help, is to get this documented out in the open... None of
> this
> "contact sales for pricing"
You have not yet received the most important and most common advice in this ML:
"Ask a
lawyer"! LOL SCNR
But seriously, what would really help would be giving the technology to
Yeah,
hush-hush "call for pricing" is a truly bogus business practice usually
utilized by scams and used car dealers.
This "gouge them for all they are worth in private" business model
really isn't valid. Even if you adamantly claim that isn't what is going
on, that is __exactly__ what it
Tukka,
I'm open to being wrong, but I just spoke with them. One of us three is
obviously in error, but I pushed back on the lack of the perpetuity clause, (it
was present at my last company) and sales was clear, it was removed...
What would really help, is to get this documented out in the
I was just in contact with them, and shocked that the perpetual nature was
removed...
I don't think I'm mistaken.
> Sent: Sunday, March 28, 2021 at 7:53 PM
> From: "Tuukka Turunen"
> To: "Jason H"
> Cc: "Roland Hughes" , "interest@qt-project.org"
> , "mike.jack...@bluequartz.net"
>
>
Hi Jason,
Please contact our sales to discuss commercial licensing. Based on the email
below you seem to misunderstand the commercial development and distribution
licensing at least partially.
Yours,
Tuukka
Lähettäjä: Jason H
Lähetetty: sunnuntaina,
On 3/28/21 10:37 AM, Christian Gagneraud wrote:
Chris
Didn't follow the whole discussion, it's getting ridiculous...
It's a lng way from ridiculous for companies choosing development
tools for a device that will generate $50+Million over the next decade.
--
Roland Hughes, President
On Mon, 29 Mar 2021 at 02:54, Jason H wrote:
>
> Tukka, you (Digia, aka "QtCo") no longer offer the perpetuity clause of the
> license. Which is absolutely insane for a commercial customer. If we are no
> longer developing that code, we should still be able to "distribute" that
> code. The
On 3/28/21 8:27 AM, Jason H wrote:
On 3/26/21 1:39 PM, Jason H wrote:
Thiago, apparently, even with a commercial license, we no longer have rights
to use whatever versions were current when we had the license. Previously, we
could use
it in perpetuity. This is probably a deal breaker at my
Il 28/03/21 13:54, Roland Hughes ha scritto:
There is documentation and Web pages that have
replicated all over stating Qt 5 supports RHEL 6. You made something
that cannot be effectively erased untrue.
The documentation in question states that _specific_ Qt 5.x versions
support RHEL 6.
Il 28/03/21 15:52, Jason H ha scritto:
But it's now under the marketplace license?
https://marketplace.qt.io/collections/most-popular/products/qtpdf ($49/
Marketplace license)
QtPdf is still LGPLv3:
https://code.qt.io/cgit/qt-labs/qtpdf.git/tree/
AFAICS, the only thing you're paying for
Tukka, you (Digia, aka "QtCo") no longer offer the perpetuity clause of the license. Which is absolutely insane for a commercial customer. If we are no longer developing that code, we should still be able to "distribute" that code. The revocation of the perpetuity clause in new licenses means we
> On 3/26/21 1:39 PM, Jason H wrote:
> > Thiago, apparently, even with a commercial license, we no longer have rights
> > to use whatever versions were current when we had the license. Previously,
> > we could use
> > it in perpetuity. This is probably a deal breaker at my new organization.
> >
On 3/28/21 5:00 AM, Thiago Macieira wrote:
On Friday, 26 March 2021 17:23:38 PDT Scott Bloom wrote:
To me, Qt should continue to support OS's/Compilers for the life of a Major
version of Qt. if it built on Qt 5.0 it should build on that OS/Compiler
in 5.15
If Qt decides that modern C++ was
On Friday, 26 March 2021 17:23:38 PDT Scott Bloom wrote:
> To me, Qt should continue to support OS's/Compilers for the life of a Major
> version of Qt. if it built on Qt 5.0 it should build on that OS/Compiler
> in 5.15
>
> If Qt decides that modern C++ was more important in 5.13, and the
On Friday, 26 March 2021 06:13:13 PDT Jason H wrote:
> Thiago, apparently, even with a commercial license, we no longer have rights
> to use whatever versions were current when we had the license. Previously,
> we could use it in perpetuity. This is probably a deal breaker at my new
>
Thanks Scott!
Yeah, I was thinking about this as I woke up this morning. Trying to
retroactively invalidate all existing perpetual licenses would be
illegal. Not just "pay a fine" illegal, go to prison illegal.
On 3/26/2021 7:30 PM, Scott Bloom wrote:
From the Qt blog post
“When Qt chased these markets it knew what the lifetimes would be. Now it has
abandoned them.”
I would like to point out that this is not a true statement. We do offer long
term support and also extended support for those customers who need it. There
are some who every now and then still need
On 27/3/21 11:47 am, Scott Bloom wrote:
Sorry for top posting...
But I disagree here. Even for mac, Qt 5 is 9 years old, 4 lived 6 (4.0->4.8
LTS initial release, 4.8 lived for 3 years)
Im not saying we go to a Qt Major version for every mac system style change.
But if they produce a SDK
Sorry for top posting...
But I disagree here. Even for mac, Qt 5 is 9 years old, 4 lived 6 (4.0->4.8
LTS initial release, 4.8 lived for 3 years)
Im not saying we go to a Qt Major version for every mac system style change.
But if they produce a SDK where previous version is so different than
On 27/3/21 11:23 am, Scott Bloom wrote:
To be clear. Roland and I are talking about very different issues.
To me, Qt should continue to support OS's/Compilers for the life of a Major
version of Qt. if it built on Qt 5.0 it should build on that OS/Compiler in
5.15
If Qt decides that modern
Forgot to mention this.
I do not expect something that built against Qt3/4/5 to build under Qt4/5/6 on
the same OS/Compiler.
If Im changing OS, or compiler. I hope to find a Qt that works on the new
combo, (that’s rarely ever been an issue) but, my old version of Qt? if the
major version is
From the Qt blog post https://www.qt.io/blog/qt-offering-changes-2020
"These changes will not have any effect on existing commercial licensing or
services agreements."
Now, it doesn’t talk about the notion that if you built and produced your code
against a commercial license, it has to remain
To be clear. Roland and I are talking about very different issues.
To me, Qt should continue to support OS's/Compilers for the life of a Major
version of Qt. if it built on Qt 5.0 it should build on that OS/Compiler in
5.15
If Qt decides that modern C++ was more important in 5.13, and the
On 3/26/21 1:39 PM, Jason H wrote:
Thiago, apparently, even with a commercial license, we no longer have rights
to use whatever versions were current when we had the license. Previously, we
could use
it in perpetuity. This is probably a deal breaker at my new organization. It is
my
On 3/26/21 1:39 PM, Michael Jackson wrote:
I'll start off by acknowledging your points, but we will just agree to
disagree. I acknowledge that you have a*lot* of years making/maintaining
software for medical devices. But I'm with Hamish on this. I don't understand.
What you are saying
Roland,
I'll start off by acknowledging your points, but we will just agree to
disagree. I acknowledge that you have a *lot* of years making/maintaining
software for medical devices. But I'm with Hamish on this. I don't understand.
What you are saying is that Qt was designed "perfectly"
The FitBit and its many fly-by-night knockoffs are a great example. Its “food
plan” app will probably soon have privileged access to all of your kitchen
appliances. And it can even be used to monitor when the supervisor at your
local nuclear power plant goes on his daily constitutional.
On 3/26/21 9:23 AM, eric.fedosej...@gmail.com wrote:
There are much worse possible outcomes than spoiled food.
“App-controlled” smart ovens are now all the rage. Even if there are
safety measures to prevent remotely burning down your house, what
fraction of ovens in a community do you need
There are much worse possible outcomes than spoiled food. “App-controlled”
smart ovens are now all the rage. Even if there are safety measures to prevent
remotely burning down your house, what fraction of ovens in a community do you
need to simultaneously preheat to bring down the entire
On 3/26/21 6:00 AM, Hamish Moffatt wrote:
I really don't understand your arguments Roland. You say you need Qt
support for 15 years, but you can't actually change one bit of your
software without FDA approval, so presumably this means you aren't
upgrading Qt anyway. Then after 15 years you want
> Sent: Thursday, March 25, 2021 at 9:41 PM
> From: "Thiago Macieira"
> To: interest@qt-project.org
> Subject: Re: [Interest] the path forward - that 7 year thing - was willy-nilly
>
> On Thursday, 25 March 2021 12:38:56 PDT Roland Hughes wrote:
> > > Qt's horizon is about 7 years.
> >
> >
On 3/26/21 6:00 AM, Thiago Macieira wrote:
It doesn't make economical sense for Qt to provide support for 15 years. If
you need Qt for that long, you should engage a consultancy that will sell you
that contract, the same way that Red Hat sells support for RHEL 6 for 14 years
total (2010-2024).
On 26/3/21 6:38 am, Roland Hughes wrote:
According to the FDA fact sheet.
https://www.fda.gov/about-fda/fda-basics/fact-sheet-fda-glance
There are currently 25,864 registered FDA medical device facilities.
Not one of them can change a single approved process without going
through the FDA
On Thursday, 25 March 2021 12:38:56 PDT Roland Hughes wrote:
> > Qt's horizon is about 7 years.
>
> That's 8 years too short.
For this industry, sure. But it's not Qt's promise. The fact that some
industries require a higher standard of support or coding practices or
stability does not
Breaking this off into its own topic. Roping in some of Andre' and Scott
Bloom too.
On Wednesday, 24 March 2021 09:58:50 PDT André Pönitz wrote:
The exact opposite is the correct thing:
- deprecation messages while compiling the source code are correct
- messages to the mailing list are
55 matches
Mail list logo
