For example: https://invent.kde.org/network/neochat/-/blob/master/LICENSE...
2,859 karma · joined October 8, 2017
Previously GnuPG and KDAB. Contact email: carl@carlschwan.eu
For example: https://invent.kde.org/network/neochat/-/blob/master/LICENSE...
There has been three big reasons why we are trying to switch from phab to Gitlab:
* Upstream wasn't very interested in external contributions or hearing our suggestions
* arcanist was a real pita to use for new contributors. Switching to gitlab really increased the number of occasional contributors.
* Setting up CI with Phabricator to run on Diff (the Phabricator equivalent to merge request) was not easy.
> To contribute to the Phabricator upstream, you must first pass a series of ancient trials and be invited to register an account in the ancestral homeland of Phabricator, here on secure.phabricator.com. The nature and location of these trials is a closely guarded secret.
Disclaimer: one of my friend is involved in this project
Location: Germany
Remote: Yes
Willing to relocate: Yes as long as it's in western/northern Europe (I speak French, German and English)
Technologies: Qt/QML, C++, Rust, VueJs, Hugo, django, PHP/Symfony
Résumé/CV: A good overview of my work can be found on my blog: https://carlschwan.eu. My CV is available at https://carlschwan.eu/cv.pdf. Gitlab: https://invent.kde.org/carlschwan
Email: carl at carlschwan dot euNow we split everything, and people complain that they are too many libraries. There is no way to make everyone happy. Note that all this packages are very small and all provides features you really want to have.
Another aspect is the licensing, GTK was licensed under LGPL way before Qt and RMS casting doubts on the legal aspect of KDE even after Qt was re-licensed under GPL didn't help.
All these played a role in the early 00s, nowadays the problems is mostly that GNOME has many more enterprise features and integration with other RedHat products and it is hard to catch on.