2,859 karma · joined October 8, 2017
Previously GnuPG and KDAB. Contact email: carl@carlschwan.eu
[1]: https://invent.kde.org/teams/eco/blue-angel-application/-/bl... [2]: https://invent.kde.org/teams/eco/be4foss
https://produktinfo.blauer-engel.de/uploads/criteriafile/en/...
Disclaimer: I'm one of the core developer of Kalendar
https://apps.kde.org/kalendar/
The first version of Kirigami (the tookit used by plasma mobile) had a very interesting concept around navigation and people hated it. We still have some remnants of this with some floating buttons that are easy to reach for the thumb but also often on top of the content.
I really prefer us to copy a bit the UX of Android/iOS than spending a lot of effort trying to come up with our own UX concept that is not inferior of the one of Android/iOS. We are just an handful of developer and none is paid to work on it.
Disclaimer: I work at Nextcloud so I'm a bit biased
I'm sorry but this feels wrong. The existing sponsors should have their subscriptions cancelled, instead of going to a new organization automatically.
KDE Itinerary and Apple Wallet make use of this. For the KDE Itinerary part, you can read more on this here: https://volkerkrause.eu/ (look at the KDE Itinerary posts)
They’re doing literal torch hikes through southern Germany at their conferences, fighting online against "cultural marxism", and their mail server has the hostname "Wolfsschanze" (see: https://twitter.com/pid_eins/status/1113738766471057408)
Source: https://twitter.com/kuschku/status/1156488420413362177
* valgrind (https://valgrind.org/): Contains a lot of tools
* Heaptrack (https://apps.kde.org/heaptrack/): For memory allocation analysis
* KCachegrind (https://apps.kde.org/kcachegrind/): For call graph vizualisations
* ELF Dissector (https://apps.kde.org/elf-dissector/): For analysis of binary files/dependencies
* Massif-Visualizer (https://apps.kde.org/massif-visualizer/): Valgrind massif visualiser
* Gammaray (https://www.kdab.com/development-resources/qt-tools/gammaray...): Tool to analysis the current state of a Qt project a bit like you would do with firefox inspector.
It's just not sustainable for a small open source community to build an open source browser engine.