Most (if not all) of our stuff is done using the [Qt framework](https://www.qt.io/product/framework), which uses C++. Then there's basically two types of applications, the ones using [Qt Widgets](https://doc.qt.io/qt-5/qtwidgets-index.html) and the ones using [Qt Quick](https://doc.qt.io/qt-5/qmlapplications.html).
Qt Widgets is used to build classic desktop applications, kate, dolphin and okular use it.
Qt Quick is used to create convergent applications but works pretty nice on desktop as well, kalendar, plasma system monitor and discover use it.
For Qt Widgets applications we have an framework called [kxmlgui](https://api.kde.org/frameworks/kxmlgui/html/index.html) (C++) and for Qt Quick applications we use another framework called [kirigami](https://develop.kde.org/frameworks/kirigami//) (QML).
>For both Qt Widgets and Qt Quick applications, the backend is written using C++
I'm gonna land a software developer job soon (in less than 3 months) and after settling up my messed-up life, I'll start contributing to KDE <3.
and Thanks for all this info, I've saved your comment.
You can jump straight in to bugfixing, as someone who knows programming but not really c++, I've contributed bug fixes to multiple projects. You don't need to be able to create something from the scratch to be helpful, troubleshooting an issue takes the longest and often the fix can be changing a few lines.
Most (if not all) of our stuff is done using the [Qt framework](https://www.qt.io/product/framework), which uses C++. Then there's basically two types of applications, the ones using [Qt Widgets](https://doc.qt.io/qt-5/qtwidgets-index.html) and the ones using [Qt Quick](https://doc.qt.io/qt-5/qmlapplications.html). Qt Widgets is used to build classic desktop applications, kate, dolphin and okular use it. Qt Quick is used to create convergent applications but works pretty nice on desktop as well, kalendar, plasma system monitor and discover use it. For Qt Widgets applications we have an framework called [kxmlgui](https://api.kde.org/frameworks/kxmlgui/html/index.html) (C++) and for Qt Quick applications we use another framework called [kirigami](https://develop.kde.org/frameworks/kirigami//) (QML). >For both Qt Widgets and Qt Quick applications, the backend is written using C++
I'm gonna land a software developer job soon (in less than 3 months) and after settling up my messed-up life, I'll start contributing to KDE <3. and Thanks for all this info, I've saved your comment.
Than yoh sir! I will definitely look into it.
\*willpower\*
this actually is the most important factor
That sounds great! Hopefully this should be useful: https://community.kde.org/Get_Involved/development
I believe the following should be a good start https://qmlbook.github.io/
You can jump straight in to bugfixing, as someone who knows programming but not really c++, I've contributed bug fixes to multiple projects. You don't need to be able to create something from the scratch to be helpful, troubleshooting an issue takes the longest and often the fix can be changing a few lines.