On Tuesday, 14 April 2020 06:01:47 CEST Nicolás Alvarez wrote:
> I agree it's possible that "we're thinking about restricting ALL Qt
> releases to paid license holders for the first 12 months" was just to
> force our hand and make us give them other concessions, and that
> they're not actually
El jue., 9 de abr. de 2020 a la(s) 09:01, Florian Bruhin
(m...@the-compiler.org) escribió:
> One possible reading of Olaf's original mail is that TQtC simply was bluffing
> in order to force "negotiations" about some other part of the agreement they
> don't like:
>
> The Qt Company says that
Hopefully this email is put in the chain as intended, if not, my apologies.
On Thu Apr 9 10:01:48 BST 2020 Boudewijn Rempt wrote:
> * There needs to be a mailing list or two
> * There needs to be a system like gerrit or gitlab to host development
> * There needs to be CI -- the Qt project has its
On Fri, Apr 10, 2020 at 4:10 PM Ivan Čukić wrote:
>
> > want use KDE as the "open version of Qt" shop then we should probably
> > first look at the number of fixes to upstream actually made through
> > KDE mirrors directly. I.e. count how many people use KDE repos to
>
> I think I agree with your
Hi Sebastian, thanks everyone for your contribution to discussion on
this important albeit unfortunate topic,
Le 2020-04-09 à 10:06, Sebastian Kügler a écrit :
On donderdag 9 april 2020 15:29:22 CEST Noah Davis wrote:
I've seen a lot of people on Reddit and various chat rooms who are a
fan of
> want use KDE as the "open version of Qt" shop then we should probably
> first look at the number of fixes to upstream actually made through
> KDE mirrors directly. I.e. count how many people use KDE repos to
I think I agree with your sentiment, but:
Not sure what you meant here - patches can
On vrijdag 10 april 2020 15:41:39 CEST Johan Ouwerkerk wrote:
> On Thu, Apr 9, 2020 at 9:04 PM Jens wrote:
> >
> > I can’t make any calls since the work isn’t on my shoulders but if the Qt
> > company are ready to pull this stunt AND then lie about it in the vaguest
> > most awkward way of
On Thu, Apr 9, 2020 at 9:04 PM Jens wrote:
>
> I can’t make any calls since the work isn’t on my shoulders but if the Qt
> company are ready to pull this stunt AND then lie about it in the vaguest
> most awkward way of saying “KDE and Qt Free are lying” they will do this
> again and forking,
It's important to differentiate things we know and
things we don't know, especially in situations that
invite speculation.
What we do know:
- There's a contract. It's a vital document that
has served everyone well for a long time.
- Parties to a contract can change in all sorts of
ways over
I can’t make any calls since the work isn’t on my shoulders but if the Qt
company are ready to pull this stunt AND then lie about it in the vaguest most
awkward way of saying “KDE and Qt Free are lying” they will do this again and
forking, even though Qt Company cowered out now, might be better
> Let's not throw the baby out with the bathwater.
This is very true.
The KFQF with all representatives remains actively
working on the issues with the same mission state-
ment, too.
Cheers,
Eike
-
KDE e.V. Vice President
On donderdag 9 april 2020 15:29:22 CEST Noah Davis wrote:
> I've seen a lot of people on Reddit and various chat rooms who are a
> fan of Kt as a name.
I'd advise against this discussion at this point, it doesn't belong here, it's
a topic that can quickly explode, lead to bike-shedding and
I've seen a lot of people on Reddit and various chat rooms who are a
fan of Kt as a name.
- It fits well in a square, which makes it great for logos.
- It's unusual, but not weird looking.
- It looks kind of like an element on a periodic table.
- In Google and DuckDuckGo searches for "kt", most
On donderdag 9 april 2020 14:12:36 CEST Clemens Toennies wrote:
> On Apr 9, 2020 11:34, "Jens" wrote:
> > > Hosting of the website also wouldn't be an issue (and if it ends up
> > > being high traffic, as long as the content is cacheable we can rely on
> > > Cloudflare). People would need to step
On 09.04.2020 10:57, Boudewijn Rempt wrote:
On donderdag 9 april 2020 10:19:00 CEST Paul Brown wrote:
To further this list, a friend in the VFX industry pointed out that
all these
non-KDE projects use the Free version of Qt (thanks Mike):
* Appleseed: https://appleseedhq.net/ ---
On Apr 9, 2020 11:34, "Jens" wrote:
>
> > Hosting of the website also wouldn't be an issue (and if it ends up
> > being high traffic, as long as the content is cacheable we can rely on
> > Cloudflare). People would need to step up to write the content and
> > produce any necessary graphics though
Hi,
(Apologies for not answering to the original mail in this thread, I only
subscribed after it was sent and can't find a Message-ID in the web archives.)
As the maintainer of a web browser[1] using QtWebEngine, I find this deeply
concerning. A year delay in security updates would be
On donderdag 9 april 2020 11:31:52 CEST Ben Cooksley wrote:
> Gerrit on the other hand is a completely different matter - it doesn't
> even know how to send email properly...
I guess a community fork of Qt can work just as well with gitlab :-)
> CI for Qt sounds like Pandora's box though, and a
Am 08.04.20 um 20:03 schrieb Nate Graham:
> On 4/8/20 9:32 AM, Christoph Cullmann wrote:
>> On 2020-04-08 15:39, Boudewijn Rempt wrote:
>>> On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
> It's heartening that KDAB has already indicated willingness to support
> such a thing should it become
> Hosting of the website also wouldn't be an issue (and if it ends up
> being high traffic, as long as the content is cacheable we can rely on
> Cloudflare). People would need to step up to write the content and
> produce any necessary graphics though :)
>
Graphics?
... you have my bow / I
On Thu, Apr 9, 2020 at 9:02 PM Boudewijn Rempt wrote:
>
> On woensdag 8 april 2020 23:20:34 CEST Jens wrote:
>
> >
> > Is there any vague calculations concerning the work that would be needed
> > being
> > done?
> >
>
> * There needs to be a mailing list or two
> * There needs to be a system
On woensdag 8 april 2020 23:20:34 CEST Jens wrote:
>
> Is there any vague calculations concerning the work that would be needed
> being
> done?
>
* There needs to be a mailing list or two
* There needs to be a system like gerrit or gitlab to host development
* There needs to be CI -- the Qt
On donderdag 9 april 2020 10:19:00 CEST Paul Brown wrote:
> To further this list, a friend in the VFX industry pointed out that all
> these
> non-KDE projects use the Free version of Qt (thanks Mike):
>
> * Appleseed: https://appleseedhq.net/ --- https://github.com/appleseedhq/
> appleseed
On miércoles, 8 de abril de 2020 23:20:34 (CEST) Jens wrote:
> On onsdag 8 april 2020 kl. 20:11:47 CEST Paul Brown wrote:
> > On miércoles, 8 de abril de 2020 20:03:37 (CEST) Nate Graham wrote:
> > > On 4/8/20 9:32 AM, Christoph Cullmann wrote:
> > > > On 2020-04-08 15:39, Boudewijn Rempt wrote:
>
On onsdag 8 april 2020 kl. 20:11:47 CEST Paul Brown wrote:
> On miércoles, 8 de abril de 2020 20:03:37 (CEST) Nate Graham wrote:
> > On 4/8/20 9:32 AM, Christoph Cullmann wrote:
> > > On 2020-04-08 15:39, Boudewijn Rempt wrote:
> > >> On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
> > >>> The
Hi,
just one quick question about this part:
But last week, the company suddenly informed both the KDE e.V. board
and the
KDE Free QT Foundation that the economic outlook caused by the Corona
virus
puts more pressure on them to increase short-term revenue. As a result,
they
are thinking
On Wednesday, 8 April 2020 21:06:12 CEST Eike Hein wrote:
> That is to say to others -- Qt Open Governance has been a
> collaborative and coordinated effort with close
> communication and will continue to be.
KDE e.V. has a statement about it as well,
Hello Till,
I'd like to affirm what others in the community have already
done and thank KDAB for its support and participation in the
open Qt ecosystem and Qt Open Governance, and also KDE e.V.
in particular, over many years and today.
I'm very confident that KDE e.V., KDAB and others will
Even in the best of times, it's always a good idea for stakeholders
in the open Qt ecosystem to maintain open lines of communication.
The KDE e.V. board can be reached at kde-ev-bo...@kde.org and is
happy to receive meeting inquiries.
Best regards,
Eike Hein
-
KDE e.V. Vice President
On miércoles, 8 de abril de 2020 20:03:37 (CEST) Nate Graham wrote:
> On 4/8/20 9:32 AM, Christoph Cullmann wrote:
> > On 2020-04-08 15:39, Boudewijn Rempt wrote:
> >> On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
> >>> The issue is for KDE is that we can't prepare ourselves. We can't
> >>>
On 4/8/20 9:32 AM, Christoph Cullmann wrote:
On 2020-04-08 15:39, Boudewijn Rempt wrote:
On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
The issue is for KDE is that we can't prepare ourselves. We can't
fork Qt,
because we lack the manpower to safely do so currently.
But if we work
On 2020-04-08 15:39, Boudewijn Rempt wrote:
On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
The issue is for KDE is that we can't prepare ourselves. We can't fork
Qt,
because we lack the manpower to safely do so currently.
But if we work together with other participants in the Qt
Hello Olaf, and also Martin,
First of, thank you very much for posting this update to our community. We are
very lucky to benefit from your experience and commitment acting as our
representatives in the KDE Free Qt Foundation.
The KDE e.V. board of directors has been working closely with you
On woensdag 8 april 2020 13:13:41 CEST Jens wrote:
> The issue is for KDE is that we can't prepare ourselves. We can't fork Qt,
> because we lack the manpower to safely do so currently.
But if we work together with other participants in the Qt community, then it
might be feasible. In fact, I
Hi Olaf,
thank you for sharing your perspective and for your important work on
the KDE Free Qt Foundation. Some comments inline below. For the
avoidance of doubt, I am speaking here as a representative of KDAB.
On 08/04/2020 12:53, Olaf Schmidt-Wischhöfer wrote:
> Our goals in negotiations:
> *
Hi Jens,
> The Qt Company says that they are willing to reconsider the approach only if
> we offer them concessions in other areas. I am reminded, however, of the
> situation half a year ago. We had discussed an approach for contract
> updates, which they suddenly threw away by restricting LTS
On onsdag 8 april 2020 kl. 12:53:47 CEST Olaf Schmidt-Wischhöfer wrote:
> But last week, the company suddenly informed both the KDE e.V. board and the
> KDE Free QT Foundation that the economic outlook caused by the Corona virus
> puts more pressure on them to increase short-term revenue. As a
Dear KDE community,
the relationship between the KDE community, the Qt project and The Qt Company
has always been close and beneficial for all three.
* The Qt Company benefits from having a large and healthy community of
contributors, developers and experts around their product.
* KDE benefits
38 matches
Mail list logo
