Qt, Open Source and corona

Paul Brown paul.brown at kde.org
Wed Apr 8 19:11:47 BST 2020


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
> >>> 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 think it's necessary to start
> >> bringing together a group of stakeholders and start preparing for a
> >> fork.
> > 
> > Actually, at least as the last possible option, if any further
> > cooperation breaks down, I agree with this.
> 
> I strongly agree. I think the sooner we demonstrate that we are capable
> of credibly maintaining a fork with other stakeholders in the FOSS Qt
> ecosystem, the stronger of a bargaining chip it will be in our
> negotiations with TQtC, so we don't have to. And in case the
> negotiations break down and we are forced to move forward with the fork,
> our prior preparation will ensure continuity so we won't have to
> scramble at the last minute.
> 
> It's heartening that KDAB has already indicated willingness to support
> such a thing should it become necessary. Are there other Qt-using
> companies who we could reach out to?

* Autodesk: https://www.autodesk.com/company/legal-notices-trademarks/open-source-distribution

* MBition (Daimler/Mercedes company -- Eike may be able to give mor 
information that).
-- 
Promotion & Communication

www: http://kde.org
Mastodon: https://mastodon.technology/@kde
Facebook: https://www.facebook.com/kde/
Twitter: https://twitter.com/kdecommunity
LinkedIn: https://www.linkedin.com/company/kde





More information about the kde-community mailing list