3 ms·

The relevant thread on the KDE Community mailing list starts here, it contains a lot of information: https://mail.kde.org/pipermail/kde-community/2020q2/006098.

by p4bl0 6y ago

The relevant thread on the KDE Community mailing list starts here, it contains a lot of information: https://mail.kde.org/pipermail/kde-community/2020q2/006098.html https://mail.kde.org/pipermail/kde-community/2020q2/006098.h... Most notably, it contains a discussion about the feasibility of a fork (and even a name is discussed). What emerges from the discussion is that the OSS community around the Qt project is quite large even outside of KDE (I remember VLC being cited, for example), and that if efforts are united, it would be feasible. The KDE project could provide the necessary infrastructure for development, including CI (which would necessitate some startup work to change framework if I understood correctly) and distribution.

em-bee 6y ago
forking qt for kde can't be that much harder than maintaining gtk for gnome. if the community is large enough, which i believe it is.
- distances 6y ago
  According to one coverage report the project sizes are 7 million lines for Qt vs. 1.2 million for GTK. If true, they are indeed much closer in size than I imagined -- I was sure it's at least one magnitude of difference in size if not even much more. https://scan.coverity.com/projects/qt-project https://scan.coverity.com/projects/qt-project https://scan.coverity.com/projects/gtk https://scan.coverity.com/projects/gtk
- xtracto 6y ago
  Given the story of successful forks (MariaDB, LibreOffice) I think it can be a good option.