On 14/5/21 6:44 AM, Eike Hein wrote:
I'm also not sure the patch collection against 5.15.2 really qualifies as
a_fork_ in the traditional sense. It's not diverging from a public branch we
could contribute to instead. At least it's not more of a fork than the (hidden)
LTS branch is.
Techni
May 13, 2021 10:29 PM, "Lorn Potter" wrote:
> On 13/5/21 8:00 PM, Kevin Kofler via Development wrote:
>
>> KDE is maintaining their own 5.15 branches, e.g.:
>> https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15
>
> I'm not kde developer, but I am sure kde has almost always had their own
> f
May 13, 2021 9:59 PM, "Oswald Buddenhagen" wrote:
> what would interest me is why you chose to host this on your own
> infrastructure instead of publicly demanding that tqtc plays by the
> rules and hosts the fork on qt project infra, where it belongs, and the
> possibility of which is explicitly
On Thursday, 13 May 2021 13:22:13 PDT Lorn Potter wrote:
> On 13/5/21 1:51 AM, Thiago Macieira wrote:
> > The problem is licensing, not Qt Company's willingness. They offered when
> > this all began. But since it's not open source, I can't look at it.
>
> Contractually or ethically?
>
> If ethica
On 13/5/21 8:00 PM, Kevin Kofler via Development wrote:
KDE is maintaining their own 5.15 branches, e.g.:
https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15
I'm not kde developer, but I am sure kde has almost always had their own
fork of Qt.
--
Lorn Potter
Freelance Qt Developer. Plat
On 13/5/21 5:05 AM, Jason H wrote:
This has forced me to reconsider Qt as essentially closed source,
wow, that seems a bit hardcore, really. Calling an open source framework
essentially closed source, just because you choose not to move on to
Qt6, which according to my research, is still op
On 13/5/21 1:51 AM, Thiago Macieira wrote:
The problem is licensing, not Qt Company's willingness. They offered when this
all began. But since it's not open source, I can't look at it.
Contractually or ethically?
If ethically, it still is certainly your own choice.
For me, the bigger pictur
On Thu, May 13, 2021 at 04:39:54PM +, Eike Hein wrote:
To make this work in general we were in a conversation with the Qt
Company before announcing the tree, to let them know that this is
happening and why, and so the Qt Company could confirm it would be
doing the patch reviews to make this
Wouldn't make releases GLP/commercial instead of commercial only solve
all the issues? Both of maintainers, and KDE.
Drop the "L" for 12 months. It would seem a compromise solution for me.
Anyhow, indeed, for me, the big problem was the awkward situation where
Qt 6 is basically unusable and FO
May 13, 2021 4:42 PM, "NIkolai Marchenko" wrote:
> The problem with kde maintaining this is that people who are switching to
> newer qt versions can no
> longer expect fixes done to this branch to exist in the newer qt. So bugs
> that have been closed by
> the community may reappear again in ac
The problem with kde maintaining this is that people who are switching to
newer qt versions can no longer expect fixes done to this branch to exist
in the newer qt. So bugs that have been closed by the community may
reappear again in actual Qt as TQTC deems them irrelevant.
On Thu, May 13, 2021 at
Jason H wrote:
> This has forced me to reconsider Qt as essentially closed source, I will
> be brushing up on my web dev skills and just going electron/cordova in the
> future. I wonder what this means for KDE. They probably have enough
> infrastructure to weather this storm, but the average person
I love Qt / QML - always after comparing with React Native or Flutter:
Qt/QML for me is the best and easiest way to develop
I'm a license holder - fortunately I'm eligible for the
'SmallBusinessLicense'
https://www.qt.io/pricing/qt-for-small-business#eligible - this license
fits perfect into my
The decision will eventually alienate OS community which will force current
licensees consider the viabilty of the platform for their next generation of
products. There is a lot of air in the QtC stock price as a result of the new
licensees and how well Qt/Qml fits the needs. I certainly hope th
14 matches
Mail list logo
